Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Tuesday, September 4, 2018 at 8:24:56 AM UTC-4, unman wrote: > On Mon, Sep 03, 2018 at 08:06:01AM -0700, Patrick wrote: > > On Monday, September 3, 2018 at 10:31:50 AM UTC-4, unman wrote: > > > On Sun, Sep 02, 2018 at 03:56:46PM -0700, Patrick wrote: > > > > On Sunday, September 2, 2018 at 3:34:34 PM UTC-4, Jean-Philippe Ouellet > > > > wrote: > > > > > On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin > > > > > wrote: > > > > > > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin > > > > > > wrote: > > > > > >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: > > > > > >> PCI device :02:00.0 is in use by driver xenlight, domain > > > > > >> sys-usb > > > > > >> > > > > > >> I don't know how to copy the log folder over and qubes doesn't > > > > > >> have the wireless network, which I believe is related, but I've > > > > > >> attached a picture of the log. > > > > > >> > > > > > >> This is a new Qubes install on a new Acer laptop Aspire > > > > > >> A515-51-86AQ > > > > > >> Booting in legacy mode. > > > > > >> > > > > > >> I can get into the main desktop and get to Dom0 terminal, but > > > > > >> can't launch any of the default domains. > > > > > >> > > > > > >> There is another thread on here with the same error. He ran: > > > > > >> $ qvm-pci attach --persistent --option permissive=true --option > > > > > >> no-strict-reset=true sys-net dom0:00_XXX > > > > > >> > > > > > >> And it worked for him, but doesn't work for me, the response I get > > > > > >> is "error : backend vm "dom0" doesn't expose device "00.XXX" > > > > > > > > > > The "XXX" in the PCI device should be filled in with your actual PCI > > > > > device. > > > > > > > > > > >> So I wonder what "xenlight" is and it won't release what pci > > > > > >> device? > > > > > > > > > > Just a library for interfacing with Xen. Unlikely to be the actual > > > > > problem. > > > > > > > > > > >> Suggestions? > > > > > >> > > > > > >> Thanks, > > > > > >> Patrick > > > > > > > > > > > > Pics attached here. > > > > > > > > > > It would be the first time I've seen this, but it might perhaps be > > > > > conceivable that changing BIOS settings caused your device to show up > > > > > with a different BDF (essentially "PCI address") than when Qubes was > > > > > installed? Use `lspci` in dom0 to enumerate them. > > > > > > > > > > An easier way than doing this via the command line is to use the > > > > > Devices tab of the Qubes VM Settings GUI - remove all devices then add > > > > > the one which looks like your network device. You can also configure > > > > > no-strict-reset via the button at the bottom of the GUI, which is > > > > > sometimes necessary. > > > > > > > > Thanks, I went to the work vm for example, and all of the devices were > > > > on the left side, nothing on the right, then I selected the wifi device > > > > and the response was "you've enabled dynamic memory balancing, some > > > > devices might not work!" > > > > > > > > and, it won't let me apply that change, saying "Can't attach pci device > > > > to a VM in pvh mode" > > > > > > > > Then I tried to issue your suggestion "$ qvm-pci attach --persistent > > > > --option permissive=true --option no-strict-reset=true sys-net > > > > dom02:00.0"which is my wireless device and the error response "no > > > > backend vm '02'" > > > > > > > > > > > > I'm wondering if this is the right way to go or maybe just try a > > > > different installation route? > > > > > > > > Thanks, > > > > Patrick > > > > > > > > > > There's a typo in your command: > > > you have dom02:00.0 and the command should be dom0:02 > > > > > > The two messages you received can be fixed in the Qube settings window. > > > You can change the VM mode on the Advanced pane - select HVM. > > > There's a checkbox for memory balancing on the same pane , if that's > > > needed. I habitually turn this off and set the memory/maxmem settings > > > low. ymmv > > > > Thanks, I'm feeling outgunned on this one. I really have no idea about what > > is truly going on - what's the root cause issue and why? What device is not > > resetting and why that matters, etc. etc. > > > > Just to be clear. While I'm able to get into the Qubes desktop, and can get > > to dom0 terminal, none of the pre-configured VMs are coming up. If I simply > > do a start from the Dom0 qubes manager, on any VM, the same error comes up: > > > > "Unable to reset PCI device :01:00.1: Internal error: active > > :01:00.0 devices on bus with :01:00.1 not doing bus reset." > > > > The log says: > > "unable to release device /dev/loop0: No such device or address" > > > > I have tried all your suggestions (HVM/mem checkbox/low mem), no change in > > result. > > > > Based on this, what is going on in the first place? I feel if I can > > understand the root of it I stand a chance in solving. > > > > Thanks, > > > > Patrick > > > > I'm as confused as you - the device
Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Tue, Sep 4, 2018 at 9:17 PM, Patrick wrote: > On Sunday, September 2, 2018 at 3:34:34 PM UTC-4, Jean-Philippe Ouellet wrote: >> On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin >> wrote: >> > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin wrote: >> >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: PCI >> >> device :02:00.0 is in use by driver xenlight, domain sys-usb >> >> >> >> I don't know how to copy the log folder over and qubes doesn't have the >> >> wireless network, which I believe is related, but I've attached a picture >> >> of the log. >> >> >> >> This is a new Qubes install on a new Acer laptop Aspire A515-51-86AQ >> >> Booting in legacy mode. >> >> >> >> I can get into the main desktop and get to Dom0 terminal, but can't >> >> launch any of the default domains. >> >> >> >> There is another thread on here with the same error. He ran: >> >> $ qvm-pci attach --persistent --option permissive=true --option >> >> no-strict-reset=true sys-net dom0:00_XXX >> >> >> >> And it worked for him, but doesn't work for me, the response I get is >> >> "error : backend vm "dom0" doesn't expose device "00.XXX" >> >> The "XXX" in the PCI device should be filled in with your actual PCI device. >> >> >> So I wonder what "xenlight" is and it won't release what pci device? >> >> Just a library for interfacing with Xen. Unlikely to be the actual problem. >> >> >> Suggestions? >> >> >> >> Thanks, >> >> Patrick >> > >> > Pics attached here. >> >> It would be the first time I've seen this, but it might perhaps be >> conceivable that changing BIOS settings caused your device to show up >> with a different BDF (essentially "PCI address") than when Qubes was >> installed? Use `lspci` in dom0 to enumerate them. >> >> An easier way than doing this via the command line is to use the >> Devices tab of the Qubes VM Settings GUI - remove all devices then add >> the one which looks like your network device. You can also configure >> no-strict-reset via the button at the bottom of the GUI, which is >> sometimes necessary. > > Wow you really know this stuff. Thanks to your advice I was able to piece it > together. I confirmed as you said, then was able to start booting the VMs > based on using PVM and removing all the device elements. I'm sure I've got a > lot of experimenting to go but the basics are there with wireless. > > Thanks so much, > Patrick Glad it was helpful! Also, in case you weren't already aware, VMs to which you wish to assign PCI devices currently need to be in HVM mode (meaning: assisted by a Qemu stub-domain for device-model emulation). This requirement should be removed in the future, but there are Xen issues to work out before we can fully ditch it and switch to PVH everywhere (meaning: without Qemu and its associated attack surface and per-VM CPU/memory overhead). To check the virtualization mode: [user@dom0 ~]$ qvm-prefs sys-net virt_mode hvm To reset the mode to default (which should automatically be HVM for VMs with PCI devices and PVH otherwise): [user@dom0 ~]$ qvm-prefs -D sys-net virt_mode If you need to explicitly set the mode, you can do so (possibly replacing "hvm" with "pvh" or the very-deprecated "pv"): [user@dom0 ~]$ qvm-prefs sys-net virt_mode hvm Cheers, Jean-Philippe -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABQWM_BbW%2BSHLOOhEZ%3DpOB0yEcJj_cSpARSSZW_%2BrBQfKBfwpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Sunday, September 2, 2018 at 3:34:34 PM UTC-4, Jean-Philippe Ouellet wrote: > On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin > wrote: > > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin wrote: > >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: PCI > >> device :02:00.0 is in use by driver xenlight, domain sys-usb > >> > >> I don't know how to copy the log folder over and qubes doesn't have the > >> wireless network, which I believe is related, but I've attached a picture > >> of the log. > >> > >> This is a new Qubes install on a new Acer laptop Aspire A515-51-86AQ > >> Booting in legacy mode. > >> > >> I can get into the main desktop and get to Dom0 terminal, but can't launch > >> any of the default domains. > >> > >> There is another thread on here with the same error. He ran: > >> $ qvm-pci attach --persistent --option permissive=true --option > >> no-strict-reset=true sys-net dom0:00_XXX > >> > >> And it worked for him, but doesn't work for me, the response I get is > >> "error : backend vm "dom0" doesn't expose device "00.XXX" > > The "XXX" in the PCI device should be filled in with your actual PCI device. > > >> So I wonder what "xenlight" is and it won't release what pci device? > > Just a library for interfacing with Xen. Unlikely to be the actual problem. > > >> Suggestions? > >> > >> Thanks, > >> Patrick > > > > Pics attached here. > > It would be the first time I've seen this, but it might perhaps be > conceivable that changing BIOS settings caused your device to show up > with a different BDF (essentially "PCI address") than when Qubes was > installed? Use `lspci` in dom0 to enumerate them. > > An easier way than doing this via the command line is to use the > Devices tab of the Qubes VM Settings GUI - remove all devices then add > the one which looks like your network device. You can also configure > no-strict-reset via the button at the bottom of the GUI, which is > sometimes necessary. Wow you really know this stuff. Thanks to your advice I was able to piece it together. I confirmed as you said, then was able to start booting the VMs based on using PVM and removing all the device elements. I'm sure I've got a lot of experimenting to go but the basics are there with wireless. Thanks so much, Patrick -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/685cdfd7-bbb0-452f-ba5b-380e951157aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Mon, Sep 03, 2018 at 08:06:01AM -0700, Patrick wrote: > On Monday, September 3, 2018 at 10:31:50 AM UTC-4, unman wrote: > > On Sun, Sep 02, 2018 at 03:56:46PM -0700, Patrick wrote: > > > On Sunday, September 2, 2018 at 3:34:34 PM UTC-4, Jean-Philippe Ouellet > > > wrote: > > > > On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin > > > > wrote: > > > > > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin > > > > > wrote: > > > > >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: > > > > >> PCI device :02:00.0 is in use by driver xenlight, domain sys-usb > > > > >> > > > > >> I don't know how to copy the log folder over and qubes doesn't have > > > > >> the wireless network, which I believe is related, but I've attached > > > > >> a picture of the log. > > > > >> > > > > >> This is a new Qubes install on a new Acer laptop Aspire A515-51-86AQ > > > > >> Booting in legacy mode. > > > > >> > > > > >> I can get into the main desktop and get to Dom0 terminal, but can't > > > > >> launch any of the default domains. > > > > >> > > > > >> There is another thread on here with the same error. He ran: > > > > >> $ qvm-pci attach --persistent --option permissive=true --option > > > > >> no-strict-reset=true sys-net dom0:00_XXX > > > > >> > > > > >> And it worked for him, but doesn't work for me, the response I get > > > > >> is "error : backend vm "dom0" doesn't expose device "00.XXX" > > > > > > > > The "XXX" in the PCI device should be filled in with your actual PCI > > > > device. > > > > > > > > >> So I wonder what "xenlight" is and it won't release what pci device? > > > > > > > > Just a library for interfacing with Xen. Unlikely to be the actual > > > > problem. > > > > > > > > >> Suggestions? > > > > >> > > > > >> Thanks, > > > > >> Patrick > > > > > > > > > > Pics attached here. > > > > > > > > It would be the first time I've seen this, but it might perhaps be > > > > conceivable that changing BIOS settings caused your device to show up > > > > with a different BDF (essentially "PCI address") than when Qubes was > > > > installed? Use `lspci` in dom0 to enumerate them. > > > > > > > > An easier way than doing this via the command line is to use the > > > > Devices tab of the Qubes VM Settings GUI - remove all devices then add > > > > the one which looks like your network device. You can also configure > > > > no-strict-reset via the button at the bottom of the GUI, which is > > > > sometimes necessary. > > > > > > Thanks, I went to the work vm for example, and all of the devices were on > > > the left side, nothing on the right, then I selected the wifi device and > > > the response was "you've enabled dynamic memory balancing, some devices > > > might not work!" > > > > > > and, it won't let me apply that change, saying "Can't attach pci device > > > to a VM in pvh mode" > > > > > > Then I tried to issue your suggestion "$ qvm-pci attach --persistent > > > --option permissive=true --option no-strict-reset=true sys-net > > > dom02:00.0"which is my wireless device and the error response "no > > > backend vm '02'" > > > > > > > > > I'm wondering if this is the right way to go or maybe just try a > > > different installation route? > > > > > > Thanks, > > > Patrick > > > > > > > There's a typo in your command: > > you have dom02:00.0 and the command should be dom0:02 > > > > The two messages you received can be fixed in the Qube settings window. > > You can change the VM mode on the Advanced pane - select HVM. > > There's a checkbox for memory balancing on the same pane , if that's > > needed. I habitually turn this off and set the memory/maxmem settings > > low. ymmv > > Thanks, I'm feeling outgunned on this one. I really have no idea about what > is truly going on - what's the root cause issue and why? What device is not > resetting and why that matters, etc. etc. > > Just to be clear. While I'm able to get into the Qubes desktop, and can get > to dom0 terminal, none of the pre-configured VMs are coming up. If I simply > do a start from the Dom0 qubes manager, on any VM, the same error comes up: > > "Unable to reset PCI device :01:00.1: Internal error: active :01:00.0 > devices on bus with :01:00.1 not doing bus reset." > > The log says: > "unable to release device /dev/loop0: No such device or address" > > I have tried all your suggestions (HVM/mem checkbox/low mem), no change in > result. > > Based on this, what is going on in the first place? I feel if I can > understand the root of it I stand a chance in solving. > > Thanks, > > Patrick > I'm as confused as you - the device you are referencing now is not the one you were concerned with earlier. Are you trying something new? Also, I don't understand why you were trying to attach a device to "work" Almost certainly the problem is with starting sys-net. That's why your qubes wont start. You could confirm this by changing the "Networking" setting to
Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Monday, September 3, 2018 at 10:31:50 AM UTC-4, unman wrote: > On Sun, Sep 02, 2018 at 03:56:46PM -0700, Patrick wrote: > > On Sunday, September 2, 2018 at 3:34:34 PM UTC-4, Jean-Philippe Ouellet > > wrote: > > > On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin > > > wrote: > > > > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin > > > > wrote: > > > >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: PCI > > > >> device :02:00.0 is in use by driver xenlight, domain sys-usb > > > >> > > > >> I don't know how to copy the log folder over and qubes doesn't have > > > >> the wireless network, which I believe is related, but I've attached a > > > >> picture of the log. > > > >> > > > >> This is a new Qubes install on a new Acer laptop Aspire A515-51-86AQ > > > >> Booting in legacy mode. > > > >> > > > >> I can get into the main desktop and get to Dom0 terminal, but can't > > > >> launch any of the default domains. > > > >> > > > >> There is another thread on here with the same error. He ran: > > > >> $ qvm-pci attach --persistent --option permissive=true --option > > > >> no-strict-reset=true sys-net dom0:00_XXX > > > >> > > > >> And it worked for him, but doesn't work for me, the response I get is > > > >> "error : backend vm "dom0" doesn't expose device "00.XXX" > > > > > > The "XXX" in the PCI device should be filled in with your actual PCI > > > device. > > > > > > >> So I wonder what "xenlight" is and it won't release what pci device? > > > > > > Just a library for interfacing with Xen. Unlikely to be the actual > > > problem. > > > > > > >> Suggestions? > > > >> > > > >> Thanks, > > > >> Patrick > > > > > > > > Pics attached here. > > > > > > It would be the first time I've seen this, but it might perhaps be > > > conceivable that changing BIOS settings caused your device to show up > > > with a different BDF (essentially "PCI address") than when Qubes was > > > installed? Use `lspci` in dom0 to enumerate them. > > > > > > An easier way than doing this via the command line is to use the > > > Devices tab of the Qubes VM Settings GUI - remove all devices then add > > > the one which looks like your network device. You can also configure > > > no-strict-reset via the button at the bottom of the GUI, which is > > > sometimes necessary. > > > > Thanks, I went to the work vm for example, and all of the devices were on > > the left side, nothing on the right, then I selected the wifi device and > > the response was "you've enabled dynamic memory balancing, some devices > > might not work!" > > > > and, it won't let me apply that change, saying "Can't attach pci device to > > a VM in pvh mode" > > > > Then I tried to issue your suggestion "$ qvm-pci attach --persistent > > --option permissive=true --option no-strict-reset=true sys-net dom02:00.0" > > which is my wireless device and the error response "no backend vm '02'" > > > > > > I'm wondering if this is the right way to go or maybe just try a different > > installation route? > > > > Thanks, > > Patrick > > > > There's a typo in your command: > you have dom02:00.0 and the command should be dom0:02 > > The two messages you received can be fixed in the Qube settings window. > You can change the VM mode on the Advanced pane - select HVM. > There's a checkbox for memory balancing on the same pane , if that's > needed. I habitually turn this off and set the memory/maxmem settings > low. ymmv Thanks, I'm feeling outgunned on this one. I really have no idea about what is truly going on - what's the root cause issue and why? What device is not resetting and why that matters, etc. etc. Just to be clear. While I'm able to get into the Qubes desktop, and can get to dom0 terminal, none of the pre-configured VMs are coming up. If I simply do a start from the Dom0 qubes manager, on any VM, the same error comes up: "Unable to reset PCI device :01:00.1: Internal error: active :01:00.0 devices on bus with :01:00.1 not doing bus reset." The log says: "unable to release device /dev/loop0: No such device or address" I have tried all your suggestions (HVM/mem checkbox/low mem), no change in result. Based on this, what is going on in the first place? I feel if I can understand the root of it I stand a chance in solving. Thanks, Patrick -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d5abd8e2-8e59-4d1b-bc3c-2d7917a12c18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Sun, Sep 02, 2018 at 03:56:46PM -0700, Patrick wrote: > On Sunday, September 2, 2018 at 3:34:34 PM UTC-4, Jean-Philippe Ouellet wrote: > > On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin > > wrote: > > > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin wrote: > > >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: PCI > > >> device :02:00.0 is in use by driver xenlight, domain sys-usb > > >> > > >> I don't know how to copy the log folder over and qubes doesn't have the > > >> wireless network, which I believe is related, but I've attached a > > >> picture of the log. > > >> > > >> This is a new Qubes install on a new Acer laptop Aspire A515-51-86AQ > > >> Booting in legacy mode. > > >> > > >> I can get into the main desktop and get to Dom0 terminal, but can't > > >> launch any of the default domains. > > >> > > >> There is another thread on here with the same error. He ran: > > >> $ qvm-pci attach --persistent --option permissive=true --option > > >> no-strict-reset=true sys-net dom0:00_XXX > > >> > > >> And it worked for him, but doesn't work for me, the response I get is > > >> "error : backend vm "dom0" doesn't expose device "00.XXX" > > > > The "XXX" in the PCI device should be filled in with your actual PCI device. > > > > >> So I wonder what "xenlight" is and it won't release what pci device? > > > > Just a library for interfacing with Xen. Unlikely to be the actual problem. > > > > >> Suggestions? > > >> > > >> Thanks, > > >> Patrick > > > > > > Pics attached here. > > > > It would be the first time I've seen this, but it might perhaps be > > conceivable that changing BIOS settings caused your device to show up > > with a different BDF (essentially "PCI address") than when Qubes was > > installed? Use `lspci` in dom0 to enumerate them. > > > > An easier way than doing this via the command line is to use the > > Devices tab of the Qubes VM Settings GUI - remove all devices then add > > the one which looks like your network device. You can also configure > > no-strict-reset via the button at the bottom of the GUI, which is > > sometimes necessary. > > Thanks, I went to the work vm for example, and all of the devices were on the > left side, nothing on the right, then I selected the wifi device and the > response was "you've enabled dynamic memory balancing, some devices might not > work!" > > and, it won't let me apply that change, saying "Can't attach pci device to a > VM in pvh mode" > > Then I tried to issue your suggestion "$ qvm-pci attach --persistent --option > permissive=true --option no-strict-reset=true sys-net dom02:00.0"which is > my wireless device and the error response "no backend vm '02'" > > > I'm wondering if this is the right way to go or maybe just try a different > installation route? > > Thanks, > Patrick > There's a typo in your command: you have dom02:00.0 and the command should be dom0:02 The two messages you received can be fixed in the Qube settings window. You can change the VM mode on the Advanced pane - select HVM. There's a checkbox for memory balancing on the same pane , if that's needed. I habitually turn this off and set the memory/maxmem settings low. ymmv -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180903143147.acek673j6y6vl3y6%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Sunday, September 2, 2018 at 3:34:34 PM UTC-4, Jean-Philippe Ouellet wrote: > On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin > wrote: > > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin wrote: > >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: PCI > >> device :02:00.0 is in use by driver xenlight, domain sys-usb > >> > >> I don't know how to copy the log folder over and qubes doesn't have the > >> wireless network, which I believe is related, but I've attached a picture > >> of the log. > >> > >> This is a new Qubes install on a new Acer laptop Aspire A515-51-86AQ > >> Booting in legacy mode. > >> > >> I can get into the main desktop and get to Dom0 terminal, but can't launch > >> any of the default domains. > >> > >> There is another thread on here with the same error. He ran: > >> $ qvm-pci attach --persistent --option permissive=true --option > >> no-strict-reset=true sys-net dom0:00_XXX > >> > >> And it worked for him, but doesn't work for me, the response I get is > >> "error : backend vm "dom0" doesn't expose device "00.XXX" > > The "XXX" in the PCI device should be filled in with your actual PCI device. > > >> So I wonder what "xenlight" is and it won't release what pci device? > > Just a library for interfacing with Xen. Unlikely to be the actual problem. > > >> Suggestions? > >> > >> Thanks, > >> Patrick > > > > Pics attached here. > > It would be the first time I've seen this, but it might perhaps be > conceivable that changing BIOS settings caused your device to show up > with a different BDF (essentially "PCI address") than when Qubes was > installed? Use `lspci` in dom0 to enumerate them. > > An easier way than doing this via the command line is to use the > Devices tab of the Qubes VM Settings GUI - remove all devices then add > the one which looks like your network device. You can also configure > no-strict-reset via the button at the bottom of the GUI, which is > sometimes necessary. Thanks, I went to the work vm for example, and all of the devices were on the left side, nothing on the right, then I selected the wifi device and the response was "you've enabled dynamic memory balancing, some devices might not work!" and, it won't let me apply that change, saying "Can't attach pci device to a VM in pvh mode" Then I tried to issue your suggestion "$ qvm-pci attach --persistent --option permissive=true --option no-strict-reset=true sys-net dom02:00.0"which is my wireless device and the error response "no backend vm '02'" I'm wondering if this is the right way to go or maybe just try a different installation route? Thanks, Patrick -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f1e058d6-10ea-41cb-b689-24ddadf64fcb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Unable to reset PCI device 0000:02.00.0
On Sun, Sep 2, 2018 at 10:12 AM, Patrick Bouldin wrote: > On Sunday, September 2, 2018 at 10:10:55 AM UTC-4, Patrick Bouldin wrote: >> Qubes 4.0 Error - "Start failed: Requested operation is not valid: PCI >> device :02:00.0 is in use by driver xenlight, domain sys-usb >> >> I don't know how to copy the log folder over and qubes doesn't have the >> wireless network, which I believe is related, but I've attached a picture of >> the log. >> >> This is a new Qubes install on a new Acer laptop Aspire A515-51-86AQ >> Booting in legacy mode. >> >> I can get into the main desktop and get to Dom0 terminal, but can't launch >> any of the default domains. >> >> There is another thread on here with the same error. He ran: >> $ qvm-pci attach --persistent --option permissive=true --option >> no-strict-reset=true sys-net dom0:00_XXX >> >> And it worked for him, but doesn't work for me, the response I get is "error >> : backend vm "dom0" doesn't expose device "00.XXX" The "XXX" in the PCI device should be filled in with your actual PCI device. >> So I wonder what "xenlight" is and it won't release what pci device? Just a library for interfacing with Xen. Unlikely to be the actual problem. >> Suggestions? >> >> Thanks, >> Patrick > > Pics attached here. It would be the first time I've seen this, but it might perhaps be conceivable that changing BIOS settings caused your device to show up with a different BDF (essentially "PCI address") than when Qubes was installed? Use `lspci` in dom0 to enumerate them. An easier way than doing this via the command line is to use the Devices tab of the Qubes VM Settings GUI - remove all devices then add the one which looks like your network device. You can also configure no-strict-reset via the button at the bottom of the GUI, which is sometimes necessary. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABQWM_Ct7943Nr7vQyjfV5j0ZCLKo9Z%3DRdU%2Be2yvW4oCO2ifmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
