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: "J. Roeleveld" <joost@xxxxxxxxxxxx>
Date: Sun, 12 Sep 2010 11:33:23 +0200
Delivery-date: Sun, 12 Sep 2010 02:34:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C7BF5E0.20305@xxxxxxxxxxxxxxxxxx>
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> <4C7BF5E0.20305@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.5 (Linux/2.6.30-gentoo-r5; KDE/4.4.5; x86_64; ; )
Hi All,

Thought I'd chip in with some info from what I experienced/noticed on my 
system. (Not seen the instability described though).
I hope these help with isolating the OPs issue.

On Monday 30 August 2010 20:18:08 Scott Garron wrote:
> On 08/30/2010 12:52 PM, Jeremy Fitzhardinge wrote:

<snipped udev>

> >> 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?"

I noticed this behaviour already in older Xen-versions:
1) " xm console x "
2) (in a different shell-session) : " xm console x "

Observed situation: input and output for the xenconsole session is "weird" in 
that commands entered and results returning are not showing where I expect it.

I believe this is " expected " behaviour.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] Making snapshot of logical volumes handling HVM domU causes OOPS and instability, J. Roeleveld <=