From: John Goerzen <jgoerzen@complete.org>
To: kvm@vger.kernel.org
Subject: virtio_ioport_write unexpected address
Date: Mon, 06 Feb 2012 09:53:43 -0600 [thread overview]
Message-ID: <4F2FF787.9020408@complete.org> (raw)
Hi,
We're setting up some KVM systems with their disk image stored in a
sparse raw file on an NFS4 server. The NFS4 filesystem is mounted with
the hard option, which means that I/O to it is blocked indefinitely when
the server goes down, and will be properly handled when the server returns.
We observed a server failure over the weekend, and when the server
returned -- not when it went down -- our Windows 2008 R2 VMs hard
rebooted, with this in the libvirt log:
virtio_ioport_write: unexpected address 0x13 value 0x1
virtio_ioport_write: unexpected address 0x13 value 0x1
The downtime had been about 30 minutes, and after the downtime, the NFS
filesystem was responsive.
We were presenting drive C to Windows as IDE, and a data drive with virtio.
The host system is Debian squeeze x64, which is running the stock Debian
2.6.32 kernel and qemu-kvm 0.12.5. The Windows VMs have the latest
virtio drivers from Fedora.
Thanks,
-- John
reply other threads:[~2012-02-06 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F2FF787.9020408@complete.org \
--to=jgoerzen@complete.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