Date: Thu, 15 Jun 2023 18:22:19 -0400 From: Sean McBride <sean@rogue-research.com> To: jason@tubnor.net Cc: freebsd-virtualization@FreeBSD.org Subject: Re: Ubuntu in bhyve Message-ID: <FC7170CD-82DA-4AE1-9D35-56982D071B36@rogue-research.com> In-Reply-To: <002401d99fd2$4c6d2470$e5476d50$@tubnor.net> References: <1AC64CF0-2CCF-4B72-9E44-75104E813CF6@rogue-research.com> <002401d99fd2$4c6d2470$e5476d50$@tubnor.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Jason,
Thanks for your reply.
We run NTP on our router (a pfsense) and both the host (TrueNAS) and
guests are using it, correctly I believe.
On TrueNAS:
# ntpdate -q time.rogue-research.com
server 10.xx.xx.1, stratum 2, offset -0.000149, delay 0.02580
15 Jun 18:19:11 ntpdate[1239]: adjust time server 10.xx.xx.1 offset
-0.000149 sec
On Ubuntu:
$ timedatectl
Local time: Thu 2023-06-15 18:17:02 EDT
Universal time: Thu 2023-06-15 22:17:02 UTC
RTC time: Thu 2023-06-15 22:17:02
Time zone: America/Toronto (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
I believe both indicate that it's working...
Sean
On 15 Jun 2023, at 17:42, jason@tubnor.net wrote:
> Make sure your guests (and host) are syncing to a reliable time
> source. I
> have heard time to time of some having this issue, but we haven't seen
> it
> though we do use OpenNTPD across our BSD/*nix guests (windows has its
> own
> time sync service).
>
>
>
> Cheers,
>
>
>
> Jason.
>
>
>
> From: owner-freebsd-virtualization@freebsd.org
> <owner-freebsd-virtualization@freebsd.org> On Behalf Of Sean McBride
> Sent: Friday, June 16, 2023 5:20 AM
> To: freebsd-virtualization@FreeBSD.org
> Subject: Ubuntu in bhyve
>
>
>
> Hi all,
>
> I am running bhyve (via TrueNAS Core 13) and have some Ubuntu 20.04
> and
> 22.04 guests.
>
> One of them rather regularly seizes up hard, where I cannot ssh to it,
> then
> after a few minutes works again. This happens repeatedly and on and
> off. In
> the Ubuntu logs I see messages like:
>
> clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc'
> as
> unstable because the skew is too large:
> clocksource: 'hpet' wd_nsec: 536417782 wd_now:
> 638cb3ff wd_last: 63036152 mask: ffffffff
> clocksource: 'tsc' cs_nsec: 536821277 cs_now:
> 225a9f9e1250b cs_last: 225a9b3891749 mask: ffffffffffffffff
> clocksource: 'tsc' is current clocksource.
> tsc: Marking TSC unstable due to clocksource watchdog
> TSC found unstable after boot, most likely due to broken BIOS. Use
> 'tsc=unstable'.
> sched_clock: Marking unstable (12899572906362,
> 9192186981)<-(12908811630850,
> -46250627)
> clocksource: Checking clocksource tsc synchronization from CPU 2 to
> CPUs
> 0-1,3.
> clocksource: Switched to clocksource hpet
> loop8: detected capacity change from 0 to 114000
>
> Although I don't fully grok these messages, they sound like something
> that
> could be bhyve's fault. Anyone know if that may indeed be the case?
>
> There is a thread about this on the TrueNAS forum too, but with no
> answers
> really:
>
>
> <https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.1083
> 76/>
> https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.10837
> 6/
>
> Thanks,
>
> Sean
[-- Attachment #2 --]
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">Jason,</p>
<p dir="auto">Thanks for your reply.</p>
<p dir="auto">We run NTP on our router (a pfsense) and both the host (TrueNAS) and guests are using it, correctly I believe.</p>
<p dir="auto">On TrueNAS:</p>
<h2>ntpdate -q time.rogue-research.com</h2>
<p dir="auto">server 10.xx.xx.1, stratum 2, offset -0.000149, delay 0.02580<br>
15 Jun 18:19:11 ntpdate[1239]: adjust time server 10.xx.xx.1 offset -0.000149 sec</p>
<p dir="auto">On Ubuntu:</p>
<p dir="auto">$ timedatectl<br>
Local time: Thu 2023-06-15 18:17:02 EDT<br>
Universal time: Thu 2023-06-15 22:17:02 UTC<br>
RTC time: Thu 2023-06-15 22:17:02<br>
Time zone: America/Toronto (EDT, -0400)<br>
System clock synchronized: yes<br>
NTP service: active<br>
RTC in local TZ: no</p>
<p dir="auto">I believe both indicate that it's working...</p>
<p dir="auto">Sean</p>
<p dir="auto">On 15 Jun 2023, at 17:42, <a href="mailto:jason@tubnor.net" style="color: #3983C4;">jason@tubnor.net</a> wrote:</p>
</div><blockquote class="embedded" style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><div id="385C24F8-818F-4661-910E-FEEBF47434BA">
<div lang="EN-AU" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1" style="page: WordSection1;">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Make sure your guests (and host) are syncing to a reliable time source. I have heard time to time of some having this issue, but we haven’t seen it though we do use OpenNTPD across our BSD/*nix guests (windows has its own time sync service).</span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Cheers,</span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Jason.</span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b> <span lang="EN-US">owner-freebsd-virtualization@freebsd.org <owner-freebsd-virtualization@freebsd.org> <b>On Behalf Of</b> Sean McBride<br>
<b>Sent:</b> Friday, June 16, 2023 5:20 AM<br>
<b>To:</b> freebsd-virtualization@FreeBSD.org<br>
<b>Subject:</b> Ubuntu in bhyve</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p><span style="font-family:"Arial",sans-serif">Hi all,</span></p>
<p><span style="font-family:"Arial",sans-serif">I am running bhyve (via TrueNAS Core 13) and have some Ubuntu 20.04 and 22.04 guests.</span></p>
<p><span style="font-family:"Arial",sans-serif">One of them rather regularly seizes up hard, where I cannot ssh to it, then after a few minutes works again. This happens repeatedly and on and off. In the Ubuntu logs I see messages like:</span></p>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7; border-radius: 5px 5px 5px 5px; overflow-x: auto; max-width: 90vw;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large:</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">clocksource: 'hpet' wd_nsec: 536417782 wd_now: 638cb3ff wd_last: 63036152 mask: ffffffff</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">clocksource: 'tsc' cs_nsec: 536821277 cs_now: 225a9f9e1250b cs_last: 225a9b3891749 mask: ffffffffffffffff</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">clocksource: 'tsc' is current clocksource.</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">tsc: Marking TSC unstable due to clocksource watchdog</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">sched_clock: Marking unstable (12899572906362, 9192186981)<-(12908811630850, -46250627)</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">clocksource: Checking clocksource tsc synchronization from CPU 2 to CPUs 0-1,3.</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">clocksource: Switched to clocksource hpet</span></code></pre>
<pre style="mso-style-priority: 99; mso-style-link: 'HTML Preformatted Char'; margin: 0cm; font-size: 10.0pt; font-family: 'Courier New'; mso-margin-top-alt: 0cm; margin-right: 11.25pt; margin-bottom: 0cm; margin-left: 11.25pt; margin-bottom: .0001pt; background: #F7F7F7;"><code style="mso-style-priority: 99; font-family: 'Courier New';"><span style="color:black;background:#F7F7F7">loop8: detected capacity change from 0 to 114000</span></code></pre>
<p><span style="font-family:"Arial",sans-serif">Although I don't fully grok these messages, they sound like something that could be bhyve's fault. Anyone know if that may indeed be the case?</span></p>
<p><span style="font-family:"Arial",sans-serif">There is a thread about this on the TrueNAS forum too, but with no answers really:</span></p>
<p><span style="font-family:"Arial",sans-serif"><a href="https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.108376/"><span style="color:#3983C4">https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.108376/</span></a></span></p>;
<p><span style="font-family:"Arial",sans-serif">Thanks,</span></p>
<p><span style="font-family:"Arial",sans-serif">Sean</span></p>
</div>
</div>
</div>
</div>
</div></div></blockquote>
<div class="markdown" style="white-space: normal;">
</div>
</div>
</body>
</html>
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FC7170CD-82DA-4AE1-9D35-56982D071B36>