Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDetect when the same PCI device got assigned to more than one VM #522
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by marmarek on 18 Apr 2012 09:11 UTC |
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the Release 1 milestone
Mar 8, 2015
marmarek
added
bug
C: core
P: major
labels
Mar 8, 2015
marmarek
assigned
marmarek
and unassigned
rootkovska
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 8, 2015
Member
Comment by marmarek on 18 Apr 2012 15:24 UTC
http://git.qubes-os.org/?p=marmarek/core.git;a=commit;h=abaea52da05265092a8e94e798e57dcd2e2b644c
|
Comment by marmarek on 18 Apr 2012 15:24 UTC |
marmarek
closed this
Mar 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by joanna on 14 Apr 2012 12:38 UTC
... this is especially important in the following practical case:
User start VM1, which got some PCI device assigned.
The user then stopped the VM1, and as soon as it disappeared from the Running VMs List in the manager, the user starts VM2, which also got the same PCI device assigned. Unfortunately, the VM2 will not start now, as the pciback is still busy cleaning up for the VM1.
Now, the only way to get the PCI device working in the VM2, is to: 1) stop VM2, wait until it fully stops (qvm-ls/xl list is your friend), then 2) start VM1, 3) stop VM1, 4) wait until it fully stops (qvm-ls/xl list), and then 5) start VM2 again.
This is connected with the ticket #520, BTW.
Migrated-From: https://wiki.qubes-os.org/ticket/522