** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
Status in qemu package in Ubuntu:
IMHO, Ubuntu Server for KVM virtualization - is BAD idea! Very BAD
idea..
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
I can't add much, except that I started noticing his issue when
migrating my VMs to an Ubuntu Precise server hypervisor where under
(heavy?) load my Win 2008 Server VM started to crash very frequently
with the error showing up in the libvirt log of the VM.
It might be useful information that I
Hello!
ANd again virtio_ioport_write: unexpected address 0x13 value 0x1.
Drvers: from virtio-win-0.1-30.iso
config: domain type='kvm'
namebuh_xp/name
uuidf0e8ac00-4545-eb5d-e8f2-c885063e5ad0/uuid
memory1097152/memory
currentMemory1097152/currentMemory
vcpu1/vcpu
os
type arch='i686'
It doesn't look like as a vritio-win driver problem.
you get the following message
virtio_ioport_write: unexpected address 0x13 value 0x1
because netkvm driver triggers BSOD event, which happened in
different stack, and then kills the hosting QEMU prccess
by writing to ISR register.
In your
I change network card in guest to RTL and no have BSOD, on all guest. Why?
How can we detect the cause?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected
and how can i use winXP without antivirus and RDP? Its nonsense!!! :-)
no sense!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
Hard to say at the moment.
In both cases the crash stack looks absolutely the same:
nt!KiDeliverApc+0x66
hal!HalpApcInterrupt+0xc5
hal!HalRequestSoftwareInterrupt+0x3b
How turn on kernel memory dump in XP?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
Status in QEMU:
New
Bug description:
http://support.microsoft.com/kb/316450
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
Status in QEMU:
New
Bug description:
can you upload the corresponding dump file?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
Status in QEMU:
New
Bug
I see in properties of drivers version 51.63.103.2700 (date is
20.04.2012).
** Attachment added: Mini052112-01.dmp
https://bugs.launchpad.net/qemu/+bug/990364/+attachment/3158501/+files/Mini052112-01.dmp
--
You received this bug notification because you are a member of qemu-
devel-ml, which
But with new drivers i got virtio_ioport_write: unexpected address 0x13
value 0x1 again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13
On Thu, May 03, 2012 at 12:16:57PM -, vrozenfe wrote:
On Monday, April 30, 2012 07:17:09 PM Vadim Rozenfeld wrote:
On Monday, April 30, 2012 03:31:03 PM Stefan Hajnoczi wrote:
Hi Vadim,
Here is a recent bug report with virtio-win-0.1-22.iso. Wanted to
bring it to your attention,
And what? Where can I get new drivers for WinXP?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
Status in QEMU:
New
Bug
On Thursday, May 03, 2012 10:17:15 PM Vitalis wrote:
And what? Where can I get new drivers for WinXP?
http://people.redhat.com/vrozenfe/build-27/virtio-win-prewhql-0.1.zip
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I forgot: guest os is Windows XP Pro SP3
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
Status in QEMU:
New
Bug description:
** Attachment added: Mini042412-01.dmp
https://bugs.launchpad.net/bugs/990364/+attachment/3111605/+files/Mini042412-01.dmp
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
** Attachment added: dmesg
https://bugs.launchpad.net/qemu/+bug/990364/+attachment/3111622/+files/dmesg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/990364
Title:
virtio_ioport_write:
19 matches
Mail list logo
