GitLab

We tried to make tabs work, but its just not worth the headache.

rather than xrbuf attachment

2. update xemem-based ringbuffer support to use xrbufs

This uses the same NIC_BRIDGE backend network device as well as the raw
packet interface.

The iface-packet host-side interface now differentiates between direct
bridging of the specified device using regular sock_sendmsg/recvmsg via
RAW packets (the existing mode) and new support for tun_sendmsg/recvmsg
through the TUN/TAP driver.

Only 2 changes are needed by userspace to use the TUN/TAP capability:
  i. add the following tag to the 'NIC_BRIDGE' XML specification:
     <tap>true</tap>
 ii. issue V3_VM_TUNTAP_CONNECT ioctl on the VMs control device, passing
     in a file descriptor previously issueed to open the TAP interface

- Abstracted ringbuffer used by iface-pisces-console and iface-pisces-stream
  into util-ringbuf.{c,h}

virtualization.

Needed to boot newer AMD hardware.

virtio driver