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 upDom0 loop devices sometimes fail to detach when AppVM is shut down #1301
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Oct 8, 2015
Member
Check if you have any errors about it in /var/log/xen/xen-hotplug.log
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Check if you have any errors about it in Best Regards, |
marmarek
added
bug
C: core
P: minor
labels
Oct 8, 2015
marmarek
added this to the Release 3.0 updates milestone
Oct 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
The log is empty, but I'll check again if/when it happens again. |
marmarek
modified the milestones:
Release 3.0 updates,
Release 3.1 updates
Nov 19, 2016
andrewdavidwong
modified the milestones:
Release 3.1 updates,
Release 3.2 updates
May 31, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
andrewdavidwong commentedOct 8, 2015
If you follow the instructions here for storing some AppVMs on a secondary drive, then some loop devices will get attached to dom0 (displayed in
qvm-block) when the AppVM is started. They're supposed to automatically be detached when the AppVM is shut down, but sometimes they don't, and this can cause problems such as the AppVM not being able to be started again. (Attempting to manually detach them usingqvm-block -dusually doesn't work either.)