From: Tim Evers <it@niemail.de>
To: xen-devel@lists.xensource.com
Subject: a ton of kernel issues
Date: Mon, 12 Dec 2011 22:44:08 +0100 [thread overview]
Message-ID: <4EE675A8.3030609@niemail.de> (raw)
Hi folks,
please forgive me if I'm not 100% right on this list but I'm going mad
about the current xen development as far as the pv_ops kernel are
involved. I've been using Xen since 3.0 in various productive setups
without any serious problems for years now.
And now, since the support for the "patched" distro-kernel like debian 5
run out I'm trying to setup a working xen+pv_ops kernel with regard to
cpu and ram hotplug and live migration. Nothing special I thought but
hell I'm totally lost: After testing two month now dozens of
combinations I was not able to find a single kernel / xen combination
which supports the abovementioned features. Some crash after hotplug on
a migrated domu, some crash right at the migration and some crash right
at the start if vcpu_avail > vcpus.
I've tested
xen-4.0
xen-4.1
debian 6 32 and 64 bit (2.6.32-x kernel)
ubuntu lucid 32 and 64 bit kernels including karmic, natty and even
oneric backports
I've put some questions on the users mailinglist, wrote bug reports but
today after two month work on this I'm as stuck as one can get.
Is it possible that there is not a single working xen+pv_ops setup out
there which matches my needs? I can't believe it.
I appreciate _any_ hint!
Regards
Tim
http://lists.xen.org/archives/html/xen-users/2011-11/msg00553.html
http://lists.xen.org/archives/html/xen-users/2011-11/msg00523.html
http://lists.xen.org/archives/html/xen-users/2011-11/msg00295.html
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/893177
next reply other threads:[~2011-12-12 21:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 21:44 Tim Evers [this message]
2011-12-12 21:56 ` a ton of kernel issues Konrad Rzeszutek Wilk
2011-12-14 9:00 ` Tim Evers
2011-12-15 1:25 ` Konrad Rzeszutek Wilk
2011-12-13 9:09 ` George Shuklin
2011-12-13 10:19 ` Alessandro Salvatori
2011-12-13 10:36 ` George Shuklin
2011-12-13 13:17 ` David Vrabel
2011-12-13 13:37 ` Ian Campbell
2011-12-13 20:59 ` George Shuklin
2011-12-13 22:30 ` Ian Campbell
2011-12-13 22:53 ` George Shuklin
2011-12-14 7:25 ` Ian Campbell
2011-12-14 12:16 ` Ian Campbell
2011-12-14 12:21 ` David Vrabel
2011-12-14 13:11 ` Jan Beulich
2011-12-14 13:48 ` Ian Campbell
2011-12-14 17:44 ` Konrad Rzeszutek Wilk
2011-12-15 12:45 ` George Shuklin
2011-12-15 16:26 ` Konrad Rzeszutek Wilk
2011-12-13 21:05 ` George Shuklin
2011-12-13 21:45 ` Konrad Rzeszutek Wilk
2011-12-14 12:28 ` David Vrabel
2011-12-14 16:57 ` Konrad Rzeszutek Wilk
2011-12-14 7:47 ` Fajar A. Nugraha
2011-12-14 18:40 ` George Shuklin
2011-12-13 14:18 ` Konrad Rzeszutek Wilk
2011-12-13 21:10 ` George Shuklin
2011-12-13 21:38 ` Konrad Rzeszutek Wilk
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=4EE675A8.3030609@niemail.de \
--to=it@niemail.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.