From: "MagicalTux (admin)" <admin@FF.st>
To: xen-devel@lists.sourceforge.net
Subject: Xen virtual machine crash
Date: Wed, 23 Mar 2005 21:47:56 +0100 [thread overview]
Message-ID: <1111610876.9837.10.camel@localhost> (raw)
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
next reply other threads:[~2005-03-23 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 20:47 MagicalTux (admin) [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 21:04 Xen virtual machine crash Ian Pratt
2005-03-24 3:38 ` MagicalTux (admin)
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=1111610876.9837.10.camel@localhost \
--to=admin@ff.st \
--cc=xen-devel@lists.sourceforge.net \
/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.