On Tue, Sep 4, 2018 at 9:17 PM, Patrick <patr...@runthisproject.com> 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
>> <patr...@runthisproject.com> 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 0000: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.

Reply via email to