On 10/21/2014 05:58 PM, Peter Maydell wrote:
> On 21 October 2014 22:33, Peter Maydell wrote:
>> Suggestions:
>
> ...you might also try asking on kvm...@lists.cs.columbia.edu, which
> is where the KVM/ARM kernel devs hang out, to see if somebody
> else has seen this.
It may be useful to also CC:
On 21 October 2014 22:33, Peter Maydell wrote:
> Suggestions:
...you might also try asking on kvm...@lists.cs.columbia.edu, which
is where the KVM/ARM kernel devs hang out, to see if somebody
else has seen this.
-- PMM
On 21 October 2014 22:15, Richard Jones wrote:
> I have now also tried virtio-blk and that doesn't work either. Same
> symptoms: no log messages at all (even with ignore_loglevel), and no
> disks appear.
>
>> Yeah, "regressed with this newer kernel" sounds more like a kernel
>> bug than a QEMU bu
I have now also tried virtio-blk and that doesn't work either. Same
symptoms: no log messages at all (even with ignore_loglevel), and no
disks appear.
> Yeah, "regressed with this newer kernel" sounds more like a kernel
> bug than a QEMU bug to me, especially if all the other virt devices
> still
