Hello <at> all, I'm tried to work with XEN3 and SuSE but I've the problem with compiling my own kernel (SMP, 64GB). So I've read the artikel about openvz and think it's better for me because I only need linux VPS on i386 machines. Is it possible to patch a running SuSE Box with openvz? And how to setup a SuSE VPS on this host, are there any good HowTos for this? German is prefered. Thanks a lot Daniel
Which suse version do you have? Specifically, we do not currently provide suse rpms, but the ones made for redhat should be OK. Latest vzctl (an utility to control VPSs) version that fixes initscript to work with SuSE will be released today or tomorrow. As for the suse VPS, there is a opensuse-10 precreated VPS template available. Unfortunately for its networking to work it requires some stuff from kernel (sysfs support from inside a VPS), and this is off by default in our kernel. The situation will be fixed with the release of 068 (or later) kernel there sysfs can be turned on/off per VPS. For now, you need to change one config setting and recompile the kernel to get opensuse-10 template working. Our future plans include releasing a custom kernel which is basically SuSE kernel (all the SuSE patches and stuff) with OpenVZ functionality added. We will also be creating more suse templates. Kir. Daniel Bauer wrote: > Hello <at> all, > > I'm tried to work with XEN3 and SuSE but I've the problem with > compiling my own kernel (SMP, 64GB). So I've read the artikel about > openvz and think it's better for me because I only need linux VPS on > i386 machines. >(Continue reading)
Hi Kir, From: "Kir Kolyshkin" <kir@...> > Which suse version do you have? 9.3 or 10.0, I prefer 9.3, the VPS should be SuSE 9.3 > Specifically, we do not currently provide suse rpms, but the ones made > for redhat should be OK. Latest vzctl (an utility to control VPSs) > version that fixes initscript to work with SuSE will be released today > or tomorrow. > > As for the suse VPS, there is a opensuse-10 precreated VPS template > available. Unfortunately for its networking to work it requires some > stuff from kernel (sysfs support from inside a VPS), and this is off > by default in our kernel. The situation will be fixed with the release > of 068 (or later) kernel there sysfs can be turned on/off per VPS. For > now, you need to change one config setting and recompile the kernel to > get opensuse-10 template working. > > Our future plans include releasing a custom kernel which is basically > SuSE kernel (all the SuSE patches and stuff) with OpenVZ functionality > added. We will also be creating more suse templates. so is it possible to patch a 9.3 kernel with the sources of OpenVZ for the host and build templates von 9.3 for the clients? Daniel(Continue reading)
Daniel Bauer wrote: > From: "Kir Kolyshkin" <kir@...> > >> Daniel Bauer wrote: >> >>>> Which suse version do you have? >>> >>> >>> 9.3 or 10.0, I prefer 9.3, the VPS should be SuSE 9.3 >> >> >> OK. I remember that somebody created some SuSE templates, search in >> forum.openvz.org. > > > I've found this message: > http://forum.openvz.org/index.php?t=msg&th=190&start=0& > > and his site > http://web150.dd01.profihoster.net/ > > but there is only a template for SuSE 9.3 64bit server-image for > openVZ (155 MB) Ask the author about x86 (i386) template as well :) if he will have enough requests he may consider doing it :) >> If you are brave enough you can try doing it all yourself. This is >> not very complicated -- basically you need to create a chrooted(Continue reading)
From: "Kir Kolyshkin" <kir@...> > Daniel Bauer wrote: >> From: "Kir Kolyshkin" <kir@...> >>> Daniel Bauer wrote: >>>>> Which suse version do you have? >>>> >>>> 9.3 or 10.0, I prefer 9.3, the VPS should be SuSE 9.3 >>> >>> >>> OK. I remember that somebody created some SuSE templates, search in >>> forum.openvz.org. >> >> >> I've found this message: >> http://forum.openvz.org/index.php?t=msg&th=190&start=0& >> >> and his site >> http://web150.dd01.profihoster.net/ >> >> but there is only a template for SuSE 9.3 64bit server-image for >> openVZ (155 MB) > > Ask the author about x86 (i386) template as well :) if he will have > enough requests he may consider doing it :) > >>> If you are brave enough you can try doing it all yourself. This is >>> not very complicated -- basically you need to create a chrooted >>> environment with all the needed stuff installed. All the needed >>> stuff are libraries, startup scripts and init, some programs (like >>> ssh) etc. Then you run this in a VPS.(Continue reading)
Daniel Bauer wrote: > ok, that sounds good, I'll have a try with SuSE. > > I've started now with installing fedora-core 4 and updated the kernel > as mentioned, some prebuild VPS are still running. But how can I > access now some physical harddiscs? I need to mount /dev/sdd1 (my data > partition). See pages 66-67 of OpenVZ User's Guide. In short, here it is. You just enable device access for a given VPS, like this: vzctl set NNN --devnodes sdd1:rw --save Next, you create the device file (you can just cp /dev/sdd1 /vz/root/NNN/dev) Next, you mount your partition from inside a VPS as usual. > How to enable the second eth interface? You want it to be dedicated to a single VPS, or you just want to access some other network via it? In the first case, see page 68 of OpenVZ User's Guide. In the second case, use it as you would do on a normal Linux box, i.e. add IP, proper routes and everything should work. > so you update this kernel with actual patches and the OpenVZ Users could > install the new one everytime it's released?(Continue reading)
From: "Kir Kolyshkin" <kir@...> > Daniel Bauer wrote: > >> ok, that sounds good, I'll have a try with SuSE. >> >> I've started now with installing fedora-core 4 and updated the kernel >> as mentioned, some prebuild VPS are still running. But how can I >> access now some physical harddiscs? I need to mount /dev/sdd1 (my >> data partition). > > See pages 66-67 of OpenVZ User's Guide. In short, here it is. > > You just enable device access for a given VPS, like this: > vzctl set NNN --devnodes sdd1:rw --save > > Next, you create the device file (you can just cp /dev/sdd1 > /vz/root/NNN/dev) > > Next, you mount your partition from inside a VPS as usual. > >> How to enable the second eth interface? > > You want it to be dedicated to a single VPS, or you just want to > access some other network via it? > > In the first case, see page 68 of OpenVZ User's Guide. In the second > case, use it as you would do on a normal Linux box, i.e. add IP, > proper routes and everything should work. Hi Kir,(Continue reading)
From: "Kir Kolyshkin" <kir@...> > Daniel Bauer wrote: >> ok, that sounds good, I'll have a try with SuSE. Is there a howto for creating templates, or should I start with building the directory tree by myself? Why is the stuff double in private and root, I thougt that the root is only the mounted stuff from private? >> I've started now with installing fedora-core 4 and updated the kernel >> as mentioned, some prebuild VPS are still running. But how can I >> access now some physical harddiscs? I need to mount /dev/sdd1 (my >> data partition). > > See pages 66-67 of OpenVZ User's Guide. In short, here it is. > > You just enable device access for a given VPS, like this: > vzctl set NNN --devnodes sdd1:rw --save > > Next, you create the device file (you can just cp /dev/sdd1 > /vz/root/NNN/dev) > > Next, you mount your partition from inside a VPS as usual. Great!!! >> How to enable the second eth interface? > > You want it to be dedicated to a single VPS, or you just want to(Continue reading)
Daniel Bauer wrote: > From: "Kir Kolyshkin" <kir@...> > >> Daniel Bauer wrote: >> >>> ok, that sounds good, I'll have a try with SuSE. >> > Is there a howto for creating templates, or should I start with > building the directory tree by myself? No, there is no formal howto, but somehow people manage to find out all the details. It is probably not that hard, and there are two approaches: (A) Currently our template tools can use yum-enabled repositories, so the way to go is: 1. Take yum-enabled repo (or create one from a bunch of RPMS using createrepo). 2. Take one of the existing OS templates metadata and find out what is it. 3. Create a metadata for your OS template, based on the above. 4. Run vzpkgcache to create a template cache. (B) Alternative approach is just to install a set of packages into chrooted environment (in RPM world you use 'rpm -i --root' for that, in Debian world you use 'debootstrap'), then do some fine tuning and finally tar this environment. The final tarball can be placed to /vz/template/cache and used as a template. Basically, you need to install some basic stuff - system libraries, init scripts, useful binaries etc.(Continue reading)
> I've three nics, but only one venet0. > i.e. eth0 is connected to intranet for use of VPS > (10.x.x.x) > eth1 is connected to internet for use of VPS > (20.x.x.x) > eth2 s connected to intranet only for use of the Host > (30.x.x.x) > > I'd like to use: > VPS1: intranet (eth0) > VPS2: internet (eth1) > VPS3: intranet (eth0) + internet (eth1) > > On the host (eth2) I don't want to have an IP of the intranet or > internet, the nics should be used for the VPS. > > As I understand it's not possible to share a real nic with Host and > diff. VPS, so howto setup this configuration? You should assign IP from intranet to VPS1, IP for internet to VPS2 and both such IPs to VPS3. > > Daniel > > _______________________________________________ > Users mailing list > Users@... > https://openvz.org/mailman/listinfo/users -- --(Continue reading)
RSS Feed23 | |
|---|---|
23 | |
24 | |
22 | |
36 | |
23 | |
42 | |
29 | |
72 | |
29 | |
49 | |
41 | |
56 | |
64 | |
113 | |
31 | |
46 | |
39 | |
83 | |
55 | |
40 | |
66 | |
8 | |
33 | |
75 | |
30 | |
33 | |
17 | |
21 | |
37 | |
41 | |
11 | |
52 | |
46 | |
122 | |
76 | |
48 | |
88 | |
67 | |
61 | |
86 | |
53 | |
57 | |
22 | |
45 | |
47 | |
42 | |
50 | |
28 | |
25 | |
58 | |
53 | |
130 | |
92 | |
94 | |
35 | |
93 | |
95 | |
65 | |
70 | |
107 | |
41 | |
68 | |
81 | |
104 | |
208 | |
85 | |
80 | |
92 | |
62 | |
51 | |
54 | |
98 | |
95 | |
147 | |
56 | |
55 | |
77 | |
50 | |
47 | |
23 | |
43 | |
15 | |
39 | |
62 | |
19 | |
66 | |
36 | |
3 | |
8 | |
18 | |
1 |
