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 615189 - serial: windows xp guest restart automatically after port hot-plug and hot-unplug
Summary: serial: windows xp guest restart automatically after port hot-plug and hot-un...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 580953
TreeView+ depends on / blocked
 
Reported: 2010-07-16 05:57 UTC by Shirley Zhou
Modified: 2015-03-05 00:51 UTC (History)
6 users (show)

Fixed In Version: virtio-win-1.1.10-0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 15:01:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Shirley Zhou 2010-07-16 05:57:10 UTC 
Description of problem:
windows xp guest restart automatically after port hot-plug and hot-unplug 

Version-Release number of selected component (if applicable):
virtio-win-1.1.8.0
qemu-kvm-0.12.1.2-2.96.el6.x86_64
kernel-2.6.32-44.1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.run windows xp guest with virtio serial
/usr/libexec/qemu-kvm  -m 2G -smp 2 -cpu qemu64,+x2apic  -usbdevice tablet -drive file=/home/winxp.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0  -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,mac=02:02:16:3F:20:1f,bus=pci.0 -uuid a4f4127c-1233-4e67-95da-8dd0a8891cc4  -name winxp  -qmp tcp:0:4444,server,nowait  -boot c -monitor stdio -spice port=5930,disable-ticketing -vga qxl -cdrom /root/RHEV-toolsSetup_2.2_46140.iso -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0 -chardev pty,id=channel0 -device virtserialport,bus=virtio-serial0.0,nr=0,id=serialport.1,chardev=channel0,name=org.linux-kvm.port.0 -fda /mnt/virtio-win-1.1.8-0.vfd
2.Install virtio serial driver 
3.reboot guest
4.checking serial info from monitor
(qemu) info qtree 
bus: main-system-bus
  type System
  dev: i440FX-pcihost, id ""
    bus: pci.0
      type PCI
      dev: virtio-serial-pci, id "virtio-serial0"
        dev-prop: vectors = 17
        dev-prop: class = 0x780
        dev-prop: indirect_desc = off
        dev-prop: publish_used = off
        dev-prop: max_ports = 16
        bus-prop: addr = 04.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        class Class 0780, addr 00:04.0, pci id 1af4:1003 (sub 1af4:0003)
        bar 0: i/o at 0xc080 [0xc09f]
        bar 1: mem at 0xf4040000 [0xf4040fff]
        bus: virtio-serial0.0
          type virtio-serial-bus
          dev: virtserialport, id "serialport.1"
            dev-prop: nr = 0
            dev-prop: chardev = channel0
            dev-prop: name = "org.linux-kvm.port.0"
             dev-prop-int: id: 0
             dev-prop-int: guest_connected: 1
             dev-prop-int: host_connected: 1
             dev-prop-int: throttled: 0
5.Do hot-unplug for virtio serial port
{"execute":"device_del","arguments":{"id":"serialport.1"}}
{"return": {}}
6.this winxp guest will restart automatically
7.checking serial info again from monitor
(qemu) info qtree 
bus: main-system-bus
  type System
  dev: i440FX-pcihost, id ""
    bus: pci.0
      type PCI
      dev: virtio-serial-pci, id "virtio-serial0"
        dev-prop: vectors = 17
        dev-prop: class = 0x780
        dev-prop: indirect_desc = off
        dev-prop: publish_used = off
        dev-prop: max_ports = 16
        bus-prop: addr = 04.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        class Class 0780, addr 00:04.0, pci id 1af4:1003 (sub 1af4:0003)
        bar 0: i/o at 0xc080 [0xc09f]
        bar 1: mem at 0xf4040000 [0xf4040fff]
        bus: virtio-serial0.0
          type virtio-serial-bus
8.do hot-plug for spicevmc
{"execute":"device_add","arguments":{"driver":"spicevmc","id":"vmc-1"}}
9.this guest restart automatically
10.checking serial info again from monitor
info qtree 
bus: main-system-bus
  type System
  dev: i440FX-pcihost, id ""
    bus: pci.0
      type PCI
      dev: virtio-serial-pci, id "virtio-serial0"
        dev-prop: vectors = 17
        dev-prop: class = 0x780
        dev-prop: indirect_desc = off
        dev-prop: publish_used = off
        dev-prop: max_ports = 16
        bus-prop: addr = 04.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        class Class 0780, addr 00:04.0, pci id 1af4:1003 (sub 1af4:0003)
        bar 0: i/o at 0xc080 [0xc09f]
        bar 1: mem at 0xf4040000 [0xf4040fff]
        bus: virtio-serial0.0
          type virtio-serial-bus
          dev: spicevmc, id "vmc-1"
            dev-prop: nr = 0
            dev-prop: debug = 0
             dev-prop-int: id: 0
             dev-prop-int: guest_connected: 0
             dev-prop-int: host_connected: 1
             dev-prop-int: throttled: 0
Actual results:
after port hot-plug and hot-unplug, winxp guest restart automatically  

Expected results:
there should be a prompt window to ask for restart, or the guest should not restart. 

Additional info:
Comment 2 RHEL Program Management 2010-07-16 06:17:31 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 4 Vadim Rozenfeld 2010-07-23 18:53:23 UTC 
(In reply to comment #0)
> Actual results:
> after port hot-plug and hot-unplug, winxp guest restart automatically  

Was it a BSOD or VM crash?
Comment 5 Shirley Zhou 2010-07-26 01:51:58 UTC 
(In reply to comment #4)
> (In reply to comment #0)
> > Actual results:
> > after port hot-plug and hot-unplug, winxp guest restart automatically  
> 
> Was it a BSOD or VM crash?    

Hi, Vadim

No bsod , no vm crash, this guest restart automatically after hot-plug and hot-unplug.
Comment 6 Vadim Rozenfeld 2010-08-03 07:38:09 UTC 
Hi, Shirley.

Can you please re-check this issue with the latest driver?

Thanks,
Vadim.
Comment 7 Shirley Zhou 2010-08-04 03:16:15 UTC 
Verify this bug on winxp guest with virtio-win-1.1.10-0, this bug does not reproduce after port hot-plug and hot-unplug.

Change status to verified.
Comment 8 releng-rhel@redhat.com 2010-11-11 15:01:56 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.