Mailinglist Archive: opensuse-bugs (4251 mails)

< Previous Next >
[Bug 1037985] New: XEN_DOMCTL_assign_device: ... failed (-12)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 08 May 2017 09:53:52 +0000
  • Message-id: <bug-1037985-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1037985


Bug ID: 1037985
Summary: XEN_DOMCTL_assign_device: ... failed (-12)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xen
Assignee: xen-bugs@xxxxxxx
Reporter: jrc@xxxxxxxxxxxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

Created attachment 724109
--> http://bugzilla.opensuse.org/attachment.cgi?id=724109&action=edit
Output of "xl dmesg"

As reported to the Xen-users mailing list:
https://lists.xenproject.org/archives/html/xen-users/2017-05/msg00005.html
----------------------------------------------------------------------
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)

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?
----------------------------------------------------------------------
https://lists.xenproject.org/archives/html/xen-users/2017-05/msg00006.html
----------------------------------------------------------------------
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
----------------------------------------------------------------------
https://lists.xenproject.org/archives/html/xen-users/2017-05/msg00007.html
----------------------------------------------------------------------
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
----------------------------------------------------------------------

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
Follow Ups