-
Notifications
You must be signed in to change notification settings - Fork 201
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
Add bitmap info to getQemuImageInfo #394
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you could add a simple test for getQemuImageInfo
with the new bitmaps information?
Something simple that creates an image, adds some bitmaps and different formats, and then checks that the info obtained is correct.
02b9fe8
to
2b7e694
Compare
2b7e694
to
7c41bd5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! Thanks for adding the checks on all those tests. Minor comment on a couple imports, but overall looks good to me.
I'll launch the pipelines to check how it looks :)
12fa5aa
to
d41690d
Compare
All fixed! CI passes (except the unrelated failure on CI / test-storage-user (centos-9)) |
Thanks! Can you please amend the last commit and push to re-trigger the CI? The test that failed is the mailbox test that tends to fail if the runners are slow. Should be safe to retry. |
You should be able to retry the run in the actions tab on GitHub. I can push again later otherwise :) |
/ost |
/ost |
1 similar comment
/ost |
Extend the GetQemuImageInfoVDSCommand command to also provide information about the bitmaps. This data will only be valid when the hypervisor has the qemu_image_info_bitmaps capability. The bitmap information can be used to validate the engine's bitmap data with the qemu-img info. VDSM PR: oVirt/vdsm#394 Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
We add bitmap info the the getQemuImageInfo output so this can be used within ovirt-engine. Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
d41690d
to
ea1a662
Compare
Extend the GetQemuImageInfoVDSCommand command to also provide information about the bitmaps. This data will only be valid when the hypervisor has the qemu_image_info_bitmaps capability. The bitmap information can be used to validate the engine's bitmap data with the qemu-img info. VDSM PR: oVirt/vdsm#394 Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
Extend the GetQemuImageInfoVDSCommand command to also provide information about the bitmaps. This data will only be valid when the hypervisor has the qemu_image_info_bitmaps capability. The bitmap information can be used to validate the engine's bitmap data with the qemu-img info. VDSM PR: oVirt/vdsm#394 Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
Extend the GetQemuImageInfoVDSCommand command to also provide information about the bitmaps. This data will only be valid when the hypervisor has the qemu_image_info_bitmaps capability. The bitmap information can be used to validate the engine's bitmap data with the qemu-img info. VDSM PR: oVirt/vdsm#394 Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
Extend the GetQemuImageInfoVDSCommand command to also provide information about the bitmaps. This data will only be valid when the hypervisor has the qemu_image_info_bitmaps capability. The bitmap information can be used to validate the engine's bitmap data with the qemu-img info. VDSM PR: oVirt/vdsm#394 Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
Extend the GetQemuImageInfoVDSCommand command to also provide information about the bitmaps. This data will only be valid when the hypervisor has the qemu_image_info_bitmaps capability. The bitmap information can be used to validate the engine's bitmap data with the qemu-img info. VDSM PR: oVirt/vdsm#394 Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be>
We add bitmap info the the getQemuImageInfo output so this can be used within ovirt-engine.
This might be a cleaner alternative to #393
As we just extend the existing call to also return the bitmap info.