From: Rick Vernam <818673@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
Date: Wed, 14 Sep 2011 15:43:22 -0000 [thread overview]
Message-ID: <20110914154322.7181.42940.malone@gac.canonical.com> (raw)
In-Reply-To: 20110730230157.13425.3564.malonedeb@chaenomeles.canonical.com
so if I use -vga std instead of -vga qxl (and of course take out the -spice stuff), I don't crash.
perhaps this is spice/qxl related?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Status in QEMU:
New
Bug description:
Qemu host is Core i7, running Linux. Guest is Windows XP sp3.
Often, qemu will crash shortly after starting (1-5 minutes) with a statement "qemu-system-x86_64: virtio: trying to map MMIO memory"
This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and qemu 0.15.0-rc1.
Qemu is started as such:
qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio -m 768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice port=1234,disable-ticketing -daemonize -monitor telnet:localhost:12341,server,nowait
The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most current spice binaries from spice-space.org.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions
next prev parent reply other threads:[~2011-09-14 15:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 23:01 [Qemu-devel] [Bug 818673] [NEW] virtio: trying to map MMIO memory Rick Vernam
2011-07-31 17:54 ` Stefan Hajnoczi
2011-07-31 18:43 ` Vadim Rozenfeld
2011-08-02 14:20 ` [Qemu-devel] [Bug 818673] " Rick Vernam
2011-08-04 21:35 ` David Rando
2011-08-05 3:10 ` Rick Vernam
2011-08-05 16:11 ` Rick Vernam
2011-08-13 4:38 ` Rick Vernam
2011-08-13 12:23 ` David Rando
2011-08-14 6:11 ` Rick Vernam
2011-08-14 15:00 ` Stefan Hajnoczi
2011-08-25 14:53 ` David Rando
2011-08-25 15:54 ` Stefan Hajnoczi
2011-08-25 19:33 ` Vadim Rozenfeld
2011-09-06 15:08 ` dx-vmonroig
2011-09-12 17:49 ` Rick Vernam
2011-09-13 16:27 ` vrozenfe
2011-09-13 23:26 ` Rick Vernam
2011-09-14 15:43 ` Rick Vernam [this message]
2011-09-14 17:52 ` Rick Vernam
2011-09-14 19:42 ` vrozenfe
2011-09-14 21:30 ` Rick Vernam
2011-09-15 16:23 ` Rick Vernam
2011-09-15 19:37 ` Rick Vernam
2011-09-16 8:52 ` hkran
2011-09-16 17:42 ` Rick Vernam
2011-09-16 19:31 ` Rick Vernam
2011-09-22 19:10 ` Rick Vernam
2011-09-23 19:07 ` Alon Levy
2011-09-23 19:49 ` Rick Vernam
2011-09-15 19:55 ` vrozenfe
2011-09-26 16:38 ` Rick Vernam
2011-09-29 2:07 ` Rick Vernam
2011-12-29 20:52 ` Arequipeno
2011-12-30 16:00 ` Ian Pilcher
2011-12-30 16:31 ` Rick Vernam
2012-01-24 16:35 ` Vitalis
2012-01-24 16:48 ` Vitalis
2012-01-24 19:25 ` Rick Vernam
2012-02-02 9:12 ` Mike Cao
2012-02-02 17:31 ` Rick Vernam
2012-02-02 17:40 ` Rick Vernam
2012-02-08 11:18 ` Vitalis
2012-02-16 17:03 ` vrozenfe
2012-02-17 7:10 ` Vitalis
2012-02-17 7:58 ` Alon Levy
2012-02-17 9:13 ` vrozenfe
2012-02-17 9:14 ` vrozenfe
2016-10-20 21:15 ` Thomas Huth
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=20110914154322.7181.42940.malone@gac.canonical.com \
--to=818673@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.