Trying to setup CentOS 9 VM as Veeam Hardened Repository but encounter below error. From forum there is suggestion to change the machine type but i have try version 8.0 on i440fx and q35, still not working. Any idea?
Hi all,
A bit of a weird one here, leaving this here in case anyone finds themselves in the same boat as we did.
Colleague installed a VEEAM backup on a clean installation of Windows Server 2019, wanted to add a Dell DD6400 Data domain as a repository. This was already working on another VEEAM VM in the same cluster, mind you.
No luck, when adding the repository, this error pops up :
A bit of a weird one here, leaving this here in case anyone finds themselves in the same boat as we did.
Colleague installed a VEEAM backup on a clean installation of Windows Server 2019, wanted to add a Dell DD6400 Data domain as a repository. This was already working on another VEEAM VM in the same cluster, mind you.
No luck, when adding the repository, this error pops up :
Code:
Detecting server configuration Error: Failed to call RPC function 'GetBiosUuid': Error code: 0x80004005. Cannot query class instance from enumerator object.
Failed to...
- Taledo
- Replies: 4
- Forum: Proxmox VE: Installation and configuration
Code:
18/4/2025 3:06:45 PM Error Detecting server configuration Error: Failed to call RPC function 'GetBiosUuid': Error code: 0x80004005. Cannot query class instance from enumerator object.
Failed to call RPC function 'GetBiosUuid': Error code: 0x80004005. Cannot query class instance from enumerator object.
18/4/2025 3:06:45 PM Error Failed to save Backup Repository: Failed to call RPC function 'GetBiosUuid': Error code: 0x80004005. Cannot query class instance from enumerator object.
18/4/2025 3:06:50 PM Error Infrastructure item save failed Error: Failed to call RPC function 'GetBiosUuid': Error code: 0x80004005. Cannot query class instance from enumerator object.
Code:
proxmox-ve: 8.4.0 (running kernel: 6.8.12-9-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.12-9
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.8-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.0-1
proxmox-backup-file-restore: 3.4.0-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.3.10
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.3
pve-firewall: 5.1.1
pve-firmware: 3.15-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.2
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2
Code:
root@pve01:~# cat /etc/pve/qemu-server/104.conf
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
efidisk0: local-data:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/CentOS-Stream-9-20230321.0-x86_64-boot.iso,media=cdrom,size=865M
memory: 4096
meta: creation-qemu=9.2.0,ctime=1744955100
name: VeeamHardenedRepo1
net0: virtio=BC:24:11:4D:43:75,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
parent: default
scsi0: local-data:vm-104-disk-1,iothread=1,size=50G
scsi1: local-data:vm-104-disk-2,iothread=1,size=100G
scsihw: virtio-scsi-single
smbios1: uuid=682d3325-baa9-438b-8c79-87f1155d6e05
sockets: 1
vmgenid: eab54a08-6846-40f0-9dd3-c57db9662e8c
[default]
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
efidisk0: local-data:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/CentOS-Stream-9-20230321.0-x86_64-boot.iso,media=cdrom,size=865M
memory: 4096
meta: creation-qemu=9.2.0,ctime=1744955100
name: VeeamHardenedRepo1
net0: virtio=BC:24:11:4D:43:75,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-data:vm-104-disk-1,iothread=1,size=50G
scsi1: local-data:vm-104-disk-2,iothread=1,size=100G
scsihw: virtio-scsi-single
smbios1: uuid=682d3325-baa9-438b-8c79-87f1155d6e05
snaptime: 1744958098
sockets: 1
vmgenid: eab54a08-6846-40f0-9dd3-c57db9662e8c
root@pve01:~#
Code:
[admin@VeeamHardenedRepo1 ~]$ sudo dmidecode -s system-uuid
[sudo] password for admin:
682d3325-baa9-438b-8c79-87f1155d6e05
[admin@VeeamHardenedRepo1 ~]$ cat /etc/machine-id
4ebfd19d786b4631999ca53439ddc1cd
[admin@VeeamHardenedRepo1 ~]$