Bug 1090784 - Error starting domain: internal error: Unable to determine model for scsi controller
Summary: Error starting domain: internal error: Unable to determine model for scsi con...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 20
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-24 07:28 UTC by Peter Rajnoha
Modified: 2014-05-27 07:16 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-27 07:16:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The VM XML description (10.34 KB, text/plain)
2014-04-24 07:28 UTC, Peter Rajnoha
no flags Details

Description Peter Rajnoha 2014-04-24 07:28:44 UTC
Created attachment 889194 [details]
The VM XML description

Description of problem:
I have a virtual machine with scsi controller with "default" model defined. I can't start the VM and an error message is issued: "Error starting domain: internal error: Unable to determine model for scsi controller".

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

How reproducible:
I'm just trying to start the VM when the host machine is booted.


Actual results:
Error starting domain: internal error: Unable to determine model for scsi controller

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/asyncjob.py", line 127, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup
    self._backend.create()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: Unable to determine model for scsi controller


Expected results:
VM started without the error above.

Additional info:
After restarting the libvirtd service (systemctl restart libvirtd.service), everything works correctly then.

Let me know if you need more debug info...

Comment 1 Cole Robinson 2014-04-24 12:18:10 UTC
So this is only an issue when trying to autostart the VM on host boot up? If so, does it always reproduce on host boot up?

Comment 2 Peter Rajnoha 2014-04-24 12:25:56 UTC
Nope, I'm starting the VM manually. The error always shows up until the libvirtd.service is restarted. Sorry for the confusion...

Comment 3 Peter Rajnoha 2014-05-27 07:16:49 UTC
I'm not sure if there was any specific update for this, but I can't reproduce this anymore. It seems to be working now (libvirt-1.1.3.5-2.fc20.x86_64).


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