RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 949411 - error shows when click disk during installation from virt-manager
Summary: error shows when click disk during installation from virt-manager
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Kletzander
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-08 06:17 UTC by tingting zheng
Modified: 2014-06-17 23:59 UTC (History)
15 users (show)

Fixed In Version: virt-manager-0.10.0-0.4.gitb68faac8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:23:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description tingting zheng 2013-04-08 06:17:20 UTC 
Description
error shows when click disk during installation from virt-manager

Version:
virt-manager-0.9.5-1.el7.noarch
libvirt-1.0.3-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. #virt-manager
2. "Create a new virtual machine" -> Name "rhel6.4" -> Network Boot(PXE).
3. Forward -> check off "Allocate entire disk now" -> Forward -> check on "Customize configuration before install"-> Finish
4. Click "Disk 1",error shows:Error refreshing hardware page: unsupported operand type(s) for /: 'NoneType' and 'int'
Detail error info:
Error refreshing hardware page: unsupported operand type(s) for /: 'NoneType' and 'int'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/details.py", line 1307, in hw_selected
    self.refresh_disk_page()
  File "/usr/share/virt-manager/virtManager/details.py", line 2905, in refresh_disk_page
    iotune_read_bytes_sec = disk.iotune_read_bytes_sec / 1024
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'

Actual results：
As describes.

Expected results:
There is no such error.

Additional info:
Tried virt-manager-0.9.4-4.el7 and virt-manager-0.9.0-18.el6,there is no such error.
Comment 2 Adam Huffman 2013-04-16 12:15:17 UTC 
I'm also seeing this on a Fedora 18 machine, with the following version of virt-manager:

virt-manager-0.9.5-1.fc18.noarch
Comment 3 Grzegorz Witkowski 2013-04-17 00:16:51 UTC 
I hit the same problem on Fedora release 17 (Beefy Miracle) with 3.8.4-102.fc17.x86_64 kernel, but it looks to me like a cosmetic issue.
Click the Start installation button, continue the installation and switch back to the "Show virtual hardware details", the (i) button and now you can click the disk and see its details and the system install completes with no problem.

libvirt-daemon-config-network-0.9.11.9-1.fc17.x86_64
libvirt-client-0.9.11.9-1.fc17.x86_64
libvirt-daemon-kvm-0.9.11.9-1.fc17.x86_64
libvirt-daemon-config-nwfilter-0.9.11.9-1.fc17.x86_64
libvirt-0.9.11.9-1.fc17.x86_64
libvirt-daemon-0.9.11.9-1.fc17.x86_64
libvirt-python-0.9.11.9-1.fc17.x86_64
virt-viewer-0.5.3-1.fc17.x86_64
python-virtinst-0.600.4-1.fc17.noarch
virt-manager-common-0.9.5-1.fc17.noarch
virt-manager-0.9.5-1.fc17.noarch

# ps -ef | grep rhel
qemu      4672     1  6 00:44 ?        00:00:25 /usr/bin/qemu-kvm -S -M pc-0.15 -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -name RHEL64-SAN -uuid 041ac405-17ce-5331-ae1f-93ea1c54f8ec -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/RHEL64-SAN.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/home/user123/KVM/images/RHEL64-SAN.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/mnt/WD10EAVS-EXT4/Resources/ISO/RHEL/rhel-server-6.4-x86_64-dvd.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5a:e7:ff,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5902,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
Comment 4 Aaron Sowry 2013-05-10 08:39:30 UTC 
(In reply to comment #3)
> I hit the same problem on Fedora release 17 (Beefy Miracle) with
> 3.8.4-102.fc17.x86_64 kernel, but it looks to me like a cosmetic issue.

Unfortunately it's more than cosmetic. If you want to create a new machine with storage format qcow (to support snapshots for example), you apparently need to do this at creation time.

Also seeing this issue on F18.
Comment 5 Louis van Dyk 2013-05-17 11:55:20 UTC 
I have the same problem with the same versions.

If I try to create it on my Fedora 18 PC, I cannot create the new Virtual Machine.  Also if I click on Disk if I choose to set advanced options, I get the same error.  Also if I then delete the Disk and create another one - e.g. SCSI Disk - in its place I get the same error.

Running virt-manager on my Fedora 18 PC and trying to create a virtual machine on an E.L. 6.3 server I also have the same problem.

Agreed that it's NOT cosmetic.  I cannot get a new virtual machine to start.
Comment 6 Volker Fröhlich 2013-05-30 13:19:31 UTC 
The error message does not appear with a F18 rebuild of virt-manager-0.10.0-0.5.gitde1695b2.fc19.
Comment 7 Martin Kletzander 2013-05-30 14:50:55 UTC 
Could you try to reproduce that with the latest package of virt-manager?  Thanks.
Comment 8 tingting zheng 2013-05-31 02:24:27 UTC 
(In reply to Martin Kletzander from comment #7)
> Could you try to reproduce that with the latest package of virt-manager? 
> Thanks.

I can not reproduce this issue on latest build:
virt-manager-0.10.0-0.4.gitb68faac8.el7.noarch
libvirt-1.0.5-2.el7.x86_64
Comment 9 Martin Kletzander 2013-05-31 10:11:01 UTC 
Moving to MODIFIED with commit RELEASE-0.9.5-1-141-g61369d2:

commit 61369d252c08a45e2e947bac9437979e417104c0
Author: Cole Robinson <crobinso>
Date:   Wed Apr 17 13:23:27 2013 -0400

    details: Fixing viewing disk details in 'customize' page
Comment 10 tingting zheng 2013-06-04 02:31:35 UTC 
Refer to comment 8,move the bug to VERIFIED.
Comment 11 Ludek Smid 2014-06-13 12:23:02 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.