Date: Mon, 27 Jun 2016 08:31:19 +0200 From: Jan Beich <jbeich@vfemail.net> To: Peter Grehan <public-grehan-h+KGxgPPiopAfugRpC6u6w@plane.gmane.org> Cc: Oleg Ginzburg <public-olevole-js7gNKDI/DUvJsYlp49lxw@plane.gmane.org>, public-freebsd-virtualization-h+KGxgPPiopAfugRpC6u6w@plane.gmane.org Subject: Re: VirtIO Ethernet driver in DragonFlyBSD under FreeBSD bhyve Message-ID: <60sv-b0so-wny@vfemail.net> References: <9893747.yFCcEWVR7f@gizmo.my.domain> <56ABFE12.4060805@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Type: text/plain Peter Grehan <grehan-h+KGxgPPiopAfugRpC6u6w@public.gmane.org> writes: > Hi, > >> I do not know whose it is a problem - DragonFlyBSD vtnet(4) driver or FreeBSD >> bhyve(4), so I decided to send on both maillist. >> >> I've try to boot DragonFlyBSD 4.4 in bhyve. All goes well, however, there is >> no network interface. During boot i see: > .. >> Boot processing : https://youtu.be/iV1eZxEvj0c >> >> bhyve executed with follow settings: >> >> /usr/sbin/bhyve -c 1 -m 4294967296 -A -H -P -s 0:0,hostbridge -s 2:0,virtio- >> rnd -s 3:0,virtio-net,tap0 ... >> >> What can be done to correct this error ? > > Firstly, very happy to see D'Fly booting under bhyve+UEFI/CSM :) > > I'll do some debug and see if this can be fixed. Any news since then? virtio-net and virtio-blk work fine if using Qemu + OVMF 20160418 (a8c39ba) on the same DragonFly disk image where Bhyve + BHYVE_UEFI_20160526.fd fails. -- # virtio-blk story: virtio_pci0: <VirtIO PCI Block adapter> port 0x2000-0x203f mem 0xc0002000-0xc0003fff irq 6 at device 4.0 on pci0 vtblk0: <VirtIO Block Adapter> on virtio_pci0 virtio_pci0: host features: 0x10000644 <RingIndirect,Topology,WriteCache,BlockSize,MaxNumSegs> virtio_pci0: negotiated features: 0x10000244 <RingIndirect,WriteCache,BlockSize,MaxNumSegs> virtio_pci0: cannot allocate interrupts vtblk0: cannot allocate virtqueue device_probe_and_attach: vtblk0 attach returned 6 virtio_pci0@pci0:0:4:0: class=0x010000 card=0x00021af4 chip=0x10011af4 rev=0x00 hdr=0x00 vendor = 'Red Hat, Inc' device = 'Virtio block device' class = mass storage subclass = SCSI bar [10] = type I/O Port, range 32, base 0x2000, size 64, enabled bar [14] = type Memory, range 32, base 0xc0002000, size 8192, enabled cap 11[40] = MSI-X supports 2 messages in map 0x14 cap 05[4c] = MSI supports 1 message, 64 bit vs. virtio_pci1: <VirtIO PCI Block adapter> port 0xc000-0xc03f mem 0xc1000000-0xc1000fff irq 11 at device 4.0 on pci0 vtblk0: <VirtIO Block Adapter> on virtio_pci1 virtio_pci1: host features: 0x71000ed4 <EventIdx,RingIndirect,NotifyOnEmpty,ConfigWCE,Topology,WriteCache,SCSICmds,BlockSize,DiskGeometry,MaxNumSegs> virtio_pci1: negotiated features: 0x10000a54 <RingIndirect,ConfigWCE,WriteCache,BlockSize,DiskGeometry,MaxNumSegs> virtio_pci1@pci0:0:4:0: class=0x010000 card=0x00021af4 chip=0x10011af4 rev=0x00 hdr=0x00 vendor = 'Red Hat, Inc' device = 'Virtio block device' class = mass storage subclass = SCSI bar [10] = type I/O Port, range 32, base 0xc000, size 64, enabled bar [14] = type Memory, range 32, base 0xc1000000, size 4096, enabled cap 11[40] = MSI-X supports 2 messages in map 0x14 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJXcMg3XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREQjQ0MzY3NEM3RDIzNTc4NkUxNDkyQ0VF NEM3Nzg4MzQ3OURCRERCAAoJEOTHeINHnb3bekUIANReoDfpRUCOBSIXD3Jot4Sh ig2Kdm/1cB4fPhAAd1KOL47FFyvJtU9bB8sbMaC9CGnv2jK7CjJHTIdrsv1Cl1dJ biRoRAdhb7uAjJNpXkvbqUJWOFYOeV9QXQ6nQC4k7dJXDQy3rr2q4s+TR1xKCIIb 1D7zfAW5nyhsamOdXoc3yBn+QuEV6qFfz0SIf72uI29IKtRRonnAqS6A7DcApKbw sxn8QsmgSZYkUL9q4uJnXCdcg9RD9VwG+aNxH7hQtROgIB8HY6j7OAWxG7UFnsi6 qilOtP1TBNDfWy7plL1viBhNh0njb29LEmt1dXmPe6J4cahpKHYp15odT6DGh8g= =+M6M -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60sv-b0so-wny>