public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 37262] New: VNC access to KVM VM is unusable
Date: Sat, 11 Jun 2011 20:04:03 GMT	[thread overview]
Message-ID: <bug-37262-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=37262

           Summary: VNC access to KVM VM is unusable
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.0.0-rc1
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: kvm
        AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
        ReportedBy: stefan.bosak@gmail.com
        Regression: No


Kernels: 2.6.39-git8 - 3.0.0-rc1
QemuKVM: latest from git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git

After try access to VNC console of KVM VM
keyboard and video interactions is not proceed
by VM. Newly created VM without OS which started
for installation process of any OS dropped
interactions after few inputs from user, host
and hosted machine running without problems.
I have tested this on 3 independent servers,
3 independent workstations.

Used VNC clients:
- from Linux: TightVNC Viewer version 1.3.10
- from Windows: RealVNC Viewer 4.1.3

Other activities except VNC access are OK.


Kernel: 2.6.39-rc1-git2
QemuKVM: latest from git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git

On this server VNC access to all KVM VM works well.

Please try to test VNC access to KVM VM
and fix issue when problem occurs. As
I can see some fixes for input and tty
are in kernel 3.0.0-rc2.

Thank you for your time.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2011-06-11 20:04 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11 20:04 bugzilla-daemon [this message]
2011-06-12 11:50 ` [Bug 37262] VNC access to KVM VM is unusable bugzilla-daemon
2011-06-12 13:24 ` bugzilla-daemon
2011-06-12 13:42 ` bugzilla-daemon
2011-06-12 13:54 ` bugzilla-daemon
2011-06-12 13:57 ` bugzilla-daemon
2011-06-12 14:41 ` bugzilla-daemon
2011-06-12 14:43 ` bugzilla-daemon
2011-06-12 14:58 ` bugzilla-daemon
2011-06-12 15:00 ` bugzilla-daemon
2011-06-12 15:39 ` bugzilla-daemon
2011-06-12 15:39 ` bugzilla-daemon
2011-06-12 15:54 ` bugzilla-daemon
2011-06-12 15:55 ` bugzilla-daemon
2011-06-12 16:00 ` bugzilla-daemon
2011-06-12 16:11 ` bugzilla-daemon
2011-06-12 16:18 ` bugzilla-daemon
2011-06-12 16:23 ` bugzilla-daemon
2011-06-12 17:01 ` bugzilla-daemon
2011-06-12 19:30 ` bugzilla-daemon
2011-06-12 22:19 ` bugzilla-daemon
2011-06-12 22:46 ` bugzilla-daemon
2011-06-12 22:49 ` bugzilla-daemon
2011-06-12 22:58 ` bugzilla-daemon
2011-06-12 23:22 ` bugzilla-daemon
2011-06-13  8:11 ` bugzilla-daemon
2011-06-13  8:59 ` bugzilla-daemon
2011-06-13  8:59 ` bugzilla-daemon
2011-06-13  9:15 ` bugzilla-daemon
2011-06-13  9:22 ` bugzilla-daemon
2011-06-13  9:35 ` bugzilla-daemon
2011-06-13  9:55 ` bugzilla-daemon
2011-06-13 12:18 ` bugzilla-daemon
2011-06-13 14:05 ` bugzilla-daemon
2011-06-13 14:12 ` bugzilla-daemon
2011-06-13 14:27 ` bugzilla-daemon
2011-06-15 17:10 ` bugzilla-daemon
2011-06-15 17:19 ` bugzilla-daemon
2011-06-15 21:44 ` bugzilla-daemon
2011-06-16 14:00   ` Avi Kivity
2011-06-15 21:46 ` bugzilla-daemon
2011-06-16 14:00 ` bugzilla-daemon
2011-06-16 14:15 ` bugzilla-daemon
2011-06-16 16:45 ` bugzilla-daemon
2011-06-16 20:39 ` bugzilla-daemon
2011-06-17  2:25   ` Xiao Guangrong
2011-06-19  8:50     ` Avi Kivity
2011-06-17  3:49 ` bugzilla-daemon
2011-06-17  7:00 ` bugzilla-daemon
2011-06-19  8:50 ` bugzilla-daemon

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=bug-37262-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox