From: Sander Eikelenboom <linux@eikelenboom.it>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [HVM} xen_platform_pci=0 doesn't prevent platform device creation and disk and nic take over by PV drivers.
Date: Wed, 9 Oct 2013 16:16:00 +0200 [thread overview]
Message-ID: <217061225.20131009161600@eikelenboom.it> (raw)
In-Reply-To: <1869834341.20131009135452@eikelenboom.it>
Hello Sander,
Wednesday, October 9, 2013, 1:54:52 PM, you wrote:
> Wednesday, October 9, 2013, 1:40:00 PM, you wrote:
>> On Wed, 9 Oct 2013, Sander Eikelenboom wrote:
>>> Hi,
>>>
>>> While trying to get to the bottom of my passthrough problem with the rom bar,
>>> i noticed that specifiying "xen_platform_pci=0" in the config file does not prevent
>>> the platform device to appear in my HVM guest and consequently the disk and nic are taken over.
>>>
>>> Running latest xen-unstable, together with upstream qemu and upstream seabios.
>> I think that xen_platform_pci has never been implemented with upstream
>> QEMU.
>> However you can pass xen_emul_unplug=never to Linux to avoid
>> initializing netfront and blkfront.
> Tried with xen_platform_pci=0 with qemu-xen-traditional and that makes a linux 3.12-rc3 kernel crash on boot
> unfortunatly the strack trace runs from the small vnc screen here :S
> screenshot of what is left attached
It also crashes on kernel 3.9.2 and 3.9.0-rc3, and 3.8.13
but not on the debian supplied 3.2.0 and 3.8.0-rc2.
So the cause seems to be introduced or backported to the 3.8 series somewhere.
> Pfrrt wat a mess
--
Best regards,
Sander mailto:linux@eikelenboom.it
prev parent reply other threads:[~2013-10-09 14:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1571692646.20131009000945@eikelenboom.it>
[not found] ` <1381320002.7600.10.camel@kazak.uk.xensource.com>
2013-10-09 12:15 ` Processed: Re: [HVM} xen_platform_pci=0 doesn't prevent platform device creation and disk and nic take over by PV drivers xen
2013-10-11 15:04 ` Ian Campbell
2013-10-11 15:22 ` Sander Eikelenboom
2013-10-11 16:53 ` Anthony PERARD
2013-10-11 17:10 ` George Dunlap
2013-10-11 17:31 ` Anthony PERARD
[not found] ` <1381505587.24708.59.camel@kazak.uk.xensource.com>
2013-10-11 15:45 ` Processed: " xen
2013-10-09 12:49 ` Sander Eikelenboom
2013-10-09 15:03 ` Stefano Stabellini
2013-10-09 16:56 ` Sander Eikelenboom
2013-10-09 15:32 ` George Dunlap
2013-10-09 17:39 ` Sander Eikelenboom
2013-10-10 10:03 ` George Dunlap
[not found] ` <alpine.DEB.2.02.1310091235150.26077@kaball.uk.xensource.com>
[not found] ` <1869834341.20131009135452@eikelenboom.it>
2013-10-09 14:16 ` Sander Eikelenboom [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=217061225.20131009161600@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@citrix.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.