KVM: Windows Server 2008 VM bluescreens on install

[Jim Salter]

Using Precise beta (upgraded from a clean install of Oneiric Server), when attempting to install Windows Server 2008 R2 w/SP1 into a new VM with hypervisor default hardware for that guest platform, it bluescreens with a STOP error before getting to the first installer interface screen.

This issue did not occur on Oneiric.
---
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
KvmCmdLine:
 UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
 104 3966 1 87 1116659 4123960 2 12:14 ? 00:06:17 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 4096 -smp 4,sockets=4,cores=1,threads=1 -name dc0 -uuid dba0cee5-0cd2-2669-6d33-7d3d302f27c9 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/dc0.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/mapper/vg0-dc0,if=none,id=drive-virtio-disk0,boot=on,format=raw,cache=writethrough -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 -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 -netdev tap,fd=19,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:7e:ee:56,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
MachineType: System manufacturer System Product Name
Package: qemu-kvm 0.14.1+noroms-0ubuntu6
PackageArchitecture: amd64
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-server root=/dev/mapper/vg0-root ro
ProcVersionSignature: Ubuntu 3.0.0-12.20-server 3.0.4
Tags: oneiric
Uname: Linux 3.0.0-12-server x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A88-M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd09/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Jim Salter (jrssnet)]

FWIW, the STOP error happens whether booting into the new 3.2 kernel or the Oneiric server kernel - so this isn't a kernel problem, it seems to be a KVM problem.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in kvm.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Jim Salter (jrssnet)]

Hm. I take it back about the problem not existing in Oneiric - I wiped the machine and reloaded clean with Oneiric Server, and am encountering the same bluescreen during installation at the same place. This may be related to the hardware platform - I *JUST* did several of these installs onto Intel i7 and AMD Opteron machines this week, but this particular host is an Athlon X3-based machine.

Maybe there's a bug related to the hardware? I don't think it's actual *faulty* hardware; the problem is too consistent and only occurs during guest installation - also, I've switched from a ripped ISO image (which worked fine for previous installs) to reading /dev/sr0 directly (from a different disc, yet) and got the exact same bluescreen.

Retrying yet again with a non-SP1 Windows Server 2008 disc at /dev/sr0 now to see if the results are any different.

[Jim Salter (jrssnet)]

Yep, same bluescreen with Server 2008 R2, non-SP1. That's three different discs and a ripped ISO image, all of which are known good, which bluescreen in the same place with the same error. I'm going to replace the motherboard and CPU with an Intel i7 and see if the problem stays with me or not.

[Jim Salter (jrssnet)]

For reference - current motherboard is Asus m5a88-M, current CPU is Athlon X3-450. I will be replacing these with an ASROCK motherboard and Intel i7-2600 ASAP and retesting. I pretty much expect the bluescreen problem will go away on the alternate hardware.

[Serge Hallyn (serge-hallyn)]

Thanks for submitting this bug. If possible, could you do

apport-collect 956374

to send us some more information on your system? I will try to reproduce here.

[Serge Hallyn (serge-hallyn)]

(This could be related to bug 921208)

[Jim Salter (jrssnet)]

OK, I did some more testing in between last post and logging in again to see your request Serge - changing hardware did not resolve the problem, but removing the VM entirely and recreating it *did*, both on the new hardware and on the old hardware.

At this point my best guess is that something was screwy in the Precise installation, since the bug followed me from hardware to hardware but went away when I deleted and re-created the VM definition itself. Note: the definition is 2 CPUs, 4096MB RAM (of 16GB available), Windows, Server 2008, all else left to default, as created by virt-manager. If it helps, I am using LVM2 and have a 40GB LV defined to use as raw storage for the guest.

I did not blow away the LV or VG from the Precise install when I reverted to Oneiric; I wiped and formatted the system LV but imported the VG and all other LVs as they were from the Precise install.

I don't have the machine in front of me right now, but I'll run apport for you as requested as soon as I'm in front of it again.

[Serge Hallyn (serge-hallyn)]

Thanks. I'm also wondering whether this is another dup of bug 944338. Hopefully apport can give us some more information.

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

apport information

[Jim Salter (jrssnet)]

^^ please note: all that stuff apport collected from the 11.10 reinstall, NOT the original 12.04 beta install that could not boot the guest! =)

[Serge Hallyn (serge-hallyn)]

Thanks for the information. If I understand right, you can't reproduce the problem now right? I'll mark the bug invalid (== unreproducible), but if you re-install precise on the host and reproduce, please let me know.

[Antonio Insuasti (wolfant)]

I have the same bug on Ubuntu 12.04 LTS.

This is the xml file
 !--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
  virsh edit 2008Server
or other application using the libvirt API.
-->

<domain type='qemu'>
  <name>2008Server</name>
  <uuid>a2dda40c-99c8-e893-cee7-dc4f30a8a5a5</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc-1.0'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <pae/>
  </features>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/Windows2008.img'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/windows.iso'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/windows.iso'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' unit='0'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:d6:dd:3e'/>
      <source bridge='br0'/>
      <model type='e1000'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes'/>
    <video>
      <model type='vga' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </memballoon>
  </devices>
</domain>

and proc_cpu,

[Antonio Insuasti (wolfant)]

more information proc/cpuinfo

[Antonio Insuasti (wolfant)]

and more .. log of libvirt

[Antonio Insuasti (wolfant)]

and more ... lspci lsusb and lsmod.. its a HP ML 350 G5 two proccesors and 26gB ... test server :)