Latest activity

  • D
    Der Harry replied to the thread Problem with time within vms.
    https://bugzilla.proxmox.com/show_bug.cgi?id=5032 I wrote this many years ago - referenced this here - and have mitigation in the ticket. ‍*shrug* I wrote several features using the hook script: https://github.com/egandro/proxmox-cpu-affinity...
  • P
    proxuser77 replied to the thread Problem with time within vms.
    So, what is the question then? I mean, your post isn't providing any concrete suggestions on how to fix it eitehr. And If it did, it would probably be better placed in the existing Bugzilla report. Complaining, "nagging", and statements such as...
  • A
    Bit late on the answer, apologies... Just updated the container to its latest release, using PBS version 4.2.0 and the issue is still there. I will keep at it without using Verify and we will see if eventually something in the future fixes the...
  • hloudes
    hloudes replied to the thread How to configure DSCP ?.
    Of course, I had already increased the config_version. I ran the test again with a value of 12. As you can see in the screenshot, Corosync does take the configuration into account, but when I look at my dump, I still see the same thing...
    • 1780320872561.png
    • 1780321045899.png
  • S
    @oxmoxmoney , @HammyHavoc : maybe also make a mention in the ticket? I assume it gets picked up if enough people give it a "thumbs up". I'm also eagerly awaiting news on this.
  • J
    Thanx! This works on Windows XP also!
  • J
    Try this, works on my win2003 and win2008, just update driver on your unknown device and point to the iso drivers folder, it will search and find the correct driver for your qemuvgid...
  • YaZoal
    YaZoal replied to the thread How to configure DSCP ?.
    Could it be due to the internal bit shift [0]? Could you test with ip_dscp 12? Remember to increase the config_version [1]. [0] https://manpages.debian.org/unstable/corosync/corosync.conf.5.en.html#ip_dscp [1]...
  • D
    Der Harry replied to the thread Problem with time within vms.
    This is a open ticket for many years - it has a Bug Report on Bugzilla with many ideas. It's a bug / not implemented feature. Not a perceived "mood issue". Not a tiny thing you can fix "in general" with NTP. You can fix it with NTP in some...
  • H
    this is not the case in general - it depends on your active rules (you need a rule with a Spam Level What object (and Block/Quarantine as Action) in the direction of the mail - which rules are active in your setup? You need to enable the...
  • B
    BobhWasatch replied to the thread Problem with time within vms.
    Sorry if I accidentally stepped on your bad mood. Was just trying to solve the immediate problem.
  • D
    Der Harry replied to the thread Problem with time within vms.
    With all respect. Don't lecture about NTP. We know what it is - we know how to so called "properly configure" it. Proxmox is lacking of a feature that RedHat explicitly mentions in the qemu guest agent and VMware also has. That is the point -...
  • D
    I will update both host and guest to latest pve kernel and test when a window becomes available and will report here after. Let's hope it was fixed at some point...
  • W
    Same here, did you find a Solution for that?
  • B
    BobhWasatch replied to the thread Problem with time within vms.
    You have to configure NTP to correct the time when the delta is large, else it won't correct this problem. How you do that varies by NTP server. For chrony you need something like "makestep 0.1 -1" in the config file. Apparently you don't all...
  • W
    This also apply for "CT" (containers), i dont know how to setup the container to use the USB device beside using the device "path" wich the USB Port number and device number... (Something like that) Thanks!
  • D
    Der Harry replied to the thread Problem with time within vms.
    Thank you. This is a very friendly response. We all know what NTP is. If that was a 100% solution, nobody would ask for a fix for 2-3 years.
  • D
    Der Harry replied to the thread Problem with time within vms.
    It is not "my" hookscript. Hookscripts are a general supported thing in Proxmox. They are called e.g. after / before start/stop/backup etc. Unfortunately not for suspend, resume etc (probably I am wrong here). When we would have this, we can...
  • B
    BobhWasatch replied to the thread Problem with time within vms.
    You could use NTP inside the VM.
  • F
    franzz replied to the thread Problem with time within vms.
    Yeah, is not nice as for enterprise envs. What does your "hookscript.pl"? In my opinion you need to catch for VM snap with RAM, then if VM is running after rollback and QEMU Guest Agent is enabled and guest agent responds to ping then call QGA...