Hello,
I'm trying to run Proxmox over 3 different hypervisors as a nested virtualized environment.
Lets focus on the VMWARE environment (which supports nesting).
Any linux distro I install all yield the same conflicts with VirtIO.
1) If I use any virtualized-hardware of VirtIO (network, or hard disk) most distros halt at boot during udev (Antix for example hangs at "Populating udev"; Archlinux and Ubuntu the same, hanging at boot). I noticed the vCPU is skyrocketing at 180% usage rates.
2) The only way to make the VMs boot is by using SCSI (non VirtIO) hard disks - but then I must manually adjust, under each vm "OPTIONS" the SCSI Controller Type to LSI53C89A5A. If I keep it at the option it had initially (no matter if I choose SCSI or VirtIO) - its always using the "SCSI VirtIO Controller" option. System hangs at BIOS-level and constantly FC. Not even booting.
What am I missing here? How come VirtIO is conflicting with Nested Virtualization? Does that mean I may not enjoy decent performance of v(hard drives) ?
Another Question
What would be the best choice to make, when it comes to hard disk configuration, if I'm aiming at Nesting my Proxmox on a poor-IOPS-rate server?
I'm trying to run Proxmox over 3 different hypervisors as a nested virtualized environment.
Lets focus on the VMWARE environment (which supports nesting).
Any linux distro I install all yield the same conflicts with VirtIO.
1) If I use any virtualized-hardware of VirtIO (network, or hard disk) most distros halt at boot during udev (Antix for example hangs at "Populating udev"; Archlinux and Ubuntu the same, hanging at boot). I noticed the vCPU is skyrocketing at 180% usage rates.
2) The only way to make the VMs boot is by using SCSI (non VirtIO) hard disks - but then I must manually adjust, under each vm "OPTIONS" the SCSI Controller Type to LSI53C89A5A. If I keep it at the option it had initially (no matter if I choose SCSI or VirtIO) - its always using the "SCSI VirtIO Controller" option. System hangs at BIOS-level and constantly FC. Not even booting.
What am I missing here? How come VirtIO is conflicting with Nested Virtualization? Does that mean I may not enjoy decent performance of v(hard drives) ?
Another Question
What would be the best choice to make, when it comes to hard disk configuration, if I'm aiming at Nesting my Proxmox on a poor-IOPS-rate server?