Latest activity

What's new Featured content New posts New profile posts Latest activity
  • T
    tomten replied to the thread QEMU 11.0 available on pve-test and pve-no-subscription as of now.
    @fiona It's an alpine linux vm (6.18.33-0-lts) running k3s with a flannel network config. agent: 1 balloon: 0 bios: seabios boot: order=scsi0;net0 cores: 4 cpu: host memory: 6144 meta: creation-qemu=7.1.0,ctime=1673013831 name: k3s-node4 net0...
  • D
    Der Harry replied to the thread Problem with time within vms.
    I mentioned it the ticket and here multiple times. It is in the ticket. Proxmox GmbH needs to just implement this. Red Had has a "set-clock" in QEmu Guest Agent. That is not as awesome as the VMware solution but - we in this thread and in the...
    • 1780325661967.png
  • P
    proxuser77 replied to the thread Problem with time within vms.
    I mean, yeah, the discussion is kind of pointless as long as nobody comes up with a specific proposal for how to actually fix the problem, which you apparently don't have either. And no, "VMware does it", "NTP is bad", or "using the hardware...
  • S
    soporte_sie posted the thread Error with driver ic3 in Proxmox VE: Installation and configuration.
    ---------- [Mon May 18 11:28:24 2026] UBSAN: shift-out-of-bounds in drivers/i3c/master/dw-i3c-master.c:1646:21 [Mon May 18 11:28:24 2026] shift exponent 18446744073709486145 is too large for 64-bit type 'long unsigned int' [Mon May 18 11:28:24...
    • 1780325230973.png
  • P
    proxuser77 reacted to BobhWasatch's post in the thread Problem with time within vms with Like Like.
    No worries, I don't need anybody to defend me. Plus, I didn't read the thread very carefully or I would have seen that the OP was using NTP but noted that his issue was the gap between VM startup and when NTP noticed the wrong time. The hook...
  • D
    Der Harry replied to the thread Problem with time within vms.
    In the bugzilla ticket, I mentioned that NTP is very clumsy. The hwclock approach is much better. But it's still not a 100% solution.
  • D
    Der Harry replied to the thread Problem with time within vms.
    ... i have no more words for you.
  • J
    Johannes S reacted to SteveITS's post in the thread PVE 8.4 — anyone just... not upgrading? with Like Like.
    Re repos, https://forum.proxmox.com/threads/new-archive-cdn-for-end-of-life-eol-releases.178957/
  • J
    Johannes S reacted to BobhWasatch's post in the thread Problem with time within vms with Like Like.
    No worries, I don't need anybody to defend me. Plus, I didn't read the thread very carefully or I would have seen that the OP was using NTP but noted that his issue was the gap between VM startup and when NTP noticed the wrong time. The hook...
  • J
    Johannes S reacted to proxuser77's post in the thread Problem with time within vms with Like Like.
    I'm not denying that there are situations where this can be critical. Although in such cases, you might simply avoid making any changes to the VM until you have a maintenance window, put the application into maintenance mode, take the snapshot...
  • J
    Johannes S reacted to proxuser77's post in the thread Problem with time within vms with Like Like.
    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...
  • B
    BobhWasatch replied to the thread Problem with time within vms.
    No worries, I don't need anybody to defend me. Plus, I didn't read the thread very carefully or I would have seen that the OP was using NTP but noted that his issue was the gap between VM startup and when NTP noticed the wrong time. The hook...
  • J
    Johannes S reacted to BobhWasatch's post in the thread Problem with time within vms with Like Like.
    Sorry if I accidentally stepped on your bad mood. Was just trying to solve the immediate problem.
  • J
    Johannes S reacted to BobhWasatch's post in the thread Problem with time within vms with Like Like.
    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...
  • P
    proxuser77 replied to the thread Problem with time within vms.
    I'm not denying that there are situations where this can be critical. Although in such cases, you might simply avoid making any changes to the VM until you have a maintenance window, put the application into maintenance mode, take the snapshot...
  • SteveITS
    SteveITS replied to the thread SSD Optimize not working inside Windows 2022 server.
    Yes. A detailed explanation is on the alldiscoveries.com site linked in that thread, which suggests 2M since it's the Hyper-V default, though that post you quoted suggests the 8M. YMMV I guess. 2M solved the issue for us.
  • 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
    Arkhen replied to the thread UPID and Node value don't match regex pattern when Verifying through GUI.
    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
Show older items
Top Bottom
Back