ISO install Error using virt-install :Error validating install location: Could not find an installable distribution at URL '/var/lib/libvirt/images/install.iso' #265
Comments
|
[root@hp-xx-16 bootc-image-builder]# virt-install --connect qemu:///system -n imagevm --hvm --accelerate -r 3096 --vcpus=3 --os-variant rhel9.0 --disk path=/var/lib/libvirt/images/testimgevm.qcow2,bus=virtio,format=qcow2,size=10 --network network=default,model=virtio --location /var/lib/libvirt/images/install.iso --debug --memballoon model=virtio --cpu host,disable=vmx --graphics vnc --video virtio --machine q35 [Thu, 14 Mar 2024 01:59:02 virt-install 2938534] DEBUG (cli:220) Received libvirt URI qemu:///system [Thu, 14 Mar 2024 01:59:04 virt-install 2938534] ERROR (cli:257) Error validating install location: Could not find an installable distribution at URL '/var/lib/libvirt/images/install.iso' The location must be the root directory of an install tree. The location must be the root directory of an install tree. |
chunfuwen
changed the title
|
root@xx bootc-image-builder]# isoinfo -d -i /var/lib/libvirt/images/install.iso |
|
Shouldn't |
|
For general iso such as RHEL ISO, it looks like support both of them : --cdrom, --location. |
|
[root@xx images]# virt-install --connect qemu:///system -n imageisovm --hvm --accelerate -r 3096 --vcpus=3 --os-variant rhel9.0 --disk path=/var/lib/libvirt/images/testimgevm2.qcow2,bus=virtio,format=qcow2,size=10 --network network=default,model=virtio --location /var/lib/libvirt/images/fedora.iso --debug --memballoon model=virtio --cpu host,disable=vmx --graphics vnc --video virtio --machine q35 |
|
Did you try |
|
Yes ,I tried --cdrom, and it worked as expected. |
|
Hmm, so I wonder if the ISO that we produce is not recognized as a distribution tree... It's good to know that |
|
As far as I'm aware you should use Should it be? |
|
Note, when trying out the linked documentation with a Fedora Server ISO it also doesn't work, I'll try with a RHEL ISO as well. |
|
So, |
|
with --location ,I use fedora iso from :https://download.fedoraproject.org/pub/fedora/linux/releases/39/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-39-1.5.iso |
|
Right so it might work for a subset of ISOs in the Fedora project as well (not Server, or IoT, which are the ones I had laying around). |
|
I ever has opportunity tried device edge iso, it also support --cdrom. See https://github.com/openshift/microshift/blob/main/docs/user/getting_started.md |
|
Distribution tree usually means something that looks like this: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/ but I think virt-install also has some code to grab that info from isos that it recognizes, but I'd have to go dig through their code to be sure. So unless you really need to append things to the kernel cmdline the right thing to use is |
|
The workaround for this problem is to examine the produced ISO to determine kernel and initrd paths to be passed explicitly in virt-install command line. Nevertheless, this is a limitation that should be fixed, IMO. |
Label the generated ISO with the osinfo expected value depending on the bootc container OS. This will make any software using libosinfo to be able to correctly detect which OS is within the ISO and where to find the initrd and the kernel. Resolves: osbuild#265 Signed-off-by: Miguel Martín <[email protected]>
Label the generated ISO with the osinfo expected value depending on the bootc container OS. This will make any software using libosinfo to be able to correctly detect which OS is within the ISO and where to find the initrd and the kernel. Resolves: osbuild#265 Signed-off-by: Miguel Martín <[email protected]>
Label the generated ISO with the osinfo expected value depending on the bootc container OS. This will make any software using libosinfo to be able to correctly detect which OS is within the ISO and where to find the initrd and the kernel. Resolves: osbuild#265 Signed-off-by: Miguel Martín <[email protected]>
Label the generated ISO with the osinfo expected value depending on the bootc container OS. This will make any software using libosinfo to be able to correctly detect which OS is within the ISO and where to find the initrd and the kernel. Resolves: osbuild#265 Signed-off-by: Miguel Martín <[email protected]>
Label the anaconda ISO depending on the container OS and make the ISO label format compatible with libosinfo. This will make any software using libosinfo to be able to correctly detect the OS contained in the ISO and where to find the initrd and the kernel. Resolves: osbuild#265 Signed-off-by: Miguel Martín <[email protected]>
Label the anaconda ISO depending on the container OS and make the ISO label format compatible with libosinfo. This will make any software using libosinfo to be able to correctly detect the OS contained in the ISO and where to find the initrd and the kernel. Resolves: osbuild#265 Signed-off-by: Miguel Martín <[email protected]>
The text was updated successfully, but these errors were encountered: