Bug #9903
closed
Image-based provisioning into Libvirt-resource uses "network" as first boot device for such VMs
Description
During image-based provisioning into Libvirt compute-resource I found that newly created VM has "network" as first boot device, which is incorrect.
The possible suspect is missing "image_id" that is supposed to be passed and considered here:
Also, the QCOW image created during the same VM create operation does not have a backing image specified at all making such VM unbootable off that disk/image. Again, missing "image_id" may be at play, IMHO.
Updated by Konstantin Orekhov about 10 years ago
- Status changed from New to Closed
False alarm, this is not a bug. My KVM HV had isues with apparmor settings. After running these commands, image-based VM provisioning through UI works as expected. API call needs to be reviewed and fixed as it apparently does something else wrong.
$ sudo apt-get install apparmor-profiles apparmor-utils
$ sudo aa-complain /usr/lib/libvirt/virt-aa-helper
Thanks!