multiple F5 in proxmox VE

[hasanibrahim]

Hi,

I am preparing for my F5 certification.
I am successfully able to spin up first F5 vm in proxmox (homelab environment).
As soon as i spin up the second F5 vm, both of the F5 vm starts behaving abnormal (bootloop and failed to boot)
I have spent few days to fix this with changing UUID for the second F5 vm disks(PV, VG and LV)
Still no luck.


Anyone faced similar issue?
More importantly , How can i spin up two fully functional F5 vm in proxmox


Thanks
Ibrahim

 

[fiona]

Hi,
does your host have enough resources for both VMs? Is there a resource passed-through to both that might not be able to be? Please share the configuration for both VMs with qm config ID replacing ID with the actual ID.

 

[hasanibrahim]

HI Fiona


Thank you for looking into this

admin@amarbasa:/tmp# qm config 122
boot:
cores: 1
cpu: x86-64-v2-AES
ide2: none,media=cdrom
memory: 8192
meta: creation-qemu=9.2.0,ctime=1761124831
name: F5-planeA
net0: virtio=BC:24:11:2A:CA:9C,bridge=vmbr0
net1: virtio=BC:24:11:02:8D:5B,bridge=vmbr1
net2: virtio=BC:24:117:34:54,bridge=vmbr2
numa: 0
ostype: l26
scsi0: local-lvm:vm-122-disk-0,size=83G
scsihw: virtio-scsi-single
smbios1: uuid=3c2782af-b07c-4b16-a651-593a20a67c7e
sockets: 2
vmgenid: bf11cd02-f246-4043-82ad-e07d18fcb96c


admin@amarbasa:/tmp# qm config 123
boot:
cores: 1
cpu: x86-64-v2-AES
ide2: none,media=cdrom
memory: 8196
meta: creation-qemu=9.2.0,ctime=1761124882
name: F5-planeB
net0: virtio=BC:24:11:6D:55:2A,bridge=vmbr0
net1: virtio=BC:24:11:C1:7E:B1,bridge=vmbr0
net2: virtio=BC:24:11:BB:93:2A,bridge=vmbr0
numa: 0
ostype: l26
scsi0: local-lvm:vm-123-disk-0,iothread=1,size=83G
scsihw: virtio-scsi-single
smbios1: uuid=2ff02053-adad-4f72-acb7-e15a23c89cf5
sockets: 2
vmgenid: 58e52e86-602b-473f-b9d4-fa5104f5654c
root@amarbasa:/tmp#



this is the output
Vm122 is working fine.
But VM123 is stuck in boot


thnaks
Ibrahim

 

[fiona]

Is there anything in the system journal of the host around the time the issue occurs? Does the second VM also not start correctly if you only start that one? How far exactly does it get when booting, what exactly do you see? Black screen? Any text from SeaBIOS?

The only differences in the configuration are memory, that all network devices have vmbr0 for the second VM and the iothread setting. Do you see the expected partitions/filesystem labels when you check with

lvchange -aly $(pvesm path local-lvm:vm-123-disk-0)
fdisk -l $(pvesm path local-lvm:vm-123-disk-0)
wipefs --no-act $(pvesm path local-lvm:vm-123-disk-0)

?