Bug 1225771 - Unable to create new VM using "New VM" wizard - "Error: Argument 1 does not allow None as a value"
Summary: Unable to create new VM using "New VM" wizard - "Error: Argument 1 does not a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 22
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-28 08:50 UTC by Peter Rajnoha
Modified: 2015-08-18 05:14 UTC (History)
5 users (show)

Fixed In Version: virt-manager-1.2.1-2.fc22
Clone Of:
Environment:
Last Closed: 2015-08-18 05:14:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Debug log from virt-manager --debug when "New VM" wizard fails (19.46 KB, text/plain)
2015-05-28 08:50 UTC, Peter Rajnoha
no flags Details
Debug log from virt-manager --debug when "New VM" wizard fails (with virt-manager-1.2.1-1.fc22) (19.90 KB, text/plain)
2015-06-09 07:16 UTC, Peter Rajnoha
no flags Details

Description Peter Rajnoha 2015-05-28 08:50:16 UTC
Created attachment 1031097 [details]
Debug log from virt-manager --debug when "New VM" wizard fails

Description of problem:
Recently, I've upgraded to F22 from F21 and I'm not able to create new VM in virt-manager anymore. The "New VM" wizard displays only the error message "Error: Argument 1 does not allow None as a value".

Version-Release number of selected component (if applicable):
$ rpm -q virt-manager
virt-manager-1.2.0-1.fc22.noarch

Actual results:
The error message displauyed when "New VM" wizard is called.

Expected results:
"New VM" wizard to allow me to create a new VM.


Additional info:
I've tried to run "virt-manager --debug", the log is attached.

Comment 1 Marian Csontos 2015-06-01 11:09:48 UTC
May be something to do the fact wlan0 is no longer wlan0 in F22?

Try Edit > Connection Details on localhost (QEMU), go to Network Interfaces and replace the wlan0 with correct name.

[Thu, 28 May 2015 10:41:23 virt-manager 12300] DEBUG (mediacombo:167) Error populating mediadev combo
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/mediacombo.py", line 165, in reset_state
    self._populate_media()
  File "/usr/share/virt-manager/virtManager/mediacombo.py", line 138, in _populate_media
    for nodedev in self.conn.filter_nodedevs(devtype="storage"):
  File "/usr/share/virt-manager/virtManager/connection.py", line 599, in filter_nodedevs
    xmlobj = dev.get_xmlobj()
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 337, in get_xmlobj
    self.ensure_latest_xml()
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 290, in ensure_latest_xml
    self.__force_refresh_xml(nosignal=nosignal)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 305, in __force_refresh_xml
    active_xml = self._XMLDesc(self._active_xml_flags)
  File "/usr/share/virt-manager/virtManager/nodedev.py", line 40, in _XMLDesc
    return self._backend.XMLDesc(flags)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 5086, in XMLDesc
    if ret is None: raise libvirtError ('virNodeDeviceGetXMLDesc() failed')
libvirtError: unable to read: /sys/class/net/wlan0/operstate: No such file or directory

Comment 2 Peter Rajnoha 2015-06-01 11:21:45 UTC
Not sure, I didn't set any of "wlan*" before, I just upgraded to F22 and I hit the error as reported...

Comment 3 Cole Robinson 2015-06-06 18:26:29 UTC
I'm not sure what is causing that wlan0 issue, seems like a libvirt problem. But it's tickling the virt-manager failure here. These virt-manager patches should avoid it

commit 07d02a13fdca1bfd11d15e2db0b0bf594558caf3
Author: Cole Robinson <crobinso>
Date:   Sat Jun 6 14:23:23 2015 -0400

    mediacombo: Ensure has_media returns bool

commit 68908c2d81fec635c0aba1bf3d4d008a06aa289a
Author: Cole Robinson <crobinso>
Date:   Sat Jun 6 14:20:21 2015 -0400

    connection: Handle nodedevs disappearing in filter_nodedevs (bz 1225545)
    
    Not exactly sure how we end up with a nodedev in the list that doesn't
    have cached XML, but whatever

Comment 4 Fedora Update System 2015-06-06 22:30:44 UTC
virt-manager-1.2.1-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/virt-manager-1.2.1-1.fc22

Comment 5 Peter Rajnoha 2015-06-08 07:31:12 UTC
Well, I've tried virt-manager-1.2.1-1.fc22.noarch, but I'm still seeing the issue (same log as pasted before).

Comment 6 Cole Robinson 2015-06-08 16:16:44 UTC
(In reply to Peter Rajnoha from comment #5)
> Well, I've tried virt-manager-1.2.1-1.fc22.noarch, but I'm still seeing the
> issue (same log as pasted before).

Make sure you fully restart virt-manager, then please post the virt-manager --debug output again... line numbers should have changed at least

Comment 7 Peter Rajnoha 2015-06-09 07:16:52 UTC
Created attachment 1036616 [details]
Debug log from virt-manager --debug when "New VM" wizard fails (with virt-manager-1.2.1-1.fc22)

OK, I've tried again, fully restarted. Please, see the log.

Comment 8 Cole Robinson 2015-06-09 15:17:42 UTC
Thanks Peter, my fix was incomplete for your error. I'll poke at it.

The root issue is that libvirt is failing when trying to dumpxml for your wireless nic nodedev.

Peter, can you try to find your NIC in 'sudo virsh nodedev-list ' (it probably has wlan0 in the name), verify that 'sudo virsh nodedev-dumpxml $nodedev-name' fails, and file a fedora libvirt bug about that?

Comment 9 Cole Robinson 2015-06-09 15:43:41 UTC
I pushed this patch upstream:

commit 77423e7a8d2061f06f9f7d0b7a791821a134c8f7
Author: Cole Robinson <crobinso>
Date:   Tue Jun 9 11:41:39 2015 -0400

    connection: catch more errors in filter_nodedevs (bug 1225771)


Peter, can you test?

git clone git://git.fedorahosted.org/virt-manager.git
cd virt-manager
./virt-manager --debug


(but even if that's fixed, please also file the libvirt bug requested in comment #8 so we can fix the root issue)

Comment 10 Peter Rajnoha 2015-06-10 07:07:29 UTC
(In reply to Cole Robinson from comment #9)
> Peter, can you test?
> 
> git clone git://git.fedorahosted.org/virt-manager.git
> cd virt-manager
> ./virt-manager --debug
> 

Yes, that allows me to move along with the wizard now. Thanks!

> 
> (but even if that's fixed, please also file the libvirt bug requested in
> comment #8 so we can fix the root issue)

Yup, filed as bug #1230024. Seems the "wlan0" is just a stale record (there's another one for the correct wireless dev name).

Comment 11 Cole Robinson 2015-06-10 14:14:19 UTC
Thanks Peter. Setting this to POST to track the virt-manager workaround

Comment 12 Fedora Update System 2015-08-11 20:11:54 UTC
virt-manager-1.2.1-2.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/virt-manager-1.2.1-2.fc22

Comment 13 Fedora Update System 2015-08-13 16:53:46 UTC
Package virt-manager-1.2.1-2.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-1.2.1-2.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-13390/virt-manager-1.2.1-2.fc22
then log in and leave karma (feedback).

Comment 14 Fedora Update System 2015-08-18 05:14:17 UTC
virt-manager-1.2.1-2.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


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