xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Need help with qemu args debug
Date: Fri, 2 Mar 2012 01:00:30 -0800 (PST)	[thread overview]
Message-ID: <1330678830304-5530386.post@n5.nabble.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203011412300.923@kaball-desktop>


Stefano Stabellini-3 wrote
> 
> On Wed, 29 Feb 2012, Fantu wrote:
>> Now I search for other options, found and tried with -global
>> qxl-vga.vram_size=4194304 but same problem...
>> 
>> do_spice_init: starting 0.10.1
>> spice_server_add_interface: SPICE_INTERFACE_MIGRATION
>> spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
>> spice_server_add_interface: SPICE_INTERFACE_MOUSE
>> qemu: hardware error: xen: failed to populate ram at 40000000
> 
> You are going in the right direction but I think QXL might be doing
> other allocations other than the main vga videoram.
> Now that I think about it, another way around the memory allocation
> problem would be to add "maxmem=MEMORY" in your VM config file, where
> MEMORY is equal to the amount of memory you assign to the VM plus the
> videram.
> 
> So if you have:
> 
> memory=1024
> 
> then you could try adding:
> 
> maxmem=1088
> 
With only maxmem add not work but also with videoram and high value start
and give other error.
With videoram=64:
qemu: hardware error: xen: failed to populate ram at 44002000
With videoram=128 start qemu and spice is working but system not.

The actual domU configuration files:
----------------------------------------------------
name='PRECISEHVM'
builder="hvm"
memory=1024
maxmem=1536
vcpus=2
#hap=1
#pae=1
#acpi=1
#apic=1
#nx=1
vif=['bridge=xenbr0']
#vfb=['vnc=1,vncunused=1,vnclisten="0.0.0.0",keymap="it"']
disk=['/mnt/vm/disks/PRECISEHVM.disk1.xm,raw,hda,rw',
'/dev/sr0,raw,hdb,ro,cdrom']
boot='c'
#xen_platform_pci=1
device_model_version='qemu-xen'
vnc=0
#vncunused=1
#vnclisten="0.0.0.0"
#keymap="it"
#stdvga=1
#videoram=16
#sdl=0
spice=1
spicehost='0.0.0.0'
spiceport=6000
spicedisable_ticketing=1
#spicepasswd='test'
device_model_override="/usr/lib/xen/bin/qemu-debug.sh"
#device_model_args=["-global qxl-vga.vram_size=8388308"]
#on_crash='preserve'
videoram=128
----------------------------------------------------

Starting QEMU with: -xen-domid 45 -chardev
socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-45,server,nowait -mon
chardev=libxl-cmd,mode=control -name PRECISEHVM -vga qxl -spice
port=6000,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on -boot
order=c -smp 2,maxcpus=3 -device
rtl8139,id=nic0,netdev=net0,mac=00:16:3e:56:77:cd -netdev
type=tap,id=net0,ifname=tap45.0,script=no -M xenfv -m 1024 -drive
file=/mnt/vm/disks/PRECISEHVM.disk1.xm,if=ide,index=0,media=disk,format=raw
-drive file=/dev/sr0,if=ide,index=1,media=cdrom,format=raw


The xl dmesg PRECISEHVM: 
http://xen.1045712.n5.nabble.com/file/n5530386/xl-dmesg-PRECISEHVM
xl-dmesg-PRECISEHVM 

Connect to domU with spice work but qemu show Boot failed: could not read
the boot disk.

If you need more data require and I will post.

--
View this message in context: http://xen.1045712.n5.nabble.com/Need-help-with-qemu-args-debug-tp5524689p5530386.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

  reply	other threads:[~2012-03-02  9:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 11:09 Need help with qemu args debug Fantu
2012-02-29 11:22 ` Ian Campbell
2012-02-29 12:44   ` Fantu
2012-02-29 13:05     ` Ian Campbell
2012-02-29 16:20       ` Ian Jackson
2012-02-29 17:31       ` Philipp Hahn
2012-02-29 18:45       ` Ian Campbell
2012-02-29 13:05     ` Fantu
2012-02-29 15:06       ` Stefano Stabellini
2012-02-29 15:30         ` Fantu
2012-02-29 15:39           ` Fantu
2012-03-01 14:27             ` Stefano Stabellini
2012-03-02  9:00               ` Fantu [this message]
2012-03-02 13:30                 ` Stefano Stabellini
2012-03-02 14:03                   ` Fantu
2012-03-02 15:36                     ` Stefano Stabellini
2012-03-06 14:18                       ` Fantu
2012-03-07 15:00                         ` Fantu
2012-03-09  0:45                           ` Ian Campbell
2012-03-08 16:59                         ` Anthony PERARD
2012-03-09 10:58                           ` Fantu
2012-03-09 14:55                             ` Anthony PERARD
2012-03-12  9:31                               ` Fantu
2012-03-13  9:14                                 ` Fantu
2012-03-13  9:33                                   ` Ian Campbell
2012-03-13  9:41                                     ` Ian Campbell
2012-03-15  9:36                                       ` Fantu
2012-03-15 17:35                                         ` Anthony PERARD
2012-03-16 10:51                                           ` Fantu
2012-03-01 14:11           ` Stefano Stabellini
2012-03-01  9:18         ` Fantu
2012-03-01  9:31           ` Ian Campbell
2012-03-01  9:43             ` Fantu
2012-03-01 10:58               ` Fantu
2012-03-01 14:40                 ` Stefano Stabellini
2012-02-29 17:25   ` Philipp Hahn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1330678830304-5530386.post@n5.nabble.com \
    --to=fantonifabio@tiscali.it \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).