From nobody Sat Aug 27 14:29:46 2022 X-Original-To: freebsd-hackers@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 4MFJxz4CXgz4ZWyg for ; Sat, 27 Aug 2022 14:29:59 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4MFJxy55wHz3V9Z for ; Sat, 27 Aug 2022 14:29:58 +0000 (UTC) (envelope-from jamie@catflap.org) X-Catflap-Envelope-From: X-Catflap-Envelope-To: freebsd-hackers@FreeBSD.org Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 27RETmf3063823; Sat, 27 Aug 2022 15:29:48 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 27RETkGg063822; Sat, 27 Aug 2022 15:29:47 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202208271429.27RETkGg063822@donotpassgo.dyslexicfish.net> Date: Sat, 27 Aug 2022 15:29:46 +0100 Organization: Dyslexic Fish To: mason@blisses.org, freebsd-hackers@FreeBSD.org Cc: eugen@grosbein.net Subject: Re: Help debugging Vultr boot delay...? References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Sat, 27 Aug 2022 15:29:48 +0100 (BST) X-Rspamd-Queue-Id: 4MFJxy55wHz3V9Z X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=catflap.org; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:300:2185:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org X-Spamd-Result: default: False [-2.70 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@FreeBSD.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:20473, ipnet:2001:19f0::/38, country:US]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[jamie]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; HAS_ORG_HEADER(0.00)[]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Mason Loring Bliss wrote: > The second issue is still there and while I've brought it to their > attention, it'd probably be useful if they had some expert help. What I'm > observing with new VMs, both their images and via FreeBSD's own install > media, is a pause of one and three quarters minutes (around 105 seconds) > between: > > ugen0.2: at usbus0 > > and the next line, which appears to be: > > hdacc0: at cad 0 on hdac0 > > FreeBSD believes it's on Hyper-V 10.0.14393 [SP0] but the same VM booted > into GNU/Linux probes KVM, so I've got to ask about that. It appears to be their new KVM software. I have a number of vultr VMs (all running FreeBSD, obviously!) and there is no problem. I created a new 13.1 and a new 12.3 and saw the problem you describe. I then snapshotted one of my live 13.0 instances, and restored that to a new VM, and the problems you describe then appeared. Remember, identical disk contents, different results. Doing a 'kenv' on both boxes, the only relevant difference is smbios.system.version / smbios.chassis.version as such: < smbios.chassis.version="pc-i440fx-5.2" > smbios.chassis.version="pc-i440fx-7.0" < smbios.system.version="pc-i440fx-5.2" > smbios.system.version="pc-i440fx-7.0" The new instances are clearly being installed with a newer QEMU/KVM host. Comparing dmesg.boot is more interesting. As you say, the hypervisor is now grocked as Microsoft Hv These are the relevant differences. Again, exactly the same disk contents (running 13.0 in this case): > Hyper-V Version: 10.0.14393 [SP0] > Features=0xa7e > PM Features=0x0 [C0] > Features3=0x108 > Timecounter "Hyper-V" frequency 10000000 Hz quality 2000 > CPU: Intel Core Processor (Skylake, IBRS) (3408.00-MHz K8-class CPU) < Hypervisor: Origin = "KVMKVMKVM" --- > Hypervisor: Origin = "Microsoft Hv" > Timecounter "Hyper-V-TSC" frequency 10000000 Hz quality 3000 > vmbus0: on pcib0 > hdac0: mem 0xfebf0000-0xfebf3fff irq 11 at device 4.0 on pci0 > hdacc0: at cad 0 on hdac0 > hdaa0: at nid 1 on hdacc0 > pcm0: at nid 3 and 5 on hdaa0 Why is the host even announcing an audio device to the guests?! And is it more than coincidence that the delay comes before hdacc0 is groked? Anyway, if the fault is with FreeBSD, it's not a recent fault, it's just that changes in their host software are revealing them. Hope this helps a bit. Cheers, Jamie