QEMU custom options behavior change since last updates

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
ppottier
Posts: 1
Joined: Thu Jul 30, 2020 9:37 am

QEMU custom options behavior change since last updates

Post by ppottier » Fri Jul 29, 2022 5:05 pm

Hi,
up to version 4.0.1-65 i was able to specify "-cdrom ../<isofile>" in the QEMU custom options of a node to attach a cloud-init iso image to auto configure the node at 1st start.
Since the upgrade to 4.0.1-86 and then 5.x this do not work anymore.

When I start the node, it just stop itself few seconds later.

After digging a bit, I noticed this is due to the "-cdrom" parameter or more precisely to the fact it is not able to find or access the iso image file 1 level upper to the node directory.
If I place the iso image file to the proper addon qemu directory and set the QEMU custom options to "-cdrom <isofile>" it's then ok because it is well copied at the creation of the node with the qcow2 image.
but unfortunately with all the other iso image file that are not dedicated to the node.

Any idea why this is not working anymore ?

Post Reply