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

one.vm.updateconf is ignoring VIRTIO_BLK_QUEUES #6414

Closed
2 of 3 tasks
dann1 opened this issue Dec 1, 2023 · 0 comments · Fixed by OpenNebula/docs#2775 or OpenNebula/docs#2776
Closed
2 of 3 tasks

one.vm.updateconf is ignoring VIRTIO_BLK_QUEUES #6414

dann1 opened this issue Dec 1, 2023 · 0 comments · Fixed by OpenNebula/docs#2775 or OpenNebula/docs#2776

Comments

@dann1
Copy link
Contributor

dann1 commented Dec 1, 2023

Description
The whole FEATURE section works when updating the VM configuration, except the newly added VIRTIO_BLK_QUEUES. This results in a VM that cannot have the feature set post deployment.

To Reproduce

  • Instantiate a VM
  • onevm updateconf <vm_id>
    • Add the feature, for example, with
FEATURES=[
  GUEST_AGENT="yes",
  VIRTIO_SCSI_QUEUES="2",
  VIRTIO_BLK_QUEUES="2"]
  • VIRTIO_BLK_QUEUES won't be added

Expected behavior

VIRTIO_BLK_QUEUES should be added like the rest of the features

Details

  • Version: 6.8+

Additional context
Even though there are explicit mentions in the CLI and the API docs, at glance there is no reason why this is the case. Most likely was ignored when the feature was introduced.

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment