| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
[Xen-users] Network configuration after upgrade
Hello,
A bit of history
================
1) I've got a normal 2.6.20 x64 Fedora 6 Linux server running several things
2) I've downloaded and installed the XenSource Administrator Console for
Windows
3) I've added 2.6.20-1.2962.fc6xen kernel, xen and vnc packages on my Linux
server
4) I rebooted the Linux server, and started xend as per user guide
Configuration
=============
Now, running ifconfig -a, I get:
eth0 Link encap:Ethernet HWaddr 00:10:18:19:A7:20
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210:18ff:fe19:a720/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1425 errors:0 dropped:0 overruns:0 frame:0
TX packets:1353 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:931363 (909.5 KiB) TX bytes:183662 (179.3 KiB)
[some eth0 aliases]
eth1 Link encap:Ethernet HWaddr 00:18:8B:1C:88:A0
inet addr:192.168.123.101 Bcast:192.168.123.255
Mask:255.255.255.0
inet6 addr: fe80::218:8bff:fe1c:88a0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:188929 errors:0 dropped:0 overruns:0 frame:0
TX packets:228205 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:62713643 (59.8 MiB) TX bytes:142612275 (136.0 MiB)
Interrupt:16
[some eth1 aliases]
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10986 errors:0 dropped:0 overruns:0 frame:0
TX packets:10986 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7103218 (6.7 MiB) TX bytes:7103218 (6.7 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1425 errors:0 dropped:0 overruns:0 frame:0
TX packets:1350 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:937063 (915.1 KiB) TX bytes:191837 (187.3 KiB)
Interrupt:16
veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1353 errors:0 dropped:0 overruns:0 frame:0
TX packets:1425 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:183662 (179.3 KiB) TX bytes:931363 (909.5 KiB)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
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:290 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:51538 (50.3 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:313 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:49141 (47.9 KiB) TX bytes:0 (0.0 b)
My xen configuration is:
(xend-http-server yes)
(xend-unix-server yes)
(xend-unix-path /var/lib/xend/xend-socket)
(xend-port 8000)
(xend-address '')
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$
^triton\\.$ ^192\\.168\\.123\\.*$')
(network-script network-bridge netdev=eth1)
(vif-script vif-bridge)
(dom0-min-mem 256)
(dom0-cpus 0)
(vncpasswd '')
Problems:
1) Using the Windows based Admin Console, I cannot connect to the XenServer
due to not knowing which address to connect to: 192.168.123.101 gives an
error, 192.168.122.1 gives an error 192.168.1.6 gives an error. All errors
state "Not a XenServer Host".
2) Installed the RedHat Virtual Machine Manager, I can immediately connect
to a local XenServer, no problems.
3) HTTP access doesn't seem to work
All the above 3 points are *very likely* due to fact that I wouldn't know
what to connect to, and honestly, for me at least, the documentation
regarding Xen is not all too revealing to understand how I should be setting
up my physical NIC cars (1 internal, 1 ISP connection), so as to connect to
the XenServer host and start playing around with virtual machines.
Can anybody please give me some advise?
Regards,
Guus
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] Network configuration after upgrade,
Guus Leeuw jr. <=
|
|
|
| |
|
Home