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>
next in thread | raw e-mail | index | archive | help
--=_MailMate_14BCE42E-BB60-4D4C-BC88-5DE111B192F3_= Content-Type: text/plain; format=flowed; markup=markdown 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 --=_MailMate_14BCE42E-BB60-4D4C-BC88-5DE111B192F3_= Content-Type: text/html Content-Transfer-Encoding: quoted-printable <!DOCTYPE html> <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"= > </head> <body><div style=3D"font-family: sans-serif;"><div class=3D"markdown" sty= le=3D"white-space: normal;"> <p dir=3D"auto">Hi all,</p> <p dir=3D"auto">I am running bhyve (via TrueNAS Core 13) and have some Ub= untu 20.04 and 22.04 guests.</p> <p dir=3D"auto">One of them rather regularly seizes up hard, where I cann= ot ssh to it, then after a few minutes works again. This happens repeated= ly and on and off. In the Ubuntu logs I see messages like:</p> <pre style=3D"margin-left: 15px; margin-right: 15px; padding: 5px; backgr= ound-color: #F7F7F7; border-radius: 5px 5px 5px 5px; overflow-x: auto; ma= x-width: 90vw;"><code style=3D"margin: 0 0; border-radius: 3px; backgroun= d-color: #F7F7F7; padding: 0px;">clocksource: timekeeping watchdog on CPU= 2: Marking clocksource 'tsc' as unstable because the skew is too large: clocksource: 'hpet' wd_nsec: 536417782 wd_now: 638c= b3ff wd_last: 63036152 mask: ffffffff clocksource: 'tsc' cs_nsec: 536821277 cs_now: 225a9= f9e1250b 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=3D= unstable'. sched_clock: Marking unstable (12899572906362, 9192186981)<-(129088116= 30850, -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=3D"auto">Although I don't fully grok these messages, they sound li= ke something that could be bhyve's fault. Anyone know if that may indeed= be the case?</p> <p dir=3D"auto">There is a thread about this on the TrueNAS forum too, bu= t with no answers really:</p> <p dir=3D"auto"><a href=3D"https://www.truenas.com/community/threads/debi= an-vms-under-bhyve-clock.108376/" style=3D"color: #3983C4;">https://www.t= ruenas.com/community/threads/debian-vms-under-bhyve-clock.108376/</a></p>= <p dir=3D"auto">Thanks,</p> <p dir=3D"auto">Sean</p> </div> </div> </body> </html> --=_MailMate_14BCE42E-BB60-4D4C-BC88-5DE111B192F3_=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1AC64CF0-2CCF-4B72-9E44-75104E813CF6>