From mboxrd@z Thu Jan 1 00:00:00 1970 From: "MagicalTux (admin)" Subject: Xen virtual machine crash Date: Wed, 23 Mar 2005 21:47:56 +0100 Message-ID: <1111610876.9837.10.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org 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