Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core: Allow RunOnce for single non-bootable disk #611

Merged
merged 1 commit into from
Sep 1, 2022

Conversation

smelamud
Copy link
Member

If a VM contains a single disk not marked as bootable, RunVmCommand
allows to boot OS from this disk. But RunOnce ignores this disk when
setting the boot order. This patch fixes this inconsistence.

Change-Id: Ia5652bb1549bdd5205284be355e3a2903fb6e9f1
Signed-off-by: Shmuel Melamud smelamud@redhat.com

If a VM contains a single disk not marked as bootable, RunVmCommand
allows to boot OS from this disk. But RunOnce ignores this disk when
setting the boot order. This patch fixes this inconsistence.

Change-Id: Ia5652bb1549bdd5205284be355e3a2903fb6e9f1
Signed-off-by: Shmuel Melamud <smelamud@redhat.com>
Copy link
Member

@ahadas ahadas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the change makes sense

@smelamud smelamud merged commit 0dabcf4 into oVirt:master Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants