© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I'm not sure how safe it is to mount the file system like that twice. I've had systems in a mess because of doing similar things and they hard lockup on me as a result.
Dom0 has to be able to mount the file systems of any DomU at any time, otherwise the DomU's wouldn't see their data. I don't think there is any code in Xen or the linux kernel, or mount utils to prevent mounting the same file system multiple, and linux has a history of letting the user hang themselves in such ways because of corner cases where doing what looks to be a silly thing is actually a desirable thing. Flexability is a wonderful thing in the hands of someone capable of dealing with any problems that arise as a result.
As for your issue did you shutdown the DomU, and then remove all the hwclock stuff I pointed out including the file in the /etc/udev/rules.d directory, I think this is the main culperate, every time I forget to remove it the DomU hangs.
If you don't believe me about hwclock causing hangs then you could look through some of the xen-tool scripts, including one called 15-disable-hwclock.
# dpkg -L xen-tools|grep hwclock
/usr/lib/
/usr/lib/
/usr/lib/
However this script only deals with hwclock scripts in init.d, not in udev, this seems to be a new for Gutsy thing.
As for still not believing me, go into google, type in "xen hwclock hang" and there is almost 1000 results, some dating back to at least 2003, so yes hwclock can hang a DomU, however the introduction of a udev rule when /dev/rtc appears causes hwclock to run and the whole thing to hang.