Recent content by xenon96

  1. X

    Proxmox Datacenter Manager - First Alpha Release

    Oh yes thanks, that looks more familiar! Note: Dropdown not working on MacOS Safari, I have to switch the theme in Firefox
  2. X

    Proxmox Datacenter Manager - First Alpha Release

    Good idea, and I'm sure many users have wanted this for a long time, including me. But why did you move from the Sencha UI / ExtJS? Sure, it's just a change, but I personally found your previous UI very nice, practical and clear!
  3. X

    Failed to destroy vGPU device.

    The workaround is no longer necessary since PVE-7.4 as it has been integrated into the proxmox qemu server (a bit better :P).
  4. X

    Unable to start most LXC containers after rebooting (run_buffer 322)

    You should uninstall pve-kernel-6.2: e.g. apt-get purge pve-kernel-6.2*, then simply reboot and a uname -a should display something like that: Linux my-pve-host 5.19.17-2-pve #1 SMP PREEMPT_DYNAMIC PVE 5.19.17-2 (Sat, 28 Jan 2023 16:40:25 x86_64 GNU/Linux
  5. X

    Unable to start most LXC containers after rebooting (run_buffer 322)

    I also have this issue when upgrading to optional 6.2 kernel. After downgrade back to 5.15 or 5.19 all LXCs starts again. But i have also observed this behavior with PVE-7.3 and 7.2 with the optional 6.1 kernel. PS: The lxc container is a proxmox-mail-gateway instance. Using LVM
  6. X

    Failed to destroy vGPU device.

    I wrote a mail to nvidia's enterprise support. Will report back if they answer me. EDIT: Their answer postet below.
  7. X

    Failed to destroy vGPU device.

    Ok apparently the mdevs are also included during a backup. For example, I have a VM which never actually runs, but it has a vgpu assigned to it. I now have the problem that I have ghost mdevs from vms that are not running. Probably this is due to the fact that I have commented out the cleanup...
  8. X

    Failed to destroy vGPU device.

    it's not that simple, unfortunately. First you have to check if it is an Nvidia GPU, and then if the Nvidia driver is >= 15.0. In addition, only < 16.0 should be checked, if nvidia changes something again in the future.
  9. X

    Failed to destroy vGPU device.

    This is just a temporary fix and may break your system/mdevs. Only use this if you're using nvidia mdevs and no other mdevs like network-cards, ... Additonally this will be overwritten on proxmox updates.
  10. X

    Failed to destroy vGPU device.

    If you DM me i can give you a hint. I wrote the message as i got an error that i can not write you. mh, i don’t unterstand why there is an error, and there is no error when this lines are commented out. Maybe the error is somewhere else? How do i print into log in perl? Maybe i can figure out...
  11. X

    Failed to destroy vGPU device.

    I'am running on 14.4 drivers since a few weeks and before on 14.3 which were really stable and did not clean up automatically. This behaviout is also new to me on drivers 15.0 and 15.1. I have no urgent reason to upgrade to 15.0/15.1 drivers (since 14.x is working great with proxmox) but i'am...
  12. X

    Failed to destroy vGPU device.

    Ok after changing commenting out the lines 6127, 6128 (which are 6099,6100 on my local /usr/share/perl5/PVE/QemuServer.pm) to sub cleanup_pci_devices { my ($vmid, $conf) = @_; foreach my $key (keys %$conf) { next if $key !~ m/^hostpci(\d+)$/; my $hostpciindex = $1...
  13. X

    Failed to destroy vGPU device.

    I can reproduce this issue using nvidia grid driver >= 15.0. To get around this, use 14.x drivers. Nevertheless my environment: root@myhost:~# uname -a Linux hostname 5.15.83-1-pve #1 SMP PVE 5.15.83-1 (2022-12-15T00:00Z) x86_64 GNU/Linux As you can see on nvidia-smi vgpu the VM...