Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 598727

Summary: [Intel 6.0 Bug] Could not create a new guest or open an old guest image on RHEL6.0, it always reports errors
Product: Red Hat Enterprise Linux 6 Reporter: sibai.li
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: low    
Version: 6.0CC: bburns, crobinso, ddugger, jane.lv, jvillalo, luyu, notting, rpacheco
Target Milestone: rc   
Target Release: 6.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-09 19:33:16 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:
Bug Depends On:    
Bug Blocks: 562808, 576638    

Description sibai.li 2010-06-01 22:31:01 UTC
Description of problem:
Could not create a new guest or open an old guest image on RHEL6.0, it always reports errors

Version-Release number of selected component (if applicable):
Redhat kernel: 2.6.32-28.el6.x86_64


How reproducible:
(1)Run VMM to create a new guest image, follow the steps to create a new image.
(2) it reports that Uninstall to complete install: 'internal error Process exited while reading console log output:char device redirected to /dev/pts/3//qemu:could not open disk image /var/lib/kvm-vm1-1.img: invalid argument.

(3)Check /var/lib/ the image is already created.


Additional info:
Log file
login as: root
root.22.61's password:
[root@localhost ~]# cd /var/log
[root@localhost log]# ls
anaconda.log          cluster     maillog           secure
anaconda.program.log  ConsoleKit  mcelog            spooler
anaconda.storage.log  cron        messages          sssd
anaconda.syslog       dmesg       ntpstats          tallylog
anaconda.xlog         dmesg.old   piranha           wpa_supplicant.log
anaconda.yum.log      gdm         pm-powersave.log  wtmp
audit                 httpd       ppp               Xorg.0.log
boot.log              lastlog     prelink           Xorg.0.log.old
brcm-iscsi.log        libvirt     sa                Xorg.9.log
btmp                  luci        samba             yum.log
[root@localhost log]# tail messages
Jun  1 10:26:45 localhost libvirtd: 10:26:45.066: error : storageVolumeLookupByName:1157 : Storage volume not found: no storage vol with matching name 'vm1.img'
Jun  1 10:26:45 localhost libvirtd: 10:26:45.129: error : storageVolumeLookupByPath:1242 : invalid storage volume pointer in no storage vol with matching path
Jun  1 10:26:45 localhost kernel: device vnet0 entered promiscuous mode
Jun  1 10:26:45 localhost kernel: virbr0: topology change detected, propagating
Jun  1 10:26:45 localhost kernel: virbr0: port 1(vnet0) entering forwarding state
Jun  1 10:26:45 localhost NetworkManager[2090]: <warn> /sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring...
Jun  1 10:26:45 localhost kernel: virbr0: port 1(vnet0) entering disabled state
Jun  1 10:26:45 localhost kernel: device vnet0 left promiscuous mode
Jun  1 10:26:45 localhost kernel: virbr0: port 1(vnet0) entering disabled state
Jun  1 10:26:45 localhost libvirtd: 10:26:45.687: error : qemudReadLogOutput:2251 : internal error Process exited while reading console log output: char device redirected to /dev/pts/3#012qemu: could not open disk image /var/lib/libvirt/images/vm1.img: Invalid argument#012
[root@localhost log]#
[root@localhost log]# ll /var/lib/libvirt/images/
total 8388612
-rw-------. 1 root root 8589934592 Jun  1 10:26 vm1.img
[root@localhost log]#

Comment 2 RHEL Program Management 2010-06-02 18:25:52 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Cole Robinson 2010-06-09 19:33:16 UTC
I believe this is fixed in qemu-kvm-0.12.1.2-2.56.el6

*** This bug has been marked as a duplicate of bug 593909 ***