This is not reliant on the physical disk but on whether the storage is being thin provisioned or not.Check the 'Discard' box if you're using an SSD
local-lvm
) and ZFS (local-zfs
) storages are both thin provisioned for example.root@pve:~# qm importdisk 103 /root/haos_ova-12.0.qcow2 local-lvm
/root/haos_ova-12.0.qcow2: non-existent or non-regular file
root@pve:~# file /root/haos_ova-15.2.qcow2
/root/haos_ova-15.2.qcow2: QEMU QCOW Image (v3), 34359738368 bytes (v3), 34359738368 bytes
Use the same filename ("-15.2") and it might work...? ;-)Any idea what the problem might be?
Use the same filename ("-15.2") and it might work...? ;-)
os update
Processing... Done
Error: No version information available, cannot update
ha> login
# ping www.google.com
google.com is alive!
That is wrong and would explain the unsupported message as it's for bare-metal. For example it comes without the guest agent. According to your picture you use the OVA though? The message comes from here. Apparently it couldn't quite figure out what the OS version is/was. I'm not sure why though and would need to see the supervisor log.the generix x86/x64 image
I followed your initial guide to the letter and set my VM up by changing the options that you said to change and leaving the ones that you didn't alone.This is wrong and unnecessary. See my message above. Use the OVAs for VMs.
Without seeing your VM's config it's hard to say why the instructions failed for you.
We use essential cookies to make this site work, and optional cookies to enhance your experience.