From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: rhel6 guest fail to do save?
Date: Thu, 13 Jan 2011 07:36:02 +0000 [thread overview]
Message-ID: <1294904162.12280.93.camel@localhost.localdomain> (raw)
In-Reply-To: <19757.57820.217472.22989@mariner.uk.xensource.com>
On Wed, 2011-01-12 at 17:16 +0000, Ian Jackson wrote:
> Zhang, Yang Z writes ("RE: [Xen-devel] rhel6 guest fail to do save?"):
> > From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
> > > I think people have generally been able to save/restore with rhel6,
> > > but there are some issues with live migration between different MHz CPUs,
> > > for example: https://bugzilla.redhat.com/show_bug.cgi?id=663755
> ...
> > Sorry, I mean the HVM.
>
> This is known not to work. It fails in my automatic tests.
>
> The current RHEL6 kernel has enough pv-on-hvm drivers to get the
> toolstack to try to negotiate with the guest during save, but not
> enough (or not working enough) drivers to actually complete the
> negotiation. So the toolstack times out and the migrate/save fails.
Does any of the pv-on-hvm functionality work at all in RHEL6?
Perhaps setting "platform_pci = 0" in the guest configuration would work
around this issue? In particular if RHEL6 has no useful pv-on-hvm
functionality in the first place then nothing is lost.
Ian.
next prev parent reply other threads:[~2011-01-13 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 2:15 rhel6 guest fail to do save? Zhang, Yang Z
2011-01-12 7:37 ` Pasi Kärkkäinen
2011-01-12 7:38 ` Zhang, Yang Z
2011-01-12 17:16 ` Ian Jackson
2011-01-12 19:37 ` Pasi Kärkkäinen
2011-01-13 2:03 ` Zhang, Yang Z
2011-01-13 7:36 ` Ian Campbell [this message]
2011-01-13 7:47 ` Pasi Kärkkäinen
2011-01-13 21:22 ` Don Dutile
2011-01-13 21:45 ` Pasi Kärkkäinen
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=1294904162.12280.93.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.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.