Quantcast
Channel: Active questions tagged ubuntu - Stack Overflow
Viewing all articles
Browse latest Browse all 7072

No IP address and no eth devices after Hyper-V migration [closed]

$
0
0

I have a virtual machine in VirtualBox that works correctly. It has Ubuntu Server 10.04 installed, and a few services running correctly.

I need to migrate the virtual machine to Hyper-V, and am having trouble getting the machine to have an IP. It Works correctly when I migrate to VMWare. The problem is that i'm not getting any IP or network interfaces.

The way I have created the VHD, is with the VBoxManage tool. I have also tried to generate the VHD with specific software for it, but the problem is still the same, so I have ruled out that the problem is in the way I create the machine.

When I try to see the IP address that the machine has, with the ifconfig command, it returns:

lo   Link encap: Local Loopback   inet addr:127.0.0.1 Mask: 255.0.0.0.0   inet6 addr: ::1/128 Scope: Host   UP LOOPBACK RUNNING MTU:16436 Metric:1   RX packets: 1594 errors:0 dropped:0 overruns:0 frame:0   TX packets: 1594 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0   RX bytes:754282 (754.2 KB) TX bytes:754282 (754.2 KB)

I have a static IP assigned in the /etc/network/interfaces file, which works correctly before the migration, but after migrating it does not show any interface, neither eth0, or any other.

I have tried deleting the file found in /etc/udev/rules.d/70-persistent-net.rules, seeing if it assigns me a new address, but it does not. Hyper-v doesn't create this file again, when I deleted it in virtualbox it did.


Viewing all articles
Browse latest Browse all 7072

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>