WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Xen virtual machine crash

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen virtual machine crash
From: "MagicalTux (admin)" <admin@xxxxx>
Date: Wed, 23 Mar 2005 21:47:56 +0100
Delivery-date: Wed, 23 Mar 2005 20:49:47 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Hi!

I just noticed a crash..

When a userlevel application (running as "nobody") tries to resize an
incomplete image file using libimagick, the virtual machine crashes...

[2005-03-23 21:31:41 xend] INFO (XendRoot:91) EVENT> xend.domain.exit
['XM_2', '3', 'crash']
[2005-03-23 21:31:41 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy
['XM_2', '3']
[2005-03-23 21:31:41 xend] INFO (XendRoot:91) EVENT> xend.domain.exit
['XM_2', '4', 'crash']
[2005-03-23 21:31:41 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy
['XM_2', '4']
[2005-03-23 21:31:41 xend] INFO (XendRoot:91) EVENT> xend.domain.exit
['XM_2', '5', 'crash']
[2005-03-23 21:31:41 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy
['XM_2', '5']
[2005-03-23 21:31:43 xend] DEBUG (XendDomain:244) XendDomain>reap>
domain died name=XM_2 id=3
[2005-03-23 21:31:43 xend] INFO (XendDomain:564) Destroying domain:
name=XM_2
[2005-03-23 21:31:43 xend] DEBUG (XendDomain:244) XendDomain>reap>
domain died name=XM_2 id=4
[2005-03-23 21:31:43 xend] INFO (XendDomain:564) Destroying domain:
name=XM_2
[2005-03-23 21:31:43 xend] DEBUG (XendDomainInfo:634) Closing console,
domain 4
[2005-03-23 21:31:43 xend] DEBUG (XendDomain:244) XendDomain>reap>
domain died name=XM_2 id=5
[2005-03-23 21:31:43 xend] INFO (XendDomain:564) Destroying domain:
name=XM_2
[2005-03-23 21:31:43 xend] DEBUG (XendDomainInfo:634) Closing console,
domain 5


For some reason the ids 3 4 and 5 refers to the same machine. I crashed
it a few times, but when crashing it didn't go out of the "xm list"
list. but if I just re-run "xm create /etc/xm_dom2" it's restarted.

Note: the same process does *not* crash on non-xen machines.

I searched a bit on google but couldn't find anything interesting.

Anyone have an idea of why it happens, and if a fix is planned/available
somewhere?


Mark


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>