OpenVZ Forum


Home » General » Support » openSUSE 11 template - please test
openSUSE 11 template - please test [message #34510] Tue, 13 January 2009 18:39 Go to next message
riggwelter is currently offline  riggwelter
Messages: 1
Registered: January 2009
Junior Member
I've produced a template of openSUSE 11.0 (11.1 to follow). I could test it myself but I'm not an OpenVZ expert. If anyone would like to seriously put it through its paces, I'd appreciate it.

It can be accessed at http://jamesthevicar.com/index.cgi/1230823878opensuse_openvz _image.jtv or if prefered, I can attach it to the forum.
Re: openSUSE 11 template - please test [message #35179 is a reply to message #34510] Fri, 06 March 2009 21:04 Go to previous message
brushek is currently offline  brushek
Messages: 1
Registered: March 2009
Junior Member
Hello,

I have tested Your opensuse 11 template. Network dosen't start at boot time, I need to do vzctl enter and then /etc/init.d/network start - then network is up.

suse11:/ # ip a l
1: lo: <LOOPBACK> mtu 16436 qdisc noop
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: venet0: <BROADCAST,POINTOPOINT,NOARP> mtu 1500 qdisc noop
link/void
suse11:/ #

suse11:/ # /etc/init.d/network start
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8 done
venet0
venet0 IP address: 127.0.0.1/32
venet0:0 IP address: x.x.x.x/ done
Setting up service network . . . . . . . . . . . . . . done.
suse11:/ #
suse11:/ # ip a l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
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
3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/void
inet 127.0.0.1/32 scope host venet0
inet x.x.x.x/32 scope global venet0:0




Also df -h dosn't show any data about / partition inside container (I think it could be suse-related).

suse11:/ # df -h
Filesystem Size Used Avail Use% Mounted on
udev 5.0G 40K 5.0G 1% /dev

suse11:/ # cat /proc/mounts
/dev/simfs / simfs rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
udev /dev tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0

Did You encounter this strange behavior too ?

Kernel: 2.6.18 with rh5 patchset


Regards
brushek
Previous Topic: [*SOLVED*] Assigning IP from within a VE
Next Topic: RTNETLINK answers: File exists for veth interface
Goto Forum:
  


Current Time: Mon Jul 28 18:07:57 GMT 2025

Total time taken to generate the page: 0.48287 seconds