Hello, thanks Daniel for your answer.
El mar, 16-08-2005 a las 14:57 +0100, Daniel Hulme escribió:
> > $ PATCH_THE_KERNEL=YES make-kpkg --config=menuconfig --arch=xen
> > --revision=1 --append-to-version=myxen0 kernel_image
>
> > 9 - I configure Grub:
>
> > module /boot/xen-linux-2.6.11myxen0 root=/dev/md0 ro console=tty0
>
> > 11 - I have this domain configured:
> >
> > kernel = "/boot/vmlinuz-2.6.11.12-xenU"
> Are you sure this is what the kernel is called? If you have compiled it
> with --append-to-version the filename will probably be different,
> looking a bit like the dom0 filename you give above. The output from
> your kernel,
> > Linux version 2.6.11.12-xenU (xenod@xxxxxxxxxxxxxxxxxxxxx) (gcc
> > version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Thu Aug 4 00:48:08
> looks like you are using one of the precompiled kernels. Try using the
> kernel you compiled. If that doesn't work, try using the same kernel
> that you use for dom0.
With the kernel I compiled I get the same results:
root@backupsid:~# xm create -c pau.conf
Using config file "/etc/xen/pau.conf".
Started domain pau, console on port 9605
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.11myxenu (root@backupsid) (gcc versión 3.3.5 (Debian
1:3.3.5-13)) #1 Thu Aug 11 22:44:39 CEST 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000012c00000 (usable)
(...)
And then stops at:
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes
xm list doesn't list the domain, just the domain-0, If I type
quickly 'xm list' just after the 'xm create' I can see the
domain while the kernel messages are shown but it dies
afterwards.
If I use the dom0 kernel I get no kernel output just:
root@backupsid:~# xm create -c pau.conf
Using config file "/etc/xen/pau.conf".
Started domain pau, console on port 9605
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
I have used different kernels, the one you comment is
the one distributed with the sources of xen, this shows
kernel messages but behaves exactly as the one I've compiled.
> Remember that the kernel gets loaded from the
> dom0's filesystem (md0 in your case), *not* the domU's filesystem.
I know :-)
>
> It should still work, though, and the failure mode you describe is quite
> bizarre.
Yes, but I'm not the only one, and it fails in different
computers.
Anyway, some more info, I have compiled bridge support but I
get this error:
root@backupsid:~# brctl show
bridge name bridge id STP enabled interfaces
xen-br0 8000.000000000000 no can't get port
info: Function not implemented
looks like a kernel module not loaded or a feature not
compiled but I have bridge support:
root@backupsid:~# ifconfig xen-br0
xen-br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:1.2.3.4 Bcast:1.2.3.255 Mask:255.255.255.255
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:378 (378.0 b)
Thanks,
Ramon
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home