Date: Thu, 15 Jun 2023 15:19:55 -0400 From: Sean McBride <sean@rogue-research.com> To: freebsd-virtualization@FreeBSD.org Subject: Ubuntu in bhyve Message-ID: <1AC64CF0-2CCF-4B72-9E44-75104E813CF6@rogue-research.com>
index | next in thread | raw e-mail
[-- Attachment #1 --] 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.108376/ 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">Hi all,</p> <p dir="auto">I am running bhyve (via TrueNAS Core 13) and have some Ubuntu 20.04 and 22.04 guests.</p> <p dir="auto">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:</p> <pre style="margin-left: 15px; margin-right: 15px; padding: 5px; background-color: #F7F7F7; border-radius: 5px 5px 5px 5px; overflow-x: auto; max-width: 90vw;"><code style="margin: 0 0; border-radius: 3px; background-color: #F7F7F7; padding: 0px;">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 </code></pre> <p dir="auto">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?</p> <p dir="auto">There is a thread about this on the TrueNAS forum too, but with no answers really:</p> <p dir="auto"><a href="https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.108376/" style="color: #3983C4;">https://www.truenas.com/community/threads/debian-vms-under-bhyve-clock.108376/</a></p>; <p dir="auto">Thanks,</p> <p dir="auto">Sean</p> </div> </div> </body> </html>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1AC64CF0-2CCF-4B72-9E44-75104E813CF6>