On Tuesday 03 July 2007 16:04, Gerry Reno wrote:
on ours, they simply multihonme the nic. eg.. eth0 primary addy is host, eth0:0 is virtual1 eth0:2 is virtual 2 etc... but yeah, to the virtual machine it appears to be its own nic even though the virtual server has no networking code to mess with a nic. > Joseph Mack NA3T wrote: > > On Tue, 3 Jul 2007, Gerry Reno wrote: > > > > > >> VE's are basically just kernel-based supercharged > >> chroot environments. > >> > > > > So they all see the same NIC (assuming a one NIC box)? If > > you have 4 VE's on the box and each has an httpd running, > > does each need a separate IP to listen on? (the answer has > > to be yes). > > > Of course, on a virtual NIC. > > > If you have 4 CPUS and 3 of the VE's aren't doing a whole > > lot, will the 4th VE be able to schedule its jobs to all the > > CPUs? (again the answer has to be yes). > > > > Joe > > > > > > > _______________________________________________ > LinuxVirtualServer.org mailing list - [email protected] > Send requests to [EMAIL PROTECTED] > or go to http://lists.graemef.net/mailman/listinfo/lvs-users > -- Rio _______________________________________________ LinuxVirtualServer.org mailing list - [email protected] Send requests to [EMAIL PROTECTED] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
