<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 04/26/2013 02:41 PM, Slater, Joseph wrote: </div> <blockquote cite="mid:007BD92917A2324FA403BCF9A464CF8436F96748@ALA-MBB.corp.ad.wrs.com" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> <div class="WordSection1"> Hi,<o:p></o:p> <o:p> </o:p> If I have these fragments in a domain definition, the guest will start with "eth0"<o:p></o:p> assigned by dhcp to an address on my lan. Things seem to work according to the documentation<o:p></o:p> I can find.<o:p></o:p> <o:p> </o:p> <network><o:p></o:p> <name>direct-macvtap</name><o:p></o:p> <forward mode='bridge'><o:p></o:p> <interface dev='eth0' /><o:p></o:p> </forward><o:p></o:p> </network><o:p></o:p> <devices><o:p></o:p> <interface type='direct'><o:p></o:p> <mac address='00:15:17:A6:BC:C9' /><o:p></o:p> <source dev='eth0' mode='bridge' /> <o:p></o:p> <model type='virtio' /><o:p></o:p> </interface><o:p></o:p> </devices><o:p></o:p> <o:p> </o:p> I don't understand the <network> part here. It doesn't seem to be documented. I inherited these pieces<o:p></o:p> so I do not know why they are as they are. </div> </blockquote> The <network> part shouldn't be in the domain's XML. It should be used to separately define a libvirt network. Put that part in "direct.xml" (for example) and run: virsh net-define direct.xml virsh net-autostart direct-macvtap virsh start direct-macvtap However, your <interface> definition isn't even using that network; it's specifying the macvtap connection directly (with <source dev='eth0' mode='bridge'/>) so the network definition isn't even needed. (btw, the <network> xml is documented here: <a class="moz-txt-link-freetext" href="http://www.libvirt.org/formatnetwork.html">http://www.libvirt.org/formatnetwork.html</a> ) <blockquote cite="mid:007BD92917A2324FA403BCF9A464CF8436F96748@ALA-MBB.corp.ad.wrs.com" type="cite"> <div class="WordSection1"> <o:p></o:p> <o:p> </o:p> If, instead, I have the following, the guest comes up with no network interface at all<o:p></o:p> (except lo). On the host, interfaces vnet0 and virbr0 exist and virbr0 is 192.168.122.1.<o:p></o:p> <o:p> </o:p> <devices><o:p></o:p> <interface type='network'><o:p></o:p> <source network='default'/> <o:p></o:p> </interface><o:p></o:p> </devices><o:p></o:p> <o:p> </o:p> Adding in<o:p></o:p> <o:p> </o:p> <model type='virtio' /><o:p></o:p> <o:p> </o:p> makes it start with "eth0", but no address has been assigned. I can manually do that and then<o:p></o:p> I can communicate with the host but it's kind of a pain to add the address and routing manually. </div> </blockquote> That could be caused by one of the problems described here: <a class="moz-txt-link-freetext" href="http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed">http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed</a> In general, take a look at <a class="moz-txt-link-freetext" href="http://wiki.libvirt.org/page/Troubleshooting">http://wiki.libvirt.org/page/Troubleshooting</a> <blockquote cite="mid:007BD92917A2324FA403BCF9A464CF8436F96748@ALA-MBB.corp.ad.wrs.com" type="cite"> <div class="WordSection1"> <o:p></o:p> Oddly enough, though, ping from host to guest works normally, but ping guest to host seems to succeed once<o:p></o:p> then hang (with no timeout).<o:p></o:p> <o:p> </o:p> It is not at all obvious to me how virtio magically creates eth0.<o:p></o:p> <o:p> </o:p> Am I doing something wrong, here? And, if anyone could advise how to use openvswitch<o:p></o:p> I'd appreciate it. I've seen adding<o:p></o:p> <o:p> </o:p> <virtualport type='openvswitch/><o:p></o:p> <o:p> </o:p> might be enough, presumably with an appropriate name for the source network. </div> </blockquote> (you're really jumping all over the place here :-) You need a new enough version of libvirt to support openvswitch (at least 0.9.11, or 0.10.0 if you're using vlans), as well as a new enough kernel, and you need to have the openvswitch package(s) installed. There are several guides for doing this. Here's one that came up on Google: <a class="moz-txt-link-freetext" href="http://blog.scottlowe.org/2012/11/07/using-vlans-with-ovs-and-libvirt/">http://blog.scottlowe.org/2012/11/07/using-vlans-with-ovs-and-libvirt/</a> </body> </html>