[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [XCP] Console with PV kernels?

  • To: admin@xxxxxxxxxxx
  • From: Todd Deshane <todd.deshane@xxxxxxx>
  • Date: Fri, 24 Jun 2011 01:34:53 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Derrik Pates <demon@xxxxxx>
  • Delivery-date: Thu, 23 Jun 2011 22:35:59 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=Bjj/0zkyZZzFXosDfnZVN5TWiV4NkmaZsrVPDtclO3ZieuqTHbW4gslSKwmd32MJ0Z Bmm+xeWZUfQg9phkShDtf14zMf4ZpmYBw9Q7TOEzokfhuNcG3JlCzsjbVlonxTqMIbTV oWGDDBftX2jPnMuzjJqv1/479+lPNI/2HbnR0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> On 24 June 2011 00:15, Derrik Pates <demon@xxxxxx> wrote:
>> All:
>> I'm currently using the older Python-based Xen tools on a cluster of
>> machines, but we're looking to transition to XCP as the platform of choice
>> for our applications. However, I've run into one issue that's sort of a
>> blocker: paravirtual Linux domUs boot and run, but the console device is
>> strangely broken. Most of the output reaches the connected user (some bytes
>> are dropped), but any input is apparently completely lost. The VMs in
>> question work perfectly with the older Xen environment, and as I mentioned,
>> everything else seems to work identically. Is there something I need to do
>> with XCP (we're currently testing with a mix of 0.5 and 1.0, we'll be moving
>> totally to 1.0 in the near future, and this happens with both) to make this
>> work right? A change in the domUs? We're just using 'console=xvc0' or
>> 'console=hvc0' as appropriate, and running a normal getty against the
>> console device. Any suggestions would be appreciated, thanks.

On Thu, Jun 23, 2011 at 7:27 PM, David Markey <admin@xxxxxxxxxxx> wrote:
> Kill all vncterm processes.

This is actually documented here:


Todd Deshane

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.