From: Anthony Liguori <aliguori@us.ibm.com>
To: "Xin, Xiaohui" <xiaohui.xin@intel.com>
Cc: Xen Developers <xen-devel@lists.xensource.com>,
Rick Gonzalez <rcgneo@us.ibm.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: Daily Xen-HVM Build Testing: cs10470: broken
Date: Wed, 21 Jun 2006 21:28:48 -0500 [thread overview]
Message-ID: <449A0060.6080209@us.ibm.com> (raw)
In-Reply-To: <D5D6EDB5B0FA7049BCDC1F4DB70161EF04A63669@pdsmsx402.ccr.corp.intel.com>
Xin, Xiaohui wrote:
> Yes, your patch works! I have tested it, the PAE guest and 32bit guest can be created now against CS 10470.:-)
>
I'm pretty sure this is the correct fix. This uncovered another bug
though that I'll let someone else hunt down. Xen appears to die quite
quickly if you attempt to do an xm destroy on a paused domain (or
perhaps on a domain that has never been started).
I'll submit as a [PATCH] tomorrow unless anyone finds additional problems.
Regards,
Anthony Liguori
> Thanks
> Xiaohui
>
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Anthony Liguori
> Sent: 2006年6月22日 5:49
> To: Nakajima, Jun
> Cc: Xen Developers; Rick Gonzalez
> Subject: Re: [Xen-devel] Daily Xen-HVM Build Testing: cs10470: broken
>
> Can ya'll try out the following patch? It seems to solve the problem
> for me.
>
> Have not run it through xm-test yet though.
>
> Regards,
>
> Anthony Liguori
>
> Nakajima, Jun wrote:
>
>> Yes, we are observing the same problem. Our team is saying it would work
>> if the changeset 10454 "Add support to Xend XML-RPC server for HTTP/1.1
>> Keep-Alive" is backed out.
>>
>> Looks like the newly created HVM guest is placed into the pause state.
>> If we do xm unpause, it starts running.
>>
>> Jun
>> ---
>> Intel Open Source Technology Center
>>
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Rick
>> Gonzalez
>> Sent: Wednesday, June 21, 2006 9:51 AM
>> To: Xen Developers
>> Subject: [Xen-devel] Daily Xen-HVM Build Testing: cs10470: broken
>>
>>
>> Hardware: x460
>>
>>
>> - 32bit and 64bit dom0 boots fine.
>> - 32bit and 64bit hvm guests do not boot at all. the get in a pause
>> state.
>> - dom0 crashes when I issue the following command "xm destroy <id>"
>> - no error messages are displayed with "xm dmesg" or "dmesg" on dom0.
>>
>> I need to hookup a console to get debug information.
>>
>> Investigation further.
>>
>>
>>
>> ------------------------
>> Rick Gonzalez
>> Linux Technology Center
>> IBM Corporation
>> Phone#: 512-838-0623
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
next prev parent reply other threads:[~2006-06-22 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 2:12 Daily Xen-HVM Build Testing: cs10470: broken Xin, Xiaohui
2006-06-22 2:28 ` Anthony Liguori [this message]
2006-06-22 17:55 ` Rick Gonzalez
-- strict thread matches above, loose matches on Subject: below --
2006-06-21 17:05 Nakajima, Jun
2006-06-21 18:28 ` Anthony Liguori
2006-06-21 21:48 ` Anthony Liguori
2006-06-21 16:50 Rick Gonzalez
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=449A0060.6080209@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=rcgneo@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiaohui.xin@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.