Bug 772227 - When creating a vm with virtIO drivers for disk, vm starts with the ide driver
Summary: When creating a vm with virtIO drivers for disk, vm starts with the ide driver
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Greg Padgett
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-06 14:27 UTC by exploit
Modified: 2016-06-12 23:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-15 13:40:08 UTC
oVirt Team: ---


Attachments (Terms of Use)

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'/>".


Note You need to log in before you can comment on or make changes to this bug.