On Friday 15 September 2006 01:45, Chuck wrote:
> On Thursday 14 September 2006 16:07, Herbert Poetzl wrote:
>
> ok... one quick question... if the host has this patch, must the guest have
> it if the guest will not be using more than 1 ip or must all guests match
> the kernel in this patch regardless? i guess a better way to ask is...
> with the host patched, can i patch only the guests needing more than 16 ip
> addys or must i patch every guest? planning whether i would have to
> provided the template patched or not.
>
This patch just defines the maximum number of IP addresses that can be
assigned to a guest. As the kernel is "host-side" and guest are pure
userspace, guest are not affected at all be the maximum number of IPs it can
have. (it's not the guest which selects its IPs anyhow)
The guest should be able to run correctly in each case.
Bruno
> > On Thu, Sep 14, 2006 at 12:44:30PM -0400, Chuck wrote:
> > > On Thursday 14 September 2006 12:18, Bruno wrote:
> > >
> > >
> > > oh .. to complete the explanation on our systems a guest would never
> > > address more than a single /24 but with the limitation that has to be
> > > divided among a gazillion guests instead..
> >
> > last time I checked, a /24 (or class C network) had 256
> > addresses (with 254 usable for ips) not a gazillion :)
> >
> > this aside, we will add it soon, but you can (for now)
> > just apply one of the 64address patches, to kernel and
> > tools, as I doubt it will cause much overhead ...
> >
> > HTH,
> > Herbert
> >
> > > > On Thursday 14 September 2006 16:27, Chuck wrote:
> > > > > someone mentioned the possibility of getting a setup on current
> > > > > vserver code that would take a /24 network and not have much if
> > > > > any slowdown.. has this ever been realized?
> > > >
> > > > I did some coding in that direction, but patch is not finished yet.
> > > > Hopefully I will get some more time after next week do continue
> > > > coding on it.
> > > >
> > > > My direction is assigning address elements to guests, either single
> > > > addresses or groups of addresses as range or mask. When there
> > > > is more than a single such item, on additional is created that
> > > > itentifies the complete range contaning the addresses of a guest.
> > > > Thus two guests with 20 IPs spread over two different /24 networks
> > > > wil be seen as a single range for most check wether IP is part of
> > > > the guest's address-space. Only on match of that outer boundary
> > > > checking of the idividual addresses or the guest is done. Mostly
> > > > missing is the handling of broadcast...
> > > >
> > > > Bruno
> > > > _______________________________________________
> > > > Vserver mailing list
> > > > Vserver@list.linux-vserver.org
> > > > http://list.linux-vserver.org/mailman/listinfo/vserver
> > >
> > > --
> > >
> > > Chuck
> > >
> > > "...and the hordes of M$*ft users descended upon me in their anger,
> > > and asked 'Why do you not get the viruses or the BlueScreensOfDeath
> > > or insecure system troubles and slowness or pay through the nose
> > > for an OS as *we* do?!!', and I answered...'I use Linux'. "
> > > The Book of John, chapter 1, page 1, and end of book
> > >
> > >
> > > _______________________________________________
> > > Vserver mailing list
> > > Vserver@list.linux-vserver.org
> > > http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Fri Sep 15 17:22:51 2006