/qubes-issues

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

Make it easier for the user to work around PCI strict reset problems #3205

Closed
rootkovska opened this Issue Oct 23, 2017 · 7 comments

Comments

Assignees

@marmarta marmarta

Labels
Projects
None yet
Milestone
  Release 4.0
5 participants
@rootkovska @marmarek @adrelanos @qubesos-bot @marmarta
@rootkovska
Member

rootkovska commented Oct 23, 2017

On some chipsets it is required to pass -o no-strict-reset=True when assigning a device to VMs. Figure out the most friendly way of how to handle this (semi-) automatically.

@rootkovska rootkovska added bug C: other P: major UX labels Oct 23, 2017

@rootkovska rootkovska added this to the Release 4.0 milestone Oct 23, 2017

@rootkovska rootkovska assigned marmarek Oct 23, 2017

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 23, 2017

Member

firstboot/salt already does that for sys-usb. No user action is needed.
Member

marmarek commented Oct 23, 2017

firstboot/salt already does that for sys-usb. No user action is needed.
@rootkovska

This comment has been minimized.

Show comment
Hide comment
@rootkovska

rootkovska Oct 23, 2017

Member

Sure, but some users might want to do that later for other devices.
Member

rootkovska commented Oct 23, 2017

Sure, but some users might want to do that later for other devices.

@marmarek marmarek added C: qubes-manager and removed C: other labels Oct 23, 2017

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 23, 2017

Member

So, probably you mean GUI VM settings, right? Adjusting issue labels for that.
Member

marmarek commented Oct 23, 2017

So, probably you mean GUI VM settings, right? Adjusting issue labels for that.

@marmarta marmarta assigned marmarta and unassigned marmarek Oct 23, 2017

@rootkovska

This comment has been minimized.

Show comment
Hide comment
@rootkovska

rootkovska Oct 25, 2017

Member

Yeah, GUI setting + brief explanation in the same window what this is for. Ideally also the error message (displayed when strict reset is unsuccessful) could be hinting this option should be used, although I realize this might be tricky, since it's not our code that displays the error.
Member

rootkovska commented Oct 25, 2017

Yeah, GUI setting + brief explanation in the same window what this is for. Ideally also the error message (displayed when strict reset is unsuccessful) could be hinting this option should be used, although I realize this might be tricky, since it's not our code that displays the error.
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 27, 2017

Member

This was quite complicated indeed to figure out. Meanwhile when someone tries doing this using command line, some hints on the syntax here.

qvm-pci
qvm-pci detach sys-usb dom0:00_1d.0
qvm-pci attach --persistent -o no-strict-reset=True sys-usb dom0:00_14.0

EDIT by @marmarek: fix option
Member

adrelanos commented Oct 27, 2017 •
edited by marmarek
Edited 1 time
  • @marmarek marmarek edited Oct 30, 2017 (most recent)

This was quite complicated indeed to figure out. Meanwhile when someone tries doing this using command line, some hints on the syntax here.

qvm-pci
qvm-pci detach sys-usb dom0:00_1d.0
qvm-pci attach --persistent -o no-strict-reset=True sys-usb dom0:00_14.0

EDIT by @marmarek: fix option

@marmarek marmarek referenced this issue Oct 30, 2017

Closed

Qubes R4 sys-usb does not start - Start failed: internal error: Unable to reset PCI device 0000:00:14.0: no FLR, PM reset or bus reset available #3262

@adrelanos adrelanos referenced this issue Oct 30, 2017

Closed

qvm-pci attach to running VM failed - fix or improve error message - Got empty response from qubesd. See journalctl in dom0 for details #3263

marmarta added a commit to marmarta/qubes-manager that referenced this issue Jan 12, 2018

@marmarta
Added 'configure no strict reset for PCI devices' button 
The button is in 'devices' tab of VM settings; it allows the user to
select which devices should have 'no-strict-reset' enabled and tells
the user not to change this setting if there are no errors.

fixes QubesOS/qubes-issues#3205
Verified
This commit was signed with a verified signature.
@marmarta marmarta Marta Marczykowska-Górecka
GPG key ID: 9A752C30B26FD04B Learn about signing commits
d0b3d60

@marmarta marmarta referenced this issue in QubesOS/qubes-manager Jan 12, 2018

Merged

Added 'configure no strict reset for PCI devices' button #55

marmarta added a commit to marmarta/qubes-manager that referenced this issue Jan 12, 2018

@marmarta
Added 'configure no strict reset for PCI devices' button 
The button is in 'devices' tab of VM settings; it allows the user to
select which devices should have 'no-strict-reset' enabled and tells
the user not to change this setting if there are no errors.

fixes QubesOS/qubes-issues#3205
Verified
This commit was signed with a verified signature.
@marmarta marmarta Marta Marczykowska-Górecka
GPG key ID: 9A752C30B26FD04B Learn about signing commits
f724866

@marmarek marmarek closed this in marmarek/qubes-manager@801014f Jan 19, 2018

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Jan 19, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.11-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

qubesos-bot commented Jan 19, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.11-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot qubesos-bot added the r4.0-dom0-cur-test label Jan 19, 2018

@qubesos-bot qubesos-bot referenced this issue in QubesOS/updates-status Jan 19, 2018

Closed

manager v4.0.11 (r4.0) #369

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Feb 6, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.13-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

qubesos-bot commented Feb 6, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.13-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@qubesos-bot qubesos-bot added r4.0-dom0-stable and removed r4.0-dom0-cur-test labels Feb 6, 2018

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