No bootable device
Hi, We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW) using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format. No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM. To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected. The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same. What are we missing here? Is anything else needed to do so the disk is bootable? Thanks.
Hi, I guess you should check Chipset / Firmware Type Setting of VM. If it is UEFI or BIOS boot. _isi_
Hi _isi_, I already tried with all chipset/firmwares available. Still I get the same result, it cannot boot with that disk. Not sure what the problem actually is, as I said, I'm pretty sure the disk is bootable under VirtualBox. Thanks. El 2022-03-23 14:50, uli.iske@elkb.de escribió:
Hi,
I guess you should check Chipset / Firmware Type Setting of VM. If it is UEFI or BIOS boot.
_isi_ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FUMIPVESOS4LVH...
Hi Nicolas You could try "fixing" the VM OS boot process by booting into rescue mode from the VM Linux distribution's installation CD - you'd need to read up on re-writing the boot software (probably grub.) and/or you could look at exporting the disk back to VirtuaBox and trying to boot it there. Regards Angus ________________________________ From: nicolas@devels.es <nicolas@devels.es> Sent: 25 March 2022 12:49 To: users@ovirt.org <users@ovirt.org> Subject: [ovirt-users] Re: No bootable device Hi _isi_, I already tried with all chipset/firmwares available. Still I get the same result, it cannot boot with that disk. Not sure what the problem actually is, as I said, I'm pretty sure the disk is bootable under VirtualBox. Thanks. El 2022-03-23 14:50, uli.iske@elkb.de escribió:
Hi,
I guess you should check Chipset / Firmware Type Setting of VM. If it is UEFI or BIOS boot.
_isi_ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... oVirt Code of Conduct: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... List Archives: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovir...
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... oVirt Code of Conduct: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... List Archives: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovir...
Hi Nicolas In oVirt 4.3: Compute -> Virtual Machines -> Select VM On the VM screen: Disks -> Highlight disk -> Edit Check the bootable tick box Hope that helps Angus ________________________________ From: nicolas@devels.es <nicolas@devels.es> Sent: 23 March 2022 14:00 To: users@ovirt.org <users@ovirt.org> Subject: [ovirt-users] No bootable device Hi, We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW) using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format. No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM. To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected. The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same. What are we missing here? Is anything else needed to do so the disk is bootable? Thanks. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... oVirt Code of Conduct: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.... List Archives: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovir...
Is it set as bootable? I have seen some QCOWs not be read correctly by ovirt. In that case I would take an OVA file and convert it manually to QCOW using the CLI, sometimes the QCOW works only with IDE from what I have seen. My way is somewhat long but usually works for me: Upload to Disk page in GUI and attach to a premade VM -- If it fails use CLI: CLI: tar -xvf <image-name>.ova it will extract to .vmdk files OR if you have a VMDK already qemu-img convert <image-name>-disk001.vmdk <image-name>.qcow2 -O qcow2 Once completed, you should verify that the file is successfully a QEMU QCOW2 Image. file <image-name>.qcow2 You can then download over winscp and upload to the GUI Disks page and attach to a VM -- Sometimes if you have errors on boot you need to choose a different CPU or set HDD to IDE or virtIO-Sata.
Hi Abe, Yes, it was set as bootable. I tried your approach, however I get the same results; converted the disk with qemu-img from vmdk to qcow2, tried any disk driver (SATA, VirtIO, VirtIO-SCSI) and also tried all chipset/firmwares available. Still I get the same result, it cannot boot with that disk. Thanks. El 2022-03-24 18:33, Abe E escribió:
Is it set as bootable? I have seen some QCOWs not be read correctly by ovirt. In that case I would take an OVA file and convert it manually to QCOW using the CLI, sometimes the QCOW works only with IDE from what I have seen.
My way is somewhat long but usually works for me: Upload to Disk page in GUI and attach to a premade VM -- If it fails use CLI: CLI: tar -xvf <image-name>.ova it will extract to .vmdk files OR if you have a VMDK already
qemu-img convert <image-name>-disk001.vmdk <image-name>.qcow2 -O qcow2
Once completed, you should verify that the file is successfully a QEMU QCOW2 Image. file <image-name>.qcow2
You can then download over winscp and upload to the GUI Disks page and attach to a VM -- Sometimes if you have errors on boot you need to choose a different CPU or set HDD to IDE or virtIO-Sata. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GZ526EVNG5Q4TU...
On Wed, Mar 23, 2022 at 3:09 PM <nicolas@devels.es> wrote:
We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page? https://github.com/brimstone/metasploitable3/releases If not, can you share the image? It will help if we can reproduce this problem locally with the same image you are using.
using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format.
Did you convert the vmdk file from the ova to qcow2?
No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM.
To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected.
The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same.
What are we missing here? Is anything else needed to do so the disk is bootable?
It sounds like you converted an image from another virtualization system (virtualbox) to qcow2 format, which may not be good enough to use the virtual machine. oVirt supports importing OVA, but based on the UI, it supports only OVA created by oVirt. You can try virt-v2v - this is an example command, you need to fill in the {} parts: virt-v2v \ -i ova {path-to-ova-file} \ -o rhv-upload \ -oc https://{engine-address}/ovirt-engine/api \ -op {engine-password-file} \ -on {vm-name} \ -os {storrage-domain-name} \ -of qcow2 \ -oo rhv-cafile={engine-ca-file} \ -oo rhv-cluster={cluster-name} I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails with this error: virt-v2v: error: inspection could not detect the source guest (or physical machine). attached virt-v2v log. Nir
On Sun, Mar 27, 2022 at 12:24 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Wed, Mar 23, 2022 at 3:09 PM <nicolas@devels.es> wrote:
We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page? https://github.com/brimstone/metasploitable3/releases
If not, can you share the image? It will help if we can reproduce this problem locally with the same image you are using.
using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format.
Did you convert the vmdk file from the ova to qcow2?
No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM.
To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected.
The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same.
What are we missing here? Is anything else needed to do so the disk is bootable?
It sounds like you converted an image from another virtualization system (virtualbox) to qcow2 format, which may not be good enough to use the virtual machine.
oVirt supports importing OVA, but based on the UI, it supports only OVA created by oVirt.
That information message is incorrect, both OVAs that are created by oVirt/RHV and OVAs that are created by VMware are supported It could work for OVAs that are VMware-compatible though Posted https://github.com/oVirt/ovirt-engine/pull/191 to emphasis that
You can try virt-v2v - this is an example command, you need to fill in the {} parts:
virt-v2v \ -i ova {path-to-ova-file} \ -o rhv-upload \ -oc https://{engine-address}/ovirt-engine/api \ -op {engine-password-file} \ -on {vm-name} \ -os {storrage-domain-name} \ -of qcow2 \ -oo rhv-cafile={engine-ca-file} \ -oo rhv-cluster={cluster-name}
I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails with this error:
virt-v2v: error: inspection could not detect the source guest (or physical machine).
attached virt-v2v log.
Nir
On Sun, Mar 27, 2022 at 01:18:43PM +0300, Arik Hadas wrote:
That information message is incorrect, both OVAs that are created by oVirt/RHV and OVAs that are created by VMware are supported It could work for OVAs that are VMware-compatible though
"VMware-compatible" is doing a bit of work there. Virt-v2v only supports (and more importantly _tests_) OVAs produced by VMware. Anything claiming to be "VMware-compatible" might or might not work. I'm on holiday at the moment but I can have a look at the OVA itself when I get back if someone posts a link. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v
On Sun, Mar 27, 2022 at 9:09 PM Richard W.M. Jones <rjones@redhat.com> wrote:
On Sun, Mar 27, 2022 at 01:18:43PM +0300, Arik Hadas wrote:
That information message is incorrect, both OVAs that are created by oVirt/RHV and OVAs that are created by VMware are supported It could work for OVAs that are VMware-compatible though
"VMware-compatible" is doing a bit of work there. Virt-v2v only supports (and more importantly _tests_) OVAs produced by VMware. Anything claiming to be "VMware-compatible" might or might not work.
I'm on holiday at the moment but I can have a look at the OVA itself when I get back if someone posts a link.
The v2v log was from this image: https://github.com/brimstone/metasploitable3/releases/download/0.1.4/Metaspl...
On Sun, Mar 27, 2022 at 10:54:54PM +0300, Nir Soffer wrote:
On Sun, Mar 27, 2022 at 9:09 PM Richard W.M. Jones <rjones@redhat.com> wrote:
On Sun, Mar 27, 2022 at 01:18:43PM +0300, Arik Hadas wrote:
That information message is incorrect, both OVAs that are created by oVirt/RHV and OVAs that are created by VMware are supported It could work for OVAs that are VMware-compatible though
"VMware-compatible" is doing a bit of work there. Virt-v2v only supports (and more importantly _tests_) OVAs produced by VMware. Anything claiming to be "VMware-compatible" might or might not work.
I'm on holiday at the moment but I can have a look at the OVA itself when I get back if someone posts a link.
The v2v log was from this image: https://github.com/brimstone/metasploitable3/releases/download/0.1.4/Metaspl...
$ tar xf Metasploitable3-0.1.4.ova $ guestfish --ro -a Metasploitable\ 3-disk001.vmdk -a Metasploitable\ 3-disk002.vmdk Welcome to guestfish, the guest filesystem shell for editing virtual machine filesystems and disk images. Type: ‘help’ for help on commands ‘man’ to read the manual ‘quit’ to quit the shell
<fs> run <fs> list-filesystems /dev/sda: vfat /dev/sdb1: ntfs
<fs> mount /dev/sda / <fs> ll / total 123719 drwxr-xr-x 2 root root 512 Jan 1 1970 . drwxr-xr-x 19 root root 4096 Mar 28 08:29 .. -rwxr-xr-x 1 root root 318173 Jul 4 2017 grldr -rwxr-xr-x 1 root root 122798595 Jul 4 2017 initramfs.gz -rwxr-xr-x 1 root root 3564944 Jul 4 2017 kernel.gz -rwxr-xr-x 1 root root 193 Jul 4 2017 menu.lst <fs> cat /menu.lst default 1 timeout 0
color cyan/blue white/blue
title Installer find --set-root /BOOTMGR && chainloader /BOOTMGR && boot find --set-root /kernel.gz kernel /kernel.gz quiet initrd /initramfs.gz
<fs> umount /
<fs> mount /dev/sdb1 / <fs> ll / total 29 drwxrwxrwx 1 root root 4096 Feb 18 2018 . drwxr-xr-x 19 root root 4096 Mar 28 08:29 .. -rwxrwxrwx 1 root root 1783 Feb 18 2018 COPYING -rwxrwxrwx 1 root root 3601 Feb 18 2018 LICENSE -rwxrwxrwx 1 root root 2900 Feb 18 2018 gitlog.txt -rwxrwxrwx 1 root root 107 Feb 18 2018 install.cmd -rwxrwxrwx 1 root root 3316 Feb 18 2018 log.bat drwxrwxrwx 1 root root 4096 Feb 18 2018 resources drwxrwxrwx 1 root root 0 Feb 18 2018 scripts -rwxrwxrwx 1 root root 36 Feb 18 2018 variables.txt drwxrwxrwx 1 root root 0 Feb 18 2018 win2k8r2
libguestfs inspection has no idea what to make of this. I guess it's some very custom embedded Linux. Virt-v2v cannot do generalised conversions, it only works for a narrow range of supported guests: https://libguestfs.org/virt-v2v-support.1.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW
Hi Nir, El 2022-03-27 10:23, Nir Soffer escribió:
On Wed, Mar 23, 2022 at 3:09 PM <nicolas@devels.es> wrote:
We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page? https://github.com/brimstone/metasploitable3/releases
Actually, the disk has been shared with us by one of our professors. It has been provided in qcow2, vmdk and raw formats, still the result was the same. I don't actually know which exact version is it, I just know the version is "3".
If not, can you share the image? It will help if we can reproduce this problem locally with the same image you are using.
I will provide the link off-list because it belongs to the professor.
using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format.
Did you convert the vmdk file from the ova to qcow2?
Yes, I also tried these steps with the same result.
No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM.
To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected.
The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same.
What are we missing here? Is anything else needed to do so the disk is bootable?
It sounds like you converted an image from another virtualization system (virtualbox) to qcow2 format, which may not be good enough to use the virtual machine.
oVirt supports importing OVA, but based on the UI, it supports only OVA created by oVirt.
You can try virt-v2v - this is an example command, you need to fill in the {} parts:
virt-v2v \ -i ova {path-to-ova-file} \ -o rhv-upload \ -oc https://{engine-address}/ovirt-engine/api \ -op {engine-password-file} \ -on {vm-name} \ -os {storrage-domain-name} \ -of qcow2 \ -oo rhv-cafile={engine-ca-file} \ -oo rhv-cluster={cluster-name}
I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails with this error:
virt-v2v: error: inspection could not detect the source guest (or physical machine).
attached virt-v2v log.
Actually, the professor also provided the OVA from which he extracted the disk files and the import process in oVirt worked with no issues. I can now boot the VM, not sure what difference made the OVA but now it works. Thanks! Nicolás
Nir
On Mon, Mar 28, 2022 at 11:01 AM <nicolas@devels.es> wrote:
Hi Nir,
El 2022-03-27 10:23, Nir Soffer escribió:
On Wed, Mar 23, 2022 at 3:09 PM <nicolas@devels.es> wrote:
We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page? https://github.com/brimstone/metasploitable3/releases
Actually, the disk has been shared with us by one of our professors. It has been provided in qcow2, vmdk and raw formats, still the result was the same. I don't actually know which exact version is it, I just know the version is "3".
If not, can you share the image? It will help if we can reproduce this problem locally with the same image you are using.
I will provide the link off-list because it belongs to the professor.
using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format.
Did you convert the vmdk file from the ova to qcow2?
Yes, I also tried these steps with the same result.
No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM.
To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected.
The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same.
What are we missing here? Is anything else needed to do so the disk is bootable?
It sounds like you converted an image from another virtualization system (virtualbox) to qcow2 format, which may not be good enough to use the virtual machine.
oVirt supports importing OVA, but based on the UI, it supports only OVA created by oVirt.
You can try virt-v2v - this is an example command, you need to fill in the {} parts:
virt-v2v \ -i ova {path-to-ova-file} \ -o rhv-upload \ -oc https://{engine-address}/ovirt-engine/api \ -op {engine-password-file} \ -on {vm-name} \ -os {storrage-domain-name} \ -of qcow2 \ -oo rhv-cafile={engine-ca-file} \ -oo rhv-cluster={cluster-name}
I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails with this error:
virt-v2v: error: inspection could not detect the source guest (or physical machine).
attached virt-v2v log.
Actually, the professor also provided the OVA from which he extracted the disk files and the import process in oVirt worked with no issues. I can now boot the VM, not sure what difference made the OVA but now it works.
Great that you solved this issue. For the benefit of the community, can you explain how you imported the OVA?
El 2022-03-28 13:12, Nir Soffer escribió:
On Mon, Mar 28, 2022 at 11:01 AM <nicolas@devels.es> wrote:
Hi Nir,
El 2022-03-27 10:23, Nir Soffer escribió:
On Wed, Mar 23, 2022 at 3:09 PM <nicolas@devels.es> wrote:
We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page? https://github.com/brimstone/metasploitable3/releases
Actually, the disk has been shared with us by one of our professors. It has been provided in qcow2, vmdk and raw formats, still the result was the same. I don't actually know which exact version is it, I just know the version is "3".
If not, can you share the image? It will help if we can reproduce this problem locally with the same image you are using.
I will provide the link off-list because it belongs to the professor.
using the GUI (Storage -> Disks -> Upload -> Start). The image is in qcow2 format.
Did you convert the vmdk file from the ova to qcow2?
Yes, I also tried these steps with the same result.
No options on the right side were checked. The upload went smoothly, so we now tried to attach the disk to a VM.
To do that, we opened the VM -> Disks -> Attach and selected the disk. As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so the "bootable" checkbox was selected.
The VM was later powered on, but when accessing the console the message "No bootable device." appears. We're pretty sure this is a bootable image, because it was tested on other virtualization infrastructure and it boots well. We also tried to upload the image in RAW format but the result is the same.
What are we missing here? Is anything else needed to do so the disk is bootable?
It sounds like you converted an image from another virtualization system (virtualbox) to qcow2 format, which may not be good enough to use the virtual machine.
oVirt supports importing OVA, but based on the UI, it supports only OVA created by oVirt.
You can try virt-v2v - this is an example command, you need to fill in the {} parts:
virt-v2v \ -i ova {path-to-ova-file} \ -o rhv-upload \ -oc https://{engine-address}/ovirt-engine/api \ -op {engine-password-file} \ -on {vm-name} \ -os {storrage-domain-name} \ -of qcow2 \ -oo rhv-cafile={engine-ca-file} \ -oo rhv-cluster={cluster-name}
I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails with this error:
virt-v2v: error: inspection could not detect the source guest (or physical machine).
attached virt-v2v log.
Actually, the professor also provided the OVA from which he extracted the disk files and the import process in oVirt worked with no issues. I can now boot the VM, not sure what difference made the OVA but now it works.
Great that you solved this issue.
For the benefit of the community, can you explain how you imported the OVA?
I uploaded the OVA to one of the hosts. Then in the GUI, went to Compute
Virtual Machines and chose the '...' icon on the right, and clicked on 'Import'. As the source, I chose "Virtual Appliance (OVA)" and wrote down the path of the OVA I uploaded before. Then I just dragged the VM to the right and clicked ok, the import process went perfectly.
Thanks. Regards.
participants (7)
-
Abe E -
Angus Clarke -
Arik Hadas -
nicolas＠devels.es -
Nir Soffer -
Richard W.M. Jones -
uli.iske＠elkb.de