Search results

IMO that's not really possible because: * to backup the vm it has to be started (in a paused state) so one can start the vm anytime (even when currently backing up) * to properly start the vm, the isos must be available, because we cannot know if they're essential for e.g. the boot process or...

could it be that there is a thermal problem? i.e. the adapters get too hot? also can you post a bit more from the dmesg? maybe there is some driver problem...

it's probably missing the newline at the end of the ticket line?

Just FYI, we're aware of the changes that NVIDIA made here (only very recently though) and we're thinking about how we can go forward here. (This is one reason for why there's no 6.8 compatibility on the wiki yet)

since this is a mostly english speaking forum, please write your post in english

from the error message it seems that the fingerprint you entered does not match the one received, but hard to say with the actual fingerprint censored out

no it hasn't changed, i faintly remember an internal discussion about it with the conclusion that it's intended the way it is, but no specifics sorry if you want, you could raise a bug at https://bugzilla.proxmox.com probably someone else knows the exact reason why it is the way it is you...

i just wanted to put it in context for future readers, to not raise expectations ;) (though i hope not many new users will start with ~20 year old hardware...)

ok, the dmesg and config look normal/ok so far, but i noticed from the dmesg that the radeon driver gets loaded on boot. could you try blacklisting that driver in pve so it does not get loaded? what about the windows event viewer entries?

did you enable the virtual functions like described here: https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE ? could you please post the whole, unfiltered dmesg? possibly not all relevant messages contain 'nvidia' ;)

mhmm... actually reading the docs, it may allocate a new media-set if the required one is missing, but what you could do is to set the 'writable' tape to status 'full' either manually or via api/cli that would mark the recent one full and a new tape would be requested

did you use the pve ui for that (since you mentioned VM), by any chance contain the directories non-ascii symbols (e.g. cyrillic, german umlauts, etc.) ? if yes, you're probably running into this (already fixed) bug: https://bugzilla.proxmox.com/show_bug.cgi?id=5465

mhmm without testing what should work i think is the following: have single media pool X allocation policy: friday sometimes before 22:30 e.g. 20:00 retention policy: 3 weeks (or depending on timing may be better to use 20 days) one backup job at friday 22:30 , + export one backup job for...

hi, what exactly is the symptom of 'not booting' ? does it show some error? a black screen? do you see the bootloader? (i.e. grub?)

can you post the output of 'dmesg' and the vm config (qm config ID)? if you boot the vm again (e.g. without the passthrough) is there anything interesting in the windows event viewer?

can you check what the sysfs says? there should be a directory with the available mdev under /sys/bus/pci/devices/<pciid>/mdev_supported_types where the pciid is either the device itself or a virtual function (not sure how it's exactly with the P4) also the lspci -vvv output of the...

hi, while some LTO-3/4 drives/changes may implement the functions/features we need to operate it, this is not guaranteed. We target LTO-5 (released in 2010 so 14 years ago) as that guarantees all functions we need to properly implement our logic.

did you try booting your host with csm/bios instead of uefi ? but changing the setup is also understandable if using virtualization is too much of a hassle..

since what you're doing is rather unusual (but cool nonetheless ;) ) i can only speculate, but my guess would be that it has something to do with how graphics cards get initialized, and especially old ones. bios + vga needs special steps in order to function correctly, and maybe the virtual bios...

i can confirm that this does not work on btrfs currently (it seems the way we collect those stats simply does not work for btrfs since it does not point directly to a block device) i opened a bug: https://bugzilla.proxmox.com/show_bug.cgi?id=5602 you can add yourself to it, then you'll get a...