I have a qcow2 image of a virtual machine that boots just fine on my home Proxmox 8.1.3 system. I exported it as qcow2, scp to another 8.1.3 machine, made a bare VM, did a qm import of the qcow2, attached it to the drive in the new VM.
When started this reports the disk is not bootable and goes to messing with PXE instead.
The qcow2 from my machine started life as a VMDK in an OVA for an old appliance that's no longer supported. I'm very familiar with this roughly Debian 10.5 based system. The OVA works fine with VirtualBox. The working VM on my home system was made importing the VMDK disk and then attaching it. I already tried this with the remote system and it didn't work there, which is why I'm now trying this with qcow2. I have experimented with direct OVA import, the instructions I've found do not address issues I encountered with the XML file that describes the VM.
I just went through the two VMs side by side and the only difference is the VM here has the Debian 10.5 ISO in its CD. I need a few things from the ISO in order to make ssh work, but I copied them to a folder I can share with VMs when I need to do that, thinking to save time/space. It is normal for me to have several of this appliance running doing different tasks, and I have to build a new one about once a month.
The VM that works has a drive type of (ide0) rather than SCSI, a legacy of the OVA creator's choices. I'm not sure what difference this would make. I've tried connecting it as both (ide0) and SCSI, no joy with either.
What do I need to do to a qcow2 to make the OS in it boot? Is there some sort of "fdisk for doctoring qcow2" utility out there?
When started this reports the disk is not bootable and goes to messing with PXE instead.
The qcow2 from my machine started life as a VMDK in an OVA for an old appliance that's no longer supported. I'm very familiar with this roughly Debian 10.5 based system. The OVA works fine with VirtualBox. The working VM on my home system was made importing the VMDK disk and then attaching it. I already tried this with the remote system and it didn't work there, which is why I'm now trying this with qcow2. I have experimented with direct OVA import, the instructions I've found do not address issues I encountered with the XML file that describes the VM.
I just went through the two VMs side by side and the only difference is the VM here has the Debian 10.5 ISO in its CD. I need a few things from the ISO in order to make ssh work, but I copied them to a folder I can share with VMs when I need to do that, thinking to save time/space. It is normal for me to have several of this appliance running doing different tasks, and I have to build a new one about once a month.
The VM that works has a drive type of (ide0) rather than SCSI, a legacy of the OVA creator's choices. I'm not sure what difference this would make. I've tried connecting it as both (ide0) and SCSI, no joy with either.
What do I need to do to a qcow2 to make the OS in it boot? Is there some sort of "fdisk for doctoring qcow2" utility out there?
