Bug 772227

Summary: When creating a vm with virtIO drivers for disk, vm starts with the ide driver
Product: [Retired] oVirt Reporter: exploit
Component: ovirt-engine-coreAssignee: Greg Padgett <gpadgett>
Status: CLOSED WORKSFORME QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, amureini, ecohen, iheim, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-15 13:40:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description exploit 2012-01-06 14:27:19 UTC 
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
Comment 1 Einav Cohen 2012-01-09 09:22:18 UTC 
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.
Comment 2 Itamar Heim 2012-06-10 08:28:47 UTC 
i assume this has been fixed since, need to do sanity test and close
Comment 3 Greg Padgett 2012-06-15 13:40:08 UTC 
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'/>".