Bug 448893

Erwan,

A bit confused:
In your first sentence, you state that a migrate generates soft lockup statements;
then you state that live migration works fine; then you state the migrated vm
shows an oops.

So, are multiple events occurring,? if so, what is the first event?
if not, please be clear what is or is not occurring.

Please provide details of dom0 (kernel rev), domU(same, kernel rev),
and xend logs from dom0's.

The migrate command you used would be nice to see as well.

oops... I saw the kernel versions above, after reading more carefully.

I would still like the details of what occurred (migrate worked) or not
(guest oops'd).

- Don

Hey Don,

To be more precise, If I do a "xm migrate mydomU mynewnode", domU's kernel shows
that trace. If I do a "xm migrate --live mydomU mynewnode", the oops rarely appears.

By rarely, I mean that most of time the "live" migrate works but sometimes this
oops appears. I think 80% of time, live migrates works whereas 100% of "xm
migrate" fails.

Created attachment 309883 [details]
x86_64 xenpv package with possible suspend fix

Erwan,

Please give the attached x86_64 patch a try.
(I'm guessing you were testing x86_64).

if you need another rpm (i686, i686-PAE), let me know, i'll post it.

- Don

Setting status to NEEDINFO so reporter can re-assign to me when reporting
test status back.

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Bugzilla is not a support tool

The Bugzilla interface at bugzilla.redhat.com is used internally by Red Hat to process changes e.g. to Red Hat Enterprise Linux and related products, as well as by the Fedora Community to develop the Fedora Project.

It is publicly available and everyone with an email address is able to create an account, file bugs, comment on bugs she or he has access to. Not all bugs are public though and not all issues filed are handled in the same way: it makes a huge difference who is behind a bug.

Red Hat does monitor Bugzilla entries, and it does review them for inclusion in errata, etc.

Nevertheless, as noted on the login page, Bugzilla is not a Support tool. It is an Engineering tool. It is used by Red Hat Engineering to track issues and product changes, as well as to interact with Egineering partners and other parties external to Red Hat on a technical level.

So while all changes to Red Hat Enterprise Linux will at a point go through Bugzilla, this difference has a number of important consequences for general product issues filed directly through Bugzilla by external users without any privileged Engineering relationship:

    * Red Hat does NOT guarantee any response time or Service Level Agreement (SLA) for Bugzilla entries. - A review might happen immediately or after a time span of any length. The SLAs for Red Hat Enterprise Linux provided by Red Hat Support can be found at:  https://www.redhat.com/support/policy/sla/production/

    * Not all comments are publicly visible. - Red Hat Support provides customers with appropriate information excerpts and status updates from that. Red Hat does not commit to provide detailed explanations, or guidance in the context of Bugzilla. Therefore for example, Bugzilla entries might be closed as it seems without any further explanation, while Red Hat Support actually provides such explanation to customers filing through the regular support channels.

    * Issues coming through the regular support process, will always be prioritized higher than issues of similar impact and severity that are being filed directly through Bugzilla (unless the later get linked to customer support tickets, like this issue was). This means that they are more likely to be addressed and they are more likely to meet inclusion criteria consistent with the Red Hat Enterprise Linux life cycle policy: http://www.redhat.com/security/updates/errata/

    * Work-arounds and Hotfixes if possible and appropriate are provided by Red Hat Support and through the regular support process. - This means that even before a permanent fix is made available through RHN,customers who raised a high severity issue through Red Hat Support, are likely to receive an interim solution.

Red Hat provides common Bugzilla access in order provide efficient development community interaction and as much transparency as possible to our customers. Our Engineers are encouraged to provide non-customer specific and non-confidential information publicly as often as possible.

So while Red Hat considers issues directly entered into Bugzilla valuable feedback - may it be as comments to existing Bugzilla entries or by opening a new one; for customers encountering production issues, Bugzilla is not the right channel.

Therefore we ask our customers to file requests important for their production systems via our Support service. Only for those issues, we can ensure a consistent communication. Information about our production support process can be found at: http://www.redhat.com/support/process/

Bugzilla can always be used as a supportive channel to that communication.

Note: If your customer is participating in the Academic program and has chosen to run a Subscription without support, they consequently have no access to Red Hat Support and thus no SLA. If you feel that this is insufficient for your use case, you should consider contacting the Red Hat Education specialist as described at: http://www.redhat.com/solutions/education/academic/individual/

Reporter, were you able to verify the patch?

I'm sorry I hadn't time for that. I'm adding this on my planning and keep you in touch

This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time.  This request will be
reviewed for a future Red Hat Enterprise Linux release.