virt-manager crashes on windows xp guest resizing screen (startup -> welcome)

[Srećko Jurić-Kavelj]

Binary package hint: virt-manager

When I use virt-manager to start Windows XP guest it crashes at the time guest changes resolution from 640x480 Windows XP starting screen to full resolution of welcome screen. I get the following entry in dmesg:

/usr/share/virt[10517]: segfault at 7f3abed71790 ip 00007f39d23d2871 sp 00007f39c10719e0 error 4 in fglrx_dri.so[7f39d1e01000+f8f000]

Gdb backtrace produces:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f14981056e0 (LWP 10535)]
0x00007f148248f871 in ?? () from /usr/lib/dri/fglrx_dri.so
(gdb) bt
#0 0x00007f148248f871 in ?? () from /usr/lib/dri/fglrx_dri.so
#1 0x00007f148242a7bc in ?? () from /usr/lib/dri/fglrx_dri.so
#2 0x00007f148201f60b in ?? () from /usr/lib/dri/fglrx_dri.so
#3 0x00007f14821dba9d in ?? () from /usr/lib/dri/fglrx_dri.so
#4 0x00007f148709f1e4 in ?? () from /usr/lib/libgtk-vnc-1.0.so.0
#5 0x00007f1487095c82 in ?? () from /usr/lib/libgtk-vnc-1.0.so.0
#6 0x00007f148709ce46 in gvnc_server_message ()
   from /usr/lib/libgtk-vnc-1.0.so.0
#7 0x00007f14870a01ec in ?? () from /usr/lib/libgtk-vnc-1.0.so.0
#8 0x00007f14870a34ab in ?? () from /usr/lib/libgtk-vnc-1.0.so.0
#9 0x00007f149732cb40 in ?? () from /lib/libc.so.6
#10 0x000000000245a918 in ?? ()
#11 0x0000000000000000 in ?? ()

If I use virsh to start the guest I can use virt-viewer to connect to welcome screen, but then the guest crashes after few minutes (even if I don't connect to guest's vnc at all). There are no relevant messages in dmesg or daemon.log.
In case I don't connect to guest's vnc server after few minutes libvirtd crashes with following signal and backtrace (most symbols are missing):

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7f8155a0d770 (LWP 10542)]
0x00007f8153379d80 in write () from /lib/libc.so.6
(gdb) bt
#0 0x00007f8153379d80 in write () from /lib/libc.so.6
#1 0x0000000000417590 in ?? ()
#2 0x0000000000406cd6 in ?? ()
#3 <signal handler called>
#4 0x00007f8153348f15 in waitpid () from /lib/libc.so.6
#5 0x00007f8154f5616a in ?? () from /usr/lib/libvirt.so.0
#6 0x00007f8154f573e2 in ?? () from /usr/lib/libvirt.so.0
#7 0x00007f8154f12c7f in __virStateCleanup () from /usr/lib/libvirt.so.0
#8 0x0000000000409fa1 in ?? ()
#9 0x00007f81532bf466 in __libc_start_main () from /lib/libc.so.6
#10 0x0000000000406b29 in ?? ()
#11 0x00007fff5da1a3a8 in ?? ()
#12 0x000000000000001c in ?? ()
#13 0x0000000000000003 in ?? ()
#14 0x00007fff5da1abe0 in ?? ()
#15 0x00007fff5da1abf3 in ?? ()
#16 0x00007fff5da1abfd in ?? ()
#17 0x0000000000000000 in ?? ()

Finally, if i start kvm (with all the arguments virt-manager passes, even tried -S) from command line the guest is stable. I can even connect to guest's vnc server immediately with vinagre. Resolution changing isn't an issue anymore.

I'm using Ubuntu 8.10. Relevant packages version:
virt-manager 0.5.4-2ubuntu1,
virt-viewer 0.0.3-2ubuntu1,
libvirt0 0.4.4-3ubuntu3,
libvirt-bin 0.4.4-3ubuntu3,
kvm 1:72+dfsg-1ubuntu6.

[royalbee (royalbee)]

same here viewer crashes when xp changes resolution

[Marcus Carlson (0-launchpad-mejlamej-nu)]

I also have this with Ubuntu 8.10 / 9.04 guest when starting up.

[Christian_K (mr-g-c)]

Same Problem here on Ubuntu 8.04 X64, manual compiled KVM84 and normal ubuntu Pckage of Libvirt (i guess 0.40).

[Marc Deslauriers (mdeslaur)]

Thanks for reporting this issue.
Do you still have it?
Are you able to reproduce this with a recent version of Ubuntu, such as Karmic or Lucid?

[Srećko Jurić-Kavelj (jksrecko)]

I switched to VirtualBox for virtualization, long time ago. So, I can't reproduce the problem. I don't even work on such a recent distro of Ubuntu. I had Karmic on my laptop (doesn't have virtualitzation extensions), but recently I downgraded it to Jaunty. I plan to install Lucid when it comes out (or maybe wait for first minor version). Maybe then I'll try to reproduce this bug. Until then... Have you tried to reproduce the bug?

[Marc Deslauriers (mdeslaur)]

I can't reproduce the issue.

[Srećko Jurić-Kavelj (jksrecko)]

Well, this bug probably resolved itself...

[Marc Deslauriers (mdeslaur)]

OK, I'm closing this bug since we can't reproduce it. Feel free to open a new bug if the problems occurs again.

Thanks!