Comment 2 for bug 379991

I'm also experiencing a similar (possible the same) KVM problem on Jaunty with various Win XP virtual machines, with kernel 2.6.30-020630-generic #020630 SMP. Running VMs via virt-manager, it appears that the Windows VMs actually boot, but the VNC screen remains blank/black. The screen goes blank right after the libvirt bios screen. In some cases, I get the message that the Windows instance isn't responding to VNC (presumably meaning that it's crashed).

When running kvm on the command line, e.g.
usr/bin/kvm -S -M pc -m 512 -smp 1 -name xpsp3_ie7 -uuid 5d26354f-748a-b22f-edd8-2b56a6362a7a -monitor pty -vga std -pidfile /var/run/libvirt/qemu/xpsp3_ie7.pid -no-acpi -boot c -drive file=/home/kvm/images/xpsp3_ie7_qcow2.img,if=ide,index=0,boot=on -net nic,macaddr=00:16:3e:7a:8b:5d,vlan=0 -net tap,fd=19,script=,vlan=0,ifname=vnet1 -serial none -parallel none -usb -usbdevice tablet

I get the warning or error:
TUNGETIFF ioctl() failed: Bad file descriptor
char device redirected to /dev/pts/7

I have a Jeos (Ubuntu Hardy) VM which I run headless, and this still seems to function properly (i.e. I can SSH into it), although also gives a black screen when trying to view the console via VNC.

This is all running on an ASUS laptop with Intel Core 2 Duo CPU T7100 @1.80GHz and 32bit Jaunty.

For the record, I installed the 2.6.30 kernel to allow testing of the new UXA support for Intel graphics chipsets.

Dave