All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Xen Developers <xen-devel@lists.xensource.com>,
	Rick Gonzalez <rcgneo@us.ibm.com>
Subject: Re: Daily Xen-HVM Build Testing: cs10470: broken
Date: Wed, 21 Jun 2006 16:48:51 -0500	[thread overview]
Message-ID: <4499BEC3.9050703@us.ibm.com> (raw)
In-Reply-To: <8FFF7E42E93CC646B632AB40643802A83D6FEF@scsmsx412.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]

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
>   


[-- Attachment #2: xend-keep-alive-hvm.diff --]
[-- Type: text/plain, Size: 1435 bytes --]

# HG changeset patch
# User Anthony Liguori <anthony@codemonkey.ws>
# Node ID ddd4d7e3d79e8bf4999c820fdb5e003d31283d5f
# Parent  411a3c01bb40681731ad50fd3b8c5d7972baf36d
Make sure to explicitly close the connection if we're using HTTP/1.0.  This
shouldn't be needed but it appears to be necessary as the Python client
just does a wfile.read() instead of only reading the reported Content-Length.

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

diff -r 411a3c01bb40 -r ddd4d7e3d79e tools/python/xen/util/xmlrpclib2.py
--- a/tools/python/xen/util/xmlrpclib2.py	Tue Jun 20 18:51:46 2006 +0100
+++ b/tools/python/xen/util/xmlrpclib2.py	Wed Jun 21 16:47:48 2006 -0500
@@ -58,8 +58,6 @@ class XMLRPCRequestHandler(SimpleXMLRPCR
     #    propagate so that it shows up in the Xend debug logs
     # 2) we don't bother checking for a _dispatch function since we don't
     #    use one
-    # 3) we never shutdown the connection.  This appears to be a bug in
-    #    SimpleXMLRPCServer.py as it breaks HTTP Keep-Alive
     def do_POST(self):
         data = self.rfile.read(int(self.headers["content-length"]))
         rsp = self.server._marshaled_dispatch(data)
@@ -71,6 +69,8 @@ class XMLRPCRequestHandler(SimpleXMLRPCR
 
         self.wfile.write(rsp)
         self.wfile.flush()
+        if self.close_connection == 1:
+            self.connection.shutdown(1)
 
 class HTTPUnixConnection(HTTPConnection):
     def connect(self):

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2006-06-21 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 17:05 Daily Xen-HVM Build Testing: cs10470: broken Nakajima, Jun
2006-06-21 18:28 ` Anthony Liguori
2006-06-21 21:48 ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-22  2:12 Xin, Xiaohui
2006-06-22  2:28 ` Anthony Liguori
2006-06-22 17:55   ` Rick Gonzalez
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=4499BEC3.9050703@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=jun.nakajima@intel.com \
    --cc=rcgneo@us.ibm.com \
    --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.