Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 928775

Summary: core dump after reboot guest(hotplug->format->unhotplug) on RHEL 5.10 host
Product: Red Hat Enterprise Linux 5 Reporter: CongLi <coli>
Component: kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.10CC: asias, juzhang, michen, mkenneth, rhod, shuang, sluo, virt-maint, xwei
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: 2013-04-10 13:40:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
gdb thread apply all bt full
none
core dump file -0
none
core dump file -1
none
core dump file -2 none

Description CongLi 2013-03-28 12:23:24 UTC 
Created attachment 717632 [details]
gdb thread apply all bt full

Description of problem:

core dump after reboot guest(hotplug->format->unhotplug) on RHEL 5.10 host

Version-Release number of selected component (if applicable):
kernel-2.6.18-348.el5
kvm-qemu-img-83-264.el5

guest os rhel6.4.64

How reproducible:
100%

Steps to Reproduce:
1. start a RHEL6.4 guest with CML:
/home/autotest-devel/client/tests/kvm/qemu -S -name vm1 -monitor stdio -serial unix:/tmp/serial-serial1-20130327-185301-Awp1Xw8p,server,nowait -drive file=/home/image/rhel-64-virtio.qcow2,if=ide,media=disk,cache=none,boot=on,snapshot=off,format=qcow2 -net nic,vlan=0,model=virtio,macaddr=9a:e1:e2:e3:e4:e5,id=idfVl4HM -net tap,vlan=0  -m 4096 -smp 4,cores=2,threads=1,sockets=2 -cpu qemu64 -M rhel5.6.0 -drive file=/home/autotest-devel/client/tests/kvm/isos/linux/RHEL6.4-20130130.0-Server-x86_64-DVD1.iso,media=cdrom  -soundhw ac97  -spice port=5000,ic=on,disable-ticketing -qxl 1  -boot c -usbdevice tablet -balloon virtio

2. 
(qemu)cont
(qemu)info status
VM status: running

3. (qemu) pci_add pci_addr=auto storage file=/home/autotest-devel/client/tests/kvm/images/storage.qcow2,if=virtio
OK domain 0, bus 0, slot 7, function 0

4.(qemu) info status
VM status: running

(qemu)info pci    # can saw a new device
  Bus  0, device   7, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 0.
      BAR0: I/O at 0x1000 [0x103f].

5. format disk in guest with CML: "mkfs.ext4 /dev/vda"

6. (qemu) pci_del pci_addr=0x7

7. Reboot guest with CML: "reboot" in guest  

Actual results:
Segmentation Fault

Expected results:
Guest reboot successfully 

Additional info:

Attached gdb thread apply all bt full
Comment 1 CongLi 2013-03-29 01:46:16 UTC 
Created attachment 717902 [details]
core dump file -0
Comment 2 CongLi 2013-03-29 02:03:29 UTC 
Created attachment 717903 [details]
core dump file -1
Comment 3 CongLi 2013-03-29 02:08:07 UTC 
Created attachment 717904 [details]
core dump file -2
Comment 6 Asias He 2013-03-29 05:39:15 UTC 
(In reply to comment #0)
> Created attachment 717632 [details]
> gdb thread apply all bt full
> 
> Description of problem:
> 
> core dump after reboot guest(hotplug->format->unhotplug) on RHEL 5.10 host
> 
> Version-Release number of selected component (if applicable):
> kernel-2.6.18-348.el5
> kvm-qemu-img-83-264.el5
> 
> guest os rhel6.4.64
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. start a RHEL6.4 guest with CML:
> /home/autotest-devel/client/tests/kvm/qemu -S -name vm1 -monitor stdio
> -serial unix:/tmp/serial-serial1-20130327-185301-Awp1Xw8p,server,nowait
> -drive
> file=/home/image/rhel-64-virtio.qcow2,if=ide,media=disk,cache=none,boot=on,
> snapshot=off,format=qcow2 -net
> nic,vlan=0,model=virtio,macaddr=9a:e1:e2:e3:e4:e5,id=idfVl4HM -net
> tap,vlan=0  -m 4096 -smp 4,cores=2,threads=1,sockets=2 -cpu qemu64 -M
> rhel5.6.0 -drive
> file=/home/autotest-devel/client/tests/kvm/isos/linux/RHEL6.4-20130130.0-
> Server-x86_64-DVD1.iso,media=cdrom  -soundhw ac97  -spice
> port=5000,ic=on,disable-ticketing -qxl 1  -boot c -usbdevice tablet -balloon
> virtio
> 
> 2. 
> (qemu)cont
> (qemu)info status
> VM status: running
> 
> 3. (qemu) pci_add pci_addr=auto storage
> file=/home/autotest-devel/client/tests/kvm/images/storage.qcow2,if=virtio
> OK domain 0, bus 0, slot 7, function 0
> 
> 4.(qemu) info status
> VM status: running
> 
> (qemu)info pci    # can saw a new device
>   Bus  0, device   7, function 0:
>     SCSI controller: PCI device 1af4:1001
>       IRQ 0.
>       BAR0: I/O at 0x1000 [0x103f].
> 
> 5. format disk in guest with CML: "mkfs.ext4 /dev/vda"
> 
> 6. (qemu) pci_del pci_addr=0x7

Did you do step 6) after step 5 is finished or not. Did you mount /dev/vda or read/write /dev/vda the device when you do setp 6.

> 7. Reboot guest with CML: "reboot" in guest  
> 
> Actual results:
> Segmentation Fault
> 
> Expected results:
> Guest reboot successfully 
> 
> Additional info:
> 
> Attached gdb thread apply all bt full
Comment 7 CongLi 2013-03-29 06:45:39 UTC 
(In reply to comment #6)
> (In reply to comment #0)
> > Created attachment 717632 [details]
> > gdb thread apply all bt full
> > 
> > Description of problem:
> > 
> > core dump after reboot guest(hotplug->format->unhotplug) on RHEL 5.10 host
> > 
> > Version-Release number of selected component (if applicable):
> > kernel-2.6.18-348.el5
> > kvm-qemu-img-83-264.el5
> > 
> > guest os rhel6.4.64
> > 
> > How reproducible:
> > 100%
> > 
> > Steps to Reproduce:
> > 1. start a RHEL6.4 guest with CML:
> > /home/autotest-devel/client/tests/kvm/qemu -S -name vm1 -monitor stdio
> > -serial unix:/tmp/serial-serial1-20130327-185301-Awp1Xw8p,server,nowait
> > -drive
> > file=/home/image/rhel-64-virtio.qcow2,if=ide,media=disk,cache=none,boot=on,
> > snapshot=off,format=qcow2 -net
> > nic,vlan=0,model=virtio,macaddr=9a:e1:e2:e3:e4:e5,id=idfVl4HM -net
> > tap,vlan=0  -m 4096 -smp 4,cores=2,threads=1,sockets=2 -cpu qemu64 -M
> > rhel5.6.0 -drive
> > file=/home/autotest-devel/client/tests/kvm/isos/linux/RHEL6.4-20130130.0-
> > Server-x86_64-DVD1.iso,media=cdrom  -soundhw ac97  -spice
> > port=5000,ic=on,disable-ticketing -qxl 1  -boot c -usbdevice tablet -balloon
> > virtio
> > 
> > 2. 
> > (qemu)cont
> > (qemu)info status
> > VM status: running
> > 
> > 3. (qemu) pci_add pci_addr=auto storage
> > file=/home/autotest-devel/client/tests/kvm/images/storage.qcow2,if=virtio
> > OK domain 0, bus 0, slot 7, function 0
> > 
> > 4.(qemu) info status
> > VM status: running
> > 
> > (qemu)info pci    # can saw a new device
> >   Bus  0, device   7, function 0:
> >     SCSI controller: PCI device 1af4:1001
> >       IRQ 0.
> >       BAR0: I/O at 0x1000 [0x103f].
> > 
> > 5. format disk in guest with CML: "mkfs.ext4 /dev/vda"
> > 
> > 6. (qemu) pci_del pci_addr=0x7
> 
> Did you do step 6) after step 5 is finished or not. Did you mount /dev/vda
> or read/write /dev/vda the device when you do setp 6.
> 
> > 7. Reboot guest with CML: "reboot" in guest  
> > 
> > Actual results:
> > Segmentation Fault
> > 
> > Expected results:
> > Guest reboot successfully 
> > 
> > Additional info:
> > 
> > Attached gdb thread apply all bt full


1. Do step 6) step 5) finished.
2. The device is not using.
3. If not format /dev/vda, it still core dump in RHEL6.4-64 guest
Comment 8 Asias He 2013-03-29 13:39:45 UTC 
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #0)
> > > Created attachment 717632 [details]
> > > gdb thread apply all bt full
> > > 
> > > Description of problem:
> > > 
> > > core dump after reboot guest(hotplug->format->unhotplug) on RHEL 5.10 host
> > > 
> > > Version-Release number of selected component (if applicable):
> > > kernel-2.6.18-348.el5
> > > kvm-qemu-img-83-264.el5
> > > 
> > > guest os rhel6.4.64
> > > 
> > > How reproducible:
> > > 100%
> > > 
> > > Steps to Reproduce:
> > > 1. start a RHEL6.4 guest with CML:
> > > /home/autotest-devel/client/tests/kvm/qemu -S -name vm1 -monitor stdio
> > > -serial unix:/tmp/serial-serial1-20130327-185301-Awp1Xw8p,server,nowait
> > > -drive
> > > file=/home/image/rhel-64-virtio.qcow2,if=ide,media=disk,cache=none,boot=on,
> > > snapshot=off,format=qcow2 -net
> > > nic,vlan=0,model=virtio,macaddr=9a:e1:e2:e3:e4:e5,id=idfVl4HM -net
> > > tap,vlan=0  -m 4096 -smp 4,cores=2,threads=1,sockets=2 -cpu qemu64 -M
> > > rhel5.6.0 -drive
> > > file=/home/autotest-devel/client/tests/kvm/isos/linux/RHEL6.4-20130130.0-
> > > Server-x86_64-DVD1.iso,media=cdrom  -soundhw ac97  -spice
> > > port=5000,ic=on,disable-ticketing -qxl 1  -boot c -usbdevice tablet -balloon
> > > virtio
> > > 
> > > 2. 
> > > (qemu)cont
> > > (qemu)info status
> > > VM status: running
> > > 
> > > 3. (qemu) pci_add pci_addr=auto storage
> > > file=/home/autotest-devel/client/tests/kvm/images/storage.qcow2,if=virtio
> > > OK domain 0, bus 0, slot 7, function 0
> > > 
> > > 4.(qemu) info status
> > > VM status: running
> > > 
> > > (qemu)info pci    # can saw a new device
> > >   Bus  0, device   7, function 0:
> > >     SCSI controller: PCI device 1af4:1001
> > >       IRQ 0.
> > >       BAR0: I/O at 0x1000 [0x103f].
> > > 
> > > 5. format disk in guest with CML: "mkfs.ext4 /dev/vda"
> > > 
> > > 6. (qemu) pci_del pci_addr=0x7
> > 
> > Did you do step 6) after step 5 is finished or not. Did you mount /dev/vda
> > or read/write /dev/vda the device when you do setp 6.
> > 
> > > 7. Reboot guest with CML: "reboot" in guest  
> > > 
> > > Actual results:
> > > Segmentation Fault
> > > 
> > > Expected results:
> > > Guest reboot successfully 
> > > 
> > > Additional info:
> > > 
> > > Attached gdb thread apply all bt full
> 
> 
> 1. Do step 6) step 5) finished.
> 2. The device is not using.
> 3. If not format /dev/vda, it still core dump in RHEL6.4-64 guest

How about RHEL5 guest?
Comment 9 CongLi 2013-03-30 07:09:43 UTC 
(In reply to comment #8)

> How about RHEL5 guest?

I have tried RHEL.5.9, just do hotplug & unhotplug,
it also prompts 'seg fault'
Comment 10 Ronen Hod 2013-04-10 13:40:06 UTC 
Closing, It does not look like a regression of a customer bug.