Qubes possibly not detecting ethernet PCI (Dell Inspiron 5593)

[fiftyfour...@gmail.com]

Hi all,

I ran into an issue while configuring my disposable sysVMs:

It turns out my sys-net is set to PVH by default instead of HVM, which allows for PCI passthrough. This led me to look around, and it turns out there are no devices attached to my sys-net despite there being an ethernet jack in my laptop.

Using qvm-pci in dom0 revealed that there are no network interfaces, but three "Unknown", two "PCI bridge" one "ISA bridge" and one "Communication controller", all from Intel Corporation. Is it possible that one of these is my ethernet interface? 

• If so, how would I go about figuring out which one and restoring it? Or do I just test them one by one?
• If not, how would I get Qubes to look for my missing ethernet?

Thanks in advance

[fiftyfour...@gmail.com]

On 18/07/2020, Tobias Gilberg <tob...@mail.de> wrote:

> One of the Unknown devices is you ethernet interface.

> With lspci -v or lspci -vv in a dom0 terminal you can get more detailt

> information about the pci-devices to determin witch one is the ethernet

> interface.

> If you still didn't find it out, post the output of lspci -vv to the

> mailinglist.

Hi Tobias,

Thanks for your response via email. I'm replying here in case others have thoughts to contribute. 

I tried lspci -v and -vv and found out a little more about the four unknowns in qvm-pci. They're all serial bus controllers, with the first three basically the same--they use kernel driver 'intel-lpss', which doesn't seem to be what I'm looking for. The last one that I missed earlier doesn't have a kernel driver in use and isn't <access denied>, so I guess this is most likely to be the ethernet device.

Is it safe to test it by connecting it to sys-net?

[Tobias Gilberg]

> I tried lspci -v and -vv and found out a little more about the four
> unknowns in qvm-pci. They're all serial bus controllers, with the first
> three basically the same--they use kernel driver 'intel-lpss', which
> doesn't seem to be what I'm looking for. The last one that I missed earlier
> doesn't have a kernel driver in use and isn't <access denied>, so I guess
> this is most likely to be the ethernet device.
>
> Is it safe to test it by connecting it to sys-net?

If you disable autostart on sys-net and have no important unsaved files open, then it's "save".
The worst thing that could happen is, if you passtrough some devices that are needed by dom0 for running the system,
like gpu, host bridge ore something else, you system will shutdown or restart.

[fiftyfour...@gmail.com]

On Sunday, 19 July 2020 20:13:46 UTC+8, Tobias Gilberg wrote:

If you disable autostart on sys-net and have no important unsaved files open, then it's "save".
The worst thing that could happen is, if you passtrough some devices that are needed by dom0 for running the system,
like gpu, host bridge ore something else, you system will shutdown or restart.

After attaching the device to sys-net, it refuses to start. Error message:

>Start failed: internal error: Unable to reset PCI device 0000:00:xx,x: no FLR, PM reset or bus reset available, see /var/log/libvirt/libxl/libxl-driver.log for details.

Is there any easy way for me to copy the lspci -v output and other logs from my unconnected Qubes PC to the one I'm using right now? 

[fiftyfour...@gmail.com]

Issue resolved

Cause of issue: User is a moron and disabled network interfaces in BIOS

Thanks for putting up with me Tobias