All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen_emul_unplug on xen 4.1, HVM guest 2.6.38
Date: Wed, 26 Oct 2011 09:49:42 -0400	[thread overview]
Message-ID: <20111026134942.GB31609@phenom.dumpdata.com> (raw)
In-Reply-To: <0050AA2F452257584F0AAA0B@nimrod.local>

On Wed, Oct 26, 2011 at 02:17:25PM +0100, Alex Bligh wrote:
> I am running Xen 4 and want users to be able to install arbitrary HVM
> images. We want both PV and emulated drivers to appear. The reason
> for this is for compatibility with images that were prepared for
> Xen 3.3, which assume emulated devices exist at boot time (particularly
> for running the boot loader).
> 
> If I do not specify on the boot line xen_emul_unplug=never, then
> under some guest OS's (e.g. Ubuntu Natty (2.6.38)), the domU kernel
> unplugs the non-PV devices, which is undesirable in my application.
> 
> I cannot arbitrarily change the kernel command line because it is
> in effect set by the user's image.
> 
> Therefore what I need to do is prevent Xen4 offering the facility
> to unplug the devices in the first place. Setting "(unpluggable 0)"
> in the config for the emulated NICs and disks does not appear
> to prevent them getting unplugged; what may be happening is that
> domU tries to unplug them (but fails) but still doesn't use them.
> Is there a way to signal from dom0 that the kernel really shouldn't
> unplug this stuff.

xen_pci_platform=0 in your guest config should do it.

  reply	other threads:[~2011-10-26 13:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 13:17 xen_emul_unplug on xen 4.1, HVM guest 2.6.38 Alex Bligh
2011-10-26 13:49 ` Konrad Rzeszutek Wilk [this message]
2011-10-26 14:12   ` Pasi Kärkkäinen
2011-10-26 14:47     ` Alex Bligh
2011-10-26 14:56       ` Ian Campbell
2011-10-26 15:59         ` Pasi Kärkkäinen
2011-10-26 16:22           ` Ian Campbell
2011-10-26 16:25         ` Alex Bligh
2011-10-26 16:43           ` Ian Campbell
2011-10-27  8:02             ` Stefan Bader
2011-10-27 13:42               ` Stefano Stabellini
2011-10-27 13:45                 ` Stefan Bader
2011-10-27 14:08                   ` Stefano Stabellini
2011-10-27 14:13                     ` Stefan Bader
2011-10-27 14:25                       ` Stefano Stabellini
2011-10-27 14:46                         ` Stefan Bader
2011-10-27 13:48                 ` Stefan Bader
2011-10-27 14:09                   ` Stefano Stabellini
2011-10-26 15:54       ` Pasi Kärkkäinen
  -- strict thread matches above, loose matches on Subject: below --
2011-10-26 17:43 Alex Bligh
2011-10-27  9:27 ` Ian Campbell
2011-10-27 13:13   ` Konrad Rzeszutek Wilk
2011-10-27 13:27     ` Stefano Stabellini
2011-10-27 13:35     ` Ian Campbell
2011-10-27 13:18   ` Alex Bligh
2011-10-27 13:35     ` Stefano Stabellini

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=20111026134942.GB31609@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=alex@alex.org.uk \
    --cc=xen-devel@lists.xensource.com \
    /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.