Unexpected boot order change (?!)

[chudak]

Hello

Here are details steps:

Initial boot order =>



Changed CD/DVD content from



to



and Saved

Final boot order results =>




Why the boot order has changed ? Feels like a bug to me, I'd expect the order was preserved.

 

[oguz]

hi,

doesn't happen here, what is your pveversion -v?

 

[chudak]

hi,

doesn't happen here, what is your pveversion -v?

root@pve:~# pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve) pve-manager: 7.0-10 (running version: 7.0-10/d2f465d3) pve-kernel-5.11: 7.0-6 pve-kernel-helper: 7.0-6 pve-kernel-5.4: 6.4-4 pve-kernel-5.11.22-3-pve: 5.11.22-6 pve-kernel-5.11.22-2-pve: 5.11.22-4 pve-kernel-5.4.124-1-pve: 5.4.124-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 14.2.21-1 corosync: 3.1.2-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown: 0.8.36 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.21-pve1 libproxmox-acme-perl: 1.2.0 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.0-4 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.0-5 libpve-guest-common-perl: 4.0-2 libpve-http-server-perl: 4.0-2 libpve-storage-perl: 7.0-9 libqb0: 1.0.5-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.9-4 lxcfs: 4.0.8-pve2 novnc-pve: 1.2.0-3 proxmox-backup-client: 2.0.7-1 proxmox-backup-file-restore: 2.0.7-1 proxmox-mini-journalreader: 1.2-1 proxmox-widget-toolkit: 3.3-6 pve-cluster: 7.0-3 pve-container: 4.0-8 pve-docs: 7.0-5 pve-edk2-firmware: 3.20200531-1 pve-firewall: 4.2-2 pve-firmware: 3.2-4 pve-ha-manager: 3.3-1 pve-i18n: 2.4-1 pve-qemu-kvm: 6.0.0-2 pve-xtermjs: 4.12.0-1 qemu-server: 7.0-11 smartmontools: 7.2-pve2 spiceterm: 3.2-2 vncterm: 1.7-1 zfsutils-linux: 2.0.5-pve1

 

[oguz]

does this VM boot?

can you try using ide0 instead of ide1 for the virtio iso

 

[chudak]

does this VM boot?

what do you mean "does this VM boot?", of cause it boots up initially and after the boot order was changed it won't

can you try using ide0 instead of ide1 for the virtio iso

It still messed the the order



My guess this is a UI bug after adding/changing h/w (CD/DVD or maybe else), the boot order list gets rearranged (add but the added device get unchecked) to some "initial" order
What do you think?

PS: the good news is that before reboot those changes can be reverted I am snot sure if revert will work after reboot, will it ? (that would be great)

 

[fabian]

this bug is already fixed in qemu-server 7.0-13, please upgrade..

 

[chudak]

this bug is already fixed in qemu-server 7.0-13, please upgrade..

that was fast !

 

[chudak]

this bug is already fixed in qemu-server 7.0-13, please upgrade..

indeed fixed, thx!!!