clock of hostsystem used in domU kernel freezes console/domU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-image-
The console for a domU kernel freezes on "Setting system clock"
This occurs for every ubuntu gutsy (and maybe others) domU, unless you add exit 0 (or some other workaround) to /etc/init.
and /etc/init.
I'm not sure yet if it's just the console or the domU itself which freezes. Seems to be the latter, but I can't be sure.
According to Stephen Seitz:
This issue is caused by an ubuntu domU kernel patch which uses the clock
of the hostsystem.
I did some similar by chmod 000 /etc/init.
which isn't a clean solution but works also.
A clean solution would be to patch the hwclock scripts to look for e.g.
/proc/xenbus . I would file a bugreport, but I assume I'm unable to handle
launchpad.net ...
Stephan
I have confirmed this bug. Adding exit 0 to /etc/init. d/hwclock. sh does solve the issue but something more graceful would be nice.