Search results

> Aus unserer täglichen CAD-Tätigkeit wissen wir, dass eine durchschnittliche Gaming-Grafikkarte völlig ausreicht reicht da nicht in den meisten fällen schon eine nvidia quadro K620 ?

wieviel ram hat denn der host und was haben alle laufenden VMs jeweils an ram zugewiesen? check mal das kernel eventlog auf oom-killer events

https://bugzilla.proxmox.com/show_bug.cgi?id=4879#c6

what do you mean with "are authorized" ? hba mode sucks with these controllers. they are not made for this and even if this may work initially, they miserably fail on disk error conditions. getting controller freezes, stuck zpool.... whatever.

where in the rules is this not allowed anymore? and how can they change thi where in the rules isn't that allowed anymore ?

fleecing works good for me, from a first point of view. but do i see this right that it is only availble when doing backup via backupjob , but not when doing backup manually via "backup now" option in vm configuration ? guess this is planned to be added later on ?

ah, ok. that makes sense. sorry, i could have found this myself :p

EDIT: this has nothing to do with 8.2 update, there was some change for alias handling last year and apparently settings getting changed if you edit and re select via dropdown box. so it's not an issue but a feature. see...

i did update my non-production test-system. i want to try new fleecing feature. what is the reason that fleecing storage "local-zfs" is selected by default and greyed out, so no other fleecing storage can be selected ?

i got another VM with this error qemu-img: Could not delete snapshot 'vor_os_update': Failed to free the cluster and L1 table: Invalid argument TASK ERROR: command '/usr/bin/qemu-img snapshot -d vor_os_update /rpool/vms-files-zstd/images/106/vm-106-disk-0.qcow2' failed: exit code 1

> https://forum.proxmox.com/threads/opt-in-linux-6-8-kernel-for-proxmox-ve-8-available-on-test-no-subscription.144557/post-651341 the reported performance differences of docker inside lxc here is one more reason for me to to NOT use docker inside LXC or recommend doing so.

hello, does anybody know some good site which is benchmarking ssd's for comparison and which provides reliable and good information regarding sustained write capability ? for many many ssd, especially the cheaper ones, sustained write really sucks ...

what makes you think the opetions are not applied? please remove quiet and splash=silent options and try again

did you try how it behaves with a different monitor model ?

sorry, i was too fast and without coffee in the morning. i don't have experience with 440ar, but for sure i can tell p410/420 has issues with hba mode

P440ar in hba mode is a bad idea

@Stoiko Ivanov , mhh, nicht problematisch ? anwendungen sperrt doch aus security gründen in einen chroot und gerade die sollten doch up to date sein !? ich habe hier mal ein bugticket aufgemacht, weil sich mir nicht erschliesst warum das nicht problematisch ist wenn der chroot inhalt veraltet...

>Yes, we know and that's why we expose disabling copy-on-write for data (which is mentioned also as workaround in the linked report), it's currently configurable per storage: https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=d3c5cf24876d2b0e1399f717e2f77eaf063ae7a7 ah, good to know...

i opened up a bugreport for this at https://bugzilla.proxmox.com/show_bug.cgi?id=5320

you should check your kernel log / dmesg for errors. i guess your usb connection isn't stable or your usb stick is not reliable . could also be related to powersave settings on usb ports