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