Prepare for a weird and pretty non-specific question. I work with F5 BIGIP devices and use a few of them in a virtual environment for labs and demo. I've been running ESXi for years and it works fine. I've run KVM as well in a few setups, it has worked flawlessly. This is the first time trying out Proxmox.
The BIGIP is a Linux-based app proxy that can run under KVM according to F5. And it does. F5 makes prepared qcow2 files and provides info about the virtual hardware recommendations. But for some people, including me, there are very weird behavior of the VM that seems to be related to reading and writing files. This is within the VM itself. An example: SSH daemon cannot start because if claims it cannot read the ssh key files. But the files are there, the path is right, there is no permission issue and no SELinux issues. And starting sshd manually with the exact same key file works just fine. Another process claims it cannot create a specific folder, but creating it manually works fine - again no obvious permission or SELinux issues (I chmod 777'd the directory and it still could not create the folder). When you activate the BIGIP license it says it cannot write the license file - but it does write info in the license file. It's confusing.
This does not seem to be Proxmox-related since other VMs does not show this behaviour, and the error is within the VM. But is also does seem to be Proxmox-related since it only happens in proxmox and other people experience the same thing. However, some people virtualize BIGIPs in Proxmox without any issue. I've compared settings with them and the only diff is usage of ceph storage and different Proxmox version.
I have troubleshooted the VM itself for a few days now and I running out of ideas. I have tried different versions of the BIGIP image, tried both qcow2 images (that should be the right one) and converted vmdk images aimed for vmware, changed pretty much all the settings I can find in the proxmox GUI for the VM, re-installed, rebooted... I get the same behaviour regardless of what I do. Maybe I'm missing something obvious?
The pretty non-specific question I have is: How do I troubleshoot this? Has anyone experienced the same behaviour in a VM and solved it? If you need any info about the VM please tell me what commands etc to run and I'll post the info.
I'm running Proxmox 6.1-3 on Intel Server hardware, storage is NVMe-disks that uses LVM thin for VM storage.
The BIGIP is a Linux-based app proxy that can run under KVM according to F5. And it does. F5 makes prepared qcow2 files and provides info about the virtual hardware recommendations. But for some people, including me, there are very weird behavior of the VM that seems to be related to reading and writing files. This is within the VM itself. An example: SSH daemon cannot start because if claims it cannot read the ssh key files. But the files are there, the path is right, there is no permission issue and no SELinux issues. And starting sshd manually with the exact same key file works just fine. Another process claims it cannot create a specific folder, but creating it manually works fine - again no obvious permission or SELinux issues (I chmod 777'd the directory and it still could not create the folder). When you activate the BIGIP license it says it cannot write the license file - but it does write info in the license file. It's confusing.
This does not seem to be Proxmox-related since other VMs does not show this behaviour, and the error is within the VM. But is also does seem to be Proxmox-related since it only happens in proxmox and other people experience the same thing. However, some people virtualize BIGIPs in Proxmox without any issue. I've compared settings with them and the only diff is usage of ceph storage and different Proxmox version.
I have troubleshooted the VM itself for a few days now and I running out of ideas. I have tried different versions of the BIGIP image, tried both qcow2 images (that should be the right one) and converted vmdk images aimed for vmware, changed pretty much all the settings I can find in the proxmox GUI for the VM, re-installed, rebooted... I get the same behaviour regardless of what I do. Maybe I'm missing something obvious?
The pretty non-specific question I have is: How do I troubleshoot this? Has anyone experienced the same behaviour in a VM and solved it? If you need any info about the VM please tell me what commands etc to run and I'll post the info.
I'm running Proxmox 6.1-3 on Intel Server hardware, storage is NVMe-disks that uses LVM thin for VM storage.
