<div>
Here is a sample config of mine. Sets the proper IP and bridge info. I am also using lvm's for the VM disks rather than image files.
</div><div><br></div><div><div>## Cfg type: XEN-PV-LOCAL-STORAGE</div><div><br></div><div>bootloader = '/usr/bin/pygrub'</div><div>extra = ''</div><div>memory = 1536</div><div>hostname = 'hostname.domain.com'</div><div>cpu_weight = 256</div><div>name = 'vm1039'</div><div>vif = ['ip=123.123.123.132, vifname=vifvm1039.0, mac=00:16:3e:1f:bf:1a, bridge=br0, model=e1000']</div><div>vnc = 0</div><div>vcpus = 4</div><div>vncviewer = 0</div><div>serial = 'pty'</div><div>disk = ['phy:/dev/vg_xm3/vm1039_img,xvda1,w', 'phy:/dev/vg_xm3/vm1039_swap,xvda2,w']</div><div><br></div></div><div><div>-- </div><div>Joe Fialkowski</div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, December 4, 2012 at 10:04 AM, Steven Spencer wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Hello list,</div><div><br></div><div>We have been using xen with CentOS for about 6 years now, always using </div><div>the libvirt and virt-install routines. After some huge problems with a </div><div>corrupted XML config file, and posts to this list earlier this year, we </div><div>decided that on all future xen builds, we would use a straight </div><div>configuration file for the builds from this point forward.</div><div><br></div><div>Recently, I retired a 5 year old xen server and decided that this would </div><div>be my test environment for the "new" (i.e., correct) way of creating and </div><div>installing DomU's. We set up a template in /etc/xen:</div><div><br></div><div>name = "vm_test"</div><div>memory = 1024</div><div>vcpus = 2</div><div>disk = [ 'tap:aio:/virtual/vm_test.img,xvda,w' ]</div><div>on_poweroff = 'destroy'</div><div>on_reboot = 'restart'</div><div>on_crash = 'restart'</div><div>vif = [ "mac=00:16:36:35:35:97,bridge=br0,script=vif-bridge" ]</div><div>kernel="/usr/lib/xen/boot/pv-grub-x86_64.gz"</div><div>extra="(hd0)/boot/grub/grub.conf"</div><div><br></div><div>And I created a disk image using dd:</div><div><br></div><div>dd if=/dev/zero of=/virtual/vm_test.img oflag=direct bs=1M count=2048</div><div><br></div><div>When we used the old virt-install routines, we always specified the IP </div><div>of the machine we were building, used a hard partitioning, rather than </div><div>Volume Groups and used the vncviewer to access the machine once the </div><div>first set of prompts was complete. In reading, I see that some of this </div><div>can be accomplished through a kickstarter file, so what I'm asking is if </div><div>this is the recommended way to specify the remaining parameters, or if I </div><div>need a more extensive configuration.</div><div><br></div><div>Your help is appreciated.</div><div><br></div><div>Thanks,</div><div>-- </div><div>-- </div><div>Steven G. Spencer, Network Administrator</div><div>KSC Corporate - The Kelly Supply Family of Companies</div><div>Office 308-382-8764 Ext. 231</div><div>Mobile 308-380-7957</div><div>_______________________________________________</div><div>kernel-xen mailing list</div><div><a href="mailto:kernel-xen@lists.wireless.org.au">kernel-xen@lists.wireless.org.au</a></div><div><a href="https://lists.wireless.org.au/mailman/listinfo/kernel-xen">https://lists.wireless.org.au/mailman/listinfo/kernel-xen</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>