Bug 690379

Summary: libvirtd will crash when hotplug a USB device
Product: Red Hat Enterprise Linux 6 Reporter: zhanghaiyan <yoyzhang>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 6.1CC: dyuan, eblake, kxiong
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-24 06:08:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description zhanghaiyan 2011-03-24 05:56:47 UTC 
Description of problem:
hotplug a USB device,libvirtd will crash

Version-Release number of selected component (if applicable):
libvirt-0.8.7-14.el6.x86_64
kernel-2.6.32-125.el6.x86_64
qemu-kvm-0.12.1.2-2.152.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.Start a vm
2.In virt-manager,select Add hardware->USB Host Device->Logitech USB Optical Mouse 

  
Actual results:
Libvirtd will crash

Expected results:


Additional info:
tail -f /var/log/messages
Mar 24 01:32:13 dhcp-93-59 kernel: libvirtd[20143]: segfault at 70 ip 00007ff6b2bdfd52 sp 00007ff6aa7557d0 error 4 in libvirt.so.0.8.7[7ff6b2bb1000+168000]
Mar 24 01:32:13 dhcp-93-59 abrt[20314]: saved core dump of pid 20138 (/usr/sbin/libvirtd) to /var/spool/abrt/ccpp-1300944733-20138.new/coredump (79826944 bytes)
Mar 24 01:32:13 dhcp-93-59 abrtd: Directory 'ccpp-1300944733-20138' creation detected
Mar 24 01:32:13 dhcp-93-59 abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1300944335-6011)

tail -f libvirt.log

usbGetDevice:182 : 6 2 006:002: initialized
01:43:00.934: 20807: debug : qemuSetupHostUsbDeviceCgroup:177 : Process path '/dev/bus/usb/006/002' for USB device
Comment 1 koka xiong 2011-03-24 06:08:11 UTC 

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