Thanks for testing. On Fri, 2012-09-07 at 13:44 +0100, Fabio Fantoni wrote:> - IMPORTANT - On restore network is up but not working, tried with W7 > pro 64 bit with gplpv last build (357) on qemu-xen-traditionalOur automated tests aren''t seeing this, might it be a GPLPV issue? Can you reproduce with e.g. PV Linux (or PVHVM Linux for that matter)?> - Cdrom hotswap is not working, tried with W7 pro 64 bit with gplpv last > build (357) on qemu-xen-traditional > xl -vvv cd-eject W7 hdb > libxl: debug: libxl.c:2143:libxl_cdrom_insert: ao 0x1461980: create: > how=(nil) callback=(nil) poller=0x14619e0 > Errore di segmentazioneThis doesn''t happen for me. Please can you run this one under gdb and when it fails type "bt" to get a backtrace.> - Vnc is working but only with parameters not supplied as value to the > vfb key, but with vfb key is not workingWhether or not that works is very much a function of exactly what the rest of your guest config looks like (it depends on PV for HVM for one thing). You''ve reported enough bugs now that I shouldn''t need to remind you about providing guest config files or link to http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen again. Ian.
On Mon, 2012-09-10 at 10:22 +0100, Fabio Fantoni wrote:> Il 07/09/2012 17:15, Ian Campbell ha scritto: > > Thanks for testing. > > > > On Fri, 2012-09-07 at 13:44 +0100, Fabio Fantoni wrote: > >> - IMPORTANT - On restore network is up but not working, tried with W7 > >> pro 64 bit with gplpv last build (357) on qemu-xen-traditional > > Our automated tests aren''t seeing this, might it be a GPLPV issue? Can > > you reproduce with e.g. PV Linux (or PVHVM Linux for that matter)? > > > >> - Cdrom hotswap is not working, tried with W7 pro 64 bit with gplpv last > >> build (357) on qemu-xen-traditional > >> xl -vvv cd-eject W7 hdb > >> libxl: debug: libxl.c:2143:libxl_cdrom_insert: ao 0x1461980: create: > >> how=(nil) callback=(nil) poller=0x14619e0 > >> Errore di segmentazione > > This doesn''t happen for me. Please can you run this one under gdb and > > when it fails type "bt" to get a backtrace. > > > >> - Vnc is working but only with parameters not supplied as value to the > >> vfb key, but with vfb key is not working > > Whether or not that works is very much a function of exactly what the > > rest of your guest config looks like (it depends on PV for HVM for one > > thing). > > > > You''ve reported enough bugs now that I shouldn''t need to remind you > > about providing guest config files or link to > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen again. > > > > Ian. > > > > > > > > > > ----- > > Nessun virus nel messaggio. > > Controllato da AVG - www.avg.com > > Versione: 2012.0.2197 / Database dei virus: 2437/5254 - Data di rilascio: 07/09/2012 > > > > > Thanks for reply, here the xl configuration file: > > ------------------------- > W7.cfg > ------ > name=''W7'' > builder="hvm" > memory=2048 > vcpus=2 > vif=[''bridge=xenbr0''] > #vfb=[''vnc=1,vncunused=1,vnclisten="0.0.0.0",keymap=it'']I don''t think it is expected that this line (even if uncommented) would do anything for Windows unless you have a PV FB frontend driver, which I''m fairly certain doesn''t exist. So I think:> Vnc is working but only with parameters not supplied as value to the > vfb key, but with vfb key is not workingis entirely expected. The vfb line is for use with PV guests which have a PVFB driver. [...]> ------------------------- > > I don''t know exactly how to use gdbsx,You just need regular gdb not gdbsx. Run it as eg.g. gdb --args xl cd-eject <aprams> then when it crashes type "bt".> Can you post me details and versions of your system installation (dom0 > domU GPLPV) with which you have cd-eject and network on restore working, > please?I tested this with Linux HVM. I don''t have any Windows domUs. Does this work without GPLPV drivers? The CDROM device should be emulated even if those are installed anyway. Ian.
On Mon, 2012-09-10 at 14:36 +0100, Fabio Fantoni wrote:> gdb --args xl -vvv cd-eject W7 hdb > GNU gdb (GDB) 7.4.1-debian > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /usr/sbin/xl...done.Oops, sorry I forget to say: Enter "run" at this point to actually run the command.> (gdb) bt > No stack. >
On Mon, 2012-09-10 at 15:26 +0100, Fabio Fantoni wrote:> gdb --args xl -vvv cd-eject W7 hdb > GNU gdb (GDB) 7.4.1-debian > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /usr/sbin/xl...done. > (gdb) run > Starting program: /usr/sbin/xl -vvv cd-eject W7 hdb > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > libxl: debug: libxl.c:2143:libxl_cdrom_insert: ao 0x623980: create: > how=(nil) callback=(nil) poller=0x6239e0 > libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk > vdev=hdb spec.backend=unknown > libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=hdb, > backend phy unsuitable as phys path not a block device > libxl: debug: libxl_device.c:210:disk_try_backend: Disk vdev=hdb, > backend tap unsuitable due to format empty > libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk > vdev=hdb, using backend qdisk > libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0x623980: > complete, rc=0 > libxl: debug: libxl.c:2236:libxl_cdrom_insert: ao 0x623980: inprogress: > poller=0x6239e0, flags=ic > libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0x623980: destroy > xc: debug: hypercall buffer: total allocations:4 total releases:4 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:1 misses:2 toobig:1 > [Inferior 1 (process 5581) exited normally] > (gdb) bt > No stack.That''s because it seems to be working for you now... There is no crash here. Ian.