From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sander Eikelenboom 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 Message-ID: <217061225.20131009161600@eikelenboom.it> References: <1571692646.20131009000945@eikelenboom.it> <1869834341.20131009135452@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1869834341.20131009135452@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-devel@lists.xen.org" Cc: Anthony Perard , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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