Search results

XXXX - VMID pci_device_id - your id pci_id - your id nano /etc/vgpu_unlock/profile_override.toml [profile.nvidia-256] num_displays = 1 display_width = 1920 display_height = 1080 max_pixels = 2073600 cuda_enabled = 1 frl_enabled = 1 framebuffer = 0x76000000 pci_device_id = 0x1E30 pci_id =...

cpu: host,flags=+ibpb;+virt-ssbd;+amd-ssbd;+amd-no-ssb;+aes change host to default, remove extra flags net0 - change e1000 to virtio

Nvidia License Server must be installed somewhere, Licenses must be purchased depending on the configuration. but there is another way: drivers and unlock (Nvidia deleted all our accounts and purchased licenses and access to the portal, respectively)

What are the properties of a VM? (qm config ID) Most interesting CPU, type, cores/socket, NUMA, maybe extraflags Maybe Proxmox writes something interesting in the logs? Is everything clean in the PVE console? (only login screen?)

https://gitlab.com/polloloco/vgpu-5.15

How to solve the problem so as not to get into iRMC / LiLO after losing the server: 1. use tmux/screen so as not to break the update. 2. apt update && apt upgrade -y && systemctl restart networking.service

PVE 7.1.1 5.15.27-1-pve openvswitch-switch openvswitch-common

OS: Proxmox VE 7.1-10 x86_64 Kernel: 5.15.19-2-pve Everything is fine after upgrade. Thnx. ThinkSystem SR630 PRIMERGY RX2540 M5 Lenovo System x3550 M5

was not attentive pve starts lightly, but console freezes on these lines [ 12.862026] fb0: switching to mgag200 from simple [ 12.867860] mgag200 0000:02:00.0: vgaarb: deactivate vga console [ 12.868344] mgag200 0000:02:00.0: [drm] *ERROR* can't reserve VRAM ThinkSystem SR630 & PRIMERGY...

Yes, everything is great. Now you do not need to boot into the old kernel to fix something from the console. there was another error in dmesg that I didn't see right away: [drm] *ERROR* can't reserve VRAM

The console freezes, but there are no problems via ssh and functioning of pve/cluster/virtual machines and other. I don't see any other errors. 3 different servers. Btrfs on hosts. My non-passing through Efi stub: I don't see any other errors. 3 different servers. Btrfs on host. [ 0.000000]...

No, autostart VM. I completely forgot.. PVE is installed on btrfs PVE Storages nfs, lvm, iscsi (no zfs) BUT storage PBS ('omega' host) is zfs with iscsi (there is no other storage option for iscsi yet) When the backup tasks are started, the memory jumps by 40-50%, yes. I am sorry to...

Memory leak, not freeing memory 83 threads of proxmox-backup-server since host reboot, not a single VM has been started only backup jobs pve+pbs installed on btrfs raid1 (clean install 7.0 & 2.0 and updated to 7.1 & 2.1) root@omega:~# pveversion -v proxmox-ve: 7.1-1 (running kernel...

after Live Migration, do I get nonreleased memory or is it just wrong data? pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-7 (running version: 7.1-7/df5740ad) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.13.19-1-pve: 5.13.19-3 ceph-fuse...

last updates to pve-kernel-5.13.14-1-pve & qemu-server: 7.0-16 reboot host, start backup VM (was stopped after reboot) INFO: starting new backup job: vzdump 1005 --node theta --storage iomegapbs --mode snapshot --remove 0 INFO: Starting Backup of VM 1005 (qemu) INFO: Backup started at...

After last updates to 5.11.22-5-pve # 1 SMP PVE 5.11.22-10 and reboot the host system caught the same error (qmp cont timeout). I reinstalled pve-qemu-kvm / qemu-server again and the backups work again.

did some experiments (PVE7 - all updates to date (pvetest): 1. Rebooted pve host (all VMs are turned off after reboot (there is no automatic VM power on) 2. apt reinstall qemu-server* 3. apt reinstall pve-qemu-kvm* 4. launched a backup (VM 1005, with which I am experiencing a backup problem)...

No. If I add 4 * 50GB, they take 200 GB, but now is not about that..: Right now - I have issued 201GB for VMs with a video card passthrough. (in total, 220GB is available on the host) After half an hour, the VM is at the merl. The VM was idle, no operations were performed on it. This was the...

The situation has not changed if I disable passthrough.

+ I started experiencing problems with backups and 'qmp command 'cont' failed - got timeout' with one of my VMs (ubuntu 20.03.04, all updates, kernel 5.11.0-36, btrfs lvm filesystem, ms sql server 2019 is installed). It doesn't matter - with or without qemu agent. Proxmox 7 - clean install on...