11.2-Beta3 - problem with VMs after upgrade

[yacenty]

Hello,
I had set up 2 VMs on Freenas 11.2-Beta2.
On on the Ubuntu 18.04, the second one on the Centos7.
Those VMs was crated and started in default way on 11.2-B2

Today I did upgrade to the 11.2-Beta3 and the are 2 problems:
1. First vm with ubuntu - lost network adapter - there is only lo adapter, in the VM settings I did not change anythiong
2. Second vm with centos - wants me to reinstall system - it seems like it boots from the CD (iso)

What should I do to not destroy those vm's there are already some important data, not critical but important.

 

[yacenty]

After disabling CD-ISO.

 

[yacenty]

next error

 

[dlavigne]

Please create a report at bugs.freenas.org and post the issue number here.

 

[yacenty]

https://redmine.ixsystems.com/issues/45710

 

[Rickinfl]

I had the same issue with Ubuntu 18 and found out if you do a ifconfig or ip a you'll notice the nic adapter name changed compared to the netplan file mine use to be enp0s3 now it is enp0s4 so just edit the file and save also don't forget to run sudo netplan apply.

 

[yacenty]

I see only lo

here is the vm config for NIC

 

[yacenty]

found it in the dmesg

but ifconig shows only lo

how can I add this nettwork card called? enp0s4 or e1000

 

[yacenty]

ok problem with ubuntu network fixed

 

[yacenty]

going back to centos problem with uefi boot

 

[Jacob H. Weeks]

Okay, you fixed it. Awesome! Can you please tell me how to do the same? I am running an Ubuntu server with IPBX on it. I'm using it for my home phone, and it has been dead since Beta 3. I have found that I too only have the lo adapter. What did you do to fix it?

 

[Jacob H. Weeks]

Okay, so I just figured it out too. For others that run into this problem, on Ubuntu edit "/etc/netplan" using vim and navigate to the link in the directory to the file listing "enp0s3". Change it to "enp0s4" by pressing "i" to insert. Save and exit by typing ":wq". Then apply using the command "netplan apply".

Thanks for your guidance Rickinfl!

 

[KrisBee]

I had the same issue with Ubuntu 18 and found out if you do a ifconfig or IP a you'll notice the nic adapter name changed compared to the netplan file mine use to be enp0s3 now it is enp0s4 so just edit the file and save also don't forget to run sudo netplan apply.

I suspect this is an unwanted side effect of the way bhyve is now evoked using the new "device order" scheme. If the NIC device is attached to a different pci slot than before, aren't the "Predictable Interface Names" going to change? I'd expect anyone with linux VMs working in Beta2 will be hit by this in Beta3.

 

[yacenty]

interesting is that the device is called "enp0s3" then is renamed to the eth0, and then once more renamed to "enp0s3" - according to the dmesg entries.

 

[KrisBee]

Okay, so I just figured it out too. For others that run into this problem, on Ubuntu edit "/etc/netplan" using vim and navigate to the link in the directory to the file listing "enp0s3". Change it to "enp0s4" by pressing "i" to insert. Save and exit by typing ":wq". Then apply using the command "netplan apply".

Thanks for your guidance Rickinfl!

Changing the "device order" in the WebUI number would be simpler. Setting it a number lower than the disk device should restore the NIC to its original slot number.

 

[Rickinfl]

I never moved my card it's a virto in a LAGG. The upgrade to Beta 3 changed something how the nics label themselves in bhyve . Reminds me of windows if you change a nic it adds a number to the end of it.
It was a pretty easy fix once I noticed the nic name changed in my netplan file. Simple fix.

 

[yacenty]

what about the problem with starting Centos VM?

Maybe also changing the order of disk is a problem?
Any idea how to fix?

Interesting is that other VM - on Ubuntu is runing fine after upgrade. Kernel on both machines is same - 4.15

 

[Rickinfl]

Good Question. I don't run Centos anymore only Ubuntu Server. Wish I could help.