New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing with usb vm in net-vm fails with 4.0-rc2 #3254

Open
o- opened this Issue Oct 29, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@o-

o- commented Oct 29, 2017

Qubes OS version:

4.0-rc2

Affected TemplateVMs:


Steps to reproduce the behavior:

Install Qubes. Select 'use sys-net as usb vm'

Expected behavior:

Qubes installs

minor point: on a failure, I would expect the installer to handle it more gracefully. When it failed I was not sure if qubes was still fully configured. Even though I managed to resolve the problem I eventually reinstalled, since I fearde the installed did not finish properly. Should I open an issue for this too?

Actual behavior:

The post-install hook fails, since sys-net does not boot

Starting sys-net says Unable to reset PCI device [...] no FLR, PM reset or bus reset available.

The controller is: USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)

no-stric-reset=TRUE was set by the installer on that device.

General notes:

I can't tell if this issue is hardware related, or if this combination is not supported any longer. I was reliably able to boot sys-net when that device was detached and trigger the issue when it was attached. The other devices attached to sys-net are an I219-LM ethernet controller and a 8265 Wireless card.

In my case I just restarted the installer and did not select the option anymore (letting the installer create separate usb and net vm) and then everything worked as expected.

Since I found a workaround I can't provide much more info. I still wanted to open this issue in case other are affected by the same problem, or the configuration is not supported anymore (in which case it should be removed from the installer screen).


Related issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment