Bug 601531
| Summary: | Can't use virtio storage bus | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Arthur Pemberton <pembo13> | ||||||
| Component: | libvirt | Assignee: | Daniel Veillard <veillard> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 13 | CC: | berrange, clalance, crobinso, itamar, jforbes, veillard, virt-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| 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: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Can you provide the /var/log/libvirt/qemu/$GUESTNAME.log file too Created attachment 422129 [details]
/var/log/libvirt/qemu/Clancy.log
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.
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. |
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.