Project

General

Profile

Bug #46271

Preserve original VM devices order

Added by Arne Klein almost 2 years ago. Updated over 1 year ago.

Status:
Done
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
Medium
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

After updating from 11.2-BETA2 to 11.2-BETA3, I can't access my VMs anymore because its NIC got renamed.

During setup of Debian Stretch, the guest OS, the NIC was named enp0s3, as the configuration in /etc/network/interfaces still reflects. Since the update, ip addr show reveals that the NIC is now called enp0s4 though, so my network configuration is now defunct.

This has happened to me before during an update from 11.0-U4 to 11.1: https://forums.freenas.org/index.php?threads/bhyve-debian-vm-changes-its-nic-name-from-eth0-to-eth1-after-updating-to-11-1.60170/

Since then, I have recreated the FreeNAS configuration from scratch, my current config is not a subsequent update of the same installation but an entirely new one (albeit on the same hardware).


Related issues

Related to FreeNAS - Bug #51425: After upgrading from 11.1-U6 to 11.2-x, the network stack stopped working in all virtual machines.Closed

Associated revisions

Revision f7bec727 (diff)
Added by William Grzybowski almost 2 years ago

fix(vm); preserve original VM devices order Ticket: #46271

Revision 81cc7266 (diff)
Added by William Grzybowski almost 2 years ago

fix(vm); preserve original VM devices order Ticket: #46271

History

#1 Updated by Arne Klein almost 2 years ago

  • Subject changed from B3 Update renamed VM NICs to 11.2-BETA3 Update renamed NICs in VM
  • Seen in set to 11.2-BETA3

#2 Updated by Chris Burge almost 2 years ago

This behaviour relates to introduction of VM "device order" numbering for VMs in BETA3. On upgrading, when starting Linux VMs the bhyve pci slot the NIC device is attached may have changed. If the linux distro uses "predictable interface names" (all major distros), then the internal interface names changes, for example from enp0s3 to enp0s4, and network connectivity is lost. Stopping the VM and changing the "device order" number of the NIC device can restore network connectivity, but there is a catch. The catch being, it's not clear how the new "device order" numbering maps to a given bhyve pci slot, nor what previous slot number was used.

Currently there is no user documentation for this new VM "device order" numbering feature.

#3 Updated by Dru Lavigne almost 2 years ago

  • Assignee changed from Release Council to William Grzybowski

#4 Updated by William Grzybowski almost 2 years ago

  • Status changed from Unscreened to Screened
  • Severity changed from New to Medium

#5 Updated by William Grzybowski almost 2 years ago

  • Target version changed from Backlog to 11.2-RC1

#6 Updated by Bug Clerk almost 2 years ago

  • Status changed from Screened to In Progress

#7 Updated by William Grzybowski almost 2 years ago

Acceptance Criteria
Install a VM (ubuntu) in BETA2 or prior and configure networking. After upgrading the VM should still have the network configured in the VM. The devices order should remain the same.

#8 Updated by Bug Clerk almost 2 years ago

  • Status changed from In Progress to Ready for Testing

#9 Updated by Dru Lavigne almost 2 years ago

  • Subject changed from 11.2-BETA3 Update renamed NICs in VM to Preserve original VM devices order
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#10 Updated by Jeff Ervin over 1 year ago

33206
33208
33217
33219
33228
33230
33239

Test Passed FreeNAS-11.2-MASTER-201810020854

Test Case: Created a VM (ubuntu) in BETA2 or prior and configured networking. After upgrading the VM should still have the network configured in the VM. The devices order should remain the same.
VM booted without issue, device order remained the same after update

#11 Updated by Dru Lavigne over 1 year ago

  • Status changed from Passed Testing to Done

#12 Updated by William Grzybowski over 1 year ago

  • Related to Bug #51425: After upgrading from 11.1-U6 to 11.2-x, the network stack stopped working in all virtual machines. added

Also available in: Atom PDF