When booting Instance the hw_video_head property isn't retrieved from the image metadata

Bug #1304937 reported by Omri Hochman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

When booting Instance the hw_video_head property isn't retrieved from the image metadata :

This functionality of modifying the number of heads for spice users should have been added in Ice-House
according to BP :
https://blueprints.launchpad.net/nova/+spec/libvirt-video-driver-selection

I've tested the other video properties (hw_video_model , hw_video_ram ) and they seems to work fine ,
the only problem is with: 'hw_video_head' .

Steps:
-----------

- nova flavor-key m1.small set hw_video:ram_max_mb=128

- glance image-update rhel64 --property hw_video_model=qxl
- glance image-update rhel64 --property hw_video_ram=64
- glance image-update rhel64 --property hw_video_head=2

+----------------------------+--------------------------------------+
| Property | Value |
+----------------------------+--------------------------------------+
| Property 'hw_video_head' | 2 |
| Property 'hw_video_model' | qxl |
| Property 'hw_video_ram' | 64 |

- boot instance from that image ^^

Look at :
---------------
/var/lib/nova/instances/<Instace ID>/libvirt.xml

<video>
      <model type="qxl" vram="64"/>
    </video>
  </devices>
</domain>

Results:
------------
- the hw_video_head property isn't retrieved from the image metadata
- there's no mention of it in the libvirt.xml

Tags: libvirt
Revision history for this message
Vladan Popovic (vpopovic) wrote :

There's no patch that retrieves the hw_video_head property in the libvirt driver, but there is a patch that sets up the libvirt config in nova [1]. This somehow slipped in the review process i guess.

[1] https://review.openstack.org/#/c/58613/6/nova/virt/libvirt/config.py

Tracy Jones (tjones-i)
tags: added: libvirt
Changed in nova:
status: New → In Progress
assignee: nobody → Vladan Popovic (vpopovic)
Revision history for this message
Vladan Popovic (vpopovic) wrote :

Can't choose Won't Fix, so I set it to Invalid status.
The reason is described in this patch - https://review.openstack.org/#/c/87300/

Changed in nova:
assignee: Vladan Popovic (vpopovic) → nobody
status: In Progress → Opinion
status: Opinion → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.