All of lore.kernel.org
 help / color / mirror / Atom feed
From: Launchpad Bug Tracker <1386197@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1386197] Re: keyboard suddenly stops working in VM and problem persists until host reboot. All super-standard setup no funny stuff
Date: Mon, 18 Jun 2018 04:17:39 -0000	[thread overview]
Message-ID: <152929545980.23342.11488699273348618523.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20141027132911.2480.54218.malonedeb@gac.canonical.com

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1386197

Title:
  keyboard suddenly stops working in VM and problem persists until host
  reboot. All super-standard setup no funny stuff

Status in QEMU:
  Expired

Bug description:
  QEMU emulator version 2.1.2, Copyright (c) 2003-2008 Fabrice Bellard
  Linux HOST 3.16.3-1-ck #1 SMP PREEMPT Sun Sep 21 11:27:46 CEST 2014 x86_64 GNU/Linux

  qemu-system-x86_64 -daemonize -enable-kvm -cpu host -smp
  4,maxcpus=4,sockets=1,cores=2,threads=1 -m 4096 -monitor
  telnet:127.0.0.1:4446,server,nowait -vga qxl -spice
  port=5556,ipv4,addr=127.0.0.1,disable-ticketing -soundhw all -net
  tap,script=no,ifname=vm6,vlan=0,vnet_hdr=on -net
  nic,macaddr=52:54:00:2A:F1:16,vlan=0,model=virtio -drive
  file=/mnt/2/VM/vm-
  centos.qcow2,cache=writeback,index=0,media=disk,if=virtio,aio=native
  -boot c -vnc :6

  I already had this with ubanto VM so I installed a centos one and it
  worked for a while, but then today I restart it and type HDD password
  in VNC suddenly keyboard stops working forever again. Kill qemu, stop
  qemu, start again ... same issue. Very strange. Problem in VNC,
  problem in vga std problem in spicec problem with options problem
  without options, SDL no SDL and nothing helps. dmesg only shows
  unhandled wrmsr like always .. so irrelevant.

  Must be problem with new kernel or nvidia driver mystery magic I
  suppose? But I had riced CK kernel before and no issue. Hardware
  didn't change. Nothing works, what is this? Can do sendkey 1 1 in
  console no issue. So why is all keyboard input dead in mid-operation?
  You see after host system reboot I open VM and no matter what VNC or
  spicec or SDL I input keyboard all normal then randomly this! BAM all
  keyboard input gone! So in ubuntu I still had mouse so I used onscreen
  keyboard to enable SSH and then I didn't care. But now I have
  harddrive password, what can I do? Install different QEMU but I
  suppose problem with new kernel xorg stuff rather ... Can't change
  that! Help much appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1386197/+subscriptions

      parent reply	other threads:[~2018-06-18  4:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 13:29 [Qemu-devel] [Bug 1386197] [NEW] keyboard suddenly stops working in VM and problem persists until host reboot. All super-standard setup no funny stuff John Smith
2014-10-27 14:24 ` [Qemu-devel] [Bug 1386197] " John Smith
2018-04-18 15:51 ` Thomas Huth
2018-06-18  4:17 ` Launchpad Bug Tracker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=152929545980.23342.11488699273348618523.malone@loganberry.canonical.com \
    --to=1386197@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.