All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: Correct format for HVM graphics
Date: Fri, 20 Apr 2012 12:28:03 -0400	[thread overview]
Message-ID: <20120420162803.GA31062@phenom.dumpdata.com> (raw)
In-Reply-To: <4F7C63EE.6000703@canonical.com>

On Wed, Apr 04, 2012 at 05:08:30PM +0200, Stefan Bader wrote:
> Hi Stefano,
> 
> quite a while back in time, you and Konrad had a discussion about some HVM setup
> problems via libvirt. One part was graphics and the problem seemed to be that
> when creating a new instance through xend for HVM, the use of vfb was wrong. It
> mostly does work but then also defines a vkbd which takes a long time in the
> xenbus setup to finally fail.

So, this patch http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=3066616ce23aad5719c23a0f21f32676402cb44b
fixes it in the kernel (and I remembered this time to stick stable@kernel.org on it).

It should eleviate some of the pains by making the timeout only 30 seconds when
vkbd is used, instead of the lengthy 6 minutes.

> 
> Because this was not a really fatal problem it did take a long time to actually
> get back to it. But now I had a look and found that libvirt indeed does use the
> vfb form for both the xen-xm and xen-sxpr formats (the latter being used to
> create guests). The decision is made based on the xend version number in the HVM
> case. Which would be wrong if I did understand your reply correctly.
> 
> I have been testing a patch to libvirt, which would not use a vfb definition
> whenever HVM is used (regardless of xend version). And it does seem to work (xm
> list -l however has a vfb device definition, but the same happens when creating
> the instance with a xm style config file that definitely has no vfb section in
> it). But I am testing based on our 12.04 release which uses Xen 4.1.2. So I want
> to make sure the solution for libvirt is correct for even the current Xen version.
> 
> So in short, is this always correct?
> 
> if (HVM or (PVM when xend is from xen < 3.0.4 / xend version < 3))
>    do not define a vfb device
> else /* PVM and xend version >= 3 */
>    define a vfb device
> 
> Thanks,
> Stefan
> 

      parent reply	other threads:[~2012-04-20 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 15:08 Correct format for HVM graphics Stefan Bader
2012-04-05 11:02 ` Stefano Stabellini
2012-04-05 12:51   ` Konrad Rzeszutek Wilk
2012-04-05 12:56   ` Stefan Bader
2012-04-05 14:26     ` Stefano Stabellini
2012-04-05 15:15       ` Stefan Bader
2012-04-05 15:29         ` Stefano Stabellini
2012-04-05 15:35           ` Stefan Bader
2012-04-20 16:28 ` Konrad Rzeszutek Wilk [this message]

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=20120420162803.GA31062@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=stefan.bader@canonical.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.