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
>
tmp
Description: Text document
|
Home