This bug was fixed in the package virtualbox - 4.1.12-dfsg-2ubuntu0.3
---
virtualbox (4.1.12-dfsg-2ubuntu0.3) precise-proposed; urgency=low
[ Felix Geyer ]
* Fix build errors with kernel 3.5. (LP: #1081307)
- Add 39-kernel-35.patch
* Fix crash when running 64-bit guests on a
This bug was fixed in the package virtualbox - 4.1.18-dfsg-1ubuntu1.2
---
virtualbox (4.1.18-dfsg-1ubuntu1.2) quantal-proposed; urgency=low
* Fix broken DNS in guests when the NetworkManager dnsmasq resolver
is used on the host. (LP: #1031217)
* Add an init script to virtuabox
I can't reproduce the original problem described in this bug on precise.
However I have tested that DNS still works with these changes.
@SRU team:
If this is not enough, please let me know and I'll upload a new SRU that
contains only the fix for bug #1081307
** Tags removed: verification-needed
I can confirm that virtualbox 4.1.18-dfsg-1ubuntu1.2 fixed VM network
access for my 12.10 install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Title:
Ubuntu 12.04's use of networkmanager+d
Can anybody using 12.04 please confirm that this bug is fixed there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Title:
Ubuntu 12.04's use of networkmanager+dnsmasq breaks DNS for virtualb
** Description changed:
- In Ubuntu 12.04, the way networkmanager now defaults to using dnsmasq as
- a local resolver seems to break many VM configuration using VirtualBox,
- because VirtualBox's DHCP server tries to inherit the host's DNS
- configuration and provide it to the guest. In the defaul
No longer using Ubuntu anywhere except my already-virtualized AWS
instance, so I'm unable to verify for this, but I appreciate the effort
to fix this. Hopefully someone else who's affected can verify.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Tags added: verification-done-quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Title:
Ubuntu 12.04's use of networkmanager+dnsmasq breaks DNS for virtualbox
VMs
To manage notifica
Just tested the new package virtualbox_4.1.18-dfsg-1ubuntu1.2 on Quantal with
Windows as guest system.
No dns problems any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Title:
Ubuntu
** Branch linked: lp:ubuntu/precise-proposed/virtualbox
** Branch linked: lp:ubuntu/quantal-proposed/virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Title:
Ubuntu 12.04's use of ne
Hello Stephanie, or anyone else affected,
Accepted virtualbox into quantal-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/virtualbox/4.1.18-dfsg-1ubuntu1.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new packag
Hello Stephanie, or anyone else affected,
Accepted virtualbox into precise-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/virtualbox/4.1.12-dfsg-2ubuntu0.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new packag
** Description changed:
In Ubuntu 12.04, the way networkmanager now defaults to using dnsmasq as
a local resolver seems to break many VM configuration using VirtualBox,
because VirtualBox's DHCP server tries to inherit the host's DNS
configuration and provide it to the guest. In the defaul
Per comment #10 from Clint, this bug is missing information needed in
order to accept this SRU. Rather than leaving this package in the
precise/quantal upload queues, I'm rejecting it.
Also, the changelog uses incorrect syntax for a bug closure (bug
#1071344), resulting in a missing reference; th
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu Quantal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Correction: Version of VBox should read: "virtualbox-4.2._4.2.6-82870
-Ubuntu-quantal_i386.deb".
I happen to have both versions in my Download directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
As of a bout a week ago I installed on 3 machines "virtualbox-4.2_4.2.4
--82684-Ubuntu-quantal_i386.deb"
both 32 bit and 64 bit. All installations worked correctly using NAT.
I have had no further problems. Comment #9 stated that the problem was
fixed, and as far as I am concerned it is.
This
Hello! This bug is missing the required information as specified in the
Ubuntu Stable Release Updates policy:
https://wiki.ubuntu.com/StableReleaseUpdates
Please add the required information. The queued upload to quantal-
proposed cannot be accepted until this is completed.
--
You received this
This bug was fixed in the package virtualbox - 4.1.22-dfsg-0ubuntu2
---
virtualbox (4.1.22-dfsg-0ubuntu2) raring; urgency=low
* Fix broken DNS in guests when the NetworkManager dnsmasq resolver
is used on the host. (LP: #1031217)
* Add an init script to virtuabox-guest-x11 whi
** Branch linked: lp:ubuntu/raring-proposed/virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Title:
Ubuntu 12.04's use of networkmanager+dnsmasq breaks DNS for virtualbox
VMs
To m
** Also affects: virtualbox (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: virtualbox (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: virtualbox (Ubuntu Raring)
Importance: Undecided
Status: Confirmed
--
You received this bu
Turns out that disabling dnsmasq (as described in
http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/ - just disable
it in /etc/NetworkManager/NetworkManager.conf) and turning off
natdnshostresolver1 in my VM got me the desired behavior back.
--
You received this bug notification because you
The workaround almost works for me. The only thing is that no matter what I
ask, I get the A record for the item as a reply.
For example, doing a 'dig zonetransfer.me ns' on Ubuntu 12.10 outside the
virtual machine, I get the expected:
---[snip]---
; <<>> DiG 9.8.1-P1 <<>> zonetransfer.m
Note that I have the same problem on 12.10 beta 2 amd64 (both host and
VM).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031217
Title:
Ubuntu 12.04's use of networkmanager+dnsmasq breaks DNS for v
And I can also confirm that the workaround in comment #2 (namely
VBoxManage modifyvm "VM name" --natdnshostresolver1 on) works perfectly
well therefore it looks like that option should be enabled by default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Summary changed:
- networkmanager+dnsmasq implementation seems to break DNS resolution for
virtualbox VMs
+ Ubuntu 12.04's use of networkmanager+dnsmasq breaks DNS for virtualbox VMs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
27 matches
Mail list logo