Does the VM boot with the never version of
pve-edk2-firmware if you remove the passthrough?Proxmox VE 7.4 released!
- Thread starter martin
- Start date
Does it happen consistently every time you try to boot these VMs or only sometimes? Does downgrading QEMU make them work again? That is, using
apt install pve-qemu-kvm=7.1.0-4 (or look at /var/log/apt/history.log to check what version you had installed before) and then shutdown/stop and start the VMs again.
Only ever use:
apt full-upgrade or: apt dist-upgrade with Proxmox products: [1]!Maybe this solves your problem already...
[1] https://forum.proxmox.com/threads/proxmox-ve-7-1-released.99847/post-463941
I completely forgot about the recommended procedure. Thank you, problem solved.
With pve-edk2-firmware 3.20230228-1 the issue doesn't appear anymore.
Glad to hear! But what about the Windows 10 VM? The config you posted doesn't even use EDK2/OVMF. If it works now, maybe it was just a one-off issue there?
Mounted proxmox-ve_7.4-1.iso as image file via ILO Integrated Remote Console on HP DL360 G7. Impossible to use installer:
The first screen with boot menu selection is 1024x768, but in initializaton phase screen switch to 640x480. Any way to stay in 1024x768 at least? Or the only way is direct USB stick?
The first screen with boot menu selection is 1024x768, but in initializaton phase screen switch to 640x480. Any way to stay in 1024x768 at least? Or the only way is direct USB stick?
at least on a HP DL380 G8 it is necessary to add `intremap=off` to the kernel cmdline (else the console is terribly sluggish) - try that for the g7 as well (hit 'e' in the boot-screen 'Install Proxmox VE' and add it to the linux line at the end after the splash=silent)
However we usually plug the ISO directly into the machine - as the iLO has caused some issues in the past - so not sure if sharing via iLO works well with the G7
I hope this helps!
Doesn't help.
It's even more crazy. Old 17" monitors are "Out of range", "No input supported", full HD same. Everything stops working after grub selection and before EULA screen.
PVE 7.1-2 iso works without hiccup.
Restored VM backup
from
pve-manager/7.3-3/c3928077 (running kernel: 5.15.74-1-pve)
to
pve-manager/7.4-3/9002ab8a (running kernel: 5.15.102-1-pve)
noVNC console doesn't work. VM is debian 11, VM is up and pingable.
from
pve-manager/7.3-3/c3928077 (running kernel: 5.15.74-1-pve)
to
pve-manager/7.4-3/9002ab8a (running kernel: 5.15.102-1-pve)
noVNC console doesn't work. VM is debian 11, VM is up and pingable.
Code:
Mar 31 10:40:04 proxmox-mon-01 pvedaemon[158819]: starting vnc proxy UPID:proxmox-mon-01:00026C63:0070E3BD:64269C64:vncproxy:101:root@pam:
Mar 31 10:40:04 proxmox-mon-01 pvedaemon[1304]: <root@pam> starting task UPID:proxmox-mon-01:00026C63:0070E3BD:64269C64:vncproxy:101:root@pam:
Mar 31 10:40:13 proxmox-mon-01 pveproxy[1310]: worker 154041 finished
Mar 31 10:40:13 proxmox-mon-01 pveproxy[1310]: starting 1 worker(s)
Mar 31 10:40:13 proxmox-mon-01 pveproxy[1310]: worker 158850 started
Mar 31 10:40:14 proxmox-mon-01 pvedaemon[158819]: connection timed out
Mar 31 10:40:14 proxmox-mon-01 pvedaemon[1304]: <root@pam> end task UPID:proxmox-mon-01:00026C63:0070E3BD:64269C64:vncproxy:101:root@pam: connection timed out
Mar 31 10:40:14 proxmox-mon-01 pveproxy[158849]: worker exit
Code:
boot: cdn
bootdisk: scsi0
cores: 2
cpu: host
ide0: local:101/vm-101-cloudinit.qcow2,media=cdrom
ide2: none,media=cdrom
ipconfig1: ip=HOSTIP/24,gw=GWIP
memory: 4096
name: test-iscsi2
net0: virtio=82:FC:B9:89:31:AC,bridge=vmbr0,link_down=1
net1: virtio=C2:36:0E:B1:A7:01,bridge=vmbr0,tag=VLANID
numa: 0
ostype: l26
protection: 1
scsi0: local:101/vm-101-disk-0.raw,discard=on,size=10G
scsihw: virtio-scsi-pci
smbios1: uuid=6967654a-06b4-4463-a28d-fc81290e8be0
sockets: 1
Keep up the good work!
One notable addition is the extended support of VM balancing. I understand that the balancing is triggered only under specific conditions such as node failure, resource/guest start-up and HA group changes. I am wondering if the VM balancing will be supported also on cases where all the nodes are healthy and the distribution of VMs/load is not even so as to automatically migrate VMs for improved load sharing between nodes.
One notable addition is the extended support of VM balancing. I understand that the balancing is triggered only under specific conditions such as node failure, resource/guest start-up and HA group changes. I am wondering if the VM balancing will be supported also on cases where all the nodes are healthy and the distribution of VMs/load is not even so as to automatically migrate VMs for improved load sharing between nodes.
@czechsys I have experienced similar sounding problems on a couple of HP servers (can't remember the models). Not a fix, but to get around it I ended up doing a minimal Debian install and installing Proxmox on top of that. Detals at https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye
Hi,
yes, this is planned. It's the
Dynamic-Load scheduling mode on the roadmap: https://pve.proxmox.com/wiki/Roadmap#Roadmap