From: Thomas Huth <441672@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 441672] Re: Windos XP BSOD with HP Photosmart usb device attached
Date: Fri, 04 Nov 2016 15:38:09 -0000 [thread overview]
Message-ID: <20161104153809.21571.69160.malone@gac.canonical.com> (raw)
In-Reply-To: 20091003195706.32421.28307.malonedeb@gangotri.canonical.com
Can you still re-create this issue with the latest version of QEMU? If
not, I think we should close this bug nowadays...
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/441672
Title:
Windos XP BSOD with HP Photosmart usb device attached
Status in QEMU:
Incomplete
Bug description:
https://bugzilla.redhat.com/show_bug.cgi?id=524723 has all the details
of the problem.
I was just testing attaching a USB device to see if it really worked, and tried my HP Photosmart C5580 All-in-One
printer/scanner, and the Windows XP box then started getting bluescreens and crashing at random
(fairly short :-) intervals.
My latest attempt was on a fedora rawhide system with pretty up to date software
(qemu-kvm-0.11.0-2.fc12.x86_64), and the crashes still happen.
A reply to that bugzilla recommended adding this upstream bug, so here
it is.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/441672/+subscriptions
next prev parent reply other threads:[~2016-11-04 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091003195706.32421.28307.malonedeb@gangotri.canonical.com>
2010-06-02 16:40 ` [Qemu-devel] [Bug 441672] Re: Windos XP BSOD with HP Photosmart usb device attached Joel Schopp
2012-02-01 15:47 ` Erik Rull
2016-11-04 15:38 ` Thomas Huth [this message]
2017-01-04 4:17 ` Launchpad Bug Tracker
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=20161104153809.21571.69160.malone@gac.canonical.com \
--to=441672@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.