Search results

  1. M

    Problem/message L1TF CPU bug and data leak

    yes it can be disabled: nano /etc/default/grub add to kernel line mitigations=off update-grub reboot warning is gone :)
  2. M

    Terminal Server Windows Server 2019/2022 on Proxmox Virtualiziation

    There are 3 answers to this: - it is cheaper - it has an excellent rdp webaccess with letsencrypt - apps that are not running on "real" terminalservers, are running in this constellation
  3. M

    Terminal Server Windows Server 2019/2022 on Proxmox Virtualiziation

    Hey, I did it, but only with Windows 10 Enterprise LTS with TSPlus addon. Works very well. 40+ Users on one TSPlus instance.
  4. M

    Opt-in Linux 5.19 Kernel for Proxmox VE 7.x available

    you can always set retbleed=off in grub.
  5. M

    Retrieving backup list from PBS runs into timeout

    I have the same issue. After reloading the Page or changing the storage on the left, it is working mostly.
  6. M

    PBS initial offline sync

    but could I mount this "external" datastore on different servers? wasn´t there a kind of encryption key?
  7. M

    Feature Suggestion: AVX/AVX2 CPU flags

    Worked. EXAMPLE FILE cpu-model: avx flags +avx;+avx2 phys-bits host hidden 0 hv-vendor-id proxmox reported-model kvm64
  8. M

    Feature Suggestion: AVX/AVX2 CPU flags

    +1
  9. M

    PBS initial offline sync

    we all want this :)
  10. M

    PBS auf Raid5?

    Mit einem Hardware Raidcontroller kannst du PBS mit Ext4 oder XFS laufen lassen aber nicht mit ZFS.
  11. M

    [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13

    It happend with "Other", as well. So no real solution.
  12. M

    [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13

    I have to say the issue came up on an old Proxmox 6.4 yesterday. So it is a Windows issue. Changing to other for now.
  13. M

    [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13

    I tried that already. Same issue. It only happens mostly on UEFI VMs. And only older VMs. Fresh installed Win10 with 6.1 or 6.2 qm do not have the issue.
  14. M

    [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13

    agent: 1 balloon: 0 bios: ovmf boot: cd bootdisk: virtio0 cores: 16 cpu: Broadwell-noTSX efidisk0: nvme-vms:base-888-disk-0/vm-1132-disk-1,size=1M ide2: none,media=cdrom machine: pc-i440fx-5.1 memory: 32768 name: fbo-ts-22 net0: virtio=16:8E:93:78:9C:xx,bridge=vmbr0,firewall=1,queues=4,tag=1002...
  15. M

    [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13

    It is a Windows 10 Enterprise 21H2 with TSPlus as Terminalserver Addon. The reboot worked fine in Proxmox 6.x. After the upgrade to 7.x the issues came up. I tried many options, also the pve-edge-kernel.
  16. M

    [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13

    Hi, I finally got it fixed (kind of)! Change OS Type to "other" and the reboot issue is gone for me. I'm glad that I can reboot my TerminalServers nightly again.
  17. M

    [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13

    same to me...wonder if there are any news to this.
  18. M

    Proxmox VM mit Windows 10 und virtio Treiber Netzwerk Fehler

    Englisches ISO nehmen und danach auf deutsch umstellen.
  19. M

    OpenGL on Windows 10 VM

    you can try this here...i got some cad working on a kvm win 10 terminalserver: https://github.com/pal1000/mesa-dist-win/releases
  20. M

    Proxmox VE 7.2 megaraid issues

    you have to fix the uefi health in the bios setup...i had the same problem, too.
Top Bottom