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

[Xen-devel] HVM driver domains do not appear to be usable with stubdomains

  • To: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Chris Brannon <cmb@xxxxxxxxx>
  • Date: Tue, 04 Dec 2018 10:10:54 -0800
  • Delivery-date: Tue, 04 Dec 2018 18:11:07 +0000
  • Dkim-filter: OpenDKIM Filter v2.11.0 mail.prgmr.com F34F628C00E
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

I set up a network driver domain for a dom0; it uses HVM
virtualization.  It worked very well when not using a device model
stubdomain, but when I requested the use of a device model stubdomain in
my xl.cfg file, the domU refused to boot.  It gave the following error

[76594.195404] xen_pciback: vpci: 0000:05:00.0: assign to virtual slot 0
[76594.195927] pciback 0000:05:00.0: registering for 35
[76594.230592] xen-pciback pci-34-0: 22 Couldn't locate PCI device
    (0000:05:00.0)! perhaps already in-use?

It seems to me that Xen is trying to pass the PCI device to both the
domU and the stubdomain, and that is why it is failing.  Has anyone
managed to get an HVM driver domain running with a stubdomain?  If so,
how did you do it?  Or is it expected that HVM driver domains won't work
with stubdomains?

-- Chris

Xen-devel mailing list



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