Need help with qemu args debug

Need help with qemu args debug

[Fantu]

I'm trying to make the necessary patches to complete the Spice support on
libxl.
Qxl graphic add do always error and I not understand why, I need to see all
dm_args for try to search the cause, I try with LIBXL__LOG (on libxl_dm.c
before the line return (char **) flexarray_contents(dm_args);) but always
fails, someone can help me to do log of full dm_args please?

Thanks for any reply and sorry for bad english.

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

Re: Need help with qemu args debug

[Ian Campbell]

On Wed, 2012-02-29 at 11:09 +0000, Fantu wrote:
> I'm trying to make the necessary patches to complete the Spice support on
> libxl.
> Qxl graphic add do always error and I not understand why, I need to see all
> dm_args for try to search the cause, I try with LIBXL__LOG (on libxl_dm.c
> before the line return (char **) flexarray_contents(dm_args);) but always
> fails, someone can help me to do log of full dm_args please?

That should be possible, but you haven't shown your code so I can't say
where you have gone wrong.

What I often do is create qemu-debug.sh:
	#!/bin/sh
	echo "Starting QEMU with: $*" >> /tmp/qemu-dbg.log
	exec /usr/lib/xen/bin/qemu-system-i386 $@

And then using device_model_override to call this instead of calling
qemu directly.

Re: Need help with qemu args debug

[Fantu]

Ian Campbell-10 wrote
> 
> That should be possible, but you haven't shown your code so I can't say
> where you have gone wrong.
> 
> What I often do is create qemu-debug.sh:
> 	#!/bin/sh
> 	echo "Starting QEMU with: $*" >> /tmp/qemu-dbg.log
> 	exec /usr/lib/xen/bin/qemu-system-i386 $@
> 
> And then using device_model_override to call this instead of calling
> qemu directly.
> 

Thanks for reply

Qxl graphic is needed for many things with spice, I start to try add it
following this: http://spice-space.org/docs/spice_user_manual.pdf

On libxl_dm.c add this line:
flexarray_append(dm_args, "-qxl 1");
before this:
flexarray_append(dm_args, "-spice");

With dm override give:
Starting QEMU with: -xen-domid 22 -chardev
socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-22,server,nowait -mon
chardev=libxl-cmd,mode=control -name PRECISEHVM -vnc 127.0.0.1:0,to=99 -qxl
1 -spice port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on
-boot order=c -smp 2,maxcpus=3 -device
rtl8139,id=nic0,netdev=net0,mac=00:16:3e:6b:81:89 -netdev
type=tap,id=net0,ifname=tap22.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

And on /var/log/xen/qemu-dm-PRECISEHVM.log:
qemu-system-i386: -qxl: invalid option

There isn't other -vga or -nographic options, I not undestand the problem,
without qxl work but on spice connect and load see the cirrus video card,
video performance is not good and is impossible resize resolution, qxl
graphic is needed.
I have also try -vga qxl but same problem.

Before i try to add permant dm_args debug on log with:
On libxl_dm.c add this line:
LIBXL__LOG(ctx, LIBXL__LOG_DEBUG, "dm_args: ", flexarray_contents(dm_args)
);
before this:
return (char **) flexarray_contents(dm_args);

Show:
libxl_dm.c: In function âlibxl__build_device_model_args_newâ:
libxl_dm.c:582:2: error: too many arguments for format
[-Werror=format-extra-args]
cc1: all warnings being treated as errors



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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Ian Campbell]

On Wed, 2012-02-29 at 12:44 +0000, Fantu wrote:
> Ian Campbell-10 wrote
> > 
> > That should be possible, but you haven't shown your code so I can't say
> > where you have gone wrong.
> > 
> > What I often do is create qemu-debug.sh:
> > 	#!/bin/sh
> > 	echo "Starting QEMU with: $*" >> /tmp/qemu-dbg.log
> > 	exec /usr/lib/xen/bin/qemu-system-i386 $@
> > 
> > And then using device_model_override to call this instead of calling
> > qemu directly.
> > 
> 
> Thanks for reply
> 
> Qxl graphic is needed for many things with spice, I start to try add it
> following this: http://spice-space.org/docs/spice_user_manual.pdf
> 
> On libxl_dm.c add this line:
> flexarray_append(dm_args, "-qxl 1");

Doesn't this need to be flexarray_append_pair(dm_args, "-qxl", "1") or
else the actual argument will be literally "-qxl 1"?

(probably the bad quoting in the example I gave has lead to the
qemu-debug.sh "correcting" this for you. I think I should have said
either 
	exec /usr/lib/xen/bin/qemu-system-i386 "$@"
or
	exec /usr/lib/xen/bin/qemu-system-i386 "$*"
(I can never remember which is correct)

> before this:
> flexarray_append(dm_args, "-spice");
> 
> With dm override give:
> Starting QEMU with: -xen-domid 22 -chardev
> socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-22,server,nowait -mon
> chardev=libxl-cmd,mode=control -name PRECISEHVM -vnc 127.0.0.1:0,to=99 -qxl
> 1 -spice port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on
> -boot order=c -smp 2,maxcpus=3 -device
> rtl8139,id=nic0,netdev=net0,mac=00:16:3e:6b:81:89 -netdev
> type=tap,id=net0,ifname=tap22.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
> 
> And on /var/log/xen/qemu-dm-PRECISEHVM.log:
> qemu-system-i386: -qxl: invalid option
> 
> There isn't other -vga or -nographic options, I not undestand the problem,
> without qxl work but on spice connect and load see the cirrus video card,
> video performance is not good and is impossible resize resolution, qxl
> graphic is needed.
> I have also try -vga qxl but same problem.

You have tried two different syntaxes here, which one is the correct
qemu command line syntax?

I think you need to consult the qemu documentation to determine what the
correct command line syntax is supposed to be. 

Perhaps it would be useful to get this working with a normal qemu (e.g.
emulated guest) process before trying to make it work with Xen?

> Before i try to add permant dm_args debug on log with:
> On libxl_dm.c add this line:
> LIBXL__LOG(ctx, LIBXL__LOG_DEBUG, "dm_args: ", flexarray_contents(dm_args)
> );

flexarray_contents returns a "char **" -- you would need to loop over
that array printing each element in turn until you find NULL.

> before this:
> return (char **) flexarray_contents(dm_args);
> 
> Show:
> libxl_dm.c: In function âlibxl__build_device_model_args_newâ:
> libxl_dm.c:582:2: error: too many arguments for format
> [-Werror=format-extra-args]
> cc1: all warnings being treated as errors
> 
> 
> 
> --
> View this message in context: http://xen.1045712.n5.nabble.com/Need-help-with-qemu-args-debug-tp5524689p5524861.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Fantu]

Fantu wrote
> 
> 
> Ian Campbell-10 wrote
>> 
>> That should be possible, but you haven't shown your code so I can't say
>> where you have gone wrong.
>> 
>> What I often do is create qemu-debug.sh:
>> 	#!/bin/sh
>> 	echo "Starting QEMU with: $*" >> /tmp/qemu-dbg.log
>> 	exec /usr/lib/xen/bin/qemu-system-i386 $@
>> 
>> And then using device_model_override to call this instead of calling
>> qemu directly.
>> 
> 
> Thanks for reply
> 
> Qxl graphic is needed for many things with spice, I start to try add it
> following this: http://spice-space.org/docs/spice_user_manual.pdf
> 
> On libxl_dm.c add this line:
> flexarray_append(dm_args, "-qxl 1");
> before this:
> flexarray_append(dm_args, "-spice");
> 
> With dm override give:
> Starting QEMU with: -xen-domid 22 -chardev
> socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-22,server,nowait -mon
> chardev=libxl-cmd,mode=control -name PRECISEHVM -vnc 127.0.0.1:0,to=99
> -qxl 1 -spice
> port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on -boot
> order=c -smp 2,maxcpus=3 -device
> rtl8139,id=nic0,netdev=net0,mac=00:16:3e:6b:81:89 -netdev
> type=tap,id=net0,ifname=tap22.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
> 
> And on /var/log/xen/qemu-dm-PRECISEHVM.log:
> qemu-system-i386: -qxl: invalid option
> 
> There isn't other -vga or -nographic options, I not undestand the problem,
> without qxl work but on spice connect and load see the cirrus video card,
> video performance is not good and is impossible resize resolution, qxl
> graphic is needed.
> I have also try -vga qxl but same problem.
> 
> Before i try to add permant dm_args debug on log with:
> On libxl_dm.c add this line:
> LIBXL__LOG(ctx, LIBXL__LOG_DEBUG, "dm_args: ", flexarray_contents(dm_args)
> );
> before this:
> return (char **) flexarray_contents(dm_args);
> 
> Show:
> libxl_dm.c: In function âlibxl__build_device_model_args_newâ:
> libxl_dm.c:582:2: error: too many arguments for format
> [-Werror=format-extra-args]
> cc1: all warnings being treated as errors
> 

See only now how -vga qxl try to start but give other error...

Starting QEMU with: -xen-domid 25 -chardev
socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-25,server,nowait -mon
chardev=libxl-cmd,mode=control -name PRECISEHVM -vga qxl -spice
port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on -boot order=c
-smp 2,maxcpus=3 -device rtl8139,id=nic0,netdev=net0,mac=00:16:3e:38:be:1d
-netdev type=tap,id=net0,ifname=tap25.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

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

The full log: 
http://xen.1045712.n5.nabble.com/file/n5524897/qemu-dm-PRECISEHVM.log
qemu-dm-PRECISEHVM.log 

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 3485 bytes --]

On Wed, 29 Feb 2012, Fantu wrote:
> Fantu wrote
> > 
> > 
> > Ian Campbell-10 wrote
> >> 
> >> That should be possible, but you haven't shown your code so I can't say
> >> where you have gone wrong.
> >> 
> >> What I often do is create qemu-debug.sh:
> >> 	#!/bin/sh
> >> 	echo "Starting QEMU with: $*" >> /tmp/qemu-dbg.log
> >> 	exec /usr/lib/xen/bin/qemu-system-i386 $@
> >> 
> >> And then using device_model_override to call this instead of calling
> >> qemu directly.
> >> 
> > 
> > Thanks for reply
> > 
> > Qxl graphic is needed for many things with spice, I start to try add it
> > following this: http://spice-space.org/docs/spice_user_manual.pdf
> > 
> > On libxl_dm.c add this line:
> > flexarray_append(dm_args, "-qxl 1");
> > before this:
> > flexarray_append(dm_args, "-spice");
> > 
> > With dm override give:
> > Starting QEMU with: -xen-domid 22 -chardev
> > socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-22,server,nowait -mon
> > chardev=libxl-cmd,mode=control -name PRECISEHVM -vnc 127.0.0.1:0,to=99
> > -qxl 1 -spice
> > port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on -boot
> > order=c -smp 2,maxcpus=3 -device
> > rtl8139,id=nic0,netdev=net0,mac=00:16:3e:6b:81:89 -netdev
> > type=tap,id=net0,ifname=tap22.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
> > 
> > And on /var/log/xen/qemu-dm-PRECISEHVM.log:
> > qemu-system-i386: -qxl: invalid option
> > 
> > There isn't other -vga or -nographic options, I not undestand the problem,
> > without qxl work but on spice connect and load see the cirrus video card,
> > video performance is not good and is impossible resize resolution, qxl
> > graphic is needed.
> > I have also try -vga qxl but same problem.
> > 
> > Before i try to add permant dm_args debug on log with:
> > On libxl_dm.c add this line:
> > LIBXL__LOG(ctx, LIBXL__LOG_DEBUG, "dm_args: ", flexarray_contents(dm_args)
> > );
> > before this:
> > return (char **) flexarray_contents(dm_args);
> > 
> > Show:
> > libxl_dm.c: In function âlibxl__build_device_model_args_newâ:
> > libxl_dm.c:582:2: error: too many arguments for format
> > [-Werror=format-extra-args]
> > cc1: all warnings being treated as errors
> > 
> 
> See only now how -vga qxl try to start but give other error...
> 
> Starting QEMU with: -xen-domid 25 -chardev
> socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-25,server,nowait -mon
> chardev=libxl-cmd,mode=control -name PRECISEHVM -vga qxl -spice
> port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on -boot order=c
> -smp 2,maxcpus=3 -device rtl8139,id=nic0,netdev=net0,mac=00:16:3e:38:be:1d
> -netdev type=tap,id=net0,ifname=tap25.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
> 
> 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
> 
> The full log: 
> http://xen.1045712.n5.nabble.com/file/n5524897/qemu-dm-PRECISEHVM.log
> qemu-dm-PRECISEHVM.log 

Try adding videoram=32 to the VM config file, I think the issue is that
the default videoram size for QXL is much larger (32MB) than the default
videoram size for Cirrus (8MB).

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Fantu]

Stefano Stabellini-3 wrote
> 
> Try adding videoram=32 to the VM config file, I think the issue is that
> the default videoram size for QXL is much larger (32MB) than the default
> videoram size for Cirrus (8MB).
> 

Already thought and tried, -videoram invalid option, is also missed in
--help of qemu-system-i386

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

Re: Need help with qemu args debug

[Fantu]

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

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

Re: Need help with qemu args debug

[Ian Jackson]

Ian Campbell writes ("Re: [Xen-devel] Need help with qemu args debug"):
> (probably the bad quoting in the example I gave has lead to the
> qemu-debug.sh "correcting" this for you. I think I should have said
> either 
> 	exec /usr/lib/xen/bin/qemu-system-i386 "$@"
> or
> 	exec /usr/lib/xen/bin/qemu-system-i386 "$*"
> (I can never remember which is correct)

"$@"

You should not normally use $* at all.

Ian.

Re: Need help with qemu args debug

[Philipp Hahn]

[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]

Hi,

just a nit:

On Wednesday 29 February 2012 12:22:35 Ian Campbell wrote:
> What I often do is create qemu-debug.sh:
> 	#!/bin/sh
> 	echo "Starting QEMU with: $*" >> /tmp/qemu-dbg.log
> 	exec /usr/lib/xen/bin/qemu-system-i386 $@

You should always put double-quotes arount the $@, otherwise the shell does 
IFS-splitting on the arguments. Probably not that important in this case, but 
since this creates nasty quoting problems in general, post "good code" for 
the archive.

Sincerely
Philipp

PS: I know there are broken shell, which don't handle "$@" correct, but hey, 
they're broken anyway.
-- 
Philipp Hahn           Open Source Software Engineer      hahn@univention.de
Univention GmbH        Linux for Your Business        fon: +49 421 22 232- 0
Mary-Somerville-Str.1  D-28359 Bremen                 fax: +49 421 22 232-99
                                                   http://www.univention.de/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Philipp Hahn]

[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]

Hello Ian,

On Wednesday 29 February 2012 14:05:38 Ian Campbell wrote:
> either
> 	exec /usr/lib/xen/bin/qemu-system-i386 "$@"
> or
> 	exec /usr/lib/xen/bin/qemu-system-i386 "$*"
> (I can never remember which is correct)

"$@" → each argument quoted by itself
"$*" → all arguments concatenated by the first char of $IFS, as one argument
$* → all arguments splited by $IFS → "lots of little garbage"
$@ → same as $*

Sincerely
Philipp
-- 
Philipp Hahn           Open Source Software Engineer      hahn@univention.de
Univention GmbH        Linux for Your Business        fon: +49 421 22 232- 0
Mary-Somerville-Str.1  D-28359 Bremen                 fax: +49 421 22 232-99
                                                   http://www.univention.de/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Ian Campbell]

On Wed, 2012-02-29 at 13:05 +0000, Ian Campbell wrote:
> 
> (probably the bad quoting in the example I gave has lead to the
> qemu-debug.sh "correcting" this for you. I think I should have said
> either 
>         exec /usr/lib/xen/bin/qemu-system-i386 "$@"
> or
>         exec /usr/lib/xen/bin/qemu-system-i386 "$*"
> (I can never remember which is correct) 

Thanks to everyone for correcting me ;-)

Ian.

Re: Need help with qemu args debug

[Fantu]

Stefano Stabellini-3 wrote
> 
> Try adding videoram=32 to the VM config file, I think the issue is that
> the default videoram size for QXL is much larger (32MB) than the default
> videoram size for Cirrus (8MB).
> 

Minimum setting of the ram was 16 mb, I applied this patch for decrese
minimum to 4 mb:
http://git.qemu.org/?p=qemu.git;a=commit;h=80105bbfb2aa3023e959b6ea682a3fc9515080a3
And retry with -global qxl-vga.vram_size=4194304 (4 MB) but give same error
/var/log/xen/qemu-dm-PRECISEHVM.log
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

Tried to change minimum patch and setting to 3 MB but always same result,
probably samething to change about xen for support qxl graphic and
assignment of its ram?
I do not know how to fix or what else to try now :(

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

Re: Need help with qemu args debug

[Ian Campbell]

On Thu, 2012-03-01 at 09:18 +0000, Fantu wrote:
> Stefano Stabellini-3 wrote
> > 
> > Try adding videoram=32 to the VM config file, I think the issue is that
> > the default videoram size for QXL is much larger (32MB) than the default
> > videoram size for Cirrus (8MB).
> > 
> 
> Minimum setting of the ram was 16 mb, I applied this patch for decrese
> minimum to 4 mb:
> http://git.qemu.org/?p=qemu.git;a=commit;h=80105bbfb2aa3023e959b6ea682a3fc9515080a3
> And retry with -global qxl-vga.vram_size=4194304 (4 MB) but give same error
> /var/log/xen/qemu-dm-PRECISEHVM.log
> 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

I think you'll need to dig into the qemu code and find out where/why
this message is coming from.

> 
> Tried to change minimum patch and setting to 3 MB but always same result,
> probably samething to change about xen for support qxl graphic and
> assignment of its ram?
> I do not know how to fix or what else to try now :(
> 
> --
> View this message in context: http://xen.1045712.n5.nabble.com/Need-help-with-qemu-args-debug-tp5524689p5527357.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Fantu]

Ian Campbell-10 wrote
> 
> On Thu, 2012-03-01 at 09:18 +0000, Fantu wrote:
>> Stefano Stabellini-3 wrote
>> > 
>> > Try adding videoram=32 to the VM config file, I think the issue is that
>> > the default videoram size for QXL is much larger (32MB) than the
>> default
>> > videoram size for Cirrus (8MB).
>> > 
>> 
>> Minimum setting of the ram was 16 mb, I applied this patch for decrese
>> minimum to 4 mb:
>> http://git.qemu.org/?p=qemu.git;a=commit;h=80105bbfb2aa3023e959b6ea682a3fc9515080a3
>> And retry with -global qxl-vga.vram_size=4194304 (4 MB) but give same
>> error
>> /var/log/xen/qemu-dm-PRECISEHVM.log
>> 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
> 
> I think you'll need to dig into the qemu code and find out where/why
> this message is coming from.
> 
>> 
>> Tried to change minimum patch and setting to 3 MB but always same result,
>> probably samething to change about xen for support qxl graphic and
>> assignment of its ram?
>> I do not know how to fix or what else to try now :(
> 

I do other search about xen limit of video ram and found old patch about
limit of qemu video ram size, is probably something about...
http://xen.1045712.n5.nabble.com/PATCH-ioemu-drop-unused-4MB-video-memory-td2487287.html
I do search on new tree but not found for now on where is xen limit of video
ram allocation, someone can help me please?

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

Re: Need help with qemu args debug

[Fantu]

Fantu wrote
> 
> 
> Ian Campbell-10 wrote
>> 
>> On Thu, 2012-03-01 at 09:18 +0000, Fantu wrote:
>>> Stefano Stabellini-3 wrote
>>> > 
>>> > Try adding videoram=32 to the VM config file, I think the issue is
>>> that
>>> > the default videoram size for QXL is much larger (32MB) than the
>>> default
>>> > videoram size for Cirrus (8MB).
>>> > 
>>> 
>>> Minimum setting of the ram was 16 mb, I applied this patch for decrese
>>> minimum to 4 mb:
>>> http://git.qemu.org/?p=qemu.git;a=commit;h=80105bbfb2aa3023e959b6ea682a3fc9515080a3
>>> And retry with -global qxl-vga.vram_size=4194304 (4 MB) but give same
>>> error
>>> /var/log/xen/qemu-dm-PRECISEHVM.log
>>> 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
>> 
>> I think you'll need to dig into the qemu code and find out where/why
>> this message is coming from.
>> 
>>> 
>>> Tried to change minimum patch and setting to 3 MB but always same
>>> result,
>>> probably samething to change about xen for support qxl graphic and
>>> assignment of its ram?
>>> I do not know how to fix or what else to try now :(
>> 
> 
> I do other search about xen limit of video ram and found old patch about
> limit of qemu video ram size, is probably something about...
> http://xen.1045712.n5.nabble.com/PATCH-ioemu-drop-unused-4MB-video-memory-td2487287.html
> I do search on new tree but not found for now on where is xen limit of
> video ram allocation, someone can help me please?
> 
Found videoram setting on xl with grep of video_memkb but not about bios
and/or xen videoram limit on source code.
Is absolutely necessary be able to have the possibility of more video ram
for start to have good multimedia domU (at least for work) with xen and
without gfx-passtrought, spice and qxl seem to be seem to be a good
opportunity.

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

Re: Need help with qemu args debug

[Stefano Stabellini]

On Wed, 29 Feb 2012, Fantu wrote:
> 
> Stefano Stabellini-3 wrote
> > 
> > Try adding videoram=32 to the VM config file, I think the issue is that
> > the default videoram size for QXL is much larger (32MB) than the default
> > videoram size for Cirrus (8MB).
> > 
> 
> Already thought and tried, -videoram invalid option, is also missed in
> --help of qemu-system-i386

You don't want any -videoram option to be passed to QEMU, you need
videoram=32 to be in the VM config file only so that XL/libxl can
account for it at domain creation.
If you specify device_model=qemu-xen xl/libxl should be smart enough to
avoid passing a -videoram argument, because the new QEMU cannot parse
it.

Re: Need help with qemu args debug

[Stefano Stabellini]

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

Re: Need help with qemu args debug

[Stefano Stabellini]

On Thu, 1 Mar 2012, Fantu wrote:
> Found videoram setting on xl with grep of video_memkb but not about bios
> and/or xen videoram limit on source code.
> Is absolutely necessary be able to have the possibility of more video ram
> for start to have good multimedia domU (at least for work) with xen and
> without gfx-passtrought, spice and qxl seem to be seem to be a good
> opportunity.

Give a try at the "maxmem" method and let me know.
If the same error persist, apply the appended patch to QEMU and post the
logs.

diff --git a/xen-all.c b/xen-all.c
index 10d53d1..1727044 100644
--- a/xen-all.c
+++ b/xen-all.c
@@ -190,6 +190,8 @@ void xen_ram_alloc(ram_addr_t ram_addr, ram_addr_t size, MemoryRegion *mr)
     xen_pfn_t *pfn_list;
     int i;
 
+    printf("DEBUG %s %d ram_addr="RAM_ADDR_FMT" size="RAM_ADDR_FMT" ram_region=%d\n",
+            __func__,__LINE__,ram_addr,size,(mr == &ram_memory));
     if (runstate_check(RUN_STATE_INMIGRATE)) {
         /* RAM already populated in Xen */
         fprintf(stderr, "%s: do not alloc "RAM_ADDR_FMT

Re: Need help with qemu args debug

[Fantu]

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.

Re: Need help with qemu args debug

[Stefano Stabellini]

On Fri, 2 Mar 2012, Fantu wrote:
> 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.

I think this might be just a disk configuration issue.
If you want to boot from the cdrom you need:

boot='dc' in the vm config file and as command line option to qemu
instead of just 'c'.

If that doesn't work, please post QEMU's logs and the output of
xenstore-ls once the VM is started.

Re: Need help with qemu args debug

[Fantu]

Stefano Stabellini-3 wrote
> 
> On Fri, 2 Mar 2012, Fantu wrote:
>> 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.
> 
> I think this might be just a disk configuration issue.
> If you want to boot from the cdrom you need:
> 
> boot='dc' in the vm config file and as command line option to qemu
> instead of just 'c'.
> 
> If that doesn't work, please post QEMU's logs and the output of
> xenstore-ls once the VM is started.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 

Tried with boot='dc', same result.
Qemu log: 
http://xen.1045712.n5.nabble.com/file/n5531045/qemu-dm-PRECISEHVM.log
qemu-dm-PRECISEHVM.log 
Xenstore-ls:  http://xen.1045712.n5.nabble.com/file/n5531045/xenstore-ls
xenstore-ls 

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

Re: Need help with qemu args debug

[Stefano Stabellini]

On Fri, 2 Mar 2012, Fantu wrote:
> Stefano Stabellini-3 wrote
> > 
> > On Fri, 2 Mar 2012, Fantu wrote:
> >> 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.
> > 
> > I think this might be just a disk configuration issue.
> > If you want to boot from the cdrom you need:
> > 
> > boot='dc' in the vm config file and as command line option to qemu
> > instead of just 'c'.
> > 
> > If that doesn't work, please post QEMU's logs and the output of
> > xenstore-ls once the VM is started.
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@.xen
> > http://lists.xen.org/xen-devel
> > 
> 
> Tried with boot='dc', same result.

I hope you remembered to update QEMU's argument as well with -boot order=dc


> Qemu log: 
> http://xen.1045712.n5.nabble.com/file/n5531045/qemu-dm-PRECISEHVM.log
> qemu-dm-PRECISEHVM.log 
> Xenstore-ls:  http://xen.1045712.n5.nabble.com/file/n5531045/xenstore-ls
> xenstore-ls 

There is nothing on the logs but SPICE, unfortunately.
You might have to add few printf to QEMU to see how far it is able to
go. For example block.c:bdrv_open.

Re: Need help with qemu args debug

[Fantu]

Stefano Stabellini-3 wrote
> 
> There is nothing on the logs but SPICE, unfortunately.
> You might have to add few printf to QEMU to see how far it is able to
> go. For example block.c:bdrv_open.
> 

Problem found, device not found is caused by maxmem parameter,domU S.O.
starts without maxmem, probably there are same unexpected cases on xen
and/or seabios with ram and videoram allocation.
I tried searching but could not find the solution to make allocation of ram
and videoram works with more than standard values.

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

Re: Need help with qemu args debug

[Fantu]

Fantu wrote
> 
> Problem found, device not found is caused by maxmem parameter,domU S.O.
> starts without maxmem, probably there are same unexpected cases on xen
> and/or seabios with ram and videoram allocation.
> I tried searching but could not find the solution to make allocation of
> ram and videoram works with more than standard values.
> 
I did more research and testing, but no solution found.
Anyone else out there can help me solving this problem please?
Thanks for any reply.

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

Re: Need help with qemu args debug

[Anthony PERARD]

On 06/03/12 14:18, Fantu wrote:
> Stefano Stabellini-3 wrote
>>
>> There is nothing on the logs but SPICE, unfortunately.
>> You might have to add few printf to QEMU to see how far it is able to
>> go. For example block.c:bdrv_open.
>>
>
> Problem found, device not found is caused by maxmem parameter,domU S.O.
> starts without maxmem, probably there are same unexpected cases on xen
> and/or seabios with ram and videoram allocation.
> I tried searching but could not find the solution to make allocation of ram
> and videoram works with more than standard values.

I tried to reproduce this, but I did not have any issue (with an iso). 
Also I could not understand why maxmem will have an issue with a drive. 
Also, spice+qemu on debian does not work well, so I'm not sure if I will 
have the same issue. When you found the issue related to the "device not 
found", do you have run the VM without qxl and spice ?

I've just send a patch that fix a memory mapping issue (at least for 
me), could you try with it? :
http://lists.xen.org/archives/html/xen-devel/2012-03/msg00627.html

Then, do you have the same issue if you use an .iso instead of /dev/sr0 
as a cdrom ?

-- 
Anthony PERARD

Re: Need help with qemu args debug

[Ian Campbell]

On Wed, 2012-03-07 at 10:00 -0500, Fantu wrote:
> Fantu wrote
> > 
> > Problem found, device not found is caused by maxmem parameter,domU S.O.
> > starts without maxmem, probably there are same unexpected cases on xen
> > and/or seabios with ram and videoram allocation.
> > I tried searching but could not find the solution to make allocation of
> > ram and videoram works with more than standard values.
> > 
> I did more research and testing, but no solution found.
> Anyone else out there can help me solving this problem please?

I think given that the person who originally submitted the spice support
to xl/libxl is no longer around (or at least is not replying) that there
is no one else who knows about this stuff. I'm sorry to say that if you
are interested in spice functionality you will need to dig into it
yourself.

Ian.

> Thanks for any reply.
> 
> --
> View this message in context: http://xen.1045712.n5.nabble.com/Need-help-with-qemu-args-debug-tp5524689p5544354.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Fantu]

Anthony PERARD-3 wrote
> 
> I tried to reproduce this, but I did not have any issue (with an iso). 
> Also I could not understand why maxmem will have an issue with a drive. 
> Also, spice+qemu on debian does not work well, so I'm not sure if I will 
> have the same issue. When you found the issue related to the "device not 
> found", do you have run the VM without qxl and spice ?
> 
> I've just send a patch that fix a memory mapping issue (at least for 
> me), could you try with it? :
> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00627.html
> 
> Then, do you have the same issue if you use an .iso instead of /dev/sr0 
> as a cdrom ?
> 

Thanks for reply, the problem is present also without spice, qxl and cdrom.
Tried to apply patch, doesn't work, probably because it is based on qemu
unstable (xen-unstable use stable-1.0 branch).
I have applied manually modified lines but to no avail, same problem.

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

Re: Need help with qemu args debug

[Anthony PERARD]

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

On 09/03/12 10:58, Fantu wrote:
>
> Anthony PERARD-3 wrote
>>
>> I tried to reproduce this, but I did not have any issue (with an iso).
>> Also I could not understand why maxmem will have an issue with a drive.
>> Also, spice+qemu on debian does not work well, so I'm not sure if I will
>> have the same issue. When you found the issue related to the "device not
>> found", do you have run the VM without qxl and spice ?
>>
>> I've just send a patch that fix a memory mapping issue (at least for
>> me), could you try with it? :
>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00627.html
>>
>> Then, do you have the same issue if you use an .iso instead of /dev/sr0
>> as a cdrom ?
>>
>
> Thanks for reply, the problem is present also without spice, qxl and cdrom.
> Tried to apply patch, doesn't work, probably because it is based on qemu
> unstable (xen-unstable use stable-1.0 branch).
> I have applied manually modified lines but to no avail, same problem.

I think there is a better solution for your spice issue. Just specify
videoram=32
in your config file, and remove your maxmem options.
Also apply the patch attached to this mail, that should fix the issue.

Regards,

-- 
Anthony PERARD

[-- Attachment #2: libxl_patch.patch --]
[-- Type: text/x-patch, Size: 628 bytes --]

diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
index 922b20b..2fe000e 100644
--- a/tools/libxl/libxl_dm.c
+++ b/tools/libxl/libxl_dm.c
@@ -518,7 +518,7 @@ static char ** libxl__build_device_model_args_new(libxl__gc *gc,
     flexarray_append(dm_args, "-m");
     flexarray_append(dm_args,
                      libxl__sprintf(gc, "%d",
-                                    libxl__sizekb_to_mb(b_info->target_memkb)));
+                                    libxl__sizekb_to_mb(b_info->max_memkb - b_info->video_memkb)));
 
     if (b_info->type == LIBXL_DOMAIN_TYPE_HVM) {
         for (i = 0; i < num_disks; i++) {

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Need help with qemu args debug

[Fantu]

Thanks, applied also that patch, with videoram=32 or 64 not start, also with
qxl-vga.vram_size for decrease vram, with videoram=128 start and Precise see
the qxl video card but xorg have segfault.
The are probably other problem, probably on seabios, I see here some patch:
http://www.mail-archive.com/seabios@seabios.org/msg01849.html
But I not understand how to apply them and try them because seabios-dir in
xen source dir is too different from upstream (not updated).

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

Re: Need help with qemu args debug

[Fantu]

Is possible build qemu and seabios upstream master instead of xen merged
stable or there are xen patches not in qemu upstream or other problem?
I want test if the new patches of seabios and qemu fix the qxl problem.
Thanks for any reply and sorry for bad english.

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

Re: Need help with qemu args debug

[Ian Campbell]

On Tue, 2012-03-13 at 09:14 +0000, Fantu wrote:
> Is possible build qemu and seabios upstream master instead of xen merged
> stable or there are xen patches not in qemu upstream or other problem?
> I want test if the new patches of seabios and qemu fix the qxl problem.

I've not tried it but you can override the settings from Config.mk by
adding a .config file. You need to override the variables:
        QEMU_UPSTREAM_URL
        SEABIOS_UPSTREAM_URL
        QEMU_UPSTREAM_REVISION
        SEABIOS_UPSTREAM_TAG
of course this means you will be trying a combination which we have not
yet validated. You will probably want to call the relevant force update
targets to make this take effect.

Another option is to just put the repos in the right places (e.g.
tools/qemu-xen-dir-remote/ and tools/firmware/seabios-dir-remote/)
checked out with the revisions you need. The Xen build system will not
override this.

I'd be surprised if you needed a newer SeaBIOS, to keep things simple
you might just want to try updating qemu first.

You might also find http://wiki.xen.org/xenwiki/QEMUUpstream useful.

Ian.

Re: Need help with qemu args debug

[Ian Campbell]

On Tue, 2012-03-13 at 09:33 +0000, Ian Campbell wrote:
> You might also find http://wiki.xen.org/xenwiki/QEMUUpstream useful.

Oops, this is the old wiki. The page hadn't been moved over so I've done
that now: http://wiki.xen.org/wiki/QEMU_Upstream

Stefano/Anthony: the page reference a bunch of git URLs like
"git://xenbits.xen.org/people/sstabellini/qemu-dm.git xen-stable-0.15"
and "git://xenbits.xen.org/people/aperard/qemu-dm.git" as being the
upstream trees to work against -- I guess these need to be updated to
some sort of actual upstream URL now? Can one of you quickly check and
update?

I'm going to update the SeaBIOS section.

Ian.

Re: Need help with qemu args debug

[Fantu]

Tried with qemu upstream updated but on s.o. start qemu hang and nothing on
log, hang also without qxl, without usbredirection and without spice.
Also tried update seabios upstream but same problem.
Probably regression in qemu upstream? Qemu tag used for test
cb72b75824c0362e5cb32eb8796930f29fa36d17
Tomorrow if I have enough time I'll just make another test with all updated
(Wheezy, xen ecc) on clean install, before with qemu and seabios of xen and
after upstream.
Or is there anything I should try?

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

Re: Need help with qemu args debug

[Anthony PERARD]

On Thu, Mar 15, 2012 at 09:36, Fantu <fantonifabio@tiscali.it> wrote:
> Tried with qemu upstream updated but on s.o. start qemu hang and nothing on
> log, hang also without qxl, without usbredirection and without spice.
> Also tried update seabios upstream but same problem.
> Probably regression in qemu upstream? Qemu tag used for test
> cb72b75824c0362e5cb32eb8796930f29fa36d17

I just try this commit as well as the latest qemu upstream, and it's broken...
QEMU tries to allocate 4 GB and failes :-(.

But you can use the tag cbedde09698d3506da429ae305dcea7f7deee554 as
this one works for me.

> Tomorrow if I have enough time I'll just make another test with all updated
> (Wheezy, xen ecc) on clean install, before with qemu and seabios of xen and
> after upstream.
> Or is there anything I should try?


-- 
Anthony PERARD

Re: Need help with qemu args debug

[Fantu]

Anthony PERARD-2 wrote
> 
> On Thu, Mar 15, 2012 at 09:36, Fantu <fantonifabio@> wrote:
>> Tried with qemu upstream updated but on s.o. start qemu hang and nothing
>> on
>> log, hang also without qxl, without usbredirection and without spice.
>> Also tried update seabios upstream but same problem.
>> Probably regression in qemu upstream? Qemu tag used for test
>> cb72b75824c0362e5cb32eb8796930f29fa36d17
> 
> I just try this commit as well as the latest qemu upstream, and it's
> broken...
> QEMU tries to allocate 4 GB and failes :-(.
> 
> But you can use the tag cbedde09698d3506da429ae305dcea7f7deee554 as
> this one works for me.
> 
>> Tomorrow if I have enough time I'll just make another test with all
>> updated
>> (Wheezy, xen ecc) on clean install, before with qemu and seabios of xen
>> and
>> after upstream.
>> Or is there anything I should try?
> 
> 
> -- 
> Anthony PERARD
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 
I had tried with qemu upstream commit
cbedde09698d3506da429ae305dcea7f7deee554.
Starting qemu with spice and qxl doesn't hang now but I have this xorg
error:
Out of video memory: Could not allocate 4198400 bytes
Fixed limit of 4 MB videoram for cirrus probably, need update also seabios
or there are other limit of videoram to change?

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