Marek Marczykowski-Górecki: > On Sun, Jun 26, 2016 at 05:07:44PM +0000, Andrew wrote: >> Keld Norman: >>> Started getting this today and lost my USB dedicated to my >>> Standalone vm: >>> >>> ERROR in output from running "dmesg" > can't claim BAR 0 [mem >>> 0xb4a20000-0xb4a2ffff 64bit]: address conflict with System >>> RAM >>> >>> Any one here have an idea of what could have caused that >>> problem ? >>> >>> I installed FruityWifi and plugged in some usb netcards, and >>> after booting the usb pci assignment to the VM failed.. >>> >>> GOOD BOOT: >>> >>> [ 1.823639] usb usb1: New USB device strings: Mfr=3, >>> Product=2, SerialNumber=1 [ 1.823643] usb usb1: Product: >>> Dummy host controller [ 1.823646] usb usb1: Manufacturer: >>> Linux 4.1.13-9.pvops.qubes.x86_64 dummy_hcd [ 1.823649] usb >>> usb1: SerialNumber: dummy_hcd.0 [ 1.823743] hub 1-0:1.0: USB >>> hub found [ 1.823763] hub 1-0:1.0: 1 port detected [ >>> 1.823788] systemd[1]: Starting udev Wait for Complete Device >>> Initialization... [ 1.824997] systemd[1]: Starting Create >>> Static Device Nodes in /dev... [ 1.825804] systemd[1]: >>> Starting Syslog Socket. [ 1.825880] systemd[1]: Listening on >>> Syslog Socket. [ 1.825922] systemd[1]: Starting Journal >>> Service... [ 1.826759] systemd[1]: Started Journal Service. >>> [ 1.846856] systemd-udevd[216]: starting version 215 [ >>> 1.879363] input: PC Speaker as >>> /devices/platform/pcspkr/input/input0 [ 1.882349] alg: No >>> test for crc32 (crc32-pclmul) [ 1.885658] Error: Driver >>> 'pcspkr' is already registered, aborting... [ 1.887460] >>> intel_rapl: Found RAPL domain package [ 1.887473] >>> intel_rapl: Found RAPL domain dram [ 1.891408] xen_netfront: >>> Initialising Xen virtual ethernet driver [ 1.910142] Adding >>> 1048572k swap on /dev/xvdc1. Priority:-1 extents:1 >>> across:1048572k SSFS [ 2.018426] EXT4-fs (dm-0): re-mounted. >>> Opts: (null) [ 4.873247] systemd-journald[207]: Received >>> request to flush runtime journal from PID 1 [ 5.064350] >>> nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ >>> 5.082180] EXT4-fs (xvdb): mounted filesystem with ordered data >>> mode. Opts: discard [ 5.096465] Bluetooth: Core ver 2.20 [ >>> 5.096490] NET: Registered protocol family 31 [ 5.096494] >>> Bluetooth: HCI device and connection manager initialized [ >>> 5.096502] Bluetooth: HCI socket layer initialized [ >>> 5.223404] Bluetooth: L2CAP socket layer initialized [ >>> 5.223413] Bluetooth: SCO socket layer initialized >>> >>> BAD BOOT: >>> >>> [ 2.019183] xen_netfront: Initialising Xen virtual ethernet >>> driver [ 2.021176] pcifront pci-0: claiming resource >>> 0000:00:00.0/0 [ 2.021186] pci 0000:00:00.0: can't claim BAR >>> 0 [mem 0xb4a20000-0xb4a2ffff 64bit]: address conflict with >>> System RAM [mem 0x00100000-0x1f9ffffff] [ 2.021195] pcifront >>> pci-0: Could not claim resource 0000:00:00.0/0! Device offline. >>> Try using e820_host=1 in the guest config. [ 2.021264] pci >>> 0000:00:00.0: can't enable device: BAR 0 [mem size 0x00010000 >>> 64bit] not assigned [ 2.021271] pci 0000:00:00.0: Can't >>> enable PCI device, BIOS handoff failed. [ 2.024076] >>> intel_rapl: Found RAPL domain package [ 2.024092] >>> intel_rapl: Found RAPL domain dram [ 2.024259] Error: Driver >>> 'pcspkr' is already registered, aborting... [ 2.025897] >>> Adding 1048572k swap on /dev/xvdc1. Priority:-1 extents:1 >>> across:1048572k SSFS [ 2.051371] EXT4-fs (dm-0): re-mounted. >>> Opts: (null) [ 2.100395] xhci_hcd 0000:00:00.0: can't enable >>> device: BAR 0 [mem size 0x00010000 64bit] not assigned >>> <------------------------------ HERE !! [ 5.153081] >>> systemd-journald[211]: Received request to flush runtime >>> journal from PID 1 [ 5.354463] nf_conntrack version 0.5.0 >>> (65536 buckets, 262144 max) [ 5.369902] EXT4-fs (xvdb): >>> mounted filesystem with ordered data mode. Opts: discard [ >>> 5.384349] Bluetooth: Core ver 2.20 [ 5.384372] NET: >>> Registered protocol family 31 [ 5.384376] Bluetooth: HCI >>> device and connection manager initialized [ 5.506630] >>> Bluetooth: HCI socket layer initialized [ 5.506633] >>> Bluetooth: L2CAP socket layer initialized [ 5.506641] >>> Bluetooth: SCO socket layer initialized >>> >>> Regards Keld >>> >>> >>> > >> Hey, > >> I encountered this problem, too. Turns out there's some sort of >> bug in Xen: >> http://lists.xen.org/archives/html/xen-devel/2014-04/msg02553.html. >> >> Basically, you might have problems assigning a PCI device to a regular >> PV AppVM if you assign more than 3G of memory to it. > >> Trimming the memory allocated to 3G solved this problem for me. > > Starting with Qubes 3.2, there is also possibility to enable > e820_host option mentioned in that error message. And actually it > is enabled by default for any VM with PCI device attached - so it > should just work. > >
Good to know. Thanks, Marek! Andrew -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/273a41ca-c989-78b1-4b1e-4def135c01bf%40riseup.net. For more options, visit https://groups.google.com/d/optout.
