Re: [Qemu-discuss] qemu-system-aarch64, cloud-init, Ubuntu Cloud Image - Help

[Peter Maydell]

On 28 November 2017 at 02:21, Aimee Ukasick <address@hidden> wrote:
> Hi. Newbie here. I am trying to access an Ubuntu image running in
> qemu-system-aarch64.

> address@hidden:~/dev/QEMU-arm64$ cloud-localds my-seed.img my-user-data
> address@hidden:~/dev/QEMU-arm64$ qemu-system-aarch64 -smp 2 -m 8192
> -M virt -bios QEMU_EFI_1602.fd -nographic \
>>        -device virtio-blk-device,drive=image \
>>        -drive
> if=none,id=image,file=xenial-server-cloudimg-arm64-uefi1.img \
>>        -device virtio-blk-device,drive=cloud \
>>        -drive if=none,id=cloud,file=my-seed.img,format=raw \
>>        -netdev user,id=user0,hostfwd=tcp::2222-:22 -device
> virtio-net-device,netdev=user0  \
>>        -cpu cortex-a57
>
> The output is a bunch of gibberish until finally:
> -------------------------------------
> Ubuntu 16.04.3 LTS ubuntu ttyAMA0
>
> ubuntu login: [  160.981732] cloud-init[1037]: Cloud-init v. 17.1
> running 'modules:config' at Tue, 28 Nov 2017 01:33:39 +0000. Up 158.09
> seconds.
> [  171.189035] cloud-init[1187]: Cloud-init v. 17.1 running
> 'modules:final' at Tue, 28 Nov 2017 01:33:49 +0000. Up 167.86 seconds.
> [  171.192742] cloud-init[1187]: Cloud-init v. 17.1 finished at Tue, 28
> Nov 2017 01:33:52 +0000. Datasource DataSourceNoCloud
> [seed=/dev/vda][dsmode=net].  Up 170.93 seconds
>
> Does anyone know why the cloud-init that qemu is using is not reading
> the user-data that's in the my-seed.img file that I passed to qemu? I've
> tried in vain to find logs and to get qemu to output to a log file using
> the -D option.
> Any help of any kind is greatly appreciated.

It looks like QEMU is correctly booting your guest, or it
wouldn't get that far.
So you don't want to try to get QEMU to do logging for
you, you just want to treat it as a problem of debugging
your guest OS. The clues will be somewher in the
"bunch of gibberish" logging that the guest prints out as
it boots.

thanks
-- PMM