VirtIO Ethernet driver in DragonFlyBSD under FreeBSD bhyve

Jan Beich jbeich at vfemail.net
Mon Jun 27 18:49:38 UTC 2016


Peter Grehan <grehan-h+KGxgPPiopAfugRpC6u6w at 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 at 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 at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 602 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-virtualization/attachments/20160627/f64afdf0/attachment.sig>


More information about the freebsd-virtualization mailing list