Hello, I can confirm that this bug with VM Manager is still lurking somewhere. I've been using Qubes 3.1 for few days now and suddenly after booting the sys-net won't start (Error starting VM 'sys-net': PCI device 08:00.0 does not exist (domain sys-net)). Funny thing, I even don't have a PCI device with that address..
In Qubes VM Manager in Devices tab theres 00:19.0 (Intel network adapter) attached, but no 08:00.0. But when listing attached devices with qvm-pci -l sys-net it shows ['00:19.0' , '08:00.0'] Then qvm-pci -d sys-net 08:00.0 resolves the situation. So at least theres still the bug that VM Manager does not list attached (but non-existing) devices, and that is now preventing from starting VMs I don't know what caused this. Only thing that can come to mind is that I've tried the PCI passthrough reset relaxation for USB VM (explained here https://www.qubes-os.org/doc/assigning-devices/ ), but that would not work, so I looked at the Xen pages and their example lists command echo 0000:08:00.0 > /sys/bus/pci/drivers/pciback/permissive instead of echo 0000:04:00.0 > /sys/bus/pci/drivers/pciback/permissive So I modified the qubes-pre-netvm.service accordingly. At first I thought these were some kind of general configuration flags for setting permissive mode, but then I realised these are actually just example PCI addresses and have to be changed to reflect the address of the actual USB controller! :) However at this point I've already tried setting the pci_strictreset false with qvm-prefs and that worked, so I forgot about the pre-netvm service until this happened. Interestingly, just disabling the problem causing service would not be enough to resolve the situation, but I had to use qvm-pci manually (only once) to remove the attachment. So somehow these settings survive the restart..? On Sunday, December 7, 2014 at 5:49:07 AM UTC+2, Eric Smith wrote: > > Yeah, I am wondering what this means. I can start appvms but can't start > any that depend on netvm. > Then, to get more info, I tried a qubes-dom0-update in Konsole. This > time, it told me that: > "/usr/lib/qubes/unbind-pci-device.sh: line 47: echo: write error: No such > device" > So I looked at the code and appearent it didn't like what was in the $BIND > variable and appearently > could not find the driver whose name was stored in the $BIND variable > appearently. > This problem started after I had to turn off the computer manually because > it froze. > I rebooted about 4 times but the problem persists. I can start the usbvm > because it's a Standalone > vm and does not depend on netvm, but not the others. I wonder how I could > fix this. > > -- 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/b5efb10a-07db-4a23-bd5e-e28cf5901e9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
