I had a power outage overnight and my server rebooted.  I don't know what happens but now it seems as if my VM running ubuntu can't see the network. I was getting a message on the VMs page about going into Network Settings and set up a bridge.  I don't understand why this is needed now.  This has been running for years without a problem and I rebooted over the weekend and there haven't been recent updates so there's no reason any of these settings would have changed.   

 

So right now when I connect via the VNC remote option and look at what the Ubuntu startup shows it's giving me errors on mounting all remote file systems and some other services then I can get into a command line and when I run ifconfig I see only lo, no eth0 or anything else.  

 

So what kind of hoops do I need to jump through to get this VM to see the network adapter again? 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                        
        inet 192.168.0.201  netmask 255.255.255.0  broadcast 192.168.0.255       
        ether d0:50:99:34:05:47  txqueuelen 1000  (Ethernet)                     
        RX packets 16230  bytes 2137660 (2.0 MiB)                                
        RX errors 0  dropped 24  overruns 0  frame 0                             
        TX packets 12057  bytes 1678291 (1.6 MiB)                                
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0               
                                                                                 
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                    
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0                  
        ether 02:42:0f:ea:80:da  txqueuelen 0  (Ethernet)                        
        RX packets 5095  bytes 358638 (350.2 KiB)                                
        RX errors 0  dropped 0  overruns 0  frame 0                              
        TX packets 4426  bytes 371064 (362.3 KiB)                                
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0               
                                                                                 
eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500               
        ether d0:50:99:34:05:47  txqueuelen 1000  (Ethernet)                     
        RX packets 38993  bytes 6748821 (6.4 MiB)                                
        RX errors 0  dropped 0  overruns 0  frame 0                              
        TX packets 26461  bytes 7369329 (7.0 MiB)                                
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0               
        device interrupt 20  memory 0xf7f00000-f7f20000                          
                                                                                 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536                                     
        inet 127.0.0.1  netmask 255.255.255.255                                  
        loop  txqueuelen 1  (Local Loopback)                                     
        RX packets 1577  bytes 116690 (113.9 KiB)                                
        RX errors 0  dropped 0  overruns 0  frame 0                              
        TX packets 1577  bytes 116690 (113.9 KiB)                                
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0               
                                                                                 
veth420bc5d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                
        ether 02:17:16:5b:b1:0b  txqueuelen 0  (Ethernet)                        
        RX packets 5095  bytes 429968 (419.8 KiB)                                
        RX errors 0  dropped 0  overruns 0  frame 0                              
        TX packets 4426  bytes 371064 (362.3 KiB)                                
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0               
                                                                                 
veth7d38cca: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                
        ether 86:35:76:86:99:97  txqueuelen 0  (Ethernet)                        
        RX packets 0  bytes 0 (0.0 B)                                            
        RX errors 0  dropped 0  overruns 0  frame 0                              
        TX packets 231  bytes 74967 (73.2 KiB)                                   
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0               
                                                                                 
virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500                             
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255     
        ether 52:54:00:6f:d9:26  txqueuelen 1000  (Ethernet)                     
        RX packets 0  bytes 0 (0.0 B)                                            
        RX errors 0  dropped 0  overruns 0  frame 0                              
        TX packets 0  bytes 0 (0.0 B)                                            
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0               
                                                                                 
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                      
        ether fe:54:00:6d:3e:e6  txqueuelen 1000  (Ethernet)                     
        RX packets 0  bytes 0 (0.0 B)                                            
        RX errors 0  dropped 0  overruns 0  frame 0                              
        TX packets 257  bytes 34152 (33.3 KiB)                                   
        TX errors 0  dropped 9306 overruns 0  carrier 0  collisions 0            
                                                                                 

Here's the ifconfig results after logging into the unraid server.  

Anybody have any idea what I can do to get this working again?  Everything was fine, then it's not.  It doesn't make sense to me.  I set up this VM a long, long time ago, and I don't recall doing anything special.  I just wanted an Ubuntu VM and it just worked.  Now it can't reach the network at all.  I've rebooted the Unraid box multiple times, I've restarted the VM, nothing, always the same, it seems that it can't establish its network connection.  I connected via VNC and hit enter so I entered emergency mode, ran ifconfig eth0 up and it brought up that device, but without an ip4 address.  Without network access it can't mount any shares and I can't run my HDHomeRun DVR, it's totally useless to me.  I also can't copy off any of my configuration files or do anything to recover the stuff I have on this VM so if I made another VM I'd be starting from scratch.  All this because the Unraid server was shutdown badly.  this doesn't make sense.  My docker containers are fine, but not this VM.  

Did you ever figure this out? I have the exact same issue after updating unraid from 6.5.0 to 6.5.2. Can provide more info if required.

I would try changing the nic type for the VM from virtio to intel.

 

So something like this:

    <interface type='bridge'>
      <mac address='xx:xx:xx:xx:xx:xx'/>
      <source bridge='br0'/>
      <model type='e1000'/>            <==== this is what you change from virtio to e1000
      <address type='pci' domain='0x0000' bus='0x0x' slot='0x00' function='0x0'/>
    </interface>

Hopefully that will fix the problem.

I have still not solved this issue. The suggestion above did not work. I have some additional information which could be useful.

 

I have another Ubuntu Server 16.04 VM which is usualy shut down. I span this up and it has network.

 

I think the issue might not be caused by upgrading Unraid but updating Ubuntu with apt, and then going into effect with rebooting the VM for upgrading unraid.