Bug 601531 - Can't use virtio storage bus
Summary: Can't use virtio storage bus
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
(Show other bugs)
Version: 13
Hardware: All Linux
low
high
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 06:57 UTC by Arthur Pemberton
Modified: 2010-06-08 10:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-08 10:55:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
XML domain file (1.77 KB, text/plain)
2010-06-08 06:57 UTC, Arthur Pemberton
no flags Details
/var/log/libvirt/qemu/Clancy.log (7.29 KB, text/plain)
2010-06-08 10:14 UTC, Arthur Pemberton
no flags Details

Description Arthur Pemberton 2010-06-08 06:57:50 UTC
Created attachment 422070 [details]
XML domain file

Description of problem:
Switching from:
<target dev='hda' bus='ide'/>
to:
<target dev='hda' bus='virtio'/>

causes failure to start the VM with error:
Error initializing device virtio-balloon-pci

Version-Release number of selected component (if applicable):
libvirt-0.7.7-4.fc13.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Setup guest (in my case Windows guest)
2. Change .XML file for guest
3. Restart libvirtd (this may not be necessary)
4. Attempt to start guest using virt-manager
  
Actual results:
Exception from libvirt

Expected results:
VM booted

Additional info:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 799, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1256, in startup
    self._backend.create()
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 317, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/3
PCI: devfn 24 not available for virtio-balloon-pci, in use by virtio-blk-pci
Error initializing device virtio-balloon-pci

I have virtio working on the network interface just fine.

Comment 1 Daniel Berrange 2010-06-08 09:17:10 UTC
Can you provide the /var/log/libvirt/qemu/$GUESTNAME.log file too

Comment 2 Arthur Pemberton 2010-06-08 10:14:28 UTC
Created attachment 422129 [details]
/var/log/libvirt/qemu/Clancy.log

Comment 3 Daniel Berrange 2010-06-08 10:38:56 UTC
Your XML shows that the disk has a drive address assigned:


    <disk type='file' device='disk'>
      <source file='/var/lib/libvirt/images/Clancy.img'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>


when you changed 'ide' to 'virtio' did you also remove the <address> line. The address shows a IDE controller address, whereas virtio disks need a PCI address. If changing from one to the other you need to remove the <address> element and let it be re-generated.

Comment 4 Arthur Pemberton 2010-06-08 10:54:55 UTC
That was the problem. Sorry about that, the docs on using virtio storage are more sparse than those for the network. Now I just need to find out how to add the virtio storage driver to an already installed Windows guest; right now I'm getting blue screens when I try to boot.


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