[Spice-devel] BSOD when booting Win7 Pro with spice

[Alon Levy]

On Sun, Jan 30, 2011 at 11:45:31PM +0100, Julian Sikorski wrote:
> W dniu 30.01.2011 22:39, Alon Levy pisze:
> > This looks like perfectly normal behavior for a qemu process (sorry, listened
> > to h2g2 recently). But it still does. So I'm going to ask if you can eradicate parts
> > of the qemu command line, or better yet do the reverse, start from the minimal
> > command line with -vga qxl -spice port=5920,disable-ticketing and see if it still
> > gives the screen. Another thing is if you can give the spicec.log file from your client,
> > it's at $HOME/.spicec/spicec.log.
> 
> This actually boots:
> 
> I think I got it: it was the -S option at fault, which is not surprising
> at all after you read the manpage: Do not start CPU at startup (you must
> type 'c' in the monitor).
Heh. Yes, I missed it too.

> Still, while the machine boots now, it seems to get stuck at the
> "Starting windows" screen.
> Only after you remove the network part from the command it boots as
> expected. I.e, the most complete machine I was able to boot is as follows:
> 
> QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvmM fedora-13 -enable-kvm -m 1024
> -smp 1,sockets=1,cores=1,threads=1 -name windows -uuid
> a5a9cf48-603e-5795-ba0f-b5692ce2d93d -nodefconfig -nodefaults -chardev
> socket,id=monitor,path=/var/lib/libvirt/qemu/windows.monitor,server,nowait
> -mon chardev=monitor,mode=control -rtc base=localtime -boot c -drive
> if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device
> ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> file=/var/lib/libvirt/images/windows.img,if=none,id=drive-virtio-disk0,boot=on,format=raw
> -device
> virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0
> -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device
> usb-tablet,id=input0 -spice port=5900,disable-ticketing -vga qxl -device
> AC97,id=sound0,bus=pci.0,addr=0x5 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
> 
> The addition of
> 
> -netdev tap,fd=42,id=hostnet0 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:6a:d1:82,bus=pci.0,addr=0x4
> 
> is the part which gets it stuck. Fortunately there is an error (which
> was there all the time I just missed it somehow):
> 
> qemu-kvm: -netdev tap,fd=42,id=hostnet0: TUNGETIFF ioctl() failed: Bad
> file descriptor
> TUNSETOFFLOAD ioctl() failed: Bad file descriptor
> 
Tough still strange that it got stuck here. qemu should either quit at startup
when it notices this (and prints the ioctl() failed message) or work correctly,
not do this.

> Once we get this to work I'll be able to download the spice VGA driver
> and test this properly.
> 
Great.

> Julian
> 

> 1296425222 INFO [21741:21741] init_key_map: using evdev mapping
> 1296425222 INFO [21741:21741] Application::main: starting 0.7.2
> 1296425222 INFO [21741:21741] MultyMonScreen::MultyMonScreen: platform_win: 39845889
> 1296425222 INFO [21741:21741] GUI::GUI: 
> 1296425224 INFO [21741:21741] ForeignMenu::ForeignMenu: Creating a foreign menu connection /tmp/SpiceForeignMenu-21741.uds
> 1296425224 INFO [21741:21743] RedPeer::connect_unsecure: Trying 127.0.0.1 5900
> 1296425224 INFO [21741:21743] RedPeer::connect_unsecure: Connected to 127.0.0.1 5900
> 1296425224 INFO [21741:21744] RedPeer::connect_unsecure: Trying 127.0.0.1 5900
> 1296425224 INFO [21741:21745] RedPeer::connect_unsecure: Trying 127.0.0.1 5900
> 1296425224 INFO [21741:21745] RedPeer::connect_unsecure: Connected to 127.0.0.1 5900
> 1296425224 INFO [21741:21744] RedPeer::connect_unsecure: Connected to 127.0.0.1 5900
> 1296425224 INFO [21741:21746] RedPeer::connect_unsecure: Trying 127.0.0.1 5900
> 1296425224 INFO [21741:21746] RedPeer::connect_unsecure: Connected to 127.0.0.1 5900
> 1296425224 WARN [21741:21743] RedClient::find_factory: no factory for 8
> 1296425224 INFO [21741:21747] RedPeer::connect_unsecure: Trying 127.0.0.1 5900
> 1296425224 INFO [21741:21747] RedPeer::connect_unsecure: Connected to 127.0.0.1 5900
> 1296425224 INFO [21741:21748] RedPeer::connect_unsecure: Trying 127.0.0.1 5900
> 1296425224 INFO [21741:21748] RedPeer::connect_unsecure: Connected to 127.0.0.1 5900
> 1296425224 INFO [21741:21741] DisplayChannel::create_sw_canvas: display 0: using sw
> 1296425227 INFO [21741:21743] RedChannel::handle_notify: remote channel 1:0 warn!!! #0: keyboard channel is insecure
>