Re: [Xen-users] Re: Xen kernel problem

[Alexander Attarian <alex@xxxxxxxxxx>]

I wasn't blaming the kernel, the kernel blame was for the previos 
problem, this one is a new one. Xen is running without any problems, and 
from dom0 i'm trying to start my newly created dom1 with the xenU 
kernel. And that starts up fine, I can login via the console to dom1 and 
to the system. The only problem is dom1 is not picking up an IP from xen.
Thanks

Jorge I. Davila L. wrote:

> well, I think that there is not enough information to say that is the xen
> kernel the problem.
>
> You have a single physical machine and you are trying to connect to the
> other domains from domain0 ??
>
> Alexander dijo:
>  
>
> > I guess FC4 is not doing very well. I just installed FC3 and compiled the
> > latest 2.0.7 xen and rebooted, everything just works fine! Had to do the
> > initrd image, and after that things are running smooth.
> >
> > The only thing that I'm working on right now is, my xenU is starting fine,
> > I
> > allocated 1GB memory to it, but somehow the network is not coming up.
> >
> > The motherboard has 2 Broadcom GbE ports, the network is currently
> > connected
> > to eth1. In xenU configuration I have "alias eth0 xen_net" in
> > /etc/modprobe.conf, and in /etc/sysconfig/network, I only have networking
> > yes and the hostname. Besides that I have a simple ifcfg-eth0 in
> > /etc/sysconfig/network-scripts/, which just says device=eth0,
> > bootproto=dhcp, onboot=on
> > The same configuration I have on a regular desktop, and it is working
> > fine.
> > Does the dual LAN do anything different here? WHen I start the network it
> > just says determining IP for eth0 and it just hangs there, and then fails
> > after a minute.
> >
> > Any help is appreciated.
> >
> > Thanks!
> >
> > Alexander writes:
> >
> >    
> >
> > > Hi everyone,
> > >
> > > I'm getting the following boot error, when installing xen-unstable on a
> > > dual opteron 246 machine, with a Tyan 2881 Motherboard, 4GB RAM, SATA
> > > Drive and ReiserFS filesystem. The machine is a Fedora Core 4.
> > > I installed the i386 FC4 on the dual opteron, I didn't want the 64bit
> > > yet.
> > > All my binaries are 32bit and I'm compiling it all with 32bit too.
> > >
> > > After downloading xen-unstable, I did make world and make install. I'm
> > > not
> > > using gcc4, I'm using gcc 3.2.3, it works fine, the compiling is without
> > > any problems. I put the following in my grub.conf:
> > >
> > > title Fedora Core-up (Xen 3.0)
> > >      root (hd0,0)
> > >      kernel /boot/xen.gz dom0_mem=262144
> > >      module /boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0
> > >
> > > I didn't put an initrd image yet because I wanted to see if Xen will
> > > boot
> > > at all, but once the machine restarts, after xen.gz it tries to load
> > > vmlinuz-2.6-xen0 and gives the following error: Error 4: Bad or
> > > incompatible header in the compressed file.
> > >
> > > It doesn't boot after that, gives me the option to go back to grub menu
> > > and choose a different boot option where I start back to my default FC4
> > > installation.
> > >
> > > Any idea why this would happen? I have a feeling xen.gz is loading fine,
> > > but the dom0 kernel is giving that error.
> > >
> > > Thanks,
> > > Alex
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> > >      
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> >    
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
> __________ NOD32 1.1170 (20050715) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
>
>  

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users