From: Jerone Young <jyoung5@us.ibm.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Big xend bug!
Date: Sun, 27 Feb 2005 23:25:35 -0600 [thread overview]
Message-ID: <1109568335.7036.21.camel@thinkpad> (raw)
While working on another bug I ran head long into an issue with xend.
When running LTP Test Suite (ltp.sf.net) simultaneously on both Dom0 & a
virtual domain.
Not going to get a chance to debug till Tuesday, I wanted to see if
others on the list could easily reproduce this on there machines. It
takes a while to get the machine in this state, because you need to wait
while LTP runs.
Here are some of my notes:
Running with Xen-unstable Feb 24, 2005
Running ltp-full-20050207
on IBM Netvista model# 8305g (Pentium 4 2.GHZ)
Case 1: Dom0 run ltp with NO virtual Domains
REBOOT WORKS FINE
Case 2: Just Dom1 (vitual Domain) run ltp
REBOOT WORKS FINE
Case 3: Dom0 & Dom1 both running LTP simultaneously
First Run:
- console to virtual domain hung, virtual domain still can be
reached via ssh
- xend totally crashed
- can't restart or get status from it xm
- When I hit a key to got from the virtual console I got the
message:
sleepython:Objects/obmalloc.o:580:PyObject_Malloc: Assertio
'bp != ((void*)0)' failed.
- run "xm console 1"
(111, 'Console refused')
ERROR: Error connecting to xend, is xend running?
- On Dom0 shutdown -h or -r does not work.
- On Dom0 only "reboot -f" will work.
--
Jerone Young
Open Virtualization
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-02-28 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 5:25 Jerone Young [this message]
2005-02-28 15:58 ` Big xend bug! Anthony Liguori
2005-02-28 16:22 ` Jerone Young
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=1109568335.7036.21.camel@thinkpad \
--to=jyoung5@us.ibm.com \
--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.