libvirt/tests/bhyveargv2xmldata/bhyveargv2xml-virtio-net4.xml

<domain type='bhyve'>
  <name>bhyve</name>
  <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid>
  <memory unit='KiB'>219136</memory>
  <currentMemory unit='KiB'>219136</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type>hvm</type>
  </os>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>destroy</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <interface type='bridge'>
      <mac address='00:00:00:00:00:00'/>
      <source bridge='virbr0'/>
      <target dev='tap1'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </interface>
  </devices>
</domain>
bhyve: add tests for bhyveParseCommandLineString 2016-06-24 18:41:20 +00:00			`<domain type='bhyve'>`
			`<name>bhyve</name>`
			`<uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid>`
			`<memory unit='KiB'>219136</memory>`
			`<currentMemory unit='KiB'>219136</currentMemory>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
			`<type>hvm</type>`
			`</os>`
			`<clock offset='localtime'/>`
			`<on_poweroff>destroy</on_poweroff>`
			`<on_reboot>destroy</on_reboot>`
			`<on_crash>destroy</on_crash>`
			`<devices>`
bhyve: fix interface type handling for argv2xml When generating a domain XML from native command (i.e. via the connectDomainXMLFromNative call), we should use interface type 'bridge' rather than 'ethernet' because we only support bridges at this point. As we don't have bridge name explicitly specified on the command line, just use 'virbr0' as a default. 2017-01-06 21:06:23 +04:00			`<interface type='bridge'>`
bhyve: add tests for bhyveParseCommandLineString 2016-06-24 18:41:20 +00:00			`<mac address='00:00:00:00:00:00'/>`
bhyve: fix interface type handling for argv2xml When generating a domain XML from native command (i.e. via the connectDomainXMLFromNative call), we should use interface type 'bridge' rather than 'ethernet' because we only support bridges at this point. As we don't have bridge name explicitly specified on the command line, just use 'virbr0' as a default. 2017-01-06 21:06:23 +04:00			`<source bridge='virbr0'/>`
bhyve: add tests for bhyveParseCommandLineString 2016-06-24 18:41:20 +00:00			`<target dev='tap1'/>`
bhyve: add e1000 nic support Recently e1000 NIC support was added to bhyve; implement that in the bhyve driver: - Add capability check by analyzing output of the 'bhyve -s 0,e1000' command - Modify bhyveBuildNetArgStr() to support e1000 and also pass virConnectPtr so it could call bhyveDriverGetCaps() to check if this NIC is supported - Modify command parsing code to add support for e1000 and adjust tests - Add net-e1000 test 2016-08-27 15:30:34 +03:00			`<model type='virtio'/>`
bhyve: add tests for bhyveParseCommandLineString 2016-06-24 18:41:20 +00:00			`<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>`
			`</interface>`
			`</devices>`
			`</domain>`