This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Making snapshot of logical volumes handling HVM domU cau

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Making snapshot of logical volumes handling HVM domU causes OOPS and instability
From: Scott Garron <xen-devel@xxxxxxxxxxxxxxxxxx>
Date: Mon, 30 Aug 2010 14:18:08 -0400
Delivery-date: Mon, 30 Aug 2010 11:19:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C7BE1C6.5030602@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C7864BB.1010808@xxxxxxxxxxxxxxxxxx> <4C7BE1C6.5030602@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100515 Icedove/3.0.4
On 08/30/2010 12:52 PM, Jeremy Fitzhardinge wrote:
Something is causing udevd to end up with bad pagetables which are
causing a kernel crash on exit.  I'm not sure if its *the* udevd or
some transient child, but either way its bad.

     If it's any help, the version of udev on the machine in question is
160.  (udev_160-1_amd64.deb)  I've now added that info in the text file
that describes my system, referenced in my original post by this URL:

I think this issue [unresponsive network interfaces] also causes xm
console to not allow you to type on the console
Hm, not familiar with this problem.  Perhaps its just something wrong
with your console settings for the domain?  Do you have "console=" on
the kernel command line?

     I have "extra = "console=hvc0"" in the domU configuration files.
The keyboard input works just fine for some time.  It ceased accepting
input at around the same time that the network interfaces stopped
responding, but that could have just been coincidental.

     I wasn't paying full attention, so this may also have been related
to me attaching to the console twice (Running xm console on one ssh
session to the dom0 in addition to running xm console from another SSH
session to the dom0).  When I couldn't connect directly to the domU via
SSH on its network interface, I tried to attach to its console to do
troubleshooting.  I may have already been attached to its console from
another SSH session to the dom0 and I suppose that might cause a
conflict.   ...  which begs the question:  "Is this the desired/expected
behavior in this scenario?"

Scott Garron

Xen-devel mailing list