From nobody Thu Sep 21 00:02:16 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 4RrbDy4p5Fz4vM8H for ; Thu, 21 Sep 2023 00:02:26 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RrbDx4P24z4gw9 for ; Thu, 21 Sep 2023 00:02:25 +0000 (UTC) (envelope-from dmarquess@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="lQ1qjW/3"; spf=pass (mx1.freebsd.org: domain of dmarquess@gmail.com designates 2607:f8b0:4864:20::d30 as permitted sender) smtp.mailfrom=dmarquess@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-io1-xd30.google.com with SMTP id ca18e2360f4ac-79f7e7342e3so13412839f.1 for ; Wed, 20 Sep 2023 17:02:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695254544; x=1695859344; darn=freebsd.org; h=mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=HQRfBAvKF/5NuvglSTi7L+91RjAwukpKh5c40pfdu6g=; b=lQ1qjW/3zaoBeGOTgV/TBPSbCBoIlb90Pp6QYQE4KGLfbyz6xgAzYmXFnzp8QvCrOT IQdPCkm8w/2JJUYDz/Ecc4UvGs1uzRY0/GAVZPjUeROxCKPewlGwxAuQI7vKMbhTVz+W 5TCgvXPJsequmjU7WUYL1LSLnp5VcdFrS/jNBK/uPQ8Mps7oOTzfWIl/m3uUvnX05LhO NEivWp3xyyPzr/h6uTERweIP5t8iF1pGGdSFJQ1hP5wXwxhQ12dyX4nk+tBgnz2y4lWe LkM7YVsxYvsGuPVe6eccCMv4/NlwUWW6J0wdTrD9Zy7rd+QRm0O9DTjnOg2ZImwA4WiQ rtwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695254544; x=1695859344; h=mime-version:subject:references:in-reply-to:message-id:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HQRfBAvKF/5NuvglSTi7L+91RjAwukpKh5c40pfdu6g=; b=hUKVZmXNu07ZQyQkZj1tO+IEnGnm8ITw6OnnsEOa5cqlKYxOT8uxveykyUi8UDk7o5 5llUDBGwDFU/4w4LD3VklOOdG9B55sCcb1uyE6hGGrkQX5C/EOvc2N0htR02ELxQd0Kp kDJubfJy+b0/N0iktXibRCDKG1Crh/0o3Z/H+umH8nmAAAgz6+9w0hEv9EBVj8dzlw6u Pi42alrjUTL8NekfrupH14zY6hktjrmcXimxB7ZRJH/uh4k/bg4jhtRoaWG1V8ZUAUNd J1CK6fedlJwG5sGvrkUqZoovUPofcc5iRzZmPb0a1TJ5utVT1O29274K22KvR7v1pcSx /Yng== X-Gm-Message-State: AOJu0Yz991EjYXrOSjG58YABHWLYTEWQu3f9hgxOXAxIPWQjIcgeGEA3 fULGEPGaokJrVbNx+g6f76IkXkADYbQBvA== X-Google-Smtp-Source: AGHT+IFZBd7jrM7iLAo7Ksn1CH05xtpF+0NxZ3X982WIkxiY2ZNfAwlpO4jxHBxYh7w8rqG1jZKjCw== X-Received: by 2002:a6b:e306:0:b0:790:9f0c:3069 with SMTP id u6-20020a6be306000000b007909f0c3069mr4111127ioc.9.1695254544301; Wed, 20 Sep 2023 17:02:24 -0700 (PDT) Received: from [2001:470:bc52:2:408a:4105:70:0] ([2001:470:bc52:2:860:15c0:3694:e826]) by smtp.gmail.com with ESMTPSA id u15-20020a5d870f000000b0078754bed499sm84740iom.37.2023.09.20.17.02.23 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2023 17:02:23 -0700 (PDT) Date: Wed, 20 Sep 2023 19:02:16 -0500 From: Dustin Marquess To: FreeBSD virtualization Message-ID: <3c3ccffc-5a57-4472-8d16-5b5cdf5da862@Spark> In-Reply-To: References: Subject: bhyve issues in 15-CURRENT X-Readdle-Message-ID: 3c3ccffc-5a57-4472-8d16-5b5cdf5da862@Spark 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="650b880d_4350c0fb_397" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.998]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d30:from]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4RrbDx4P24z4gw9 --650b880d_4350c0fb_397 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline I just upgraded from a kernel+userland of 15-CURRENT from a release 20 days ago (git commit 565c887) to one today (git commit e39e6be). Afterwards, I've noticed two things that are probably really the same thing: - My Windows Server 2023 VM says that there's not enough resources for COM2 & COM4 - My OpenBSD 7.3 VM dies with: acpicmos0 at acpi0 "Bhyve_V_Gen_Counter_V1" at acpi0 not configured cpu0: using VERW MDS workaround pvbus0 at mainbus0: bhyve pci0 at mainbus0 bus 0 0:3:0: io address conflict 0xc000/0x80 0:5:0: io address conflict 0xc080/0x40 pchb0 at pci0 dev 0 function 0 vendor "AMD", unknown product 0x7432 rev 0x00 virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Storage" rev 0x00virtio0: can't map i/o space : Cannot attach (5) virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Network" rev 0x00 vio0 at virtio1: address 1e:17:37:23:2f:cb virtio1: msix per-VQ In this case, 0:3:0 is the virtio-blk device and 0:5:0 is the virtio-net device. If I boot it using a snapshot install74.img then it dies at: acpicmos0 at acpi0 "Bhyve_V_Gen_Counter_V1" at acpi0 not configured cpu0: using VERW MDS workaround pvbus0 at mainbus0: bhyve pci0 at mainbus0 bus 0 0:2:0: io address conflict 0xc080/0x80 0:3:0: io address conflict 0xc000/0x80 0:5:0: io address conflict 0xc100/0x40 pchb0 at pci0 dev 0 function 0 vendor "AMD", unknown product 0x7432 rev 0x00 virtio0 at pci0 dev 2 function 0 "Qumranet Virtio Storage" rev 0x00virtio0: can't map i/o space : Cannot attach (5) virtio1 at pci0 dev 3 function 0 "Qumranet Virtio Storage" rev 0x00 vioblk0 at virtio1 scsibus0 at vioblk0: 1 targets sd0 at scsibus0 targ 0 lun 0: sd0: 8192MB, 512 bytes/sector, 16777216 sectors virtio1: msix per-VQ virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Network" rev 0x00 vio0 at virtio2: address ff:ff:ff:ff:ff:ff panic: vq_size not power of two: 65535 0:3:0 are virtio-blk and 0:5:0 is virtio-net, as above. 0:2:0 is the extra virtio-blk for the .img file. Any ideas on what change caused this? Thanks! -Dustin --650b880d_4350c0fb_397 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I just upgraded from a kernel+userland of 15-CURREN= T from a release 20 days ago (git commit 565c887) to one today (git commi= t e39e6be). Afterwards, I've noticed two things that are probably really = the same thing:

- My Windows Server 2023 VM says that there's not enough resources for CO= M2 & COM4
- My OpenBSD 7.3 VM dies with:

acpicmos0 at acpi0
=22Bhyve=5FV=5FGen=5FCounter=5FV1=22 at acpi0 not configured
cpu0: using VERW MDS workaround
pvbus0 at mainbus0: bhyve
pci0 at mainbus0 bus 0
0:3:0: io address conflict 0xc000/0x80
0:5:0: io address conflict 0xc080/0x40
pchb0 at pci0 dev 0 function 0 vendor =22AMD=22, unknown product 0x7432 r= ev 0x00
virtio0 at pci0 dev 3 function 0 =22Qumranet Virtio Storage=22 rev 0x00vi= rtio0: can't map i/o space
: Cannot attach (5)
virtio1 at pci0 dev 5 function 0 =22Qumranet Virtio Network=22 rev 0x00 vio0 at virtio1: address 1e:17:37:23:2f:cb
virtio1: msix per-VQ

In this case, 0:3:0 is the virtio-blk device and 0:5:0 is the virtio-net = device.

If I boot it using a snapshot install74.img then it dies at:

acpicmos0 at acpi0
=22Bhyve=5FV=5FGen=5FCounter=5FV1=22 at acpi0 not configured
cpu0: using VERW MDS workaround
pvbus0 at mainbus0: bhyve
pci0 at mainbus0 bus 0
0:2:0: io address conflict 0xc080/0x80
0:3:0: io address conflict 0xc000/0x80
0:5:0: io address conflict 0xc100/0x40
pchb0 at pci0 dev 0 function 0 vendor =22AMD=22, unknown product 0x7432 r= ev 0x00
virtio0 at pci0 dev 2 function 0 =22Qumranet Virtio Storage=22 rev 0x00vi= rtio0: can't map i/o space
: Cannot attach (5)
virtio1 at pci0 dev 3 function 0 =22Qumranet Virtio Storage=22 rev 0x00 vioblk0 at virtio1
scsibus0 at vioblk0: 1 targets
sd0 at scsibus0 targ 0 lun 0: <VirtIO, Block Device, >
sd0: 8192MB, 512 bytes/sector, 16777216 sectors
virtio1: msix per-VQ
virtio2 at pci0 dev 5 function 0 =22Qumranet Virtio Network=22 rev 0x00 vio0 at virtio2: address ff:ff:ff:ff:ff:ff
panic: vq=5Fsize not power of two: 65535

0:3:0 are virtio-blk and 0:5:0 is virtio-net, as above. 0:2:0 is the extr= a virtio-blk for the .img file.

Any ideas on what change caused this=3F

Thanks=21

-Dustin
--650b880d_4350c0fb_397--