All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Vorlicek <patrick.vorlicek@udo.edu>
To: kvm-ia64@vger.kernel.org
Subject: BSOD on plug&play searched because of lost harddrive on virtio scsi controller
Date: Fri, 09 Aug 2013 14:04:38 +0000	[thread overview]
Message-ID: <5204F6F6.3040608@udo.edu> (raw)

Hello,

I have a problem with mit my Windows 7 x64 / Windows Server 2008 R2 
guest on a Ubuntu Server (Kernel 3.11.0-rc2) Host with two Intel Xeon CPUs.

Both guests have the RedHat VirtIO drivers for the disk and network 
adapter installed. I tried version 1.65 from 
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/ but also version 
1.59.

Everytime I hotadd a disk or just search for new devices in the device 
manager, the system (or even all discs) get lost resulting in a BSOD 
with CRITICAL_OBJECT_TERMINATION (0x000000f4 stop code) after some kind 
of timeout. I couldn't find any documentation of a simular issue, so I'm 
asking here for help.

Minidumps can be found here:
http://www.vorlicek.de/minidump/080913-13852-01.dmp
http://www.vorlicek.de/minidump/080913-9375-01.dmp
http://www.vorlicek.de/minidump/080913-9375-02.dmp

The xml-description of the virtual machine - i'm using libvirt - looks 
like this:

<domain type='kvm' id='10'>
   <name>gekko</name>
   <uuid>48c7d582-45b4-a648-fe46-ee73b0a3f157</uuid>
   <memory unit='KiB'>4194304</memory>
   <currentMemory unit='KiB'>2097152</currentMemory>
   <vcpu placement='static'>4</vcpu>
   <os>
     <type arch='x86_64' machine='pc-1.2'>hvm</type>
     <boot dev='hd'/>
   </os>
   <features>
     <acpi/>
     <apic/>
     <pae/>
   </features>
   <cpu>
     <topology sockets='1' cores='4' threads='1'/>
   </cpu>
   <clock offset='localtime'/>
   <on_poweroff>destroy</on_poweroff>
   <on_reboot>restart</on_reboot>
   <on_crash>restart</on_crash>
   <devices>
     <emulator>/usr/bin/kvm</emulator>
     <disk type='file' device='disk'>
       <driver name='qemu' type='qcow2' cache='writeback'/>
       <source file='/data/qcow2/gekko.qcow2'/>
       <target dev='vda' bus='virtio'/>
       <alias name='virtio-disk0'/>
       <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 
function='0x0'/>
     </disk>
     <disk type='file' device='cdrom'>
       <driver name='qemu' type='raw'/>
       <source file='/data/iso/virtio-win-0.1-65.iso'/>
       <target dev='hda' bus='ide'/>
       <readonly/>
       <alias name='ide0-0-1'/>
       <address type='drive' controller='0' bus='0' target='0' unit='1'/>
     </disk>
     <controller type='usb' index='0'>
       <alias name='usb0'/>
       <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
function='0x2'/>
     </controller>
     <controller type='ide' index='0'>
       <alias name='ide0'/>
       <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
function='0x1'/>
     </controller>
     <interface type='bridge'>
       <mac address='52:54:00:5e:40:33'/>
       <source bridge='br0'/>
       <target dev='vnet3'/>
       <model type='virtio'/>
       <alias name='net0'/>
       <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
function='0x0'/>
     </interface>
     <serial type='pty'>
       <source path='/dev/pts/2'/>
       <target port='0'/>
       <alias name='serial0'/>
     </serial>
     <console type='pty' tty='/dev/pts/2'>
       <source path='/dev/pts/2'/>
       <target type='serial' port='0'/>
       <alias name='serial0'/>
     </console>
     <input type='tablet' bus='usb'>
       <alias name='input0'/>
     </input>
     <input type='mouse' bus='ps2'/>
     <graphics type='vnc' port='5904' autoport='no' listen='0.0.0.0' 
keymap='de'>
       <listen type='address' address='0.0.0.0'/>
     </graphics>
     <video>
       <model type='vga' vram='9216' heads='1'/>
       <alias name='video0'/>
       <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 
function='0x0'/>
     </video>
     <hostdev mode='subsystem' type='usb' managed='no'>
       <source>
         <vendor id='0x0557'/>
         <product id='0x2221'/>
         <address bus='5' device='2'/>
       </source>
       <alias name='hostdev0'/>
     </hostdev>
     <memballoon model='virtio'>
       <alias name='balloon0'/>
       <address type='pci' domain='0x0000' bus='0x00' slot='0x05' 
function='0x0'/>
     </memballoon>
   </devices>
   <seclabel type='none'/>
</domain>

I hope that's all information needed. Except this issue everything works 
fine and stable with these virtual machines.

Greetings,
Patrick Vorlicek

                 reply	other threads:[~2013-08-09 14:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5204F6F6.3040608@udo.edu \
    --to=patrick.vorlicek@udo.edu \
    --cc=kvm-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.