Recent content by uncle.cripple

  1. Proxmox update from 7.2-4 GRUB update failure

    Same problems with the Update on two Proxmox Servers, running with ZFS-mirror Boot devices. proxmox-ve: 7.2-1 (running kernel: 5.15.53-1-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-10 pve-kernel-helper: 7.2-10 pve-kernel-5.13: 7.1-9 pve-kernel-5.4: 6.4-10...
  2. [SOLVED] hostname not set via CloudInit with --cicustom and Ubuntu 22.04

    Turns out, there is a quite simple - albeit not obvious, at least not to me - solution to set the hostname in the above mentioned scenario, while still using the cloudinit-user.yml and cloudinit-vendor.yml files! As mentioned in the cloud-init documentation for the datasource NoCloud you can...
  3. [SOLVED] hostname not set via CloudInit with --cicustom and Ubuntu 22.04

    @bbgeek17 Thanks for your answer and sorry for the late reply. Is there a way to dynamically add the Meta-Configuration to the Template, depending on the VM-ID? Or is it possible to use a Variable in the Meta-Template to reference the hostname from the VM-configuration? My users creating a...
  4. [SOLVED] hostname not set via CloudInit with --cicustom and Ubuntu 22.04

    I have an issue with CloudInit on Proxmox 7.2 and Ubuntu 22.04, that the hostname of the VM given in the Proxmox GUI will not be set in the VM. As basis i use the CloudImage jammy-server-cloudimg-amd64.img of Ubuntu from https://cloud-images.ubuntu.com/jammy/current/ I have two CloudInit...
  5. DirtyPipe (CVE-2022-0847) fix for Proxmox VE

    I updated two Cluste-nodes to 5.13.19-5-pve #1 SMP PVE 5.13.19-12 this morning. One node (still) behaves normal. From the other node i got fencing-messages later this morning (mail-subject "FENCE: Try to fence node 'pve-06'"). I discovered that the node had a /var/log/syslog of roughly 164 GB in...
  6. Proxmox VE 7.1 released!

    I just glanced over the VM configs and Task histories and i don't know if it's important. But for the Windows 2016 VM you see unused0: nas02-images:100010/vm-100010-disk-0.qcow2. I moved the disk to a different NAS on 2021-12-09 at around 10:00 o'clock in the morning - previously it was on the...
  7. Proxmox VE 7.1 released!

    Thanks for the quick reply. - Dell PowerEdge R440 with 40 x Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz (2 Sockets) - Dell PowerEdge R630 with 48 x Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (2 Sockets) - Fujitsu PRIMERGY RX2530 M1 with 48 x Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (2 Sockets)...
  8. Proxmox VE 7.1 released!

    I upgraded from PVE 6.4 to PVE 7.1 last week (2021-12-02) and still experience the freezing problems over the last week with my Windows VMs (2012R2/2016) which are using SATA-disks. The freezing seems most likely to happen when the integrated Windows Server Backup starts due to higher disk I/O...
  9. PVE update: Backups failed on LXCs with bind mount points

    I can confirm the same issue. The linked temporary solution apt install pve-container=3.2-2 fixed the problem for now.
  10. [SOLVED] VMs won't boot after upgrade

    What i don't understand is, why does it work with pc-q35-4.1 but not with q35, when the later is only an alias for ther first? q35 Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-4.1)
  11. [SOLVED] VMs won't boot after upgrade

    Here are the different results: pc-q35-4.1 /usr/bin/kvm -id 110 -name enterprise -chardev 'socket,id=qmp,path=/var/run/qemu-server/110.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control'...
  12. Problem with VM boot OS Windows 2012

    Correct me if i'm wrong, but does OVMF (UEFI) not require the machine type q35? Maybe there is also a bug in the current release when UEFI-booting a Default (i440fx) machine as there is with q35! Looks like the default machine-aliases are not handled correctly for UEFI VMs. Can you try setting...
  13. [SOLVED] VMs won't boot after upgrade

    I tried it out too. Setting machine: pc-q35-4.1 works for me also! Really strange!
  14. [SOLVED] VMs won't boot after upgrade

    OK, got my VM running again with the hint from @onepamopa in this thread to switch to machine type pc-q35-3.1. I edited my configuration /etc/pve/qemu-server/110.conf and replaced the line machine: q35 with machine: pc-q35-3.1 and the VM booted just fine! The list of supported machine types...
  15. [SOLVED] VMs won't boot after upgrade

    Same problem here! VMs with OVMF (UEFI) won't boot anymore! No problems with Default (SeaBIOS) VM though! BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x)/Pci(0x1E,0x0)/Pci(0x1,0x0)/pci(0x5,0x0)/Scsi/0x0,0x0): Not Found Configuration of problematic VM: root@pve01:~#...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!