** Changed in: qemu
Status: Incomplete => Fix Committed
** 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/1383857
Title:
aarch64
Oh yes, long fixed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1383857
Title:
aarch64: virtio disks don't show up in guest (neither blk nor scsi)
Status in QEMU:
Incomplete
Bug description:
Richard -- I assume we fixed this one way or another, right?
** 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/1383857
Title:
aarch64: virtio disk
I was just about to get to testing this stuff, but thanks for working
through it on your own, and apologies I didn't get to it before.
Cc'ing Marc so he's aware of the progress.
-Christoffer
On Mon, Dec 1, 2014 at 3:46 PM, Richard Jones wrote:
> Finally found the problem, patch posted:
> https:
Finally found the problem, patch posted:
https://lists.gnu.org/archive/html/qemu-devel/2014-12/msg00034.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1383857
Title:
aarch64: virtio disks don't
Still happening with latest upstream kernel. It seems to involve using
the -initrd option at all, with any cpio file, even a tiny one. More
results posted here:
https://lists.cs.columbia.edu/pipermail/kvmarm/2014-December/012557.html
--
You received this bug notification because you are a memb
Finally finished the git bisect (of the guest kernel, not qemu):
421520ba98290a73b35b7644e877a48f18e06004 is the first bad commit
commit 421520ba98290a73b35b7644e877a48f18e06004
Author: Yalin Wang
Date: Fri Sep 26 03:07:09 2014 +0100
ARM: 8167/1: extend the reserved memory for initrd to be
