From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 37262] VNC access to KVM VM is unusable
Date: Wed, 15 Jun 2011 17:10:06 GMT [thread overview]
Message-ID: <201106151710.p5FHA6hL009322@demeter1.kernel.org> (raw)
In-Reply-To: <bug-37262-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=37262
--- Comment #36 from Steve <stefan.bosak@gmail.com> 2011-06-15 17:10:04 ---
git bisect log:
# bad: [0ce790e7d736cedc563e1fb4e998babf5a4dbc3d] Linux 2.6.39-rc1
# good: [521cb40b0c44418a4fd36dc633f575813d59a43d] Linux 2.6.38
git bisect start 'v2.6.39-rc1' 'v2.6.38'
# good: [179198373cf374f0ef793f1023c1cdd83b53674d] Merge branch
'nfs-for-2.6.39' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6
git bisect good 179198373cf374f0ef793f1023c1cdd83b53674d
# bad: [da23ef0549d4205ca9b576cf6cce9a80d0c3e43a] adfs: add hexadecimal
filetype suffix option
git bisect bad da23ef0549d4205ca9b576cf6cce9a80d0c3e43a
# bad: [e16b396ce314b2bcdfe6c173fe075bf8e3432368] Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial
git bisect bad e16b396ce314b2bcdfe6c173fe075bf8e3432368
# bad: [411f5c7a502769ccc0377c5ba36cb0b283847ba8] Merge branch 'devel-stable'
of master.kernel.org:/home/rmk/linux-2.6-arm
git bisect bad 411f5c7a502769ccc0377c5ba36cb0b283847ba8
# bad: [6d7ed21d17e640b120b902a314143e5ef4917a70] Merge branches 'defcfg',
'drivers' and 'cyberpro-next' of master.kernel.org:/home/rmk/linux-2.6-arm
git bisect bad 6d7ed21d17e640b120b902a314143e5ef4917a70
After this VNC access is OK.
Now it's time to mark as git bisect good
and then git tells some information.
Am I right ?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-06-15 17:10 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 20:04 [Bug 37262] New: VNC access to KVM VM is unusable bugzilla-daemon
2011-06-12 11:50 ` [Bug 37262] " 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 [this message]
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=201106151710.p5FHA6hL009322@demeter1.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