I just wanted to comment since I have been researching this for a couple of hours myself. Once I added
extra='xencons=tty' to my domain.cfg files, I was able to use the console to monitor the bootup. I saw an immediate error about not being able to set the hardware clock, but the boot continued. I used "update-rc.d hwclock remove; update-rc.d hwclockfirst remove" to remove the clock set from the bootup and now I do not have an issue with that. I use ntp to set the clock anyway. The reason I was trying to work with the console in the first place was due to https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/150805, which also has a workaround. Note: while the xenconsole workaround was necessary, no hwclock or udev/network changes were necessary for my gutsy dom0/dapper domU. This entire process was only an issue with a gutsy dom0/domU setup. -- xen guest hangs after mounting filesystem https://bugs.launchpad.net/bugs/144631 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
