New user and my first post, be gentle... 
I have a fresh install of 7.1-10 running on ASUS ROG B450MB and a Ryzen 5600G w 48Gig Ram, mirrored SSD's for boot and a "data" SSD for VM storage. I am transferring VirtualBox VM's over with the final hopes of killing VB. I'm using the RAW image format to move them, most are Ubuntu OS, some server some desktop.
Several VM's transferred almost shockingly easy. They are up and fully functional, on the network, apps are running, web services up and reachable, I am happy. PiHole, SmokePing, and Observium all running great...
A couple other VM's wind up with no assigned DHCP IP address even though I followed the same migration process and regardless of what I do. I'm not using any fancy network setup, no extra bridges, no multiple adapters, it's a single interface and a /24 private IP subnet in my home, all VM's are assigned by default to vmbr0 and using the virtio driver.
My most important IP-challenged VM move is my NextCloud VM. This NextCloud Ubuntu VM starts, but has no IP. I ran the "grep -i virtio /boot/config-$(uname -r)" command to see if the virtio driver is in the VM image I'm transfering over, it looks like it's not, as I get an "=m" result from the command.
I tried using the 3 other Proxmox-selectable driver types (vmxnet, etc) to no avail, still no assigned IP. Solution "seems" to be that I download the virtio driver and go through 20 some commands to install it and recompile the kernel. I am waaaaaaay out of my element with that. Is there anything I've missed in the process, or perhaps an easier way to move this Ubuntu 21.04 NextCloud VM from VirtualBox to Proxmox??
(see attached qm config and /etc/network/interfaces outputs)
Thanks much for your review and consideration,
Gary
I have a fresh install of 7.1-10 running on ASUS ROG B450MB and a Ryzen 5600G w 48Gig Ram, mirrored SSD's for boot and a "data" SSD for VM storage. I am transferring VirtualBox VM's over with the final hopes of killing VB. I'm using the RAW image format to move them, most are Ubuntu OS, some server some desktop.Several VM's transferred almost shockingly easy. They are up and fully functional, on the network, apps are running, web services up and reachable, I am happy. PiHole, SmokePing, and Observium all running great...
A couple other VM's wind up with no assigned DHCP IP address even though I followed the same migration process and regardless of what I do. I'm not using any fancy network setup, no extra bridges, no multiple adapters, it's a single interface and a /24 private IP subnet in my home, all VM's are assigned by default to vmbr0 and using the virtio driver.
My most important IP-challenged VM move is my NextCloud VM. This NextCloud Ubuntu VM starts, but has no IP. I ran the "grep -i virtio /boot/config-$(uname -r)" command to see if the virtio driver is in the VM image I'm transfering over, it looks like it's not, as I get an "=m" result from the command.
I tried using the 3 other Proxmox-selectable driver types (vmxnet, etc) to no avail, still no assigned IP. Solution "seems" to be that I download the virtio driver and go through 20 some commands to install it and recompile the kernel. I am waaaaaaay out of my element with that. Is there anything I've missed in the process, or perhaps an easier way to move this Ubuntu 21.04 NextCloud VM from VirtualBox to Proxmox??
(see attached qm config and /etc/network/interfaces outputs)
Thanks much for your review and consideration,
Gary
Attachments
Last edited:
