Created attachment 1906463 [details] journal Description of problem: [root@dell-per430-27 ~]# virt-install --connect qemu:///system --name FT --ram=2048 --vcpus=2 --location=/var/lib/libvirt/images/$image_name --disk path=/var/lib/libvirt/images/test.qcow2,size=15,format=qcow2,device=disk,bus=virtio,perms=rw,cache=writethrough --network network=default,model=virtio --extra-args="inst.ks=https://lnie.fedorapeople.org/beaker-kvm-install.ks" WARNING Graphics requested but DISPLAY is not set. Not running virt-viewer. WARNING No console to launch for the guest, defaulting to --wait -1 Starting install... ERROR Command '['xorriso', '-indev', '/var/lib/libvirt/images/Fedora-Server-dvd-x86_64-37-20220816.n.0.iso', '-print', 'VIRTINST_BEGINLIST', '-find']' returned non-zero exit status 5. Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start FT otherwise, please restart your installation. I see "libvirtd[42602]: internal error: child reported (status=125): Kernel does not provide mount namespace: No such file or directory" in journal Version-Release number of selected component (if applicable): osinfo-db-20220727-1.fc37.noarch virt-install-4.1.0-1.fc37.noarch libvirt-8.6.0-3.fc37.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Thanks for the report. Can you reproduce with `virt-install --debug ...` and attach the full output? What's the output of the failing command? xorriso -indev /var/lib/libvirt/images/Fedora-Server-dvd-x86_64-37-20220816.n.0.iso -print VIRTINST_BEGINLIST -find
Here is the output of xorriso command: [root@dell-per430-27 ~]# xorriso -indev /var/lib/libvirt/images/Fedora-Server-dvd-x86_64-37-20220816.n.0.iso -print VIRTINST_BEGINLIST -find xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. libisoburn: WARNING : ISO image size 1188173s larger than readable size 3526s xorriso : NOTE : Loading ISO image tree from LBA 0 libisofs: WARNING : Found hidden El-Torito image. Its size could not be figured out, so image modify or boot image patching may lead to bad results. libisofs: NOTE : Found hidden El-Torito image for EFI. libisofs: NOTE : EFI image start and size: 1183059 * 2048 , 20392 * 512 libburn : SORRY : Read start address 1183059s larger than number of readable blocks 3526 libisofs: FAILURE : Read error occurred with IsoDataSource xorriso : FAILURE : Cannot read ISO image tree xorriso : HINT : You might get a partial or altered ISO image tree by option -error_behavior 'image_loading' 'best_effort' if -abort_on is set to be tolerant enough. xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
Created attachment 1906842 [details] virt-install --debug output
Hi Inie, would it be possible to test the build osinfo-db-20220727-2.fc37 [0][1] that has the fix for Bug 2103835 ? It is possible that this is the same issue. [0] https://koji.fedoraproject.org/koji/buildinfo?buildID=2053770 [1] https://bodhi.fedoraproject.org/updates/FEDORA-2022-9df0b297cc
The updates fixes the other bug,but not this one
I downloaded latest f37 server dvd here: https://dl.fedoraproject.org/pub/fedora/linux/development/37/Server/x86_64/iso/Fedora-Server-dvd-x86_64-37-20220907.n.0.iso Then on f36, this command succeeds: xorriso -indev Fedora-Server-dvd-x86_64-37-20220907.n.0.iso -print VIRTINST_BEGINLIST -find So if it's failing for you, I'm guessing it's either: 1) that server dvd compose was broken, 2) your particular download is broken, 3) xorriso/libisoburn on f37 has problems. @lnie can you check server dvd?
I was planning to say "it couldn't be the server dvd's problem,as I checked --cdrom option before report this bug",but just in case I downloaded the latest server dvd you mentioned,and I didn't see this bug.So,it is likely the server dvd's problem. I checked a broken dvd server on purpose,guess what?The "virt-install --connect qemu:///system --name FT --ram=2048 --vcpus=2 --cdrom=/var/lib/libvirt/images/$image_name --disk path=/var/lib/libvirt/images/test.qcow2,size=15,format=qcow2,device=disk,bus=virtio,perms=rw,cache=writethrough --network network=default,model=virtio" command shows" Domain is still running. Installation may be in progress. Waiting for the installation to complete.",as if it's a fine server dvd,shouldn't virt-install tells users that the server dvd is broken?
--location $ISO needs to poke into iso contents on the host side, so if the iso file is corrupt, virt-install detects it immediately and can't continue --cdrom doesn't do any of that, and instead it's only up to the guest to access and probe the .iso contents, so you'll instead see a failure to boot inside the VM. that can't be easily communicated to virt-install, so the error isn't reported in the same way Sounds like the root issue isn't relevant with latest media, so let's close this