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

[Xen-users] XEN_DOMCTL_assign_device: ... failed (-12)

  • To: <xen-users@xxxxxxxxxxxxx>
  • From: John Connett <jrc@xxxxxxxxxxxxxxxxxx>
  • Date: Tue, 2 May 2017 16:11:21 +0100
  • Delivery-date: Tue, 02 May 2017 15:12:57 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

I'm trying to test OPNsense 17.1 (based on FreeBSD 11) in a Xen x86_64
domU with dom0 openSUSE Tumbleweed / xen-4.8.0. Installation and update
went smoothly and I can access the console and web interface.

My plan is to have the WAN bridged to dom0 and the LAN to use PCI pass
through to an old Ralink corp. RT2500 Wireless 802.11bg (rev 01). It is
in the PCI assignable list:

# lspci | fgrep Ralink
03:00.0 Network controller: Ralink corp. RT2500 Wireless 802.11bg (rev 01)
# xl pci-assignable-list

However, when I use Add Hardware to add the PCI Host Device the VM then
fails to start:

# cat /var/log/xen/qemu-dm-opnsense.log
char device redirected to /dev/pts/8 (label serial0)
qemi-system-i386: terminating on signal 1 from pid 2868 (/usr/sbin/libvirtd)

There is also a console message:

XEN_DOMCTL_assign_device: assign 000:3:00.0 to dom4 failed (-12)

I'm using "loglvl=all guest_loglvl=all com1=115200,8n1,0x3f8,4
console=com1,vga lapic=debug apic_verbosity=debug apic=debug
iommu=verbose" in the grub command line. Is there anything else I can
add to gain more information?

Anything else I can try?

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-users mailing list



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