Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Sep 2023 08:29:17 +0200
From:      Corvin =?ISO-8859-1?Q?K=F6hne?= <corvink@FreeBSD.org>
To:        Dustin Marquess <dmarquess@gmail.com>, FreeBSD virtualization <freebsd-virtualization@freebsd.org>
Subject:   Re: bhyve issues in 15-CURRENT
Message-ID:  <3cf178349ce0483b031bc5705be33a177dabf1ba.camel@FreeBSD.org>
In-Reply-To: <3c3ccffc-5a57-4472-8d16-5b5cdf5da862@Spark>
References:  <b4fd0c74-c077-475b-82e7-0477a3c5067a@Spark> <3c3ccffc-5a57-4472-8d16-5b5cdf5da862@Spark>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-IReORZkXQ1f0orGFsQrY
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, 2023-09-20 at 19:02 -0500, Dustin Marquess wrote:
>=20
>=20
>=20
> 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:
>=20
> - My Windows Server 2023 VM says that there's not enough resources
> for COM2 & COM4
> - My OpenBSD 7.3 VM dies with:
>=20
> 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
>=20
> In this case, 0:3:0 is the virtio-blk device and 0:5:0 is the virtio-
> net device.
>=20
> If I boot it using a snapshot install74.img then it dies at:
>=20
> 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: <VirtIO, Block Device, >
> 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
>=20
> 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.
>=20
> Any ideas on what change caused this?
>=20
> Thanks!
>=20
> -Dustin

Please make sure to call bhyve with the -A option.


--=20
Kind regards,
Corvin

--=-IReORZkXQ1f0orGFsQrY
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEgvRSla3m2t/H2U9G2FTaVjFeAmoFAmUL4r0ACgkQ2FTaVjFe
AmrIYA/+PVBAT26vpiiKFgqw52H1SN56zKdw6AY5qR05b2CZjFDiPuJJHsEprltl
AUDDbL7vsefr7eURMBd+NPveS1uGBfTK3a7dWu06CssBJEi2KZ9FkuIrEFVPsKPc
th/t7llFjY56k/mFwlV8k9iJqXnoGDnEX6RwH+7ZOQL99VvTFj672V5dSvi04cYI
OAuYn90t18I2KPxjQN3Ypv/CrTQfJmQt5L4lG8rXC4Vqbgza9t6RUxu/j9Dsnkyr
eeOOfcLbxVJCRoHfls8WfGZsjVkLji8p5kZslePzXfWa0pTeCj0WVktz9TLTqInz
2D8I/0wGA3jSj8Wrkyw+dOWhEpBFqfTPObAH14n3bBmB7LbNRgc/3HSztlkoRqUp
UML1iwiLLj5mtnah6J+tIH6t4zglrjMGo+H9+Xj6ISQ3Bb8wLkas2AjVB9IHYGK2
042w745GvoDEdRBfgi+PfS4/g6GotVAn1Uwd+tMfCrEVwxByPG1oegmAnv+0ShNf
NifhcM2tfrb2Pe9Ym7TmUeAzAh+slDLhvK21ZQTM2LX+hOc5eUFkvBJER2hR7quG
owmlq6hObqc19b3QQsAENvU12ijNkUAKAtnKLv7R/bCySTC/FnimClha10JkJdd+
jQTR59s+9Kx5C5xKnb8oyhI01fZ0P5Vk7+1czXSUT2lrVQQAkWo=
=LGMe
-----END PGP SIGNATURE-----

--=-IReORZkXQ1f0orGFsQrY--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3cf178349ce0483b031bc5705be33a177dabf1ba.camel>