Changing the network adapter type on your VPS

You change the virtual network adapter on your VPS in Virtualizor, not inside the operating system. Pick the adapter model in the VPS configuration, reboot for it to take effect, then make sure your network configuration still matches the new interface name and MAC address. On Ubuntu that means Netplan. On AlmaLinux that means NetworkManager.

Before you start

• Adapter model is a hypervisor-side setting. Virtualizor controls it. Inside the OS you do not switch E1000 to VirtIO. You prepare the OS to handle the change, then change it in Virtualizor.
• A restart is required. Libvirt and KVM apply NIC model changes at boot. Plan a short maintenance window.
• Interface names can change. Systemd’s predictable names use the hardware path and driver. Changing the NIC model can rename your interface. If your config is tied to the old name, networking may not come up after reboot. You will fix this in Netplan on Ubuntu or in NetworkManager on AlmaLinux.
• Ubuntu 24.04 moved the default NetworkManager Netplan file to /lib/netplan/00-network-manager-all.yaml. Do not edit it. Put your overrides in /etc/netplan/*.yaml.
• Modern Linux kernels include VirtIO drivers. AlmaLinux 9 and Ubuntu 24.04 have virtio-net built in. No driver package is needed for Linux guests.
• Have a fallback console ready. Keep the Virtualizor HTML5 VNC console open during changes so you can recover if SSH drops. If you lock yourself out, Virtualizor Rescue Mode can boot a temporary image so you can repair network config.
• Do not click OS Re-Install or Rebuild in Virtualizor. That wipes the disk and deploys a fresh OS. It is destructive and not needed for a NIC model change.
• If you cannot see a NIC type option in Virtualizor for your VPS, it might be provider-restricted. You can open a support ticket and we will help.

Step 1: Record your current interface name and MAC address

You will use this to match your adapter in configuration and to recognise any rename after the change.

This command shows a one-line summary of all interfaces so you can see the current device name and MAC address.

Ubuntu 24.04

ip -br link

AlmaLinux 9

ip -br link

Find the interface that carries your VPS IP, for example ens3 or enp1s0. Note its MAC address from the output, or print it directly with this command which reads the kernel’s view of the MAC.

Ubuntu 24.04

IFACE=$(ip -br addr | awk '$2 ~ /UP/ {print $1; exit}')
cat /sys/class/net/"$IFACE"/address

AlmaLinux 9

IFACE=$(ip -br addr | awk '$2 ~ /UP/ {print $1; exit}')
cat /sys/class/net/"$IFACE"/address

Optional: this command shows which driver the interface is using. It helps you confirm you are moving from an emulated device like e1000 to virtio_net after the change. If ethtool is missing, the first command installs it.

Ubuntu 24.04

sudo apt update && sudo apt install -y ethtool
sudo ethtool -i "$IFACE"

AlmaLinux 9

sudo dnf install -y ethtool
sudo ethtool -i "$IFACE"

Step 2: Prepare Ubuntu 24.04 Netplan to survive an interface rename

Ubuntu uses Netplan. You will create a file under /etc/netplan/ that matches the NIC by MAC address and gives it a stable name. This avoids a boot-time mismatch if the kernel renames the interface after the NIC model switch. Do not edit /lib/netplan/00-network-manager-all.yaml.

This command opens a new Netplan file for editing. Replace the MAC address and set DHCP or your static settings as required.

Ubuntu 24.04

sudo nano /etc/netplan/50-hostworld-stable.yaml

Example for DHCP:

network:
  version: 2
  ethernets:
    stable0:
      match:
        macaddress: "aa:bb:cc:dd:ee:ff"
      set-name: stable0
      dhcp4: true
      dhcp6: false

Example for static IPv4:

network:
  version: 2
  ethernets:
    stable0:
      match:
        macaddress: "aa:bb:cc:dd:ee:ff"
      set-name: stable0
      addresses:
        - 203.0.113.10/24
      routes:
        - to: 0.0.0.0/0
          via: 203.0.113.1
      nameservers:
        addresses: [1.1.1.1, 9.9.9.9]

Save the file. This command checks and applies the new Netplan with a timed rollback. If networking fails, it will revert automatically after 120 seconds. Keep the Virtualizor console open while you test.

Ubuntu 24.04

sudo netplan try

If the test succeeds, confirm permanently:

Ubuntu 24.04

sudo netplan apply

Step 3: Prepare AlmaLinux 9 NetworkManager to handle a rename

AlmaLinux uses NetworkManager. You will make the active connection tolerant of interface name changes, and you will be ready to update the MAC binding if the NIC change gives you a new MAC.

This command shows active connections and which device each uses. Note the connection name.

AlmaLinux 9

nmcli -t -f NAME,DEVICE,TYPE con show --active

This command removes any hard binding to a single interface name so the profile can follow a rename. It then adds a match rule that allows common Ethernet-style names. Replace YOUR-CONNECTION with the name you noted.

AlmaLinux 9

CON="YOUR-CONNECTION"
sudo nmcli connection modify "$CON" connection.interface-name ""
sudo nmcli connection modify "$CON" match.interface-name "en*;eth*"

This command backs up the current profile to a file so you can restore it if needed.

AlmaLinux 9

FILE=$(sudo nmcli -g connection.uuid,connection.id con show | awk -F: -v c="$CON" '$2==c{print $1}')
sudo cp "/etc/NetworkManager/system-connections/$CON.nmconnection" "/etc/NetworkManager/system-connections/$CON.nmconnection.bak" || true

This command reloads NetworkManager’s profiles and re-activates the connection. Be ready on the Virtualizor console in case your SSH session drops.

AlmaLinux 9

sudo nmcli connection reload
sudo nmcli connection up "$CON"

Note: if your environment relies on binding by MAC address, you can add it now with the current MAC so the profile cannot float to a different NIC in future. You may need to update this after the change if the MAC changes.

AlmaLinux 9

CURMAC=$(cat /sys/class/net/"$(nmcli -t -f DEVICE con show "$CON" | awk -F: '/^DEVICE:/{print $2}')" /address)
sudo nmcli connection modify "$CON" ethernet.mac-address "$CURMAC"

Step 4: Change the NIC model in Virtualizor

You apply the model change in the Hostworld Virtualizor panel. Go to the Hostworld client area at https://portal.hostworld.uk/, open your VPS service, then use the link to open Virtualizor. In Virtualizor, look for the VPS configuration that includes a setting called Virtual Network Interface Type or similar. Options include Default and E1000. If VirtIO is enabled, Virtualizor will use VirtIO as the virtual NIC type.

Select the adapter you want and save the change. Do not use OS Re-Install or Rebuild. Those actions format the VPS and deploy a fresh image.

If your account does not expose the NIC type option, open a support ticket and tell us which VPS you want changed and which model you prefer.

Step 5: Power cycle the VPS from Virtualizor

The change takes effect after a restart. Use the Stop and Start controls in Virtualizor, or its Reboot control if presented. A full power cycle is safest for device model changes. Keep your Virtualizor console open while it boots.

Step 6: Bring networking up after the change

First check what changed. These commands show your current interfaces and routing so you can spot a rename or MAC change.

Ubuntu 24.04

ip -br link
ip route

AlmaLinux 9

ip -br link
ip route

Ubuntu 24.04: verify Netplan and apply if needed

If you created a Netplan file with set-name: stable0, confirm that the interface appears as stable0. If you still see a different name but the MAC matches, adjust your /etc/netplan/50-hostworld-stable.yaml and apply again.

This command safely applies Netplan with a timed rollback. Use this if you are connected remotely.

Ubuntu 24.04

sudo netplan try

Once you are happy, confirm it permanently.

Ubuntu 24.04

sudo netplan apply

AlmaLinux 9: rebind the connection and update MAC if it changed

Check device status and which connection, if any, is active on the new interface.

AlmaLinux 9

nmcli device status
nmcli -t -f NAME,DEVICE,TYPE,STATE con show

If your connection did not autoconnect, activate it on the detected interface. Replace YOUR-CONNECTION with the profile name and NEWIFACE with the interface you now see, for example ens3.

AlmaLinux 9

CON="YOUR-CONNECTION"
NEWIFACE="ens3"
sudo nmcli connection modify "$CON" connection.interface-name "$NEWIFACE"
sudo nmcli connection up "$CON"

If the NIC change produced a new MAC address and your profile is bound by MAC, update it and bring the connection up again.

AlmaLinux 9

NEWMAC=$(cat /sys/class/net/"$NEWIFACE"/address)
sudo nmcli connection modify "$CON" ethernet.mac-address "$NEWMAC"
sudo nmcli connection up "$CON"

Confirm basic connectivity

These commands test reachability to a public IP, then DNS resolution. Replace example.org if you prefer.

Ubuntu 24.04

ping -c 3 1.1.1.1
getent hosts example.org

AlmaLinux 9

ping -c 3 1.1.1.1
getent hosts example.org

Step 7: Tidy up and make the change permanent

• Ubuntu: remove any old Netplan files in /etc/netplan/ that refer to the pre-change interface name so they cannot conflict later. Keep your 50-hostworld-stable.yaml with the stable name.
• AlmaLinux: once you confirm the final interface name, set connection.interface-name in your profile to that exact name and keep or remove the match.interface-name wildcard as you prefer.
• If you changed adapter type to test performance and want to go back, reverse the Virtualizor setting. Your OS-side preparation will still protect you from renames.

Recovery if you lose network access

• Launch the Virtualizor HTML5 VNC console for your VPS and undo any recent config edits. You will find it from the same Virtualizor page where you manage power.
• Use Virtualizor Rescue Mode to boot a temporary rescue image. Mount your root volume and repair /etc/netplan/*.yaml on Ubuntu or the NetworkManager profile on AlmaLinux. Then reboot back into your installed OS. Virtualizor documents these features here: VNC console and Rescue Mode.
• If you need a hand or the NIC option is not visible for your VPS, open a support ticket.

What next

If you are comparing VPS options for a new deployment, have a look at our UK location in Maidenhead on Linux VPS. For more articles like this, browse our VPS guides. If at any point you get stuck, please open a support ticket so we can help from our side.