<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Lee,</div><div><br></div><div>I managed to get this working, but I'm not in front of my computer at the moment. I used KOAN and Cobbler with a few caveats...I'll try to follow up to tomorrow.</div><div><br></div><div><br></div><div><div style="font-size:8px;color:#575757">Sent from my Verizon Wireless 4G LTE Smartphone</div></div><br><br>-------- Original message --------<br>From: lee <lee@yun.yagibdah.de> <br>Date:06/01/2014 8:45 PM (GMT-05:00) <br>To: centos-virt@centos.org <br>Subject: [CentOS-virt] xen setup documentation for centos? <br><br>Hi,<br><br>what is the proposed way to create domU guests on centos 6.5? At first<br>I tried to follow the documentation on the xen project website which<br>recommends using xl. I created a config file and ended up with getting<br>a message that the kernel is not bootable when trying to create a guest.<br>I also had to stop some daemon (xend?) because it said that xl isn`t<br>compatible with it and the daemon must be stopped first.<br><br>Then I followed redhat documentation which suggests to use virt-manager<br>--- which doesn`t work because servers don`t have GUIs. So I finally<br>managed to create a guest with virt-install. I can start and stop the<br>guest (which is also running centos), though I don`t think this is the<br>right way to create one.<br><br>So how exactly are you supposed to create guests?<br><br><br>Now I can`t get the networking to work. I`ve been reading lots of<br>documentation and still don`t understand how that is supposed to work.<br>As far as I understand, you get three different network interfaces:<br><br><br>dom0: a bridge (virbr0)<br>dom0: a virtual network interface (vifN.X)<br>domU: a virtual network interface which doesn`t appear to be virtual to<br> domU<br><br><br>And dom0 keeps it`s own network interface(s), like eth0, which is a<br>physical one.<br><br>Is vifN.X the same as eth0 in domU? Or what is it for? If it`s the<br>same, is it supposed to have the same IP on both sides?<br><br>How do I make it so that domU has network access (beyond dom0)? How<br>does this network stuff work? Do the virtual devices have to be in<br>different subnets? When they are not, the network becomes reachable via<br>multiple interfaces, and I`m guessing that either packet loops may be<br>created or some paths might be disabled by STP.<br><br>Do I have to set up shorewall (or the like) on dom0 to be able to handle<br>network access for guests? Would I need to create a bridge for every<br>guest to be able to handle them separately for firewalling purposes<br>because otherwise packets circumvent firewall rules by directly going<br>over the bridge? If so, why are bridges needed?<br><br>I would understand doing things like adding those guests that are<br>visible to the LAN only to the same bridge to have them all reachable<br>likewise. When doing that, it would seem to make sense to use a<br>different subnet for guests in the DMZ.<br><br>All the documentation tells you many different things, none of them work<br>and it`s totally confusing. Is there any /good/ documentation<br>somewhere?<br><br><br>-- <br>Knowledge is volatile and fluid. Software is power.<br>_______________________________________________<br>CentOS-virt mailing list<br>CentOS-virt@centos.org<br>http://lists.centos.org/mailman/listinfo/centos-virt<br></body>