hi, there, 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. VM image : "/boot/xenolinux.gz" VM ramdisk : " " VM memory (MB) : "64" VM IP address(es): "169.254.1.1" VM block device(s): "phy:hdc1,hdc1,w" VM cmdline : "ip=169.254.1.1:169.254.1.0:169.254.1.0:255.255.0.0::eth0:on root=/dev/hdc1 ro 4 VMID=1" 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? (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 ..." And then it just stucks there. what does this mean? Thanks, Qian ------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> 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. > > What could be possiblely wrong?Please tell us about the file system you''re using (RH9, SuSE etc), the version of xen and xenolinux, and send the full output of xc_dom_create.py and the full output of the domain that is booting. 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I''m using RH9, ther version of xen and xenolinux is 1.2. The output of domain 0 is: [root@localhost root]# xc_dom_create.py -fmyvm1.conf -Dvmid=1 Parsing config file ''/etc/xc/myvm1.conf'' VM image : "/boot/xenolinux.gz" VM ramdisk : "" VM memory (MB) : "64" VM IP address(es) : "169.254.1.1" VM block device(s) : "phy:hdc1,hdc1,w" VM cmdline : "ip=169.254.1.1:169.254.1.0:169.254.1.0:255.255.0.0::eth0:on root=/dev/hdc1 ro 4 VMID=1" VM started in domain 1 the output of xc_dom_create is attatched as ''tmp''. the output of xc_dom_control.py list is: Dom Name Mem(kb) CPU State Time(s) 0 Domain-0 32768 0 r- 192 1 This is VM 1 65536 0 -- 139 As said before, now the problem is I cannot ping 169.254.1.1,so cannot ssh in DOM1 either. Thanks for your time. Qian On Tue, 30 Mar 2004, Ian Pratt wrote:> > > 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. > > > > What could be possiblely wrong? > > Please tell us about the file system you''re using (RH9, SuSE > etc), the version of xen and xenolinux, and send the full output > of xc_dom_create.py and the full output of the domain that is > booting. > > Ian >
> As said before, now the problem is I cannot ping 169.254.1.1,so cannot ssh > in DOM1 either.First, kill ''kudzu'', ''keytable'' and ''gpm'' from the rc scripts. It looks like you''re using run level for, so: rm /etc/rc4.d/*{kudzu,gpm, keytable} Next, it looks like your rc scripts are trying to use DHCP to get an IP address, overriding the address you''re passing in on the command line. [you could use DHCP to configure the address, but it doesn''t look like you''ve configured such a server] Make sure that "BOOTPROTO=static" in /etc/sysconfig/network-scripts/ifcfg-eth0 Also check all the files under /etc/sysconfig/networking/ 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Thanks a lot! It''s just the problem of DHCP, now I can ssh in it. :) Qian On Wed, 31 Mar 2004, Ian Pratt wrote:> > > As said before, now the problem is I cannot ping 169.254.1.1,so cannot ssh > > in DOM1 either. > > First, kill ''kudzu'', ''keytable'' and ''gpm'' from the rc scripts. It > looks like you''re using run level for, so: > > rm /etc/rc4.d/*{kudzu,gpm, keytable} > > Next, it looks like your rc scripts are trying to use DHCP to > get an IP address, overriding the address you''re passing in on > the command line. [you could use DHCP to configure the address, > but it doesn''t look like you''ve configured such a server] > > Make sure that "BOOTPROTO=static" in > /etc/sysconfig/network-scripts/ifcfg-eth0 > > Also check all the files under /etc/sysconfig/networking/ > > 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Hi,
I have similar problem as the previous email--I cannot ping 169.254.1.1.
But the ways that Ian suggested don''t work for me.
When I create a new domain,
./xc_dom_create.py -Dvmid=1
Parsing config file ''/etc/xc/defaults''
VM image : "/boot/xenolinux.gz"
VM ramdisk : ""
VM memory (MB) : "16"
VM IP address(es) : "169.254.1.1"
VM block device(s) : "phy:hda12,hda12,w; phy:hda11,hda11,r"
VM cmdline :
"ip=169.254.1.1:169.254.1.0:155.99.182.1:255.255.254.0::eth0:on
root=/dev/hda12 ro 4 VMID=1"
VM started in domain 2
But when I used "./xc_dom_control.py list", there is only one domain.
Dom Name Mem(kb) CPU State Time(s)
0 Domain-0 480000 0 r- 5152
The output of the xen_read_console is in the attachment.
I have killed ''kudzu'', ''keytable'' and
''gpm'', and set "BOOTPROTO=static".
Could you help me figure out where is the problem?
Thanks.
Xiaofang
> > As said before, now the problem is I cannot ping 169.254.1.1,so cannot
ssh> > in DOM1 either.
>
> First, kill ''kudzu'', ''keytable'' and
''gpm'' from the rc scripts. It
> looks like you''re using run level for, so:
>
> rm /etc/rc4.d/*{kudzu,gpm, keytable}
>
> Next, it looks like your rc scripts are trying to use DHCP to
> get an IP address, overriding the address you''re passing in on
> the command line. [you could use DHCP to configure the address,
> but it doesn''t look like you''ve configured such a server]
>
> Make sure that "BOOTPROTO=static" in
> /etc/sysconfig/network-scripts/ifcfg-eth0
>
> Also check all the files under /etc/sysconfig/networking/
>
> Ian
Excuse me, I change the previous question into this one:
Still cannot ping 169.254.1.1.
When I create a new domain,
./xc_dom_create.py -Dvmid=1
Parsing config file ''/etc/xc/defaults''
VM image : "/boot/xenolinux.gz"
VM ramdisk : ""
VM memory (MB) : "16"
VM IP address(es) : "169.254.1.1"
VM block device(s) : "phy:hda12,hda12,w; phy:hda11,hda11,w"
VM cmdline :
"ip=169.254.1.1:169.254.1.0:155.99.182.1:255.255.254.0::eth0:on
root=/dev/hda11 ro 4 VMID=1"
VM started in domain 6
"./xc_dom_control.py list" gives
Dom Name Mem(kb) CPU State Time(s)
0 Domain-0 480000 0 r- 11240
6 This is VM 1 16384 0 -- 26
The output of the xen_read_console is in the attachment.
Thanks a lot for your time.
Xiaofang
> I have similar problem as the previous email--I cannot ping 169.254.1.1. > But the ways that Ian suggested don''t work for me. > > <...> > > But when I used "./xc_dom_control.py list", there is only one domain. > Dom Name Mem(kb) CPU State Time(s) > 0 Domain-0 480000 0 r- 5152The domain isn''t running -- so it''s unlikely to respond to network packets.> [1] root_device_name = hda12 > [1] FAT: bogus logical sector size 0 > [1] UMSDOS: msdos_read_super failed, mount aborted. > [1] FAT: bogus logical sector size 0 > [1] FAT: bogus logical sector size 0 > [1] Kernel panic: VFS: Unable to mount root fs on 03:0cIt failed to mount a root fs. In fact, the domain didn''t find any virtual block devices. This isn''t a networking problem. Try executing ''xc_dom_control.py listvbds'' before the domain dies and see if anything is listed. If the domain dies too quickly for you to be able to list its VBDs, then temporarily remove the call to xc.domain_start() in xc_dom_create.py. -- Keir ------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel