[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] HVM domain crash due to qemu-dm quit


  • To: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>
  • Date: Wed, 18 May 2011 16:26:36 +0800
  • Delivery-date: Wed, 18 May 2011 01:32:12 -0700
  • Importance: Normal
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi:
 
     I've confronted one of my HVM domain frequently crash due to qemu-dm quit abnormally.
 
Xend.log
[2011-05-18 14:32:44 24651 1301875008] INFO (XendDomain:1259) Domain 322-2.vhd (2645) unpaused.
[2011-05-18 14:38:26 24651 1201162560] WARNING (image:552) domain 322-2.vhd: device model failure: pid 8637: died due to signal 7; see /var/log/xen/qemu-dm-322-2.vhd.log
[2011-05-18 14:38:26 24651 1108842816] WARNING (XendDomainInfo:2270) Domain has crashed: name=322-2.vhd id=2645.
[2011-05-18 14:38:26 24651 1201162560] INFO (XendDomainInfo:2481) Preserving dead domain 322-2.vhd (2645).
 
in dmesg, I saw
 
privcmd_fault: vma=ffff88007b13ef18 7f8cf182e000-7f8cf192e000, pgoff=96, uv=00007f8cf18c4000
 
There are two VHD file I have, VHDA & VHDB, all have windows 2003 x86 64 rc2 installed, but has some different softwares.
 
Since all crash happened short after VM running, so I did extra test, snapshot VHDA and start VM from snapshot, to see whether VM crash.
 
In 814 times test, VHDA crash 83 times.
In 773 times test, VHDB got no crash.
 
It looks like has relation with the VHD, maybe VHDA has something wrong?
 
What's this output indicates?
 
 
Thanks. 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.