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 1270277 - aarch64: backtrace on storage allocation
Summary: aarch64: backtrace on storage allocation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.1
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-09 13:21 UTC by Andrew Jones
Modified: 2018-01-27 10:41 UTC (History)
9 users (show)

Fixed In Version: virt-manager-1.3.2-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-27 10:41:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrew Jones 2015-10-09 13:21:23 UTC 
Description:

Using a typical virt-install command line to create a new guest (it's new, so has no storage allocated yet), we get a backtrace. Everything proceeds fine, creating the storage as it should. See below

$ virt-install -n guest -l http://$SERVER/nightly/latest-RHEL-7/compose/Server/aarch64/os/ --vcpus=4 --memory 4096 --disk size=6 --network default --boot uefi

Starting install...
Retrieving file vmlinuz...                                                                                                                               |  11 MB  00:00:05 !!! 
Retrieving file initrd.img...                                                                                                                            |  62 MB  00:00:08 !!! 
Exception in thread Checking storage allocation:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/share/virt-manager/virtinst/storage.py", line 838, in _progress_thread
    ignore, ignore, alloc = vol.info()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3374, in info
    if ret is None: raise libvirtError ('virStorageVolGetInfo() failed', vol=self)
libvirtError: Storage volume not found: no storage vol with matching path '/home/drjones/.local/libvirt/images/guest.qcow2'

Allocating 'guest.qcow2'                                                                                                                            | 6.0 GB  00:00:00     
Creating domain...                                       |    0 B  00:00:01
...

Expected results:
No backtrace
Comment 2 Pavel Hrdina 2015-11-02 14:32:52 UTC 
Hi, I've tried to reproduce it, but I was not able to hit any exception.  Could you please try it again with latest virt-install and libvirt packages and using --debug option?
Comment 3 Andrew Jones 2015-11-16 16:25:47 UTC 
(In reply to Pavel Hrdina from comment #2)
> Hi, I've tried to reproduce it, but I was not able to hit any exception. 
> Could you please try it again with latest virt-install and libvirt packages
> and using --debug option?

Still reproduces with virt-install-1.2.1-8.el7.noarch, which is the version we currently have in the rhelsa virt repo. If it's fixed with a later version, then I guess we need to tag a later build to get that into the repo. Are there 7.3 builds for virt-install and libvirt that we can start taging for rhelsa-7.3 work?

Thanks,
drew
Comment 4 Cole Robinson 2015-11-17 16:07:54 UTC 
I'll be cutting a new virt-manager build before monday, at which point we should pull it into RHEL. So... soon :)
Comment 5 Pavel Hrdina 2015-11-19 16:10:17 UTC 
Upstream commit:

commit 0ccbcd8883c17097b9a3bc5975c1a83517ab0b22
Author: Pavel Hrdina <phrdina>
Date:   Thu Nov 19 14:48:25 2015 +0100

    storage: remove attempt counter from disk allocation thread
    
    Remove the lookup counter from _progress_thread, it's not necessary, the
    loop is terminated by _install_finished boolean.
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1270277
    
    Signed-off-by: Pavel Hrdina <phrdina>
Comment 7 Mike McCune 2016-03-28 23:17:33 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 9 Pavel Hrdina 2016-09-13 11:20:26 UTC 
This bug is now fixed, the installation doesn't print the backtrace anymore.  This can be moved to verified.
Comment 10 tingting zheng 2016-09-13 11:54:50 UTC 
Refer to comment 9,move the bug to VERIFIED.
Note You need to log in before you can comment on or make changes to this bug.