From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xenproject.org
Subject: xend vs xl with pci=['<bdf'] wherein the '<bdf>' are not owned by pciback or pcistub will still launch.
Date: Mon, 6 Jan 2014 12:57:13 -0500 [thread overview]
Message-ID: <20140106175713.GB28636@phenom.dumpdata.com> (raw)
In Xend, if I had a pci entry in the guest config and the
PCI device was not assigned to xen-pciback or pci-stub it
would refuse to launch the guest.
Not so with 'xl'. It will complain but still launch:
-bash-4.1# cd drivers/pciback/
-bash-4.1# ls
0000:01:00.0 0000:03:08.1 0000:03:0a.0 0000:03:0b.1 irq_handlers new_slot remove_id uevent
0000:01:00.1 0000:03:09.0 0000:03:0a.1 bind module permissive remove_slot unbind
0000:03:08.0 0000:03:09.1 0000:03:0b.0 irq_handler_state new_id quirks slots
-bash-4.1# echo "0000:03:0b.0" > unbind
-bash-4.1# echo "0000:03:0b.1" > unbind
-bash-4.1# xl create /mnt/lab/security/security.cfg
Parsing config from /mnt/lab/security/security.cfg
libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:3:b.0 is not assignable
libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:3:b.1 is not assignable
-bash-4.1# xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 2047 4 r----- 14.7
security 1 1023 1 -b---- 8.0
-bash-4.1#
-bash-4.1# cat /mnt/lab/security/security.cfg |grep -v \#
device_model_version="qemu-xen-traditional"
builder="hvm"
memory = 1024
name = "security"
vcpus=1
vif = [ 'mac=00:0F:4B:00:00:84,bridge=switch' ]
disk = [ 'phy:/dev/sda,xvda,w' ]
pci= ['0000:03:08.0', '000:03:08.1', '0000:03:09.0', '0000:03:09.1', '0000:03:0a.0', '0000:03:0a.1', '0000:03:0b.0', '0000:03:0b.1']
vnc=1
vnclisten='0.0.0.0'
vncunused=1
serial="pty"
And naturally when shutting/destroying the guest it will say:
-bash-4.1# xl destroy 1
libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed: No such device
libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed: No such device
(XEN) [2014-01-06 17:54:39] deassign 0000:03:0b.0 from dom1 failed (-19)
(XEN) [2014-01-06 17:54:39] deassign 0000:03:0b.1 from dom1 failed (-19)
because it tries to de-allocate them even though they were not
part of the guest.
next reply other threads:[~2014-01-06 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 17:57 Konrad Rzeszutek Wilk [this message]
2014-01-07 11:22 ` xend vs xl with pci=['<bdf'] wherein the '<bdf>' are not owned by pciback or pcistub will still launch Ian Campbell
2014-01-07 11:30 ` Processed: " xen
2014-01-07 14:29 ` Konrad Rzeszutek Wilk
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=20140106175713.GB28636@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xenproject.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.