Bug 1151205 - Unable to complete install: 'internal error: No PCI buses available'
Summary: Unable to complete install: 'internal error: No PCI buses available'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL: http://pastebin.com/HEVzQcWy
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-09 19:19 UTC by Phill. Whiteside
Modified: 2014-10-10 22:16 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-10 22:16:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Phill. Whiteside 2014-10-09 19:19:10 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/37.0.2062.94 Chrome/37.0.2062.94 Safari/537.36
Build Identifier: 

When creating a new VM in ubuntu 14.10 the below error occurs at the last step.

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 1820, in do_install
    guest.start_install(meter=meter)
  File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install
    noboot)
  File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest
    dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3398, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error: No PCI buses available

Reproducible: Always

Steps to Reproduce:
1. Select New VM
2. Follow Setup
3. Error occurs
Actual Results:  
Unable to complete install: 'internal error: No PCI buses available'

Expected Results:  
VM should be created

This has been confirmed by another user of 14.10

Comment 1 Cole Robinson 2014-10-09 20:02:15 UTC
Thanks for the report. Please provide:

- libvirt version
- qemu version
- virt-manager version
- virt-manager --debug output when reproducing

Comment 2 Phill. Whiteside 2014-10-09 20:14:05 UTC
2014-10-09 20:04:20.941+0000: 26167: info : libvirt version: 1.2.8, package: 1.2.8-0ubuntu10

QEMU emulator version 2.1.0 (Debian 2.1+dfsg-4ubuntu5), Copyright (c) 2003-2008 Fabrice Bellard


virt-manager is version 1.0.1

phillw@piglet:~$ virt-manager --debug
[Thu, 09 Oct 2014 21:12:50 virt-manager 26261] DEBUG (cli:187) Launched with command line: /usr/share/virt-manager/virt-manager --debug
[Thu, 09 Oct 2014 21:12:50 virt-manager 26261] DEBUG (virt-manager:150) virt-manager version: 1.0.1
[Thu, 09 Oct 2014 21:12:50 virt-manager 26261] DEBUG (virt-manager:151) virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>

** (virt-manager:26261): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
[Thu, 09 Oct 2014 21:12:53 virt-manager 26261] DEBUG (virt-manager:209) GTK version: 3.12.2
[Thu, 09 Oct 2014 21:12:56 virt-manager 26261] DEBUG (engine:484) libguestfs inspection support: False
[Thu, 09 Oct 2014 21:12:56 virt-manager 26261] DEBUG (systray:152) Showing systray: False
[Thu, 09 Oct 2014 21:12:56 virt-manager 26261] DEBUG (engine:231) About to connect to uris ['qemu+ssh://root/system', 'qemu:///system']

Comment 3 Phill. Whiteside 2014-10-10 19:35:22 UTC
Hi Cole Robinson I had a hard drive check in sick, so this reply is later than I would have wished. The other guy on ubuntu 14.10 informed me that a fix appeared 'as if by magic' over night. Both of us doubt this and thank you for the behinds the scenes stuff that goes on.

Feel free to mark this bug as 'fixed'.

Regards,

Phill.

Comment 4 Phill. Whiteside 2014-10-10 22:16:46 UTC
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1379346

marked as fixed.

Thanks.


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