From mboxrd@z Thu Jan  1 00:00:00 1970
From: "J. Roeleveld" <joost@antarean.org>
Subject: Re: Making snapshot of logical volumes handling HVM domU
	causes OOPS and instability
Date: Sun, 12 Sep 2010 11:33:23 +0200
Message-ID: <201009121133.23613.joost@antarean.org>
References: <4C7864BB.1010808@sce.pridelands.org> <4C7BE1C6.5030602@goop.org>
	<4C7BF5E0.20305@sce.pridelands.org>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4C7BF5E0.20305@sce.pridelands.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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.

--
Joost