Search results

>Würde ich beim LXC Container aber eher nicht empfehlen Distro upzugraden auch wenns funktioniert. sondern ?

moin falk, >Genau diese Anleitung schreibt auch, dass man forcerescan nutzen soll. hier steht was anderes : https://www.suse.com/support/kb/doc/?id=000018876 welche sg3_utils version hast du ?

i have opened the following RFE: https://bugzilla.proxmox.com/show_bug.cgi?id=5956

furthermore - it would perhaps be helpful to print "warning" when a task/step is causing a warning, otherwise it's difficult to distinguish, what's causing the warning 2024-11-30T09:24:20+01:00: Starting datastore sync job...

ok. thanks. it seems there was another warning in that job, so i thought that job warning would result from this. now after another sync, i'm getting these message for every snapshot, so it looks now logical to me. anyhow - wouldn't it make sense to log the group/vm name which is being skipped...

Hello, i'm getting these warnings on push sync. What does that mean or what's causing these? How do i get rid of them ? regards 2024-11-30T09:24:20+01:00: Starting datastore sync job 'pbs_msb:repli_pve-maker-bonn_backup:backup_pve-maker-bonn::s-d709b329-dc73' 2024-11-30T09:24:20+01:00: sync...

what about trying proftpd on a fresh debian12 VM to see how it behaves there? otherwise, give vsftpd a try.

>setup was failing for seemingly Proxmox specific reasons what proxmox specific reason ?

memory ballooning ballooning also sometimes kicks in when there is no need for it, e.g. https://bugzilla.proxmox.com/show_bug.cgi?id=3859

furthermore - memory usage on the host level is completerly inaccurate too, because it has never been highly prioritized to improve memory display. that is especially true, if you use local ZFS storage (since ZFS ARC cache needs extra handling) https://bugzilla.proxmox.com/show_bug.cgi?id=1454...

thanks for pointing that out and making things clear - i totally agree with you !

>Why actually try the original reproducer from the linked bugzilla, which was confirmed to still trigger just yesterday, >instead of some completely different pattern...? @t.lamprecht , because hannes reinecke (=experienced kernel hacker) made this bold statement "Which means that the test...

also added an RFE for live migration with memory compression : https://bugzilla.proxmox.com/show_bug.cgi?id=5766

the problem happens when doing manual backup via vzdump or pbs when there is notification mode "auto" and "none" is set in the email field. apparently it's fixed after upgrade to 8.2.7. it happened with 8.2.2

the gui dialog saves all input just fine. ich changed the real host/domain names into something different, for privacy reason

Hello, i'm getting INFO: Backup job finished successfully ERROR: could not notify via target `smtp-notify`: could not notify via endpoint(s): smtp-notify: Invalid input TASK OK how can i determine what the "invalit input" is about ?

man efibootmgr

Can someone give some insight if proxmox is using any type of compression for live migration? at least for the ram transfer, i know qemu has this feature - but it does not seem to be used (see info migrate_capabilities below)...

i can confirm that. removing snapshots quickly does not show the problem. but removing them after some usage/writes, i also get freezes on removal external snapshot support is coming. this may fix the problem https://lists.proxmox.com/pipermail/pve-devel/2024-September/065401.html do we...

still no vzdump backup encryption. not even on the roadmap. that's sad.