ubuntu vm arm

hi,

have you changed the arch variable to aarch64 inside the config file?

could you post the contents of your config and the output from pveversion -v?
 
Proxmox
Virtual Environment 7.1-7

Code: 
arch: aarch64
balloon: 512
bios: ovmf
boot: dcn
bootdisk: scsi0
cores: 2
efidisk0: local-lvm:vm-107-disk-2,size=64M
memory: 2048
name: ubuntuARM
net0: virtio=42:A1:3F:26:49:A0,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-lvm:vm-107-disk-0,size=32G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=44d79ea7-810e-4b91-936a-21735b3dbfaf
sockets: 1
vga: serial

TASK ERROR: Failed to run vncproxy.
 
vm 101 - unable to parse value of 'vga' - format error
type: value 'serial' does not have a value in the enumeration 'cirrus, qxl, qxl2, qxl3, qxl4, none, serial0, serial1, serial2, serial3, std, virtio, vmware'
TASK ERROR: no such logical volume pve/vm-107-disk-0 at /usr/share/perl5/PVE/Storage/LvmThinPlugin.pm line 219.


Can't use an undefined value as an ARRAY reference at /usr/share/perl5/PVE/QemuServer.pm line 3268. (500)
 
robytump said:
TASK ERROR: Failed to run vncproxy.
Click to expand...
just means the VM isn't running (therefore the VNC isn't starting either)

robytump said:
vm 101 - unable to parse value of 'vga' - format error
type: value 'serial' does not have a value in the enumeration 'cirrus, qxl, qxl2, qxl3, qxl4, none, serial0, serial1, serial2, serial3, std, virtio, vmware'
TASK ERROR: no such logical volume pve/vm-107-disk-0 at /usr/share/perl5/PVE/Storage/LvmThinPlugin.pm line 219.
Click to expand...
did you edit this file manually?

your line with vga: serial should be i guess instead vga: serial0. can you make that change and try again?
 
Code: 
  GNU nano 5.4                            101.conf                                     
arch: aarch64
balloon: 512
bios: ovmf
boot: dcn
bootdisk: scsi0
cores: 2
efidisk0: local-lvm:vm-101-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/ubuntu-21.04-live-server-arm64.iso,media=cdrom,size=1106796K
memory: 2048
name: ubuntuARM
net0: virtio=42:A1:3F:26:49:A0,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: local-lvm:vm-101-disk-0,size=50G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=d14e180b-9d03-4116-8213-f09ad5f91f1d
sockets: 1
vga: serial0

created vm gui web entered the code & add original links vm efidisk0, ide2, smbios1,sata0.
does not work does not turn on vnc error 5001.
how to create vm terminal code? proxmox cannot update?
W: Some index files failed to download. They have been ignored, or old ones used instead.
 
robytump said:
created vm gui web entered the code & add original links vm efidisk0, ide2, smbios1,sata0.
does not work does not turn on vnc error 5001.
Click to expand...
could you check the boot order of your VM to make sure it's trying to boot from the CD drive?

robytump said:
how to create vm terminal code? proxmox cannot update?
W: Some index files failed to download. They have been ignored, or old ones used instead.
Click to expand...
seems like another possible issue with your package lists, maybe you should make a new thread for that (i don't think it's related to your current problem)
 
starts from cd-rom but fails to start the vm. a code x to do everything through the terminal?

my proxmox is just format.
 
I am currently trying my hand at the ARM Ubuntu VM have made the same settings as mentioned in the article above.

But unfortunately I get the following error message when starting the VM

TASK ERROR: Can't use an undefined value as an ARRAY reference at /usr/share/perl5/PVE/QemuServer.pm line 3313.
Click to expand...

I am using Proxmox 7.2-3 here and this is the output of pveversion -v


proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
pve-kernel-5.15: 7.2-4
pve-kernel-helper: 7.2-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
Click to expand...

Here is the content of the .conf for di

arch: aarch64
bios: ovmf
boot: order=scsi1;scsi0;net0
cores: 2
efidisk0: central:146/vm-146-disk-0.raw,efitype=4m,pre-enrolled-keys=1,size=528K
memory: 2048
meta: creation-qemu=6.2.0,ctime=1654849927
name: gitlabrunner-arm
net0: virtio=7E:7C:FE:3E:24:DF,bridge=vmbr45,firewall=1
numa: 1
ostype: l26
scsi0: central:146/vm-146-disk-1.raw,discard=on,size=32G,ssd=1
scsi1: central:iso/Ubuntu_-_ubuntu-22.04-live-server-arm64.iso,media=cdrom,size=1395660K
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=87d9f231-a29b-447c-94b1-cd9330c00a3a
sockets: 1
vga: serial0
#vmgenid: 82bc77ad-7d47-4e92-b743-4730595b5595
Click to expand...
How can I solve the problem?
Thanks

Best regards,

Bjoern
 
Hi, I'm having exactly the same problem. Did you manage to solve it?

Thanks
 
Last edited:
looking through the code for QemuServer.pm

sub get_ovmf_files($$$) {
my ($arch, $efidisk, $smm) = @_;

my $types = $OVMF->{$arch}
or die "no OVMF images known for architecture '$arch'\n";

my $type = 'default';
if (defined($efidisk->{efitype}) && $efidisk->{efitype} eq '4m') {
$type = $smm ? "4m" : "4m-no-smm";
$type .= '-ms' if $efidisk->{'pre-enrolled-keys'};
}

return $types->{$type}->@*;
}



this is where its failing, will play around with the OVMF a little more
 
Removing the EFI disk seems to allow it to boot, Maybe the EFI disk is too small? Will continue to troubleshoot



Screenshot 2022-07-25 141405.png
 
Confirmed, removal of the EFI disk does not impact booting from local disk in the VM.
 
OK finally got everything working, i think. I have no idea why, but the Aarch hates the efi disk that is created by the gui. I had to skip the GUI efi disk add, edit the config
/etc/pve/nodes/<host_name>/qemu-server/<vm_id>.conf
arch: aarch64
remove vmgenid:
change any ide<#> to scsi<#>

then run

qm set VMID --efidisk0 storage:0

Then boot.
Here is a copy of my VM.conf
arch: aarch64 bios: ovmf boot: order=scsi2;net0 cores: 4 efidisk0:XXXXXX:vm-111-disk-0,size=64M memory: 8192 name: debian-arm net0: virtio=96:03:AA:70:20:97,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 scsi0:XXXXXXXX:vm-111-disk-1,size=100G scsi2: XXXXXXX:iso/debian-11.4.0-arm64-netinst.iso,media=cdrom,size=327980K scsihw: virtio-scsi-pci serial0: socket sockets: 1 vga: serial0

@oguz any idea why the gui would fail but command line passes?
 
aghadjip said:
@oguz any idea why the gui would fail but command line passes?
Click to expand...
did you have the option for pre-enrolled keys checked on the UI when adding the efidisk?
 
You must log in or register to reply here.
Top Bottom