Bug 1043431 - Virt-manager crashes during creation of new Virtual machine
Summary: Virt-manager crashes during creation of new Virtual machine
Keywords:
Status: CLOSED DUPLICATE of bug 1038512
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.5
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: virt-mgr-maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 10:09 UTC by Pankaj
Modified: 2013-12-19 18:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-19 18:42:28 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Pankaj 2013-12-16 10:09:46 UTC
Description of problem:
Virt-manager crashes during creation of new VM.

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-19.el6.x86_64

How reproducible:
100% 

Steps to Reproduce:
1. Open the Virt-manager.
2. Right click on the QEMU and click on create a new.
3. Enter the VM name and select "Import existing disk image".
4. Browse and Provide the existing storage path.
5. While selecting the disk image from the path , the virt-manager crashes.


Actual results:
The virt-manager crashes.

Expected results:
The virt-manager should not crash and new VM should be created.

Additional info:
rpm -qa | grep virt
libvirt-java-0.4.9-1.el6.noarch
libvirt-0.10.2-29.el6.x86_64
virt-v2v-0.9.1-4.el6.x86_64
fence-virtd-libvirt-0.2.3-15.el6.x86_64
virt-who-0.8-9.el6.noarch
virt-viewer-0.5.6-8.el6.x86_64
fence-virtd-serial-0.2.3-15.el6.x86_64
libvirt-python-0.10.2-29.el6.x86_64
fence-virtd-checkpoint-0.2.3-15.el6.x86_64
fence-virtd-multicast-0.2.3-15.el6.x86_64
libvirt-client-0.10.2-29.el6.x86_64
libvirt-snmp-0.0.2-4.el6.x86_64
fence-virt-0.2.3-15.el6.x86_64
virt-what-1.11-1.2.el6.x86_64
python-virtinst-0.600.0-18.el6.noarch
libvirt-cim-0.6.1-9.el6.x86_64
virt-manager-0.9.0-19.el6.x86_64
fence-virtd-0.2.3-15.el6.x86_64
virt-top-1.0.4-3.15.el6.x86_64

Comment 1 Martin Kletzander 2013-12-16 10:17:35 UTC
Can you provide a backtrace for this issue?  Thanks

Comment 2 Pankaj 2013-12-16 10:36:18 UTC
Can you provide me the list of files you are looking for?

Comment 3 Giuseppe Scrivano 2013-12-16 10:46:31 UTC
(In reply to Pankaj from comment #2)
> Can you provide me the list of files you are looking for?

I've tried to reproduce this problem on my machine but I couldn't.  As Martin suggested, please run virt-manager as "virt-manager --debug" from a terminal, the output you get can give us more useful information.

Comment 4 Pankaj 2013-12-16 11:43:16 UTC
virt-manager --debug
2013-12-16 16:20:54,678 (cli:71): virt-manager startup
2013-12-16 16:20:54,679 (virt-manager:292): Launched as: /usr/share/virt-manager/virt-manager.py --debug
2013-12-16 16:20:54,679 (virt-manager:293): GTK version: (2, 20, 1)
2013-12-16 16:20:54,679 (virt-manager:294): virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>
2013-12-16 16:20:54,799 (engine:555): No inspection thread because libguestfs is too old, not available, or libvirt is not thread safe.
2013-12-16 16:20:54,801 (engine:346): About to connect to uris ['qemu:///system']
2013-12-16 16:20:54,854 (engine:471): window counter incremented to 1
2013-12-16 16:20:58,077 (connection:977): Scheduling background open thread for qemu:///system
2013-12-16 16:20:58,078 (connection:1163): Background 'open connection' thread is running
2013-12-16 16:20:58,110 (connection:1191): Background open thread complete, scheduling notify
2013-12-16 16:20:58,110 (connection:1196): Notifying open result
2013-12-16 16:20:58,125 (connection:1203): qemu:///system capabilities:
<capabilities>

  <host>
    <uuid>0e6ed102-48b3-11df-a9af-e41f13620ef0</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Nehalem</model>
      <vendor>Intel</vendor>
      <topology sockets='1' cores='4' threads='2'/>
      <feature name='rdtscp'/>
      <feature name='dca'/>
      <feature name='pdcm'/>
      <feature name='xtpr'/>
      <feature name='tm2'/>
      <feature name='est'/>
      <feature name='vmx'/>
      <feature name='ds_cpl'/>
      <feature name='monitor'/>
      <feature name='dtes64'/>
      <feature name='pbe'/>
      <feature name='tm'/>
      <feature name='ht'/>
      <feature name='ss'/>
      <feature name='acpi'/>
      <feature name='ds'/>
      <feature name='vme'/>
    </cpu>
    <power_management>
      <suspend_disk/>
    </power_management>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
      </uri_transports>
    </migration_features>
    <topology>
      <cells num='2'>
        <cell id='0'>
          <cpus num='8'>
            <cpu id='0' socket_id='0' core_id='0' siblings='0,8'/>
            <cpu id='1' socket_id='0' core_id='1' siblings='1,9'/>
            <cpu id='2' socket_id='0' core_id='2' siblings='2,10'/>
            <cpu id='3' socket_id='0' core_id='3' siblings='3,11'/>
            <cpu id='8' socket_id='0' core_id='0' siblings='0,8'/>
            <cpu id='9' socket_id='0' core_id='1' siblings='1,9'/>
            <cpu id='10' socket_id='0' core_id='2' siblings='2,10'/>
            <cpu id='11' socket_id='0' core_id='3' siblings='3,11'/>
          </cpus>
        </cell>
        <cell id='1'>
          <cpus num='8'>
            <cpu id='4' socket_id='1' core_id='0' siblings='4,12'/>
            <cpu id='5' socket_id='1' core_id='1' siblings='5,13'/>
            <cpu id='6' socket_id='1' core_id='2' siblings='6,14'/>
            <cpu id='7' socket_id='1' core_id='3' siblings='7,15'/>
            <cpu id='12' socket_id='1' core_id='0' siblings='4,12'/>
            <cpu id='13' socket_id='1' core_id='1' siblings='5,13'/>
            <cpu id='14' socket_id='1' core_id='2' siblings='6,14'/>
            <cpu id='15' socket_id='1' core_id='3' siblings='7,15'/>
          </cpus>
        </cell>
      </cells>
    </topology>
    <secmodel>
      <model>selinux</model>
      <doi>0</doi>
    </secmodel>
    <secmodel>
      <model>dac</model>
      <doi>0</doi>
    </secmodel>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/libexec/qemu-kvm</emulator>
      <machine>rhel6.5.0</machine>
      <machine canonical='rhel6.5.0'>pc</machine>
      <machine>rhel6.4.0</machine>
      <machine>rhel6.3.0</machine>
      <machine>rhel6.2.0</machine>
      <machine>rhel6.1.0</machine>
      <machine>rhel6.0.0</machine>
      <machine>rhel5.5.0</machine>
      <machine>rhel5.4.4</machine>
      <machine>rhel5.4.0</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/libexec/qemu-kvm</emulator>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
      <pae/>
      <nonpae/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/libexec/qemu-kvm</emulator>
      <machine>rhel6.5.0</machine>
      <machine canonical='rhel6.5.0'>pc</machine>
      <machine>rhel6.4.0</machine>
      <machine>rhel6.3.0</machine>
      <machine>rhel6.2.0</machine>
      <machine>rhel6.1.0</machine>
      <machine>rhel6.0.0</machine>
      <machine>rhel5.5.0</machine>
      <machine>rhel5.4.4</machine>
      <machine>rhel5.4.0</machine>
      <domain type='qemu'>
      </domain>
      <domain type='kvm'>
        <emulator>/usr/libexec/qemu-kvm</emulator>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

</capabilities>

2013-12-16 16:20:58,227 (connection:594): Interface XML inactive flag not supported.
2013-12-16 16:20:58,442 (connection:578): Connection managed save support: True
2013-12-16 16:20:58,644 (connection:160): Using libvirt API for netdev enumeration
2013-12-16 16:20:58,645 (connection:200): Using libvirt API for mediadev enumeration
2013-12-16 16:21:01,454 (create:832): Guest type set to os_type=hvm, arch=x86_64, dom_type=kvm
2013-12-16 16:21:15,054 (config:717): get_default_directory(image): returning /var/lib/libvirt/images/vols_f3270-132-121/vol_os_f121
**
Gtk:ERROR:gtkfilechooserdefault.c:8151:get_display_name_from_file_list: assertion failed: (had_selection)
Aborted (core dumped)

Comment 5 Martin Kletzander 2013-12-16 11:58:04 UTC

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

Comment 6 Pankaj 2013-12-18 11:57:06 UTC
The Duplicate Bug 1038512 is closed with out any resolution.I am reopening it and do let me know in case you need more data for the this bug.

Comment 7 Dave Allan 2013-12-19 18:42:28 UTC
Pakaj, BZ 1038512 is not closed and this BZ is a duplicate of it.  Please work with the assignee of that bug to prvovide any information required to resolve it, and please do not reopen this bug as there is nothing the virt-manager team can do to resolve it.

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


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