qun
May 18, 2023, 1:16pm
#1
Hey!
I try to run QubesOS on Tuxedo BU1506. As it seems it runs on Clevo N250BU.
I installed it with enabled UEFI and it worked well.
If I try to start sys-firewall, I get:
internal error: Unable to reset PCI device 0000:03:00:1: internal error: Active 0000:03:00:0 devices on bus with 0000:03:00:1, not doing bus reset, see /var/log/libvirt/libxl/libxl-driver.log for details
As it seems, there’s a similar issue here:
opened 09:55PM - 08 Nov 15 UTC
help wanted
C: kernel
C: doc
C: Xen
T: task
P: default
[Reported by troubadour in Whonix forum.](https://www.whonix.org/forum/index.php… /topic,1914.msg11397.html#msg11397)
> With Qubes-R3.0-x86_64-DVD.iso.
>
> The output of qubes-dom0-update:
>
> ```
> Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
> Running command on VM: 'sys-firewall'...
> Starting the VM 'sys-firewall'...
> --> Starting NetVM sys-net...
> --> Creating volatile image: /var/lib/qubes/servicevms/sys-net/volatile.img...
> --> Loading the VM (type = NetVM)...
> Traceback (most recent call last):
> File "/bin/qvm-run", line 199, in <module>
> main()
> File "/bin/qvm-run", line 194, in main
> r = vm_run_cmd(vm, cmdstr, options)
> File "/bin/qvm-run", line 64, in vm_run_cmd
> gui = options.gui, filter_esc = options.filter_esc)
> File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1529, in run
> self.start(verbose=verbose, start_guid = gui, notify_function=notify_function)
> File "/usr/lib64/python2.7/site-packages/qubes/modules/006QubesProxyVm.py", line 82, in start
> retcode = super(QubesProxyVm, self).start(**kwargs)
> File "/usr/lib64/python2.7/site-packages/qubes/modules/005QubesNetVm.py", line 121, in start
> xid=super(QubesNetVm, self).start(**kwargs)
> File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1733, in start
> self.netvm.start(verbose = verbose, start_guid = start_guid, notify_function = notify_function)
> File "/usr/lib64/python2.7/site-packages/qubes/modules/005QubesNetVm.py", line 121, in start
> xid=super(QubesNetVm, self).start(**kwargs)
> File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1773, in start
> self.libvirt_domain.createWithFlags(libvirt.VIR_DOMAIN_START_PAUSED)
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1037, in createWithFlags
> if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
> libvirt.libvirtError: internal error: Unable to reset PCI device 0000:05:00.2: internal error: Active 0000:05:00.0 devices on bus with 0000:05:00.2, not doing bus reset
> ```
>
> This error shows also in a narrow window after installing the service vm's at first boot.
>
> May be anecdotal, may be not, during installation the mouse is not responding (it does work with Qubes R2).
under 03:00.0 I could find a unsigned controller, which has something to do with network. I’m not sure, but I think it’s UMTS module.
So I made this in dom0:
sudo su
echo -n "1" > /sys/bus/pci/devices/0000\:03\:00.0/remove
and sys-firewall works well with sys-net.
For I already done the mentioned above, I can not look, what kind of device it was exactly (but also some kind of Realtek Express Card). But I think after the reboot, it will be there again.
So is this the only workaround up 2015?
To write this in /etc/systemd/system/qubes-pre-netvm.service
:
[Unit]
Description=Netvm fixup
Before=qubes-netvm.service
[Service]
ExecStart=/bin/sh -c 'echo -n "1" > /sys/bus/pci/devices/0000:03:00.0/remove`'
Type=oneshot
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Best regards
qun
#Edit1:
it’s unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) under 03:00.0
#Edit2:
the workaround above doesn’t work after reboot.
Did you check that this device is not attached to multiple VMs?
This issue is likely to occur if you have the same device assigned to more than one VM.
PCI troubleshooting | Qubes OS