| 1 |
Hello, people. |
| 2 |
|
| 3 |
I've been trying for the past few days to get Xen working on Gentoo, |
| 4 |
still no success. |
| 5 |
I already have a dom0 kernel working, but can't get domU guests to |
| 6 |
boot. I got installed: |
| 7 |
|
| 8 |
sys-kernel/xen-sources-2.6.18-r12 |
| 9 |
app-emulation/xen-tools-3.4.2 |
| 10 |
app-emulation/xen-3.4.2 |
| 11 |
|
| 12 |
The dom0 kernel is 2.6.18-r12 (the recommended). For the domU, I tried |
| 13 |
both the same and the latest gentoo-sources, but neither of them |
| 14 |
works. |
| 15 |
According to /var/log/xen/xend.log, there seems to be a problem with |
| 16 |
hotplug scripts. I don't know the internals of Xen, so I'm not sure if |
| 17 |
this is a udev issue, or something within /etc/xen/scripts |
| 18 |
Anyway, here's the script for the domU guest I'm trying to run: |
| 19 |
|
| 20 |
name = "tidus"; |
| 21 |
memory = 1024; |
| 22 |
kernel = "/boot/vmlinuz-2.6.31-domU"; |
| 23 |
disk = [ 'phy:machines/tidus.system,xvda1,w', |
| 24 |
'phy:machines/tidus.swap,xvda2,w' ]; |
| 25 |
root = "/dev/xvda1 ro"; |
| 26 |
|
| 27 |
Pretty basic. For the disk, I've tried both phy:machines/tidus.system |
| 28 |
and phy:/dev/machines/tidus-system, they both fail exactly the same. |
| 29 |
When I try to 'xm create -c' the vm, I get these in xend.log: |
| 30 |
|
| 31 |
|
| 32 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices vif. |
| 33 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices vkbd. |
| 34 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for |
| 35 |
devices ioports. |
| 36 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices tap. |
| 37 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for |
| 38 |
devices console. |
| 39 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:144) Waiting for 0. |
| 40 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices vscsi. |
| 41 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:139) Waiting for devices vbd. |
| 42 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:144) Waiting for 51713. |
| 43 |
[2009-12-19 18:02:59 2905] DEBUG (DevController:629) |
| 44 |
hotplugStatusCallback |
| 45 |
/local/domain/0/backend/vbd/4/51713/hotplug-status. |
| 46 |
|
| 47 |
It then stops there for some time, and finally gives up and destroys |
| 48 |
the vm. xm create gets the error: "Error: Device 51713 (vbd) could |
| 49 |
not be connected. Hotplug scripts not working." |
| 50 |
The rest in xend.log is just some messages destroying and releasing resources. |
| 51 |
I can mount the lvm device without a problem (installed Gentoo on it |
| 52 |
by mounting on /mnt/gentoo). |
| 53 |
Dom0 kernel is working fine, all hardware is fine. I have the relevant |
| 54 |
sections turned on (backend stuff for dom0 and frontend stuff for |
| 55 |
domU). |
| 56 |
From the udev rules (/etc/udev/rules.d/xen-backend.rules), I see that |
| 57 |
for the "vbd" devices, it should be calling /etc/xen/scripts/block: |
| 58 |
|
| 59 |
SUBSYSTEM=="xen-backend", KERNEL=="vbd*", RUN+="/etc/xen/scripts/block |
| 60 |
$env{ACTION}" |
| 61 |
|
| 62 |
However, I edited this file and put a simple "echo" in the beginning, |
| 63 |
and it seems udev is not calling this script. |
| 64 |
I googled a lot, searched a lot, but still can't get this to work. I'm |
| 65 |
using this list as a last resort :) |
| 66 |
This is a clean install of Gentoo, using profile |
| 67 |
hardened/linux/amd64/10.0/no-multilib, if it makes a difference. My |
| 68 |
CFLAGS: "-O2 -fomit-frame-pointer -march=nocona |
| 69 |
-mno-tls-direct-seg-refs -pipe" |
| 70 |
|
| 71 |
Anyone shed some light on this? |
| 72 |
|
| 73 |
Thanks! |
| 74 |
|
| 75 |
-- |
| 76 |
Bruno Lustosa <bruno@×××××××.net> |
| 77 |
http://www.lustosa.net/ |
Archives