Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    VMware patch for clock stopping issue with FreeBSD 8.x and 9.x clients

    Scheduled Pinned Locked Moved Virtualization
    5 Posts 3 Posters 11.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dhatz
      last edited by

      A VMware patch was just released to solve an issue reported among others at http://forums.freebsd.org/showthread.php?t=31929

      http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032586

      PR887134: Timer stops in FreeBSD 8.x and 9.x as virtual hardware HPET main counter register fails to update due to comparison failure between signed and unsigned integer values.

      I thought others here will find it helpful.

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        Thanks for the heads up, I posted it to the mailing list too since there have been a few threads on it there recently.

        1 Reply Last reply Reply Quote 0
        • M
          mattlach
          last edited by

          Looks like this patch is only for ESXi 5.0.

          Is the new ESXi 5.1 release not affected by this bug?

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            I presume all those issues were fixed in 5.1 and back ported, since the KB doesn't list it as an affected version.

            1 Reply Last reply Reply Quote 0
            • M
              mattlach
              last edited by

              I never noticed the clock stopping, buit it was probably just cause I wasn't observant enough.

              I wonder if this was related at all to my puzzling pfSense stability problems under ESXi 5.0.0 where the DHCP function would just stop working at random intervals.  Clients already assigned IP's would continue to work just fine nd data would be routed to them,  but new clients would not get IP's and not function at all.

              It was a puzzling issue I never quite figured out.  In the process of reinstalling with 5.1 now, time will tell if the issue disappears.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.