More info:
When I start the nat network "vagrant-libvirt", 2 process dnsmasq are
started with the same configuration:
nobody 474777 1 0 18:20 ? 00:00:00 /usr/bin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/vagrant-libvirt.conf --leasefile-ro
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
root 474778 474777 0 18:20 ? 00:00:00 /usr/bin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/vagrant-libvirt.conf --leasefile-ro
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
Is that normal?
When start the routed network "vagrant-puppet0" (see pastebin) only 1
process is started
nobody 470306 1 0 17:55 ? 00:00:00 /usr/bin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/vagrant-puppet0.conf --leasefile-ro
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
When I see the (vagrant-libvirt) /var/lib/libvirt/dnsmasq/virbr1.macs
content is
[
{
"domain": "node01",
"macs": [
"52:54:00:5a:a3:fb"
]
},
{
"domain": "node02",
"macs": [
"52:54:00:7d:b1:b8"
]
},
]
But if I see the content of /var/lib/libvirt/dnsmasq/virbr1.status
(vagrant-libvirt) I see this:
[
{
"ip-address": "192.168.121.154",
"mac-address": "52:54:00:7d:b1:b8",
"hostname": "node02",
"client-id": "ff:d7:6b:blablabla",
"expiry-time": 1569623017
}
]
This file should be have both configuration, I guess, but when I start
node02 after node01, the node01 status is replaced by node02 status, that
is ok?
Cheers.
On Friday, September 27, 2019 at 12:26:19 PM UTC-3, Carlos Albornoz wrote:
>
> Hi Alvaro,
>
> Sure, https://pastebin.com/BkCwLEsu (is more large but essentially is
> that)
>
> I think is not a configuration problem, on Debian work ok, may be dnsmasq
> have some issue with the dhcp.
>
> On Thursday, September 26, 2019 at 5:31:11 PM UTC-3, Alvaro Miranda
> Aguilera wrote:
>>
>> can you share both Vagrantfiles ?
>>
>> On Thu, Sep 26, 2019 at 9:12 PM Carlos Albornoz <[email protected]>
>> wrote:
>>
>>> Hi, I have installed vagrant-2.2.5-2 + libvirt as provider on Archlinux,
>>> when up a VM the nat network set correctly the IP, but when up a second VM,
>>> dhcp lease the same IP, with the obvious network problems for that
>>> configuration, any idea what is happens?
>>>
>>> Cheers.
>>>
>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> IRC: #vagrant on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Vagrant" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/vagrant-up/15dd3d8a-9756-4cfe-8f7a-faa868d96f72%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/vagrant-up/15dd3d8a-9756-4cfe-8f7a-faa868d96f72%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> --
>> Alvaro
>>
>>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/ee04ad2b-c0d4-4d1a-a214-28d2988a1463%40googlegroups.com.
