This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1311055
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1311055
Title:
hyper-v: DNS Server settings are not getting injected inside Ubuntu
13.10 during Failover and Test-Failover
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
[HyperV Replica :: http://technet.microsoft.com/en-us/library/jj134172.aspx]
[Guest IP Injection ::
http://blogs.technet.com/b/virtualization/archive/2012/05/29/inject-ip-address-into-the-vm-during-failover.aspx]
DNS server settigns are not getting injected inside Ubuntu 13-10 for a
network adapter that is attached to an external network before
Failover and is configured using static Guest IP injection during
Failover. The settings are updated correctly inside
/etc/network/interfaces.
The DNS server entries updated to specified values after next reboot.
1 Create anUbuntu-13.10 VM with external network attached to it.
2 Check DNS entries
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver X.Y.Z.W
nameserver X.Y.Z.K
search dummy.fake.com
3 Enable Replication.
4 Set Failover IPv4 (static IP) settings.
Set-VMNetworkAdapterFailoverConfiguration -ComputerName bharatl-test1 -VMName
lol -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.255.0
-IPv4PreferredDNSServer 192.168.100.101 -IPv4DefaultGateway 192.168.100.1
-VMNetworkAdapterName 'Network Adapter'
5 Do Failover.
6 Check DNS settings.
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver X.Y.Z.W
nameserver X.Y.Z.K
search dummy.fake.com
7 Reboot the Guest.
8 Check DNS settings
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.100.101
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311055/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
