[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] XEN_DOMCTL_assign_device: ... failed (-12)
On 02/05/17 17:35, George Dunlap wrote: > On Tue, May 2, 2017 at 4:11 PM, John Connett <jrc@xxxxxxxxxxxxxxxxxx> wrote: >> 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 >> 0000:03:00.0 >> # >> >> 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) > > When reporting a bug, please always at least include the output of "xl > dmesg" and "dmesg" (or /var/log/messages, or whatever). > > Error -12 is "Not enough memory" (or "Couldn't allocate memory"); it > would be good to know what might have gone into that. > > Thanks, > -George > I kept the original message brief in case it wasn't a bug but my mistake. Output of "xl dmesg" and "dmesg" attached. Please let me know if you need any further information. Many thanks -- John Attachment:
xl-dmesg Attachment:
dmesg Attachment:
signature.asc _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx https://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |