On Thu, 30 Mar 2017, Ludovic Orban wrote:
; I personally don't need ipadm in my LX zones, nerver missed it and I'm
; pretty certain I wouldn't use it even if it was available.
Same here.
Andy
--
Citrus IT Limited | +44 (0)870 199 8000 | enquir...@citrus-it.co.uk
Rock House Farm | Green Moor
I personally don't need ipadm in my LX zones, nerver missed it and I'm
pretty certain I wouldn't use it even if it was available. I'd *much*
prefer to have 7388 though (sorry for insisting, I couldn't resist ;-))
On Thu, Mar 30, 2017 at 9:19 AM, Guenther Alka wrote:
>
On Thu, 30 Mar 2017, Guenther Alka wrote:
I would prefer a more ESXi like behaviour where settings
about hardware like (lofi) disks, CPU, RAM, vnics are zone
settings while network configuration is done by the VM
itself with the different but regular Linux tools and ways.
The "regular Linux
Michael Talbott writes:
> I have experienced the same /etc/resolv.conf issue in a CentOS 6 and 7 LX
> zones. No DNS servers get propagated from zonecfg.
Me, too. The default search domain does get set, however. Maybe it
is a trivial thing.
Regards -- Volker
--
On Thu, 30 Mar 2017, Michael Talbott wrote:
I have experienced the same /etc/resolv.conf issue in a CentOS 6 and
7 LX zones. No DNS servers get propagated from zonecfg.
The only way it could possibly work is if /etc/resolv.conf gets
updated in the zone. This is because native user-space
> On Mar 30, 2017, at 3:19 AM, Guenther Alka wrote:
>
> Setting ip properties atthe virtualisation layer
> seems not straight forward to me. Lately I was
> asked about the problem where DNS onUbuntu 16
> was not working despite the setting in the zone.cfg
> (Configurating
I have experienced the same /etc/resolv.conf issue in a CentOS 6 and 7 LX
zones. No DNS servers get propagated from zonecfg.
Oh, and I am on the same boat with ipadm. Would likely never use it inside an
LX zone.
Michael
> On Mar 30, 2017, at 12:21 PM, Dan McDonald wrote:
> On Mar 30, 2017, at 4:26 PM, Bob Friesenhahn
> wrote:
>
> The only way it could possibly work is if /etc/resolv.conf gets updated in
> the zone. This is because native user-space apps/libraries take care of the
> DNS lookups rather than kernel code.
Check
On Thu, 30 Mar 2017, Dan McDonald wrote:
On Mar 30, 2017, at 4:26 PM, Bob Friesenhahn
wrote:
The only way it could possibly work is if /etc/resolv.conf gets updated in the
zone. This is because native user-space apps/libraries take care of the DNS
lookups
> On Mar 30, 2017, at 5:02 PM, Bob Friesenhahn
> wrote:
>
> On Thu, 30 Mar 2017, Dan McDonald wrote:
>
>>
>>> On Mar 30, 2017, at 4:26 PM, Bob Friesenhahn
>>> wrote:
>>>
>>> The only way it could possibly work is if
On Thu, Mar 30, 2017 at 04:02:52PM -0500, Bob Friesenhahn wrote:
> Linux DHCP can overwrite files at any time, possibly weeks after boot.
You can configure it not to; for example, with dhcpcd, you would use the
option '--nohook resolv.conf'. Other clients have similar options.
On Thu, 30 Mar 2017, Paul B. Henson wrote:
Linux DHCP can overwrite files at any time, possibly weeks after boot.
You can configure it not to; for example, with dhcpcd, you would use the
option '--nohook resolv.conf'. Other clients have similar options.
This is all very true.
Something I
I'd like to see a way that network configuration can be disabled from
within the zone so that it's set by the host admin and not the zone admin
(assuming they are different people).
Is this a possibility?
On Mar 30, 2017 5:04 PM, "Dan McDonald" wrote:
>
> > On Mar 30, 2017,
> On Mar 30, 2017, at 5:11 PM, Brian Hechinger wrote:
>
> I'd like to see a way that network configuration can be disabled from within
> the zone so that it's set by the host admin and not the zone admin (assuming
> they are different people).
I thought more people would
14 matches
Mail list logo