Yep, Been running Hardy Xen Dom0 here, solid as a rock, on top of gutsy gibbon. I downloaded source and backported Xen. Just added patch here, and recompiled, now DomU is running sweetly too!
I have been running Debian Etch 2.6.18 DomU (maintained source tree), and also have a 2.6.25 paravirt Ops DomU working as well. Here are few tips: Hard drives are /dev/xvda1, /dev/xvda2 etc. Edit /etc/fstab accordingly. Console is /dev/xvc0 - Just edit /etc/inittab to run 1 getty on console, and comment out all the rest, add console=xvc0 to 'extra' line in domain config file in /etc/xen. Also, install udev in your DomUs, and create a minimal /dev to go underneath it on /dev so that you get console messages after init is started. The console on the kernel config line will give you a console while an initrd is loaded. To get a linux 2.6.25 Xen kernel working, strip the vmlinux in the top of the source tree after compile and compress: $ strip vmlinux -o vmlinux-striped $ gzip -c vmlinux-striped > vmlinuz and use that as Xen kernel. xm create cannot load a staright bzImage kernel yet. Networking goes sweetly as I use my own network configuration package. The Hard source is now on track! Cheers, Matthew Grant PS: If you are wondering, I am a Debian Maintainer -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
