I can recreate my system from backup in
Seconds Minutes Hours Days Weeks Never tested Never backed up ( 454 votes ~ 6 comments )
You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.
To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.
This is the comment you were replying to, attached to the weblog Using vserver
#5 Re: vserver vs xen (and best-practices) Posted by Steve (80.68.xx.xx) on Thu 22 Mar 2007 at 11:09 I use Xen internally for providing seperate machines, these are used for things like running my master CFengine server, or to provide a build-environment for Debian packages. VServer could easily do this. Where it fails is allowing interesting network setup. With Xen I can be very flexable and setup different networks linked with VPNs, etc. VServer doesn't seem suited to that kind of setup, since the networking is shared rather than virtualised. The other reason it fails, for me, is that each guest uses the same kernel. I like to have different ones - right now I'm running three different Xen kernels: The stock Debian packaged one for most of the guests. A custom one I had to build to get NFS ROOT support - as described on this site previously. I super-stripped down tiny one for "small" guests. Hopefully the first and second will become identical soon - I keep meaning to report a bug asking for the Debian kernels to have the NFSROOT option set, but I've not yet done so. Actually I'm not sure if VServer can boot over NFS? If it can't thats another reason for it to fail! Steve
I use Xen internally for providing seperate machines, these are used for things like running my master CFengine server, or to provide a build-environment for Debian packages.
VServer could easily do this.
Where it fails is allowing interesting network setup. With Xen I can be very flexable and setup different networks linked with VPNs, etc.
VServer doesn't seem suited to that kind of setup, since the networking is shared rather than virtualised.
The other reason it fails, for me, is that each guest uses the same kernel. I like to have different ones - right now I'm running three different Xen kernels:
Hopefully the first and second will become identical soon - I keep meaning to report a bug asking for the Debian kernels to have the NFSROOT option set, but I've not yet done so.
Actually I'm not sure if VServer can boot over NFS? If it can't thats another reason for it to fail!
Steve
Posting Format:
Inappropriate comments will be removed.
Some help on entry formatting is available
Username:
Password:
[ Advanced Login ]
Register Account
