Hide Forgot
Description of problem: When creating a vm with virtIO drivers for disk, vm starts with the ide driver Version-Release number of selected component (if applicable): latest ovirt engine source How reproducible: create a disk vm through the webadmin interface with virtio drivers. Steps to Reproduce: 1. 2. 3. Actual results: when starting the vm, virtio appear to be used in the webadmin interface as expected. When doing virsh edit vm on the node, ide drivers are used instead of virtio as expected. Expected results: <bus=virtio> Additional info: On the linux vm, vda must appear instead of hda
When starting the VM, the GUI doesn't send to the engine-core any parameters regarding the VM disks/drivers -> moving to the engine-core component for further investigation.
i assume this has been fixed since, need to do sanity test and close
This is working on the current codebase. Virtio disk devices show as e.g. /dev/vda in the VM, and virsh reports "<target dev='vda' bus='virtio'/>".