From: Andreas Olsowski <andreas.olsowski@leuphana.de>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: dom0 system functions impaired after creating domU on xen4.1 running 2.6.32-jeremy
Date: Wed, 15 Jun 2011 13:08:25 +0200 [thread overview]
Message-ID: <4DF892A9.3010403@leuphana.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2106 bytes --]
I decided to migrate from my old Xen platform (xen4.0 with 2.6.31-pvops
dom0 and 2.6.32 guests) to my new one (xen4.1 with 2.6.32-jeremy dom0
and 2.6.39 guests).
Everything was going fine when, without indication of any problems, "xm
create /etc/xen/domains/xy.sxp -c" didnt produce output anymore and the
guest didnt start. (no output = no kernel booting, no error message,
nothing, zip, nada)
So i went to cancel the process, destroy the domain, retry with xm, try
a different guest, but to no avail. (I tried xl too at that point)
Just to se whats going on i ran "ps auxw" ... it hung itself after
listing some processes.
So in addition to not beeing able to create new guests i couldnt even
list my processes.
I live migrated all the guests to another host and went on to "init 6"
the affected server.
At the stage where is suppose all remaining processes received the
signal to stop, the terminal i initially ran "xm create" on popped out 2
lines of text i sadly neglected to copy (i guess some generic error
creating domain, or creation cancelled, sth like that)
Additionally "ps auxw" started working again and after a short while the
box rebooted as expected.
I had noticed this behavior earlier, like 2 weeks ago, but didnt think
much of it, since i was working on the system configuration and had to
reboot the server anyway.
Does anybody have a clue what could lead to this behavior?
The systems are pretty much what i would expect most xen hosts to be,
some linux (debian 6.0 in my case), a current version of Xen and a
current jeremy pvops dom0 kernel. (kernel is 2.6.32.40 now and was an
earlier version when i first encountered the problem)
Should i maybe restrain myself from using xm to create guests or even
from using it altogether? (xl has no live migration and cant xl new ...
xl start)
Input would be greatly appreciated.
with best regards
--
Andreas Olsowski
Leuphana Universität Lüneburg
Rechen- und Medienzentrum
Scharnhorststraße 1, C7.015
21335 Lüneburg
Tel: ++49 4131 677 1309
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6595 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-06-15 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 11:08 Andreas Olsowski [this message]
2011-06-15 14:29 ` dom0 system functions impaired after creating domU on xen4.1 running 2.6.32-jeremy Konrad Rzeszutek Wilk
2011-06-15 15:25 ` Stefano Stabellini
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=4DF892A9.3010403@leuphana.de \
--to=andreas.olsowski@leuphana.de \
--cc=xen-devel@lists.xensource.com \
/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.