I installed High Sierra on Proxmox successfully previously, but can never install further instances of MacOS because I am always prompted with the boot shell that cannot access fs0. Does anyone know what I'm missing here?
I could make a new VM with exactly the same settings, but the UEFI won't be loaded during boot. This is not a settings issue, I have done this 30 times.
Furthermore, during testing, I have deleted all partitions using 3rd party tools from Hirens Boot PE, and I noticed the boot records remained. Not something I thought was happening from Hirens. I'm hoping someone here can steer me on the right path.
Expecting to destroy the environment, within pve shell I can remove everything from /boot and install Proxmox again and recreate the High Sierra VM with the same settings fine. I can't seem to boot another instance.
I am about to start again, here is what is currently in /boot after a re-install of Proxmox with entries remaining from previous installation where I haven't wiped the /boot directory with linux commands....
Can anyone tell me the best way of cleaning this up?
High Sierra 1010.conf below.
if I nuked the /boot directory and started from scratch it works, but I'd like to know how I should get this working better than my previous efforts and at the same time, install multiple VM's (not using clone) which will enable me to understand how a new VM can access its boot process, so I can access fs0 in the boot shell.
let me know if there is more details I should provide from shell.
EDIT: I have recently disabled legacy boot options in my hardware BIOS and all virtualization settings are on and supported.
Hardware MSI BIOS 5 Boot Order: #1 Proxmox, #2 UEFI OS
Version details:
I could make a new VM with exactly the same settings, but the UEFI won't be loaded during boot. This is not a settings issue, I have done this 30 times.
Furthermore, during testing, I have deleted all partitions using 3rd party tools from Hirens Boot PE, and I noticed the boot records remained. Not something I thought was happening from Hirens. I'm hoping someone here can steer me on the right path.
Expecting to destroy the environment, within pve shell I can remove everything from /boot and install Proxmox again and recreate the High Sierra VM with the same settings fine. I can't seem to boot another instance.
I am about to start again, here is what is currently in /boot after a re-install of Proxmox with entries remaining from previous installation where I haven't wiped the /boot directory with linux commands....
root@pve:/boot# ls -l
total 164312
-rw-r--r-- 1 root root 275520 Sep 28 23:53 config-6.2.16-15-pve
-rw-r--r-- 1 root root 275161 Jun 17 15:58 config-6.2.16-3-pve
drwxr-xr-x 3 root root 4096 Jan 1 1970 efi
drwxr-xr-x 6 root root 4096 Oct 25 20:47 grub
-rw-r--r-- 1 root root 62666721 Oct 25 20:47 initrd.img-6.2.16-15-pve
-rw-r--r-- 1 root root 61876031 Oct 25 20:39 initrd.img-6.2.16-3-pve
-rw-r--r-- 1 root root 138712 Feb 11 2023 memtest86+ia32.bin
-rw-r--r-- 1 root root 139776 Feb 11 2023 memtest86+ia32.efi
-rw-r--r-- 1 root root 144312 Feb 11 2023 memtest86+x64.bin
-rw-r--r-- 1 root root 145408 Feb 11 2023 memtest86+x64.efi
drwxr-xr-x 2 root root 4096 Oct 25 20:47 pve
-rw-r--r-- 1 root root 7683384 Sep 28 23:53 System.map-6.2.16-15-pve
-rw-r--r-- 1 root root 7675732 Jun 17 15:58 System.map-6.2.16-3-pve
-rw-r--r-- 1 root root 13602336 Sep 28 23:53 vmlinuz-6.2.16-15-pve
-rw-r--r-- 1 root root 13595360 Jun 17 15:58 vmlinuz-6.2.16-3-pve
Can anyone tell me the best way of cleaning this up?
High Sierra 1010.conf below.
if I nuked the /boot directory and started from scratch it works, but I'd like to know how I should get this working better than my previous efforts and at the same time, install multiple VM's (not using clone) which will enable me to understand how a new VM can access its boot process, so I can access fs0 in the boot shell.
root@pve:~# cat /etc/pve/qemu-server/1010.conf
agent: 1
args: -device isa-applesmc,osk="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc
bios: ovmf
boot: order=ide2;ide0;sata0
cores: 4
cpu: host
efidisk0: local-lvm:vm-1010-disk-0,efitype=4m,size=4M
ide0: MYNAS-proxmox:iso/High Sierra 10.13.6 v13.6.02.iso,cache=unsafe,size=6000M
ide2: MYNAS-proxmox:iso/OpenCore-v20.iso,cache=unsafe,size=150M
machine: q35
memory: 8192
meta: creation-qemu=8.0.2,ctime=1698234069
name: MacOSHighSierra1
net0: vmxnet3=A2:34:73:50:09:6A,bridge=vmbr0
numa: 0
ostype: other
sata0: local-lvm:vm-1010-disk-1,backup=0,discard=on,size=32G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=2e668781-96cb-4824-bb57-ac7dc0613336
sockets: 1
vga: vmware
vmgenid: e4f65099-10bb-4638-be5f-f2ca39a78412
let me know if there is more details I should provide from shell.
EDIT: I have recently disabled legacy boot options in my hardware BIOS and all virtualization settings are on and supported.
Hardware MSI BIOS 5 Boot Order: #1 Proxmox, #2 UEFI OS
Version details:
root@pve:/etc/kernel# pveversion --verbose
proxmox-ve: 8.0.2 (running kernel: 6.2.16-15-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.3
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2: 6.2.16-15
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.26-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.5
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.9
libpve-guest-common-perl: 5.0.5
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.3-1
proxmox-backup-file-restore: 3.0.3-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.9
pve-cluster: 8.0.4
pve-container: 5.0.4
pve-docs: 8.0.5
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.8-2
pve-ha-manager: 4.0.2
pve-i18n: 3.0.7
pve-qemu-kvm: 8.0.2-6
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.7
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.13-pve1
Last edited: