Same problems here with ubuntu gutsy, adding a new line to the DomU configuration file: extra='xencons=tty'
This does make the VMs Virtually work but now they hung in the state of "setting the system clock.." forever! In other words, this must be a complicated problem an yes it might be the case that we have a problem there as well. I have seen many problems with gutsy and Xen 3.1. I simply and strongly believe that it is not a prod setup by any means. First I got the /lib/tls problem, then the extra='xencons=tty', now the hwclock and in the past loads of problems with the cupsys incompatibilities in the Host (don't ask why i wanted cupsys. The case we are facing now is the worst. Guest domains will simply not boot properly without great intervention. Furthermore the minute you solve one problem another one shows up -- 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
