WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Create DOM1 problems again

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Create DOM1 problems again
From: Qian Huang <qhuang@xxxxxxxxx>
Date: Tue, 30 Mar 2004 13:52:26 -0800 (PST)
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 30 Mar 2004 23:02:45 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1B8GEZ-0006R8-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1B8GEZ-0006R8-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
hi Ian,
Thanks a lot for your kind reply.
yes, it is part of the console output when domain1 is booting.
Here is the output:
"
[1] Setting network parameters: [OK]
[1] Bringing up loopback interface: Error, some other host already uses
address 127.0.0.1.
[1] [FAILED]
[1] Bringing up interface eth0:
[1] Determining IP information for eth0 ... failed.
[1] [FAILED]
"
So I can't get eth0 up. I can ping 169.254.1.0, but can't for 169.254.1.1
which confirms that the nat is working but the eth0 isn't up.

I tried adding NOZEROCONF=yes to ifcfg-lo. But the problem is still there.

What could be possiblely wrong?

--Qian


On Tue, 30 Mar 2004, Ian Pratt wrote:

>
> > I'm trying to create the new domain, using the Xen 1.2  installation. I
> > met problems before, it turned out that's because insufficiency of memory.
> > But still don't have luck to make it run.
> > Two things are confusing me:
> >
> > (1) The xen_read_console prints:
> > "Bringing up loopback interface: Error, some other host already uses
> > address 127.0.0.1
> > [Failed]"
> > Is this normal? If not how to solve it?
>
> You mean that this message is part of the console output of the
> other domain that is booting?
>
> What root file system are you using? RH9?
> If so, append "NOZEROCONF=yes" to /etc/sysconfig/networking-scripts/ifcfg-lo
>
> > (2)In the end, the xen_read_console prints:
> > "INIT: Id "1" respawning too fast: disabled for 5 minutes
> > INIT: Id "4" respawning too fast: disabled for 5 minutes
> > INIT: Id "2" respawning too fast: disabled for 5 minutes
> > INIT: Id "3" respawning too fast: disabled for 5 minutes
> > INIT: Id "5" respawning too fast: disabled for 5 minutes
> > INIT: Id "6" respawning too fast: disabled for 5 minutes
> > INIT: no more processes left in this runlevel
> > ..."
> > what does this mean?
>
> It means that you need to edit your /etc/inittab to comment out
> the lines that are running a *getty on tty[123456]. If you were
> running 1.3 you could start a mingetty on xen/cons (having done
> the mknod), but in 1.2 you'll have to log in over the network.
>
> If sshd is starting in your new domain, and you've configured
> its network correctly, you should be able to ssh in.
>
> Best,
> Ian
>


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel