Just as a follow up, I got it up and running.
It seems to be an issue with the old 2.6.18 kernel. I grabbed a recent
ebuild from http://code.google.com/p/gentoo-xen-kernel/downloads/list
(2.6.31), and it's now working like a charm.
Thanks anyway!
On Sat, Dec 19, 2009 at 8:11 PM, Bruno Lustosa <bruno.li...@gmail.com> wrote:
> Hello, people.
>
> I've been trying for the past few days to get Xen working on Gentoo,
> still no success.
> I already have a dom0 kernel working, but can't get domU guests to
> boot. I got installed:
>
> sys-kernel/xen-sources-2.6.18-r12
> app-emulation/xen-tools-3.4.2
> app-emulation/xen-3.4.2
>
> The dom0 kernel is 2.6.18-r12 (the recommended). For the domU, I tried
> both the same and the latest gentoo-sources, but neither of them
> works.
> According to /var/log/xen/xend.log, there seems to be a problem with
> hotplug scripts. I don't know the internals of Xen, so I'm not sure if
> this is a udev issue, or something within /etc/xen/scripts
> Anyway, here's the script for the domU guest I'm trying to run:
>
> name = "tidus";
> memory = 1024;
> kernel = "/boot/vmlinuz-2.6.31-domU";
> disk = [ 'phy:machines/tidus.system,xvda1,w',
> 'phy:machines/tidus.swap,xvda2,w' ];
> root = "/dev/xvda1 ro";
>
> Pretty basic. For the disk, I've tried both phy:machines/tidus.system
> and phy:/dev/machines/tidus-system, they both fail exactly the same.
> When I try to 'xm create -c' the vm, I get these in xend.log:
>
>
> [2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices vif.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices vkbd.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for
> devices ioports.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices tap.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for
> devices console.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:144) Waiting for 0.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices
> vscsi.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices vbd.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:144) Waiting for 51713.
> [2009-12-19 18:02:59 2905] DEBUG (DevController:629)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/4/51713/hotplug-status.
>
> It then stops there for some time, and finally gives up and destroys
> the vm. xm create gets the error: "Error: Device 51713 (vbd) could
> not be connected. Hotplug scripts not working."
> The rest in xend.log is just some messages destroying and releasing resources.
> I can mount the lvm device without a problem (installed Gentoo on it
> by mounting on /mnt/gentoo).
> Dom0 kernel is working fine, all hardware is fine. I have the relevant
> sections turned on (backend stuff for dom0 and frontend stuff for
> domU).
> From the udev rules (/etc/udev/rules.d/xen-backend.rules), I see that
> for the "vbd" devices, it should be calling /etc/xen/scripts/block:
>
> SUBSYSTEM=="xen-backend", KERNEL=="vbd*", RUN+="/etc/xen/scripts/block
> $env{ACTION}"
>
> However, I edited this file and put a simple "echo" in the beginning,
> and it seems udev is not calling this script.
> I googled a lot, searched a lot, but still can't get this to work. I'm
> using this list as a last resort :)
> This is a clean install of Gentoo, using profile
> hardened/linux/amd64/10.0/no-multilib, if it makes a difference. My
> CFLAGS: "-O2 -fomit-frame-pointer -march=nocona
> -mno-tls-direct-seg-refs -pipe"
>
> Anyone shed some light on this?
>
> Thanks!
>
> --
> Bruno Lustosa <br...@lustosa.net>
> http://www.lustosa.net/
>
--
Bruno Lustosa <br...@lustosa.net>
http://www.lustosa.net/
