Bug 1294121

Summary:	keyboard didn't work after deleted keyboard device in qemu interface
Product:	Red Hat Enterprise Linux 6	Reporter:	jingzhao <jinzhao>
Component:	qemu-kvm	Assignee:	Gerd Hoffmann <kraxel>
Status:	CLOSED NEXTRELEASE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.8	CC:	ailan, chayang, jinzhao, juzhang, mkenneth, rbalakri, virt-bugs, virt-maint
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:	2016-01-15 11:38:18 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:

Description jingzhao 2015-12-25 05:30:29 UTC

Description of problem:
keyboard didn't work after deleted keyboard device in qemu interface

Version-Release number of selected component (if applicable):
kernel version:2.6.32-592.el6.x86_64
qemu-kvm-0.12.1.2-2.481.el6.x86_64
guest: win10-64

How reproducible:
3/3

Steps to Reproduce:
1.Boot vm with following cli:
/usr/libexec/qemu-kvm \
-name rhel6 \
-machine rhel6.6.0,accel=kvm \
-realtime mlock=off \
-cpu SandyBridge \
-m 6G   \
-smp 4,cores=2,threads=1,sockets=2  \
-uuid 49a3438a-70a3-4ba8-92ce-3a05e0934608 \
-nodefaults \
-rtc base=utc,driftfix=slew \
-monitor unix:/tmp/monitor-unix,server,nowait \
-global kvm-pit.lost_tick_policy=discard \
-global PIIX4_PM.disable_s3=1 \
-global PIIX4_PM.disable_s4=1 \
-boot order=c,menu=on,strict=on \
-readconfig ich9-ehci-uhci.cfg \
-drive file=/home/usb/win10usb.img,if=none,id=ide,media=disk,cache=none,format=raw \
-device ide-drive,drive=ide,id=ide0,bootindex=0 \
-cdrom /usr/share/virtio-win/virtio-win.iso \
-netdev tap,id=hostnet1  \
-device e1000,netdev=hostnet1,id=virtio-net-pci1,mac=b6:2f:a8:85:72:6c,bus=pci.0,multifunction=off \
-monitor stdio \
-qmp tcp:0:4466,server,nowait -serial unix:/tmp/ttym,server,nowait \
-vga qxl \
-spice port=5910,addr=0.0.0.0,disable-ticketing,seamless-migration=on \
-k en-us \


2.used passwd and entered into the win10 system and no output through "info usb" command 

3. add keyboard device and also can enter into the system through passwd

(qemu) device_add usb-kbd,id=kbd1
(qemu) info usb
  Device 0.1, Port 1, Speed 12 Mb/s, Product QEMU USB Keyboard

4. then deleted the keyboard device
(qemu) device_del kbd1

Actual results:
Didn't enter into the system through password and also didn't enter into the system after reboot the system.

Expected results:
We can enter into the system correctly after deleted the keyboard device 

Additional info:

Comment 4 Gerd Hoffmann 2016-01-04 12:46:25 UTC

Why this has high Severity?

Comment 5 jingzhao 2016-01-05 01:34:06 UTC

(In reply to Gerd Hoffmann from comment #4)
> Why this has high Severity?

--I marked as high serverity because the keyboard didn't work and will impact the customer

Comment 6 Gerd Hoffmann 2016-01-05 06:58:41 UTC

(In reply to jingzhao from comment #5)
> (In reply to Gerd Hoffmann from comment #4)
> > Why this has high Severity?
> 
> --I marked as high serverity because the keyboard didn't work

Only when plugging and un-plugging the usb keyboard.
What is the use case for doing this?

> and will
> impact the customer

Any actual customer reports?

Comment 7 jingzhao 2016-01-05 07:53:04 UTC

(In reply to Gerd Hoffmann from comment #6)
> (In reply to jingzhao from comment #5)
> > (In reply to Gerd Hoffmann from comment #4)
> > > Why this has high Severity?
> > 
> > --I marked as high serverity because the keyboard didn't work
> 
> Only when plugging and un-plugging the usb keyboard.
> What is the use case for doing this?
---Didn't for special use, just do hot-plug operations.

> 
> > and will
> > impact the customer
> 
> Any actual customer reports?  --No, really describe as impact I use.

Comment 8 Gerd Hoffmann 2016-01-05 09:02:07 UTC

(In reply to jingzhao from comment #7)
> (In reply to Gerd Hoffmann from comment #6)
> > (In reply to jingzhao from comment #5)
> > > (In reply to Gerd Hoffmann from comment #4)
> > > > Why this has high Severity?
> > > 
> > > --I marked as high serverity because the keyboard didn't work
> > 
> > Only when plugging and un-plugging the usb keyboard.
> > What is the use case for doing this?
> ---Didn't for special use, just do hot-plug operations.

Why would a customer hotplug a usb keyboard,
given that there is a ps/2 keyboard anyway?

I still fail to see how this affects customers in practice
and why it is important to backport the fix to RHEL-6 ...

Comment 9 Ademar Reis 2016-01-15 11:38:18 UTC

corner case, fixed in rhel7/upstream, will hardly hit customers in practice.