[Users] oVirt 3.2 and win 7 VM often in blue screen

Thu Feb 21 16:48:05 UTC 2013

This is a really great program to debug Blue Screens just FYI.  Its a lot
easier to use than Microsoft's tools.

http://www.majorgeeks.com/BlueScreenView_d6200.html

On Thu, Feb 21, 2013 at 11:41 AM, Gianluca Cecchi <gianluca.cecchi at gmail.com
> wrote:

> Hello,
> I have f18 engine server + another f18 node with 3.2 final.
> I have a win7 vm *32bit) that repeatedly goes blue screen after a
> couple of hours...
>
> qemu options are :
>
> qemu      8067     1 17 17:16 ?        00:03:44 /usr/bin/qemu-kvm
> -name w7 -S -M pc-0.14 -cpu Opteron_G2 -enable-kvm -m 1024 -smp
> 1,sockets=1,cores=1,threads=1 -uuid
> cc62f232-2172-4f66-8a06-0ec549277049 -smbios
> type=1,manufacturer=oVirt,product=oVirt
>
> Node,version=18-1,serial=34353439-3036-435A-4A38-303330393338,uuid=cc62f232-2172-4f66-8a06-0ec549277049
> -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/w7.monitor,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=2013-02-21T17:16:05,driftfix=slew -no-shutdown -device
> ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device
>
> ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5
> -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1
> -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2
> -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive
> if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device
> ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
>
> file=/rhev/data-center/5849b030-626e-47cb-ad90-3ce782d831b3/14b5167c-5883-4920-8236-e8905456b01f/images/5fa75ba2-ea0c-47e3-91d9-42148b75b1cf/aec75a91-ecac-4275-8728-9355e86b890c,if=none,id=drive-virtio-disk0,format=qcow2,serial=5fa75ba2-ea0c-47e3-91d9-42148b75b1cf,cache=none,werror=stop,rerror=stop,aio=native
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=32 -device
>
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:04:04:5c,bus=pci.0,addr=0x3
> -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/w7.com.redhat.rhevm.vdsm,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/w7.org.qemu.guest_agent.0,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev spicevmc,id=charchannel2,name=vdagent -device
>
> virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
> -spice
> port=5903,tls-port=5904,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir
> -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -device
> intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
> hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev
> spicevmc,id=charredir0,name=usbredir -device
> usb-redir,chardev=charredir0,id=redir0 -chardev
> spicevmc,id=charredir1,name=usbredir -device
> usb-redir,chardev=charredir1,id=redir1 -chardev
> spicevmc,id=charredir2,name=usbredir -device
> usb-redir,chardev=charredir2,id=redir2 -chardev
> spicevmc,id=charredir3,name=usbredir -device
> usb-redir,chardev=charredir3,id=redir3 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8
>
>
> On engine events I see
>
> 2013-Feb-21, 12:28 VM w7 started on Host f18ovn03.ceda.polimi.it
>
> then
> 2013-Feb-21, 13:04 VM w7 is down. Exit message: User shut down
> (but I didn't shutdown it...)
>
> I start it at 17:16 and I get the black background page asking if I
> want to start normally. I say yes and after booting I get the window
> regarding unclean shutdown:
>
> Problem signature:
>   Problem Event Name: BlueScreen
>   OS Version: 6.1.7601.2.1.0.256.48
>   Locale ID: 1040
>
> Additional information about the problem:
>   BCCode: 1000008e
>   BCP1: C0000005
>   BCP2: 8B923037
>   BCP3: 8A623ACC
>   BCP4: 00000000
>   OS Version: 6_1_7601
>   Service Pack: 1_0
>   Product: 256_1
>
> Files that help describe the problem:
>   C:\Windows\Minidump\022113-10155-01.dmp
>   C:\Users\politest1\AppData\Local\Temp\WER-23025-0.sysdata.xml
>
> Read our privacy statement online:
>   http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
>
> If the online privacy statement is not available, please read our
> privacy statement offline:
>   C:\Windows\system32\en-US\erofflps.txt
>
> What can I do to debug?
> Are the two files referred (the .dmp and the .xml that I collected)
> useful to analyze anything?
> Do the contain sensitive data?
>
> The win7 VM has spice-guest-toos-0.3 installed and defined with spice
> console.
>
> It is the first win7 VM on final 3.2, while on another cluster with
> 3.2 beta I have another similar one (same iso) that stays up for
> several days without problem, so I presume something possible with
> particular hw of this node:
>
> HP BL685c G1 with 32Gb of ram
> AMD Opteron G2 (quad sockets dualcore)
> OS Version: Fedora - 18 - 1
> kernel 3.7.8 - 202.fc18.x86_64
> qemu-kvm 1.2.2 - 6.fc18
> vdsm-4.10.3-8.fc18
> libvirt-0.10.2.3-1.fc18
> spice 0.12.2 - 3.fc18
>
> active VMs : 4
>
> Thanks,
> Gianluca
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>

-- 
Chris Noffsinger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130221/4dcf14ec/attachment-0001.html>