On Tue, Oct 07, 2014 at 10:12:16AM -0500, Joel Schopp wrote: > > >> --------------------- > >> Last bit of console output before init dies. Have also tried with > >> Ubuntu init, which also dies but differently. > >> > >> VFIO - User Level meta-driver version: 0.3 > >> device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: > >> dm-devel@xxxxxxxxxx > >> device-mapper: multipath: version 1.7.0 loaded > >> device-mapper: multipath round-robin: version 1.0.0 loaded > >> TCP: cubic registered > >> NET: Registered protocol family 10 > >> sit: IPv6 over IPv4 tunneling driver > >> NET: Registered protocol family 17 > >> Bridge firewalling registered > >> 9pnet: Installing 9P2000 support > >> NET: Registered protocol family 37 > >> Btrfs loaded > >> drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > >> XFS (vda4): Mounting V4 Filesystem > >> XFS (vda4): Ending clean mount > >> VFS: Mounted root (xfs filesystem) readonly on device 254:4. > > Using ext4 instead of xfs here. > I have ext4 in the host filesytem and in the filesystem in the disk > image. XFS must be coming from qemu's virtio-blk-device. I've tried > several disk images (Linaro, Redhat, Ubuntu) all of which die in init. I > am running with: virtio-blk-device is just the transport block mechanism, the file system should be completely dependent on the disk image you're using only. > > -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, -Christoffer _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
