anyone knows how to resolve this? after I setup my virtual machines, then turned off PC, and next boot up within Xen kernel I cannot get ping or internet access?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There’s not a lot to go on here. Which version of OpenSUSE? What network
information do you have? Can you do anything from the host or VMs (or
neither)? Do other boxes on the network work? What is the output from:
ip addr show
ip route show
cat /etc/resolv.conf
uname -a
Good luck.
niceseb wrote:
> anyone knows how to resolve this? after I setup my virtual machines,
> then turned off PC, and next boot up within Xen kernel I cannot get ping
> or internet access?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJKHxT3AAoJEF+XTK08PnB5B78QAKSV7MaDh492OSU6TuNe6Tnz
CsaEW26iIfGeQWRyL4SvnoU1Glhzy4zh2lyBXp2duFg/rWsqnaVuJjMprL9eaPcg
YvEmhMi56n6BVmfur6IEQk3eJvlj5P+2TZ6g1ZVxfx4Iw9KTa+ks0F8dDXppfDKG
66UM0pbGO9FtfesigswnvL6IOTWIwhiRVLHukzxQh0s1CC1+ky/o+M0ZuWER4Pnh
hwI7Tim4p8va9vmXPgarc373RZYTEIcMlyU0xQzz7lQ0Ms7D0mhzzt214Ixs2j0P
aTDjmTY2b/shKvjWDMW+Ju5hAxNHxx31EPV8OnPCvRB3jzhfBg35U6HyowZq6lOs
2NmazdlKsr+Hf1A1c0oQ0HSvvEEVTCq0ZGtzDOHjAy16flXZnMV/6GNQmGZegLWV
HHwUYc0wQyEP01iDbjemq9ZVaalcUGJXLMCNvLgyAU9EJ4hQhv4E98L/y8X/lOWH
+vV/El8YYFtDOrLxfGwtaKMM1i4juk1nMBUUCYXn8fOxIm5RgCV1sXWl90Z768VG
t2zzjYof4MUU/m3Acf8IbJ3ZFOL9tc7TAHY+IaF3vxz8UJgVfT9OjsSVB/jk0F15
sGD52Cm4szm7nzGc1DS7afIQoET6p5HwmLg3s1y6V1recRrQdQWTrmOtEPjcXO1d
WH3P4Fds7N5oYCQxYGpY
=4Bsn
-----END PGP SIGNATURE-----
from host:
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: peth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 100
link/ether 00:1a:a0:8e:48:7d brd ff:ff:ff:ff:ff:ff
inet6 fe80::21a:a0ff:fe8e:487d/64 scope link
valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 00:1a:a0:8e:48:7d brd ff:ff:ff:ff:ff:ff
inet 192.168.0.3/24 brd 192.168.0.255 scope global eth0
inet6 fe80::21a:a0ff:fe8e:487d/64 scope link
valid_lft forever preferred_lft forever
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether ce:94:93:29:df:8c brd ff:ff:ff:ff:ff:ff
inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
inet6 fe80::cc94:93ff:fe29:df8c/64 scope link
valid_lft forever preferred_lft forever
ip route show
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.3
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
169.254.0.0/16 dev eth0 scope link
127.0.0.0/8 dev lo scope link
default via 192.168.0.1 dev eth0
cat /etc/resolv.conf
/etc/resolv.conf file autogenerated by netconfig!
Before you change this file manually, consider to define the
static DNS configuration using the following variables in the
/etc/sysconfig/network/config file:
NETCONFIG_DNS_STATIC_SEARCHLIST
NETCONFIG_DNS_STATIC_SERVERS
NETCONFIG_DNS_FORWARDER
or disable DNS configuration updates via netconfig by setting:
NETCONFIG_DNS_POLICY=’’
See also the netconfig(8) manual page and other documentation.
Note: Manual change of this file disables netconfig too, but
may get lost when this file contains comments or empty lines
only, the netconfig settings are same with settings in this
file and in case of a “netconfig update -f” call.
Please remove (at least) this line when you modify the file!
uname -a
Linux linux-gvsh 2.6.27.21-0.1-xen #1 SMP 2009-03-31 14:50:44 +0200 i686 i686 i386 GNU/Linux
this is the feedback, am I not setting any files correcting?
But within the Xen kernal, when I start the Yast -> Network Devices -> Network Settings I get a message
A Xen network bridge was detected.
Due to the renaming of network interfaces by the bridge script,
network interfaces should not be configured or restarted.
See/usr/share/doc/packages/xen/README.SuSE for details
but after reading few times I still not sure what to set?
also not sure why after within Xen kernel, the Network Settings -> Overview’s Add, Edit and Delete are non selectable?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ah, well, two things come to mind. First you have two devices on the same
network (br0 and eth0) with different IP addresses. SLES 11 makes this
all much simpler. First, Yast works for network things when using the Xen
kernel (doesn’t in SLES 10 and it’s made to work that way). Second, it
sets up those two devices for you nicely (I don’t remember SLES 10 SP2
doing it for me). If possible I"d highly recommend going with SLES 11 for
Xen. Based on my experience (somewhat limited; I’m not a Xen expert yet)
it has been better.
Either way give your IP address to the br0 device and then set that device
to bridge with eth0. Set eth0 to be not configured. In SLES 11 there is
an option for this that it says is to be used with bonded devices, but it
also works with the bridged device. All traffic then goes through
br0/eth0 once instead of, like in your system, having two options to go
out or come back. I’m not sure how the OS tries to handle your situation
but every report I’ve heard of one box with two interfaces on the same
network that wasn’t doing bonding was a bad experience.
Good luck.
niceseb wrote:
> also not sure why after within Xen kernel, the Network Settings →
> Overview’s Add, Edit and Delete are non selectable?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJKIXLEAAoJEF+XTK08PnB5TdkQAInJiqp387Az/oH6qF/k2YQ5
lnXxm+v1KNMxJOOkBJ0Yw7HW/291Uz+J0nZQHqfc1byHvVPjp1y91Pb1Uwp76JNv
wUizBTcynQHbKTvA4nAP5QDjg2347TRrEYwATVhox41fVgqmItOYcU6bXwfL8nke
awBRPkxxF0lB/70NqrRstR1/sfB6eUJfFf/RwOA7A4dJobT3mvt1NUpSCqcbH2tZ
/PBAgyzGAzVGN9QkiAz64036BcN3yosdBpib9ilJQB6euY9ni5KFCEZt4Fcn/2Pw
Rg17njS6OQ4FV0ch7etICJi5VbVPpyY5ORTRUX2lFdBy92Bb7O3DpfQ6T6v08b57
N/f/FUZnQhN+tZ2R7Wvn09I1pbmHdXtFpoxv5UHSYCYPBrUrTlkKom8UCkchO6fz
XrqNAiw0EbsDCzXczN4+reXxmebfrLEddBIMWO+nuyfGt3jP4R6g+e3jjvjeKCnt
XL7hudF0VaYQB8Ur8ni1B3SXRbcIC1KMdE+THevLKqQF5V4uKWbPtk/VqcIelECx
AvCeYllxQJ62oVVqbFVXAVzv5BF+abAHwB0m8TgXEqz5l7gj6O25D6amoOWQIXc0
soQrYBdrPr0AQAowLdIUP+AHGBPI6jSKjrP45y8h633FoxKkAk9WaYDyZXDDrXzB
FVvM9DdrUwa7dUHm27SL
=bE9V
-----END PGP SIGNATURE-----