You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A PV guest is correctly shown in the disk tab with the "Boot flag" toggle to toggle a vbd as bootable or not.
Once the machine gets converted from pv to pv-in-pvh, this toggle is not visible anymore.
This is the correct setting for a full hvm machine, because there the bootable flag is not needed anymore as the boot order is defined in a different fashion.
For pv-in-pvh however, the bootable flag is still set just like it is for a pv guest.
To Reproduce
Create a pv guest.
shutdown the guest
unset the bootable flag on the vbd.
observe machine not starting.
convert machine to pv-in-pvh using xe vm-param-set domain-type=pv-in-pvh uuid=...
observe machine not starting with the error indicating that no bootable disk is available.
Set vbd to bootable using xe vbd-param-set uuid=... bootable=true
Start machine correctly
Expected behavior
Ability to toggle bootable flag.
Environment (please provide the following information):
Ah yes, we probably to add another check to display it: not just for "pv" but also "pvh". Can you confirm me the type is pv-in-pvh? That should be trivial to fix :)
Describe the bug
A PV guest is correctly shown in the disk tab with the "Boot flag" toggle to toggle a vbd as bootable or not.
Once the machine gets converted from pv to pv-in-pvh, this toggle is not visible anymore.
This is the correct setting for a full hvm machine, because there the bootable flag is not needed anymore as the boot order is defined in a different fashion.
For pv-in-pvh however, the bootable flag is still set just like it is for a pv guest.
To Reproduce
xe vm-param-set domain-type=pv-in-pvh uuid=...
xe vbd-param-set uuid=... bootable=true
Expected behavior
Ability to toggle bootable flag.
Environment (please provide the following information):
The text was updated successfully, but these errors were encountered: