On 5/24/19 12:21 PM, Andrija Panic wrote:
In other words - you are hitting an internal interface of a VR?
The VR has two NIC's. I presume that the Guest NIC as vs the Control NIC
is the "internal" NIC?
TypeShared
Traffic TypeGuest
Network NameShared
Netmask 255.255.0.0
In other words - you are hitting an internal interface of a VR?
I would replace (for a test) bind9 with just the default setup of DNSmasq,
while specifying it's uper/ROOT DNS servers to be the VR IP - i.e. client
--> DNSmasq (internal server) --> DNSmasq (VR).
See if that work - so you can draw
On 5/24/19 10:16 AM, Andrija Panic wrote:
Eric,
your BIND9 servers is on a "Public" network (trying to talk to the Public
IP of the VR during forwarding DNS requests) or a VM inside an Isolated
network behind VR)?
It's on *a* public network, but not *the* public network. I don't have
any
Eric,
if you are sucessful in your interesting project - please consider a blog
post somewhere (and share here on ML) - it always helps the community.
Cheers
Andrija
On Fri, 24 May 2019 at 03:11, Eric Pretorious wrote:
> Thank you, Rohit:
>
> Commenting-out the portions of XML related to the
Eric,
your BIND9 servers is on a "Public" network (trying to talk to the Public
IP of the VR during forwarding DNS requests) or a VM inside an Isolated
network behind VR)?
Andrija
On Fri, 24 May 2019 at 02:15, Eric Lee Green
wrote:
> I had this working under 4.9. All I did was, on my main
Piotr,
yes, sorry for the confusion - in 4.12 there is only
"enable.additional.vm.configuration' to be enabled - that second global
setting thing (from video slides) you mentioned, is in MASTER, yet to come
(probably 4.13).
4.12 should, besides specific XML chunks needed for DPDK, also support
Hi Andrija,
Yes, I'm testing it on 4.12 and I can confirm that with the example of
"hugepages" everything works as it should.
I do not only understand this option, I do not see it in global settings even
as root admin:
A configurable global config 'allow.additional.vm.configuration.list.kvm'
