** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1204697
Title:
guest disk accesses lead to ATA errors + host vcpu0 unhandled
The fix is in a62eaa26c1d6d48fbdc3ac1d32bd1314f5fdc8c9 ahci: Fix FLUSH
command, should be in 1.6 and 1.5.3.
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
From a first test of the Debian package in experimental, I'd say that the
issue has been fixed :)
Thanks a lot for all your help!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1204697
Title:
** Changed in: qemu (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1204697
Title:
guest disk accesses lead to ATA errors + host vcpu0 unhandled
Having tried now with virtio as well: works
So:
virtio, ide = OK
sata = broken
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1204697
Title:
guest disk accesses lead to ATA errors + host vcpu0
So, what changed so you were able to boot from IDE without errors? As
far as I understand, your initial prob was I/O errors on IDE (virtual)
drive, but now you can boot it without errors. Or was it always SATA
not IDE?
The rdmsr/wrmsr are unrelated, I already told you that, it is accessing
Sorry for the confusion.
The initial problem was _always_ with SATA... I couldn't try IDE at first, as
the guest initrd haven't had and the IDE drivers.
Yesterday then, I tried IDE and it worked with that.
Sure, I just wanted to confirm that you were really right ;-)
Sorry I have missed the
For the record, the difference between debian qemu 1.5.0-4 and 1.5.0-5
is the 1.5.1 patch - I applied it without actually changing the
upstream version number.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Hi.
Finally I was able to get it running with IDE instead of SATA.
That works,... fine... no ATA errors.
As you already expected,.. I still get the:
[20424.793207] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c1 data 0
[20424.793211] kvm [20947]: vcpu0 unhandled wrmsr: 0x682 data 0
[20424.793215] kvm
Also, when using SATA for the virtual disk,... it seems that it takes
much longer till it get's to the point where it (the initrd) tries to
mount root.
Till that point I see no errors... but then, after some time hanging at
the root mount... it starts with the ATA errors.
--
You received this
** Changed in: qemu (Debian)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1204697
Title:
guest disk accesses lead to ATA errors + host vcpu0 unhandled
** Changed in: qemu (Debian)
Status: Unknown = 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/1204697
Title:
guest disk accesses lead to ATA errors + host vcpu0 unhandled
12 matches
Mail list logo
