Ubuntu ARM VM breaks after force-restarted

[gradygambrell]

Describe the issue
I know that the issue is closed (referring to #2682) but the solutions are scattered up and when I tried them, they all appear not working when I install a new copy of Ubuntu 20.04 ARM.

Here's the steps I've made (this is the normal run):

1. Boot from CD and completed the installation.
2. When the update step begins, it'll stop right in the path of unpacking files and won't do ANYTHING
3. Do a "cancel and reboot" option and it will appear a blinking line.
4. Force reboot and it'll appear the issue before.

NOTE: I would like to install Ubuntu Desktop. But that failed.

Here's the steps I tried.

• M1 Cap. is not the issue.
• Can boot into Console Only, but sadly unable to install the Desktop (see below). Also with the "Use Hypervisor" off, it'll work.
• Networking ain't working to ports.ubuntu.com either. Had major trouble editing the internet files.
• Don't know how to do via VLC.
• ran the sudo fsck /dev/disk/by-label/<your disk> but appears locked. And even after that, it aborts.
• Never tried converting.
• Tried sudo apt install linux-image-5.4.0-100-generic but cannot connect to ports.ubuntu.com.
• Tried fsck -y /dev/mapper/ubuntu--vg-ubuntu--lv but either I typed it wrong or the command is not working (like it can't find it).
• Updated both QEMU and UTM to the latest version and it didn't work with normal settings. Never tried with the work-around.

Note that I'm using Emulated VLAN because I have Internet Sharing on.

Configuration

• UTM Version: 3.1.5
• QEMU: 6.2.0_1
• OS Version: 12.3
• Intel or Apple Silicon? Apple

Crash log
N/A

Debug log
N/A

Upload VM
N/A

[ssukienn]

Facing the same problem. It worked for the first time and then I encountered this error. UMT (3.1.5) both Ubuntu (20.04 [5.4.0-105-generic kernel] / 21.10). It seemed that workaround with this getting into GRUB (shift key durng boot) and selecting Ubuntu version from "Advanced" option (resulting with the same error, but booting, just needed to wait) worked. But now it stays on the error and does not proceed.

[conath]

Have you tried setting a manual DNS server in your VM? This helps me when I have trouble with Internet and emulated VLAN. This needs to be set during install and then once again after the VM is rebooted for the first time because Ubuntu seems to forget about the manual settings.

[ssukienn]

I have no experience with the above. Could you direct me to some tutorial, documentation? Thanks in advance

[gradygambrell]

Have you tried setting a manual DNS server in your VM? This helps me when I have trouble with Internet and emulated VLAN. This needs to be set during install and then once again after the VM is rebooted for the first time because Ubuntu seems to forget about the manual settings.

I have not. What should I use?

[conath]

Regarding the stuck VM on boot. I talked someone through a similar request on Discord today that ended up being a corrupted hard disk, possibly due to force-restarting the VM. You can see that it is corrupted if you boot the VM in console mode (Display config => Console only), and it ends up at an (iniramfs) prompt. The solution was to re-install and instead of using the restart button when it gets stuck, close the VM (to force-power down) and start it again.

[conath]

Regarding seemingly no internet in the VM, this is #2353 and in that thread there is a mention of setting the Ubuntu DNS manually. #2353 (comment) If I remember correctly, the Ubuntu Server installer also gives you the choice to do a manual network configuration. If you're using emulated VLAN option, you want to put in the following information:
IP 10.0.2.16
Subnet 255.255.255.0
Gateway 10.0.2.2
DNS 1.1.1.1

[gradygambrell]

OK. Nevermind. It works. The thing I did is this:

• Go to Shell first
• Go to /etc/netplan
• Run sudo apt update
• exit.
• When the installer gets stuck on here, i force power down.
• [Keep the CD inserted]
• Boot it up.
• Wait... (not very long)
• and log in.

[gradygambrell]

Here's where it was stuck

.