Quantcast

XEN_DOMCTL_assign_device: ... failed (-12)

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

XEN_DOMCTL_assign_device: ... failed (-12)

John Connett
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?


_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xen.org/xen-users

signature.asc (321 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: XEN_DOMCTL_assign_device: ... failed (-12)

George Dunlap-5
On Tue, May 2, 2017 at 4:11 PM, John Connett <[hidden email]> 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

_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: XEN_DOMCTL_assign_device: ... failed (-12)

John Connett
On 02/05/17 17:35, George Dunlap wrote:

> On Tue, May 2, 2017 at 4:11 PM, John Connett <[hidden email]> 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

_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xen.org/xen-users

xl-dmesg (28K) Download Attachment
dmesg (101K) Download Attachment
signature.asc (321 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: XEN_DOMCTL_assign_device: ... failed (-12)

John Connett
On 02/05/17 23:21, John Connett wrote:

> [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]
>
> On 02/05/17 17:35, George Dunlap wrote:
>> On Tue, May 2, 2017 at 4:11 PM, John Connett <[hidden email]> 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
Logged as a bug against openSUSE Tumbleweed:
https://bugzilla.opensuse.org/show_bug.cgi?id=1037985


_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xen.org/xen-users

signature.asc (321 bytes) Download Attachment
Loading...