From nobody Thu Jun 15 19:19:55 2023 X-Original-To: freebsd-virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QhsYr1px3z4fKwD for ; Thu, 15 Jun 2023 19:20:00 +0000 (UTC) (envelope-from sean@rogue-research.com) Received: from mail.rogue-research.com (mail.rogue-research.com [207.115.102.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.rogue-research.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QhsYq4QM3z3lBs for ; Thu, 15 Jun 2023 19:19:59 +0000 (UTC) (envelope-from sean@rogue-research.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of sean@rogue-research.com designates 207.115.102.151 as permitted sender) smtp.mailfrom=sean@rogue-research.com; dmarc=pass (policy=none) header.from=rogue-research.com Received: from localhost (localhost [127.0.0.1]) by mail.rogue-research.com (Postfix) with ESMTP id C772CE47BD14 for ; Thu, 15 Jun 2023 15:19:58 -0400 (EDT) X-Virus-Scanned: amavisd-new at rogue-research.com Received: from mail.rogue-research.com ([127.0.0.1]) by localhost (kingu.rogue-research.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rIKuw-Whlyef for ; Thu, 15 Jun 2023 15:19:57 -0400 (EDT) Received: from [172.16.6.1] (dullahan.rogue-research.com [10.29.19.120]) by mail.rogue-research.com (Postfix) with ESMTPSA id B4B9EE47BCFD for ; Thu, 15 Jun 2023 15:19:57 -0400 (EDT) From: Sean McBride To: freebsd-virtualization@FreeBSD.org Subject: Ubuntu in bhyve Date: Thu, 15 Jun 2023 15:19:55 -0400 X-Mailer: MailMate (1.14r5937) Message-ID: <1AC64CF0-2CCF-4B72-9E44-75104E813CF6@rogue-research.com> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_14BCE42E-BB60-4D4C-BC88-5DE111B192F3_=" X-Spamd-Result: default: False [-3.69 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.98)[-0.979]; NEURAL_HAM_SHORT(-0.91)[-0.914]; DMARC_POLICY_ALLOW(-0.50)[rogue-research.com,none]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:11478, ipnet:207.115.96.0/20, country:CA]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MLMMJ_DEST(0.00)[freebsd-virtualization@FreeBSD.org]; RCVD_COUNT_THREE(0.00)[4]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[sean]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QhsYq4QM3z3lBs X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --=_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

Hi all,

I am running bhyve (via TrueNAS Core 13) and have some Ub= untu 20.04 and 22.04 guests.

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:

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

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?

There is a thread about this on the TrueNAS forum too, bu= t with no answers really:

https://www.t= ruenas.com/community/threads/debian-vms-under-bhyve-clock.108376/

=

Thanks,

Sean

--=_MailMate_14BCE42E-BB60-4D4C-BC88-5DE111B192F3_=--