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

[Alon Levy]

On Sat, Jan 29, 2011 at 10:56:16AM +0100, Julian Sikorski wrote:
> W dniu 2011-01-29 10:47, Alon Levy pisze:
> > On Fri, Jan 28, 2011 at 09:54:37PM +0100, Julian Sikorski wrote:
> >> W dniu 28.01.2011 21:06, Alon Levy pisze:
> >>> On Fri, Jan 28, 2011 at 08:48:06PM +0100, Julian Sikorski wrote:
> >>>> W dniu 28.01.2011 15:32, Alon Levy pisze:
> >>>>> On Fri, Jan 28, 2011 at 12:45:07AM +0100, Julian Sikorski wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> I wanted to try spice on Fedora 14. I have a Win7 Pro 32bit image which
> >>>>>> was created with virt manager. I later added virtio network and drive to
> >>>>>> it, installing drivers in the guest as well.
> >>>>>> The problem is that if I try to use this machine as per F14 wiki, i.e.:
> >>>>>> qemu /var/lib/libvirt/images/windows.img -usbdevice tablet -soundhw ac97
> >>>>>> -vga qxl -spice port=5930,password=asd -enable-kvm
> >>>>>> the windows guest will BSOD during boot (note that I need to do this as
> >>>>>> su due to the way how virt-manager sets permissions).
> >>>>>> Is this issue known? What info could I provide to help resolving this?
> >>>>>
> >>>>> So which version do you have, 0.7.2?
> >>>>
> >>>> I tried both the version from f14 updates and from f14 preview repo.
> >>>> Neither of them works.
> >>>>
> >>>>> does the vm boot normally when booting without spice?
> >>>>
> >>>> Yes, I can boot the machine via the virt-manager just fine.
> >>>>
> >>>> does the vm have qxl driver installed already?
> >>>>
> >>>> IIRC it does not. Where I can downlad such driver, and would it be OK to
> >>>> install it while booted via virt-manager with no spice?
> >>>>
> >>> If you didn't install it it wouldn't have, the driver isn't part of win7
> >>> install or available via updates or something. But actually I don't want you
> >>> to install it, I mean it might help (so you might want to try that - it's
> >>> available at http://www.spice-space.org/download.html) but this means the
> >>> problem is with the qxl device vga emulation. (I still have no clue)
> >>
> >> I'm not sure how to install the driver with the device not present I'm
> >> afraid...
> > 
> > My bad, I souldn't have suggested that, I didn't understand. I don't know either
> > btw, wish I did.
> > 
> >>
> >>>
> >>>>> can you give the bsod screenshot (from monitor in qemu you can do screendump <filename.ppm>)?
> >>>>
> >>>> http://belegdol.fedorapeople.org/spicebsod.png
> >>>
> >>> How much memory do you give the vm? it seems like you are giving it the default. Could you try enlarging that? I'm just saying this because
> >>> http://support.microsoft.com/kb/326679
> >>>
> >>
> >> Looks like you were right. In virt-manager I gave it 1 GB, which was
> >> enough. But when I added -m 1596 to the command line spice also started
> >> to work. Unfortunately, it brought the machine to crawl since I only
> >> have 2 GB physical ram in this laptop.
> > 
> > I run win7 32 bit win7 vm's with -m 1024. I'm not running F14, but git (actually
> > some strange hybrid), so I can't be sure it's exactly the same.
> 
> I will try with the packages from the virt-preview repo maybe that will
> help.
> 
> > 
> >> By the way, is the configuration made with virt-manager respected when
> >> you run qemu from the command line? To me it seemed like virtio harddisk
> >> was gone since windows was looking for a driver for a qemu harddrive or
> >> something along these lines.
> > It shouldn't be. I'm not even sure where virt-manager keeps it's configuration.
> 
> IIRC it keeps it in the domain xml file wherever that is stored. In that
> case, what would be the command line to enable virtio disk and network?
Just run virt-manager, then ps xaw | grep qemu and pick it from there :)

I think this is correct, but I'm no expert on these parameters: (i.e.
 this is what I'm running)

  "-net nic,macaddr=00:00:11:11:22:00,model=virtio"
  '-drive file="%(image)s",index=0,media=disk,cache=writeback,if=virtio'

> 
> >>
> >>>>
> >>>> I hope this will make it more clear what I am trying to accomplish, or
> >>>> show where I am doing the wrong thing.
> >>>
> >>> It certainly helps, thanks for taking the time to report this.
> >>>
> >>
> >> No problem.
> >>
> >> Cheers,
> >> Julian
>