Bill Pye wrote: > ----- Original Message ----- > From: "Marz" <[EMAIL PROTECTED]> > To: [email protected] > Sent: 31 July 2007 21:22:26 o'clock (GMT+0100) Europe/Berlin > Subject: Re: [Efw-user] xen or network install help > > Bill Pye wrote: >> Hi all >> >> Could someone help me with answers to a couple of questions? >> >> I like to do installs on my machines via pxe so I wondered if it is possible >> to install efw via a network install rather than burning a cd each upgrade? >> Normally I'd just extract the iso data to a directory on an ftp server but >> the efw iso doesn't seem to want to install via that method. I'm still >> fairly new to linux and don't know much about creating a directory that can >> be booted/installed, what's need to do this for efw? >> >> I'm also just starting to test xen and would like to consolidate several >> machines onto one server but I have a need for a para-virtualized install on >> a centos5 server. I don't think it's possible to boot a cd in xen unless >> it's s fully virtualized system, someone please correct me if I'm wrong. >> >> I'm at a total loss as to how I get efw into a xen into a para-virtualized >> domU, I've tried following the instructions on neobiker's wiki but as it's >> for a different distribution it's lost on me. >> >> I'd appreciate some pointers to any instructions, help, advice or general >> installation instructions for my type of set-up? >> >> TIA >> >> regards >> >> Bill >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Efw-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/efw-user >> > > Hi Bill, (at first sorry for my crappy English!) > > Maybe I can help you with Xen. I did it this way: > > At first install Vmware or Virtual Box on your Workstation. Mount the > EFW iso Image as a CD Drive an istall it (not the Xen Kernel!). > > When you are finish with this reboot the VM an login as root. Now you > have to find a way to move this installation to the Dom0. I simply > created the directory /tar and put all the files into an Archive. > > for example: > $tar -cSp --numeric-owner --atime-preserve -f /tar/efw.tar / > > I took scp to copy this to Dom0. > > $scp /tar/efw.tar [EMAIL PROTECTED]:~ > > In the Dom0 you have to extract the EFW to your DomU partition. I use LVM. > > $mount /dev/vg0/efw /mnt/efw > $cd /mnt/efw > $tar -xSpv --atime-preserve -f /root/efw.tar > > Next install the xen kernel. > > $chroot /mnt/efw > $rpm -Uvh kernel-xenU-2.6.9-55.EL.endian19.i386.rpm --nodeps > $exit #(leave the chroot) > > (I get the rpm form here > http://downloads.sourceforge.net/efw/EFW-COMMUNITY-2.1.1-devel-RPMS.tar.bz2) > > To boot the efw as a domU you have to copy the vmlinuz and the initrd. > $cp /mnt/efw/boot/initrd-2.6.9-55.EL.endian19-xenU.img /boot > $cp /mnt/efw/boot/vmlinuz-2.6.9-55.EL.endian19-xenU /boot > > The last thing is the DomU config. This is my one: > > # -*- mode: python; -*- > kernel = "/boot/vmlinuz-2.6.9-55.EL.endian19-xenU" > ramdisk = "/boot/initrd-2.6.9-55.EL.endian19-xenU.img" > memory = 128 > name = "domU_efw" > vif = [ 'bridge=xenbr0', 'bridge=xenbr1', 'bridge=xenbr2' ] > #pci = [ '02:05.0' ] I look forward when this will work! > disk = ['phy:/dev/vg0/efw,hda1,w','phy:/dev/vg0/efw-swap,hda2,w'] > root = "/dev/hda1 ro" > > > Any further questions? ;) > > Marz > > > Hi Marz > > I started this project a couple of days earlier than I anticipated and to my > great surprise and your excellent instructions I've got a working EFW in a > domU. > > In setting this up I changed slightly from your instruction by using the > 2.1.2 efw iso to install on a VMware image, that was the easy part. <g> A > couple of questions have arisen if you wouldn't mind answering them for me? > > 1. When following your instructions I got to the bit about doing a tar of the > files (on the VMWare image) and got these messages: > > tar: /proc/3122/fd/4: Cannot stat: No such file or directory > tar: Removing leading '/' from hard link targets > tar: /tar/efw212.tar file is the archive; not dumped > tar: Error exit delayed from previous errors > > Are they important? >
No they aren't important. /proc is an virtual file system. It shows informations about the kernel and the process control. The files are generated at the runtime. (Unix: everything's a file) > 2. Everything gets copied to the xen server and I untar it to an LVM > partition. I've also copied the kernel RPMs from the 2.1.2 iso to the server, > I then install the new kernel as follows: > > [EMAIL PROTECTED] efw]# chroot /mnt/efw > bash-3.00# rpm -Uvh kernel-xenU-2.6.9-55.EL.endian19.i386.rpm --nodeps > Preparing... ########################################### [100%] > 1:kernel-xenU ########################################### [100%] > /var/tmp/rpm-tmp.1223: line 2: 21739 Segmentation fault /usr/sbin/kudzu > -qs -k 2.6.9-55.EL.endian19 > WARNING: > /lib/modules/2.6.9-55.EL.endian19-xenU/kernel/drivers/pci/hotplug/pciehp.ko.gz > needs unknown symbol pcibios_set_irq_routing > WARNING: > /lib/modules/2.6.9-55.EL.endian19-xenU/kernel/drivers/pci/hotplug/shpchp.ko.gz > needs unknown symbol pcibios_set_irq_routing > WARNING: > /lib/modules/2.6.9-55.EL.endian19-xenU/kernel/drivers/char/synclink.ko.gz > needs unknown symbol isa_virt_to_bus > WARNING: No module ata_piix found for kernel 2.6.9-55.EL.endian19-xenU, > continuing anyway > grubby fatal error: unable to find a suitable template > bash-3.00# > > I guess that's not too serious a problem as I'm able to boot the domU > successfully or is it anything to be concerned about? > I got similar outputs. I think this are some unsolved dependencies or perhaps problems with the chroot environment. That's of no importance. > 3. I needed to make a change to the fstab on the efw domU, the original file > is as follows: > > /dev/hda1 /boot ext3 nodev,nosuid,noatime 1 2 > /dev/hda3 / ext3 noatime 1 1 > /dev/hda4 /var ext3 noatime,mand 1 1 > none /proc proc defaults 0 0 > none /dev/pts devpts gid=5,mode=620 0 0 > /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 > /dev/hda2 none swap sw 0 0 > > I removed the lines for /boot & /var and changed the root partition entry to > /dev/hda1 to match the domU file. That fixed a booting/crash problem. > > My domU config file looks similar to your and is as follows: > > name="efw" > kernel = "/boot/vmlinuz-2.6.9-55.EL.endian19-xenU" > ramdisk = "/boot/initrd-2.6.9-55.EL.endian19-xenU.img" > memory=128 > disk = [ 'phy:/dev/lvm-raid/efw.root,hda1,w', > 'phy:/dev/lvm-raid/efw.swap,hda2,w' ] > root="/dev/hda1 ro" > vif = [ 'bridge=xenbr0', 'bridge=xenbr1' ] > vcpus = 1 > on_reboot = 'restart' > on_crash = 'destroy' > > I don't have a swap file set-up yet but I'll try that later today. > Oh yes I forgot to mention that you have to change the fstab file. It's better to have a swap. Otherwise it is possible that the kernel kills some processes because of an memory lack. > 4. You mention in your domU config file this: > > #pci = [ '02:05.0' ] I look forward when this will work! > > What functionality will that give to xen and when it it supposed to be > available? > The special about Xen is that it does not emulate the CPU (like Vmware). It is a technique called hypervisor (<http://www.linuxmagazin.de/var/linux_magazin/storage/images/media/linux_magazin/ausgabe/2006/04/der_eigene_mini_mainframe/abb1_jpg/7542-1-ger-DE/abb1_jpg.jpg>). So Xen has the ability to allocate devices to different DomU's. An very popular example is to allocate an ISDN card to an domU an build in there a telephone system like a voip gateway. The current kernel (2.6.18) in the Xen binary support this function (module called pciback). The DomU Xen kernel of the efw is an older one (2.6.9) where this function is not implemented or activated. > The only other step that caused me a bit of late night googling was how to > create a another bridge after installing the second NIC in my server. Xen > documentation doesn't make this an easy task for the novice, does it? > This is the point. If pciback were possible it would be more easier because you could give the efw direct access to the NIC devices. The present way is to bridge the traffic through the Dom0. The con is that this solution is little slower and requires more configurations. But currently this is the only way it will work. My bridges look like this: $brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif1.0 vif1.1 vif2.0 vif3.0 xenbr1 8000.feffffffffff no eth1 vif2.1 xenbr2 8000.feffffffffff no eth2 vif2.2 xenbr0 is green (local network) xenbr1 is red (bad www) xenbr2 is blue (wlan) xenbr3 will coming soon (DMZ with web server) I really recommend the network-fw script from neobiker. The wiki is in german language but I think the script is understandable for you. <http://www.neobiker.de/wiki/index.php?title=XEN_Netzwerk_f%C3%BCr_Firewall> I use a little adapted one. some further links about Xen and networking: http://wiki.xensource.com/xenwiki/XenNetworking http://lists.xensource.com/archives/html/xen-users/2006-02/msg00602.html http://www.shorewall.net/Xen.html http://www.shorewall.net/XenMyWay.html http://lists.xensource.com/archives/html/xen-users/2006-02/msg00030.html > I really can't thank you enough for those instruction, without them I'd have > been struggling for a long time. Apart from a few hiccups that caused me a > bit of grief you've turned a difficult task (for me) into something extremely > simple. > I really know this! Sometimes I were very frustrated and just want to give up because I see no chance to solve a problem. The feeling of success is so much the better. Xen is great and so it is good to help people to use this. Xen is getting more popular from day to day. There are already some distributions which make it very easy for users (<http://www.eisxen.org/> or <http://www.ctserver.org/>). > I'm going to play around with this for a couple of days and tidy up my notes, > when I've done that I'll post the full steps back to this list. > > Many, many thanks. > > Bill > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Efw-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/efw-user > Looking forward for your succeed message ;) Marz ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Efw-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/efw-user
