RE: Installing and running ubuntu on arm64/virt machine (Guest has not initialized the display (yet).")

[ckim]

Hi, 
I found this tutorial : 
https://gist.github.com/george-hawkins/16ee37063213f348a17717a7007d2c79  
(actually arm@support once told me about this info and tried it once).
And when I followed it I could the ubuntu 16.04 gets installed in the VM and 
could see the log in prompt. I was supposed to log in with ssh but couldn't. It 
said if I do ssh-key-gen again, I may be able to login but I didn't try. (I 
didn't want mess up with accessing our team's git server). I'll try some time 
later and this seems pretty good to use for our application.
Below is the log. 

Ubuntu 16.04.7 LTS ubuntu ttyAMA0

ubuntu login: 

ubuntu login: [  298.275376] cloud-init[1350]: Cloud-init v. 
21.1-19-gbad84ad4-0ubuntu1~16.04.2 running 'modules:config' at Tue, 18 May 2021 
13:39:28 +0000. Up 291.32 seconds.
[  298.314839] cloud-init[1350]: 2021-05-18 13:39:35,135 - ug_util.py[WARNING]: 
Format for 'users' key must be a comma separated string or a dictionary or a 
list and not NoneType
[  299.544796] cloud-init[1350]: Generating locales (this might take a while)...
[  331.032030] cloud-init[1350]:   en_US.UTF-8... done
[  331.066795] cloud-init[1350]: Generation complete.
[  372.114405] cloud-init[1394]: Cloud-init v. 
21.1-19-gbad84ad4-0ubuntu1~16.04.2 running 'modules:final' at Tue, 18 May 2021 
13:40:40 +0000. Up 364.02 seconds.
[  372.140718] cloud-init[1394]: 2021-05-18 13:40:48,977 - ug_util.py[WARNING]: 
Format for 'users' key must be a comma separated string or a dictionary or a 
list and not NoneType
<14>May 18 13:40:49 ec2: 
<14>May 18 13:40:49 ec2: 
#############################################################
<14>May 18 13:40:49 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
<...
<14>May 18 13:40:49 ec2: 2048 
SHA256:X7Q46HBfKlO70LJtwvktU60t++0C3VS61hRS6GeZbmw root@ubuntu (RSA)
<14>May 18 13:40:49 ec2: -----END SSH HOST KEY FINGERPRINTS-----
<14>May 18 13:40:49 ec2: 
#############################################################
-----BEGIN SSH HOST KEY KEYS-----
ecdsa-sha2-nistp256 
AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBKvNpRQ1Rwtok5zo0wP+faH8kN2uFp9QDQ23N/m2x68u/ndKfAAb0wFId4Y9xubTs5extgkn5BBjTeasoS1miO0=
 root@ubuntu
ssh-ed25519 
AAAAC3NzaC1lZDI1NTE5AAAAIE3F1NRvXUewr5d/2kozqBaWVnXPw0e+2BMV6Cz5jjw/ root@ubuntu
ssh-rsa 
AAAAB3NzaC1yc2EAAAADAQABAAABAQDGgdGhR43AdqhzZ8WAQ56S+lkJZNtvD+WgZWDvWTRmMItJ3cc6zg2TRKBNNI6FI+I+..../BqaEoOCFr44s+VzA7L0f1eqRR1
 root@ubuntu
-----END SSH HOST KEY KEYS-----
[  374.302737] cloud-init[1394]: Cloud-init v. 
21.1-19-gbad84ad4-0ubuntu1~16.04.2 finished at Tue, 18 May 2021 13:40:50 +0000. 
Datasource DataSourceNoCloud [seed=/dev/vda][dsmode=net].  Up 373.90 seconds

Ubuntu 16.04.7 LTS ubuntu ttyAMA0

> -----Original Message-----
> From: Peter Maydell <peter.maydell@linaro.org>
> Sent: Tuesday, May 18, 2021 7:10 PM
> To: Chan Kim <ckim@etri.re.kr>
> Cc: qemu-discuss <qemu-discuss@nongnu.org>
> Subject: Re: Installing and running ubuntu on arm64/virt machine (Guest
> has not initialized the display (yet).")
> 
> On Tue, 18 May 2021 at 10:45, <ckim@etri.re.kr> wrote:
> >
> > Hi, Peter Maydell,(and all)
> >
> > Thank you for the explanation (I was aware of the two pass run though).
> > But I have a question about the serial port connection.
> >
> > > You'll probably find it easier to debug if you use a serial console;
> > > that way you'll be able to see the guest booting and log in and can
> > > debug what's going on a bit better from there. In particular, the
> > > installer does
> > > *not* use the graphics device, so you will absolutely need to find
> > > out where it's putting the serial output in order to use the installer.
> >
> > When I pass -kernel=  option, I can pass the serial port to connect
> using -append = ".." option.
> > But in this case, (I have only -cdrom and -drive option), how can I know
> the serial port the install program on the CDROM uses?
> 
> I hadn't noticed that. That's what your problem is. For x86 QEMU, you can
> supply just a drive and expect it to boot, but for aarch64 QEMU you can't
> do that, because QEMU will not load a bios image by default. You need to
> either (a) supply a kernel directly or
> (b) pass a UEFI bios image (eg via the -bios option) which will then know
> how to read the disk.
> 
> General rule: you cannot just take a tutorial/command line for
> x86 and just change it to qemu-system-aarch64 and expect it to work.
> 
> It is definitely possible to boot an aarch64 distro from CDROM media and
> install it, but you need to find an *aarch64* tutorial and follow it.
> 
> thanks
> -- PMM