On 10/07/2014 01:34 PM, Christoffer Dall wrote: > On Tue, Oct 07, 2014 at 01:28:38PM -0500, Joel Schopp wrote: >>>> -drive file=/Image.img,id=fs -device virtio-blk-device,drive=fs >>>> >>>> more specifically >>>> ./aarch64-softmmu/qemu-system-aarch64 -smp 1 --enable-kvm -nographic >>>> -kernel /Image -drive file=/Image.img,id=fs -device >>>> virtio-blk-device,drive=fs -m 1024 -M virt -cpu host -no-reboot -append >>>> "console=ttyAMA0 console=ttyS0 rootwait root=/dev/vda4 rw" >>>> >>> Can you post your guest kernel config somewhere for me to try and >>> reproduce? >> Thanks for offering to help. Before you spend some time on it let me >> debug and see what progress I can make. Since I can reproduce it >> reliably now I can narrow things down with git bisect. >> > Sounds good to me. > > I had a fluke thought if 1G of memory could be too little with your > specific file system and 64K pages? > > -Christoffer I had the same thought with 512MB (which is what I was using and works with 3.16), which is why I had bumped it to 1G. If we can't boot to a console login prompt with 1GB of memory we need to go on a diet. _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
