Hello all, I''m about to separate the existing two (2) Apache 2.x virtual hosts into its own virtual OS so that for each virtual hosts with a different domain should have its own private place. And I came across this Xen and VServer which I believe a good solution for my needs. I am currently running Debian GNU/Linux Etch AMD64 on my Dell PowerEdge 1950. I already installed the following packages on my Debian GNU/Linux Etch AMD64 system: # dpkg -l | grep vserver ii linux-image-2.6.18-5-xen-vserver-amd64 2.6.18.dfsg.1-13etch2 Linux 2.6.18 image on AMD64 ii linux-modules-2.6.18-5-xen-vserver-amd64 2.6.18.dfsg.1-13etch2 Linux 2.6.18 modules on AMD64 ii util-vserver 0.30.212-1 user-space tools for Linux-VServer virtual p ii vserver-debiantools 0.3.4 Tools to manage debian virtual servers ii xen-linux-system-2.6.18-5-xen-vserver-amd64 2.6.18.dfsg.1-13etch2 XEN system with Linux 2.6.18 image on AMD64 # dpkg -l | grep xen ii linux-image-2.6.18-5-xen-vserver-amd64 2.6.18.dfsg.1-13etch2 Linux 2.6.18 image on AMD64 ii linux-modules-2.6.18-5-xen-vserver-amd64 2.6.18.dfsg.1-13etch2 Linux 2.6.18 modules on AMD64 ii xen-hypervisor-3.0.3-1-amd64 3.0.3-0-2 The Xen Hypervisor on AMD64 ii xen-linux-system-2.6.18-5-xen-vserver-amd64 2.6.18.dfsg.1-13etch2 XEN system with Linux 2.6.18 image on AMD64 ii xen-utils-3.0.3-1 3.0.3-0-2 XEN administrative tools ii xen-utils-common 3.0.3-0-2 XEN administrative tools - common files And now, I''m running the newly installed Linux kernel: # uname -r 2.6.18-5-xen-vserver-amd64 Also, Xen is currently running on my server: # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 256 8 r----- 136.2 # xm info host : host release : 2.6.18-5-xen-vserver-amd64 version : #1 SMP Thu Aug 30 03:23:33 UTC 2007 machine : x86_64 nr_cpus : 8 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 1861 hw_caps : bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001 total_memory : 4095 free_memory : 3766 xen_major : 3 xen_minor : 0 xen_extra : .3-1 xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Tue Oct 17 22:09:52 2006 +0100 cc_compiler : gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19) cc_compile_by : ultrotter cc_compile_domain : debian.org cc_compile_date : Fri Nov 3 00:21:27 CET 2006 xend_config_format : 2 I was also planning to create a "template" OS which is also based on Debian GNU/Linux Etch AMD64, so I created the following LVs for my "template" OS: # lvdisplay -Ca | grep lvxen lvxen_root vg0 -wi-ao 1.00G lvxen_swap vg0 -wi-ao 1.00G lvxen_tmp vg0 -wi-ao 1.00G lvxen_usr vg0 -wi-ao 2.00G lvxen_var vg0 -wi-ao 4.00G And mounted them: # mount | grep xen /dev/mapper/vg0-lvxen_root on /mnt/xen type ext3 (rw) /dev/mapper/vg0-lvxen_tmp on /mnt/xen/tmp type ext3 (rw) /dev/mapper/vg0-lvxen_usr on /mnt/xen/usr type ext3 (rw) /dev/mapper/vg0-lvxen_var on /mnt/xen/var type ext3 (rw) none on /mnt/xen/proc type proc (rw) After that, I moved to the /mnt/xen/ directory and did this: # debootstrap --arch amd64 etch . http://ftp.us.debian.org/debian/ My question now is: what will be my next move? My plan is to run a single Xen domU and inside of that, I will run two (2) VServers that runs two (2) different Debian GNU/Linux Etch AMD64 intended for my two (2) web servers (domains). I am now lost. Please take note that I haven''t changed any Xen or VServer related configuration files as of this time. Please advice. Thank you in advance. GNUbie _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
GNUbie wrote:> Hello all, > > I''m about to separate the existing two (2) Apache 2.x virtual hosts into > its own virtual OS so that for each virtual hosts with a different > domain should have its own private place. And I came across this Xen > and VServer which I believe a good solution for my needs. I am > currently running Debian GNU/Linux Etch AMD64 on my Dell PowerEdge 1950. > > I already installed the following packages on my Debian GNU/Linux Etch > AMD64 system: >[...]> Please advice. > > Thank you in advance. > > GNUbie >You''ll need to modify your template domU''s /etc/fstab (see how to write a Xen config first), and since you''re using Debian you''ll also have to fill-in /etc/network/interfaces and /etc/hostname. Then you''ll need to create a Xen configuration file (e.g. /etc/xen/my-template-domU) for your template domU. Once that''s done you should be able to boot into it and watch the progress of the domU''s console, then be able to login... # xm create -c my-template-domU After that you can create copies of your Logical Volumes, alter their contents slightly (network config etc), create new Xen config files for them, and start them as new DomUs. There are now various tools to help you (e.g. Debian''s xen-tools package), so check them out first. Read the Xen docs and Wiki and check out the man page for xm for more info. Simon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Simon Capstick wrote:> GNUbie wrote: >> Hello all, >> >> I''m about to separate the existing two (2) Apache 2.x virtual hosts >> into its own virtual OS so that for each virtual hosts with a >> different domain should have its own private place. And I came across >> this Xen and VServer which I believe a good solution for my needs. I >> am currently running Debian GNU/Linux Etch AMD64 on my Dell PowerEdge >> 1950. >> >> I already installed the following packages on my Debian GNU/Linux Etch >> AMD64 system: >> > > [...] > >> Please advice. >> >> Thank you in advance. >> >> GNUbie >> > > You''ll need to modify your template domU''s /etc/fstab (see how to write > a Xen config first), and since you''re using Debian you''ll also have to > fill-in /etc/network/interfaces and /etc/hostname. > > Then you''ll need to create a Xen configuration file (e.g. > /etc/xen/my-template-domU) for your template domU. > > Once that''s done you should be able to boot into it and watch the > progress of the domU''s console, then be able to login... > > # xm create -c my-template-domU > > After that you can create copies of your Logical Volumes, alter their > contents slightly (network config etc), create new Xen config files for > them, and start them as new DomUs. > > There are now various tools to help you (e.g. Debian''s xen-tools > package), so check them out first. > > Read the Xen docs and Wiki and check out the man page for xm for more info. > > Simon >.. Oh and don''t forget to unmount your DomU filesystems in Dom0 before you try running a DomU, although you should get a warning about this. Simon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users