Comment 0 for bug 1018619
Revision history for this message
| Wer Wie Was (kzqd-deactivatedaccount-deactivatedaccount) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I'm created a Dom0 with Xen 4.1 as hypervisor on Ubuntu 12.04 and created a new root filesystem (also 12.04 in paravirtualization mode) with debootstrap.
Then I wrote the Xen DomU configuration file and tried to boot the DomU with the 3.2.0-25-generic kernel. The DomU gets created but stucks in the boot process at the following sequence:
7.179839] EXT3-fs (xvda1): mounted filesystem with ordered data mode
Begin: Running /scripts/
done.
Begin: Running /scripts/
fsck from util-linux 2.20.1
/dev/xvda1: clean, 15756/1310720 files, 215621/5242880 blocks
Seems to be a bug. In the Dom0/Xen logs are no errors reported. Other guests like Debian Squeeze work with the same kernel as DomU kernel. So I think its a problem with the kernel it self or with the interaction of the system with the kernel.
Does someone has a solution for this problem?
The problem can be reproduced by creating a paravirtualized DomU on Ubuntu Precise Pangolin 12.04 with Xen 4.1 (all packages from normal distro repository) and boot the DomU with the actual standard Ubuntu 3.2.0-25-generic kernel.
Best Regards