Was running fine, but I wanted lsusb on host and saw that was a feature thta was only in 25.04, so I upgraded with the idea that I would have to recreate my VMs using the new instance infrastructure.
But I can’t seem to.
There didn’t seem to be any way to directly import them, ok, but I can import the ZVOLs and manually assign them to new disks.
But it seems to want to create a new root volume and copy data to it?
I tried with a less important VM, and its just stuck virt.instance.create where it says its 0% down, but 100% unpacked.
Did I miss some advance creation where one can specify details at a finer grain level without going through the handholding where it would want to create a new root device / new VM.
am I screwed?
so I don’t think I’m screwed, I just don’t know how to set it up correctly.
I figured, lets try to create a VM from the provided ubuntu images with the same size root as I had, and with my old zvol attached to it.
Ok, this creates a new ubuntu, but it partitions the disk to only have a 4GB of used space (i.e. I created a 1TB image, and in fdisk I see, 100MB for EFI mount, 3.9GB for ubuntu, and the rest free. But I don’t see a good way to extend the partition to the whole block device.
I also see my old zvol as something I can mount, but I don’t see the ability to use it as my root FS, but the data is all there, so that’s good.
Is there a way to get a “new install” to be the size of the full block device I specify? If so, I can manage.
more progress: I was using a linuxcontainer catalog image, and I’m guessing that’s why the partition issue is what I see. Apparently can’t use old ISOs that I uploaded previously, as it doesn’t see them in /mnt/primary, going to try with a new one, and figure that should give me the ability to control partitioning
Further Notes: if one had a bios not EFI VM, one cannot easily bring it up now, but with an EFI VM, one can just create a minimal boot disk that one ignores (I believe I saw elsewhere that this is neccessary, annoying to waste 5GB, but whatever)
