/etc/resolv.conf seems to be hardcoded in vmbuilder when building ubuntu VMs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vm-builder (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: python-vm-builder
When I create ubuntu virtual machines (well, I only used "ubuntu --suite intrepid --flavour virtual --arch i386"), the guest machine's /etc/resolv.conf looks like this:
#######
nameserver 192.168.1.122
nameserver 127.0.0.1
#######
This happens even when I changed the default networking in libvirt like this:
/etc/libvirt/
#######
<network>
<name>
<uuid>
<bridge name="virbr%d" />
<forward/>
<ip address=
<dhcp>
<range start="
</dhcp>
</ip>
</network>
#######
/etc/vmbuilder/
#######
<devices>
<emulator>
<interface type='network'>
<source network='default'/>
<model type='virtio'/>
</interface>
...
</devices>
#######
I think, in this case, the guest machine should get a /etc/resolv.conf like this:
#######
nameserver 10.10.10.1
nameserver 127.0.0.1
#######
PS: Using Intrepid with:
python-vm-builder 0.9-0ubuntu3.1
libvirt-bin 0.4.4-3ubuntu3.1
Changed in vm-builder (Ubuntu): | |
assignee: | Chuck Short (zulcss) → nobody |
Thanks for the bug report. Ill take a look at adding an option for dns.
Regards
chuck