http://www.ruslansivak.com This is the development blog. en-us Tue, 07 Sep 2010 22:39:15 -0400 Wed, 23 Jun 2010 23:52:00 -0400 BlogCFC http://blogs.law.harvard.edu/tech/rss russ@ruslansivak.com russ@ruslansivak.com russ@ruslansivak.com no http://www.ruslansivak.com/2010/6/23/XenServer-56- First we follow instructions on the <a href="http://linux.dell.com/wiki/index.php/Repository/hardware">Dell Wiki</a> to install the OpenManage repository and install the OpenManage Server Administrator. <code> # wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash Downloading GPG key: http://linux.dell.com/repo/hardware/latest/RPM-GPG-KEY-dell Importing key into RPM. Downloading GPG key: http://linux.dell.com/repo/hardware/latest/RPM-GPG-KEY-libsmbios Importing key into RPM. Write repository configuration Downloading repository RPM Installing repository rpm: http://linux.dell.com/repo/hardware/latest/platform_independent/rh50/prereq/dell-omsa-repository-2-5.noarch.rpm Installing yum plugins for system id Loaded plugins: fastestmirror Determining fastest mirrors citrix | 951 B 00:00 citrix/primary | 243 B 00:00 dell-omsa-indep | 1.9 kB 00:00 dell-omsa-indep/primary | 74 kB 00:00 dell-omsa-indep 525/525 dell-omsa-specific | 1.9 kB 00:00 dell-omsa-specific/primary | 74 kB 00:00 dell-omsa-specific 525/525 Setting up Install Process Resolving Dependencies ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: yum-dellsysid i386 2.2.19-10.1.el5 dell-omsa-indep 15 k Installing for dependencies: libsmbios i386 2.2.19-10.1.el5 dell-omsa-specific 1.5 M python-ctypes i386 1.0.2-1.1.el5 dell-omsa-specific 211 k python-smbios i386 2.2.19-10.1.el5 dell-omsa-specific 69 k smbios-utils-python i386 2.2.19-10.1.el5 dell-omsa-specific 56 k Transaction Summary ================================================================================ Install 5 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 1.8 M Downloading Packages: (1/5): yum-dellsysid-2.2.19-10.1.el5.i386.rpm | 15 kB 00:00 (2/5): smbios-utils-python-2.2.19-10.1.el5.i386.rpm | 56 kB 00:00 (3/5): python-smbios-2.2.19-10.1.el5.i386.rpm | 69 kB 00:00 (4/5): python-ctypes-1.0.2-1.1.el5.i386.rpm | 211 kB 00:00 (5/5): libsmbios-2.2.19-10.1.el5.i386.rpm | 1.5 MB 00:00 -------------------------------------------------------------------------------- Total 1.6 MB/s | 1.8 MB 00:01 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : libsmbios 1/5 Installing : python-ctypes 2/5 Installing : python-smbios 3/5 Installing : smbios-utils-python 4/5 Installing : yum-dellsysid 5/5 Installed: yum-dellsysid.i386 0:2.2.19-10.1.el5 Dependency Installed: libsmbios.i386 0:2.2.19-10.1.el5 python-ctypes.i386 0:1.0.2-1.1.el5 python-smbios.i386 0:2.2.19-10.1.el5 smbios-utils-python.i386 0:2.2.19-10.1.el5 Complete! Loaded plugins: dellsysid, fastestmirror No plugin match for: rhnplugin Cleaning up Everything Cleaning up list of fastest mirrors Done! </code> Optionally we install OpenManage Server Administrator. In order to install it, we need some packages not currently installed. Because of that, we will need to temporarily enable the CentOS base repository. <code> # yum --enablerepo base install srvadmin-all Loaded plugins: dellsysid, fastestmirror Loading mirror speeds from cached hostfile * base: ftp.lug.udel.edu Excluding Packages from CentOS-5 - Base Finished Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package srvadmin-all.i386 0:6.2.0-1.5.el5 set to be updated --> Processing Dependency: srvadmin-webserver = 6.2.0 for package: srvadmin-all --> Processing Dependency: srvadmin-storageservices = 6.2.0 for package: srvadmin-all --> Processing Dependency: srvadmin-base = 6.2.0 for package: srvadmin-all --> Processing Dependency: srvadmin-idrac = 6.2.0 for package: srvadmin-all --> Processing Dependency: srvadmin-rac4 = 6.2.0 for package: srvadmin-all --> Processing Dependency: srvadmin-standardAgent = 6.2.0 for package: srvadmin-all --> Processing Dependency: srvadmin-rac5 = 6.2.0 for package: srvadmin-all --> Running transaction check ---> Package srvadmin-base.i386 0:6.2.0-1.5.el5 set to be updated --> Processing Dependency: srvadmin-cm = 6.2.0 for package: srvadmin-base --> Processing Dependency: srvadmin-omacore = 6.2.0 for package: srvadmin-base --> Processing Dependency: srvadmin-smcommon = 6.2.0 for package: srvadmin-base ---> Package srvadmin-idrac.i386 0:6.2.0-1.5.el5 set to be updated --> Processing Dependency: srvadmin-idracdrsc = 6.2.0 for package: srvadmin-idrac --> Processing Dependency: srvadmin-idracadm = 6.2.0 for package: srvadmin-idrac ---> Package srvadmin-rac4.i386 0:6.2.0-1.5.el5 set to be updated --> Processing Dependency: srvadmin-racdrsc4 = 6.2.0 for package: srvadmin-rac4 --> Processing Dependency: srvadmin-racadm4 = 6.2.0 for package: srvadmin-rac4 --> Processing Dependency: srvadmin-racsvc = 6.2.0 for package: srvadmin-rac4 ---> Package srvadmin-rac5.i386 0:6.2.0-1.5.el5 set to be updated --> Processing Dependency: srvadmin-racdrsc5 = 6.2.0 for package: srvadmin-rac5 --> Processing Dependency: srvadmin-racadm5 = 6.2.0 for package: srvadmin-rac5 ---> Package srvadmin-standardAgent.i386 0:6.2.0-1.5.el5 set to be updated --> Processing Dependency: srvadmin-itunnelprovider = 6.2.0 for package: srvadmin-standardAgent ---> Package srvadmin-storageservices.i386 0:6.2.0-10.1.2.el5 set to be updated --> Processing Dependency: srvadmin-storelib = 6.2.0 for package: srvadmin-storageservices --> Processing Dependency: srvadmin-storage-populator = 6.2.0 for package: srvadmin-storageservices --> Processing Dependency: srvadmin-storage = 6.2.0 for package: srvadmin-storageservices --> Processing Dependency: srvadmin-sysfsutils = 6.2.0 for package: srvadmin-storageservices --> Processing Dependency: srvadmin-fsa = 6.2.0 for package: srvadmin-storageservices --> Processing Dependency: srvadmin-megalib = 6.2.0 for package: srvadmin-storageservices --> Processing Dependency: srvadmin-storelib-sysfs for package: srvadmin-storageservices --> Processing Dependency: srvadmin-storelib-libpci for package: srvadmin-storageservices ---> Package srvadmin-webserver.i386 0:6.2.0-1.5.el5 set to be updated --> Processing Dependency: srvadmin-iws = 6.2.0 for package: srvadmin-webserver --> Processing Dependency: srvadmin-smweb = 6.2.0 for package: srvadmin-webserver --> Running transaction check ---> Package srvadmin-cm.i386 0:6.2.0-677 set to be updated ---> Package srvadmin-fsa.i386 0:6.2.0-1.6.el3 set to be updated ---> Package srvadmin-idracadm.i386 0:6.2.0-677 set to be updated --> Processing Dependency: srvadmin-hapi = 6.2.0 for package: srvadmin-idracadm --> Processing Dependency: srvadmin-omilcore for package: srvadmin-idracadm --> Processing Dependency: srvadmin-omilcore for package: srvadmin-idracadm ---> Package srvadmin-idracdrsc.i386 0:6.2.0-677 set to be updated --> Processing Dependency: srvadmin-idrac-components = 6.2.0 for package: srvadmin-idracdrsc --> Processing Dependency: libomacs32.so.1 for package: srvadmin-idracdrsc --> Processing Dependency: libdcsgen32.so.5 for package: srvadmin-idracdrsc --> Processing Dependency: libdcsdrs32.so for package: srvadmin-idracdrsc --> Processing Dependency: srvadmin-idrac-components for package: srvadmin-idracdrsc ---> Package srvadmin-itunnelprovider.i386 0:6.2.0-1.6.el5 set to be updated --> Processing Dependency: openwsman-client >= 2.1.5 for package: srvadmin-itunnelprovider --> Processing Dependency: openwsman-server >= 2.1.5 for package: srvadmin-itunnelprovider --> Processing Dependency: libwsman1 >= 2.1.5 for package: srvadmin-itunnelprovider --> Processing Dependency: sblim-sfcb >= 1.3.2 for package: srvadmin-itunnelprovider --> Processing Dependency: libcmpiCppImpl0 >= 2.0.0 for package: srvadmin-itunnelprovider --> Processing Dependency: sblim-sfcc >= 2.1.0 for package: srvadmin-itunnelprovider --> Processing Dependency: libcmpiCppImpl.so.0 for package: srvadmin-itunnelprovider ---> Package srvadmin-iws.i386 0:6.2.0-1.18.el5 set to be updated --> Processing Dependency: srvadmin-jre for package: srvadmin-iws ---> Package srvadmin-megalib.i386 0:6.2.0-1.6.el3 set to be updated ---> Package srvadmin-omacore.i386 0:6.2.0-1.18.el5 set to be updated --> Processing Dependency: libxmlsup.so.2 for package: srvadmin-omacore --> Processing Dependency: libdcship.so.5 for package: srvadmin-omacore ---> Package srvadmin-racadm4.i386 0:6.2.0-677 set to be updated ---> Package srvadmin-racadm5.i386 0:6.2.0-677 set to be updated ---> Package srvadmin-racdrsc4.i386 0:6.2.0-677 set to be updated --> Processing Dependency: srvadmin-rac4-components = 6.2.0 for package: srvadmin-racdrsc4 --> Processing Dependency: srvadmin-rac4-components for package: srvadmin-racdrsc4 ---> Package srvadmin-racdrsc5.i386 0:6.2.0-677 set to be updated --> Processing Dependency: srvadmin-rac5-components = 6.2.0 for package: srvadmin-racdrsc5 --> Processing Dependency: srvadmin-rac5-components for package: srvadmin-racdrsc5 ---> Package srvadmin-racsvc.i386 0:6.2.0-677 set to be updated ---> Package srvadmin-smcommon.i386 0:6.2.0-1.29.el5 set to be updated ---> Package srvadmin-smweb.i386 0:6.2.0-1.29.el5 set to be updated ---> Package srvadmin-storage.i386 0:6.2.0-1.29.el5 set to be updated ---> Package srvadmin-storage-populator.i386 0:6.2.0-1.25.el3 set to be updated ---> Package srvadmin-storelib.i386 0:6.2.0-1.11.el3 set to be updated ---> Package srvadmin-storelib-libpci.i386 0:6.2.0-1.1.el5 set to be updated ---> Package srvadmin-storelib-sysfs.i386 0:6.2.0-1.1.el5 set to be updated ---> Package srvadmin-sysfsutils.i386 0:6.2.0-2.1.el5 set to be updated --> Running transaction check ---> Package libcmpiCppImpl0.i386 0:2.0.0Dell-1.1.el5 set to be updated ---> Package libwsman1.i386 0:2.1.5Dell-2.1.el5 set to be updated ---> Package openwsman-client.i386 0:2.1.5Dell-2.1.el5 set to be updated ---> Package openwsman-server.i386 0:2.1.5Dell-2.1.el5 set to be updated ---> Package sblim-sfcb.i386 0:1.3.5-40.el5 set to be updated --> Processing Dependency: perl(LWP::UserAgent) for package: sblim-sfcb ---> Package sblim-sfcc.i386 0:2.2.1-40.el5 set to be updated ---> Package srvadmin-deng.i386 0:6.2.0-1.6.el5 set to be updated ---> Package srvadmin-hapi.i386 0:6.2.0-1.17.el5 set to be updated ---> Package srvadmin-idrac-components.i386 0:6.2.0-677 set to be updated ---> Package srvadmin-isvc.i386 0:6.2.0-1.16.el5 set to be updated ---> Package srvadmin-jre.i386 0:6.2.0-1.17.el5 set to be updated ---> Package srvadmin-omcommon.i386 0:6.2.0-1.19.el5 set to be updated ---> Package srvadmin-omilcore.noarch 0:6.2.0-1.9.el5 set to be updated --> Processing Dependency: smbios-utils-bin for package: srvadmin-omilcore ---> Package srvadmin-rac4-components.i386 0:6.2.0-677 set to be updated ---> Package srvadmin-rac5-components.i386 0:6.2.0-677 set to be updated ---> Package srvadmin-xmlsup.i386 0:6.2.0-1.17.el5 set to be updated --> Processing Dependency: libxslt.so.1 for package: srvadmin-xmlsup --> Running transaction check ---> Package libxslt.i386 0:1.1.17-2.el5_2.2 set to be updated ---> Package perl-libwww-perl.noarch 0:5.805-1.1.1 set to be updated --> Processing Dependency: perl-HTML-Parser >= 3.33 for package: perl-libwww-perl --> Processing Dependency: perl(URI::URL) for package: perl-libwww-perl --> Processing Dependency: perl(URI) for package: perl-libwww-perl --> Processing Dependency: perl(HTML::Entities) for package: perl-libwww-perl --> Processing Dependency: perl(Compress::Zlib) for package: perl-libwww-perl --> Processing Dependency: perl(URI::Heuristic) for package: perl-libwww-perl --> Processing Dependency: perl(URI::Escape) for package: perl-libwww-perl ---> Package smbios-utils-bin.i386 0:2.2.19-10.1.el5 set to be updated --> Running transaction check ---> Package perl-Compress-Zlib.i386 0:1.42-1.fc6 set to be updated ---> Package perl-HTML-Parser.i386 0:3.55-1.fc6 set to be updated --> Processing Dependency: perl-HTML-Tagset >= 3.03 for package: perl-HTML-Parser --> Processing Dependency: perl(HTML::Tagset) for package: perl-HTML-Parser ---> Package perl-URI.noarch 0:1.35-3 set to be updated --> Running transaction check ---> Package perl-HTML-Tagset.noarch 0:3.10-2.1.1 set to be updated --> Finished Dependency Resolution Dependencies Resolved =============================================================================================================================================================================================================== Package Arch Version Repository Size =============================================================================================================================================================================================================== Installing: srvadmin-all i386 6.2.0-1.5.el5 dell-omsa-indep 2.5 k Installing for dependencies: libcmpiCppImpl0 i386 2.0.0Dell-1.1.el5 dell-omsa-indep 93 k libwsman1 i386 2.1.5Dell-2.1.el5 dell-omsa-indep 211 k libxslt i386 1.1.17-2.el5_2.2 base 485 k openwsman-client i386 2.1.5Dell-2.1.el5 dell-omsa-indep 115 k openwsman-server i386 2.1.5Dell-2.1.el5 dell-omsa-indep 146 k perl-Compress-Zlib i386 1.42-1.fc6 base 52 k perl-HTML-Parser i386 3.55-1.fc6 base 92 k perl-HTML-Tagset noarch 3.10-2.1.1 base 15 k perl-URI noarch 1.35-3 base 116 k perl-libwww-perl noarch 5.805-1.1.1 base 376 k sblim-sfcb i386 1.3.5-40.el5 base 1.3 M sblim-sfcc i386 2.2.1-40.el5 base 101 k smbios-utils-bin i386 2.2.19-10.1.el5 dell-omsa-indep 105 k srvadmin-base i386 6.2.0-1.5.el5 dell-omsa-indep 2.4 k srvadmin-cm i386 6.2.0-677 dell-omsa-indep 17 M srvadmin-deng i386 6.2.0-1.6.el5 dell-omsa-indep 714 k srvadmin-fsa i386 6.2.0-1.6.el3 dell-omsa-indep 2.6 k srvadmin-hapi i386 6.2.0-1.17.el5 dell-omsa-indep 817 k srvadmin-idrac i386 6.2.0-1.5.el5 dell-omsa-indep 2.4 k srvadmin-idrac-components i386 6.2.0-677 dell-omsa-indep 62 k srvadmin-idracadm i386 6.2.0-677 dell-omsa-indep 2.6 M srvadmin-idracdrsc i386 6.2.0-677 dell-omsa-indep 17 k srvadmin-isvc i386 6.2.0-1.16.el5 dell-omsa-indep 6.2 M srvadmin-itunnelprovider i386 6.2.0-1.6.el5 dell-omsa-indep 2.0 M srvadmin-iws i386 6.2.0-1.18.el5 dell-omsa-indep 4.9 M srvadmin-jre i386 6.2.0-1.17.el5 dell-omsa-indep 40 M srvadmin-megalib i386 6.2.0-1.6.el3 dell-omsa-indep 528 k srvadmin-omacore i386 6.2.0-1.18.el5 dell-omsa-indep 1.7 M srvadmin-omcommon i386 6.2.0-1.19.el5 dell-omsa-indep 4.1 M srvadmin-omilcore noarch 6.2.0-1.9.el5 dell-omsa-indep 28 k srvadmin-rac4 i386 6.2.0-1.5.el5 dell-omsa-indep 2.4 k srvadmin-rac4-components i386 6.2.0-677 dell-omsa-indep 52 k srvadmin-rac5 i386 6.2.0-1.5.el5 dell-omsa-indep 2.4 k srvadmin-rac5-components i386 6.2.0-677 dell-omsa-indep 61 k srvadmin-racadm4 i386 6.2.0-677 dell-omsa-indep 190 k srvadmin-racadm5 i386 6.2.0-677 dell-omsa-indep 1.3 M srvadmin-racdrsc4 i386 6.2.0-677 dell-omsa-indep 16 k srvadmin-racdrsc5 i386 6.2.0-677 dell-omsa-indep 17 k srvadmin-racsvc i386 6.2.0-677 dell-omsa-indep 66 k srvadmin-smcommon i386 6.2.0-1.29.el5 dell-omsa-indep 592 k srvadmin-smweb i386 6.2.0-1.29.el5 dell-omsa-indep 12 M srvadmin-standardAgent i386 6.2.0-1.5.el5 dell-omsa-indep 2.4 k srvadmin-storage i386 6.2.0-1.29.el5 dell-omsa-indep 778 k srvadmin-storage-populator i386 6.2.0-1.25.el3 dell-omsa-indep 1.2 M srvadmin-storageservices i386 6.2.0-10.1.2.el5 dell-omsa-indep 2.6 k srvadmin-storelib i386 6.2.0-1.11.el3 dell-omsa-indep 277 k srvadmin-storelib-libpci i386 6.2.0-1.1.el5 dell-omsa-indep 41 k srvadmin-storelib-sysfs i386 6.2.0-1.1.el5 dell-omsa-indep 41 k srvadmin-sysfsutils i386 6.2.0-2.1.el5 dell-omsa-indep 47 k srvadmin-webserver i386 6.2.0-1.5.el5 dell-omsa-indep 2.4 k srvadmin-xmlsup i386 6.2.0-1.17.el5 dell-omsa-indep 49 k Transaction Summary =============================================================================================================================================================================================================== Install 52 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 101 M Is this ok [y/N]:y Downloading Packages: (1/52): srvadmin-base-6.2.0-1.5.el5.i386.rpm | 2.4 kB 00:00 (2/52): srvadmin-idrac-6.2.0-1.5.el5.i386.rpm | 2.4 kB 00:00 (3/52): srvadmin-rac5-6.2.0-1.5.el5.i386.rpm | 2.4 kB 00:00 (4/52): srvadmin-standardAgent-6.2.0-1.5.el5.i386.rpm | 2.4 kB 00:00 (5/52): srvadmin-rac4-6.2.0-1.5.el5.i386.rpm | 2.4 kB 00:00 (6/52): srvadmin-webserver-6.2.0-1.5.el5.i386.rpm | 2.4 kB 00:00 (7/52): srvadmin-all-6.2.0-1.5.el5.i386.rpm | 2.5 kB 00:00 (8/52): srvadmin-fsa-6.2.0-1.6.el3.i386.rpm | 2.6 kB 00:00 (9/52): srvadmin-storageservices-6.2.0-10.1.2.el5.i386.rpm | 2.6 kB 00:00 (10/52): perl-HTML-Tagset-3.10-2.1.1.noarch.rpm | 15 kB 00:00 (11/52): srvadmin-racdrsc4-6.2.0-677.i386.rpm | 16 kB 00:00 (12/52): srvadmin-racdrsc5-6.2.0-677.i386.rpm | 17 kB 00:00 (13/52): srvadmin-idracdrsc-6.2.0-677.i386.rpm | 17 kB 00:00 (14/52): srvadmin-omilcore-6.2.0-1.9.el5.noarch.rpm | 28 kB 00:00 (15/52): srvadmin-storelib-libpci-6.2.0-1.1.el5.i386.rpm | 41 kB 00:00 (16/52): srvadmin-storelib-sysfs-6.2.0-1.1.el5.i386.rpm | 41 kB 00:00 (17/52): srvadmin-sysfsutils-6.2.0-2.1.el5.i386.rpm | 47 kB 00:00 (18/52): srvadmin-xmlsup-6.2.0-1.17.el5.i386.rpm | 49 kB 00:00 (19/52): srvadmin-rac4-components-6.2.0-677.i386.rpm | 52 kB 00:00 (20/52): perl-Compress-Zlib-1.42-1.fc6.i386.rpm | 52 kB 00:00 (21/52): srvadmin-rac5-components-6.2.0-677.i386.rpm | 61 kB 00:00 (22/52): srvadmin-idrac-components-6.2.0-677.i386.rpm | 62 kB 00:00 (23/52): srvadmin-racsvc-6.2.0-677.i386.rpm | 66 kB 00:00 (24/52): perl-HTML-Parser-3.55-1.fc6.i386.rpm | 92 kB 00:00 (25/52): libcmpiCppImpl0-2.0.0Dell-1.1.el5.i386.rpm | 93 kB 00:00 (26/52): sblim-sfcc-2.2.1-40.el5.i386.rpm | 101 kB 00:00 (27/52): smbios-utils-bin-2.2.19-10.1.el5.i386.rpm | 105 kB 00:00 (28/52): openwsman-client-2.1.5Dell-2.1.el5.i386.rpm | 115 kB 00:00 (29/52): perl-URI-1.35-3.noarch.rpm | 116 kB 00:00 (30/52): openwsman-server-2.1.5Dell-2.1.el5.i386.rpm | 146 kB 00:00 (31/52): srvadmin-racadm4-6.2.0-677.i386.rpm | 190 kB 00:00 (32/52): libwsman1-2.1.5Dell-2.1.el5.i386.rpm | 211 kB 00:00 (33/52): srvadmin-storelib-6.2.0-1.11.el3.i386.rpm | 277 kB 00:00 (34/52): perl-libwww-perl-5.805-1.1.1.noarch.rpm | 376 kB 00:00 (35/52): libxslt-1.1.17-2.el5_2.2.i386.rpm | 485 kB 00:00 (36/52): srvadmin-megalib-6.2.0-1.6.el3.i386.rpm | 528 kB 00:00 (37/52): srvadmin-smcommon-6.2.0-1.29.el5.i386.rpm | 592 kB 00:00 (38/52): srvadmin-deng-6.2.0-1.6.el5.i386.rpm | 714 kB 00:00 (39/52): srvadmin-storage-6.2.0-1.29.el5.i386.rpm | 778 kB 00:00 (40/52): srvadmin-hapi-6.2.0-1.17.el5.i386.rpm | 817 kB 00:00 (41/52): srvadmin-storage-populator-6.2.0-1.25.el3.i386.rpm | 1.2 MB 00:00 (42/52): srvadmin-racadm5-6.2.0-677.i386.rpm | 1.3 MB 00:00 (43/52): sblim-sfcb-1.3.5-40.el5.i386.rpm | 1.3 MB 00:00 (44/52): srvadmin-omacore-6.2.0-1.18.el5.i386.rpm | 1.7 MB 00:00 (45/52): srvadmin-itunnelprovider-6.2.0-1.6.el5.i386.rpm | 2.0 MB 00:00 (46/52): srvadmin-idracadm-6.2.0-677.i386.rpm | 2.6 MB 00:00 (47/52): srvadmin-omcommon-6.2.0-1.19.el5.i386.rpm | 4.1 MB 00:01 (48/52): srvadmin-iws-6.2.0-1.18.el5.i386.rpm | 4.9 MB 00:02 (49/52): srvadmin-isvc-6.2.0-1.16.el5.i386.rpm | 6.2 MB 00:02 (50/52): srvadmin-smweb-6.2.0-1.29.el5.i386.rpm | 12 MB 00:04 (51/52): srvadmin-cm-6.2.0-677.i386.rpm | 17 MB 00:05 (52/52): srvadmin-jre-6.2.0-1.17.el5.i386.rpm | 40 MB 00:37 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 1.6 MB/s | 101 MB 01:03 warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID e8562897 base/gpgkey | 1.5 kB 00:00 Importing GPG key 0xE8562897 "CentOS-5 Key (CentOS 5 Official Signing Key) <centos-5-key@centos.org>" from /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5 Is this ok [y/N]: y Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : srvadmin-hapi 1/52 Installing : libwsman1 2/52 Installing : openwsman-client 3/52 Installing : sblim-sfcc 4/52 Installing : srvadmin-sysfsutils 5/52 Installing : srvadmin-megalib 6/52 Installing : srvadmin-storelib 7/52 Installing : openwsman-server 8/52 Installing : srvadmin-storelib-libpci 9/52 Installing : libxslt 10/52 Installing : srvadmin-xmlsup 11/52 Installing : libcmpiCppImpl0 12/52 Installing : smbios-utils-bin 13/52 Installing : srvadmin-storelib-sysfs 14/52 Installing : perl-Compress-Zlib 15/52 Installing : srvadmin-omilcore 16/52 ********************************************************** After the install process completes, you may need to log out and then log in again to reset the PATH variable to access the Dell OpenManage CLI utilities To start all installed services without a reboot, enter the following command: srvadmin-services.sh start ********************************************************** Installing : srvadmin-smcommon 17/52 Installing : srvadmin-racadm4 18/52 Installing : srvadmin-racsvc 19/52 Installing : srvadmin-racadm5 20/52 Installing : srvadmin-jre 21/52 Installing : srvadmin-idracadm 22/52 Installing : srvadmin-fsa 23/52 Installing : perl-HTML-Tagset 24/52 Installing : perl-URI 25/52 Installing : srvadmin-deng 26/52 Installing : srvadmin-omcommon 27/52 Installing : srvadmin-isvc 28/52 Installing : srvadmin-omacore 29/52 Installing : srvadmin-storage 30/52 Installing : srvadmin-storage-populator 31/52 Installing : srvadmin-iws 32/52 Installing : perl-HTML-Parser 33/52 Installing : srvadmin-idrac-components 34/52 Installing : srvadmin-cm 35/52 Installing : srvadmin-storageservices 36/52 Installing : srvadmin-base 37/52 Installing : srvadmin-idracdrsc 38/52 Installing : srvadmin-idrac 39/52 Installing : srvadmin-rac4-components 40/52 Installing : srvadmin-racdrsc4 41/52 Installing : srvadmin-rac4 42/52 Installing : srvadmin-rac5-components 43/52 Installing : srvadmin-racdrsc5 44/52 Installing : srvadmin-rac5 45/52 Installing : perl-libwww-perl 46/52 Installing : srvadmin-smweb 47/52 Installing : sblim-sfcb 48/52 Installing : srvadmin-webserver 49/52 Installing : srvadmin-itunnelprovider 50/52 Installing : srvadmin-standardAgent 51/52 Installing : srvadmin-all 52/52 Installed: srvadmin-all.i386 0:6.2.0-1.5.el5 Dependency Installed: libcmpiCppImpl0.i386 0:2.0.0Dell-1.1.el5 libwsman1.i386 0:2.1.5Dell-2.1.el5 libxslt.i386 0:1.1.17-2.el5_2.2 openwsman-client.i386 0:2.1.5Dell-2.1.el5 openwsman-server.i386 0:2.1.5Dell-2.1.el5 perl-Compress-Zlib.i386 0:1.42-1.fc6 perl-HTML-Parser.i386 0:3.55-1.fc6 perl-HTML-Tagset.noarch 0:3.10-2.1.1 perl-URI.noarch 0:1.35-3 perl-libwww-perl.noarch 0:5.805-1.1.1 sblim-sfcb.i386 0:1.3.5-40.el5 sblim-sfcc.i386 0:2.2.1-40.el5 smbios-utils-bin.i386 0:2.2.19-10.1.el5 srvadmin-base.i386 0:6.2.0-1.5.el5 srvadmin-cm.i386 0:6.2.0-677 srvadmin-deng.i386 0:6.2.0-1.6.el5 srvadmin-fsa.i386 0:6.2.0-1.6.el3 srvadmin-hapi.i386 0:6.2.0-1.17.el5 srvadmin-idrac.i386 0:6.2.0-1.5.el5 srvadmin-idrac-components.i386 0:6.2.0-677 srvadmin-idracadm.i386 0:6.2.0-677 srvadmin-idracdrsc.i386 0:6.2.0-677 srvadmin-isvc.i386 0:6.2.0-1.16.el5 srvadmin-itunnelprovider.i386 0:6.2.0-1.6.el5 srvadmin-iws.i386 0:6.2.0-1.18.el5 srvadmin-jre.i386 0:6.2.0-1.17.el5 srvadmin-megalib.i386 0:6.2.0-1.6.el3 srvadmin-omacore.i386 0:6.2.0-1.18.el5 srvadmin-omcommon.i386 0:6.2.0-1.19.el5 srvadmin-omilcore.noarch 0:6.2.0-1.9.el5 srvadmin-rac4.i386 0:6.2.0-1.5.el5 srvadmin-rac4-components.i386 0:6.2.0-677 srvadmin-rac5.i386 0:6.2.0-1.5.el5 srvadmin-rac5-components.i386 0:6.2.0-677 srvadmin-racadm4.i386 0:6.2.0-677 srvadmin-racadm5.i386 0:6.2.0-677 srvadmin-racdrsc4.i386 0:6.2.0-677 srvadmin-racdrsc5.i386 0:6.2.0-677 srvadmin-racsvc.i386 0:6.2.0-677 srvadmin-smcommon.i386 0:6.2.0-1.29.el5 srvadmin-smweb.i386 0:6.2.0-1.29.el5 srvadmin-standardAgent.i386 0:6.2.0-1.5.el5 srvadmin-storage.i386 0:6.2.0-1.29.el5 srvadmin-storage-populator.i386 0:6.2.0-1.25.el3 srvadmin-storageservices.i386 0:6.2.0-10.1.2.el5 srvadmin-storelib.i386 0:6.2.0-1.11.el3 srvadmin-storelib-libpci.i386 0:6.2.0-1.1.el5 srvadmin-storelib-sysfs.i386 0:6.2.0-1.1.el5 srvadmin-sysfsutils.i386 0:6.2.0-2.1.el5 srvadmin-webserver.i386 0:6.2.0-1.5.el5 srvadmin-xmlsup.i386 0:6.2.0-1.17.el5 Complete! </code> Now we start up the server administrator: <code> # /opt/dell/srvadmin/sbin/srvadmin-services.sh start Starting Systems Management Device Drivers: Starting dell_rbu: [ OK ] Starting ipmi driver: [ OK ] Starting Systems Management Device Drivers: Starting dell_rbu: Already started [ OK ] Starting ipmi driver: [ OK ] Starting Systems Management Data Engine: Starting dsm_sa_datamgrd: [ OK ] Starting dsm_sa_eventmgrd: [ OK ] Starting dsm_sa_snmpd: [ OK ] Starting DSM SA Shared Services: [ OK ] which: no lockfile in (/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin) Starting DSM SA Connection Service: invcol Error: Cannot find utilities on the system to execute Inventory Collector. Make sure the following utilities are in the path: tar gzip tail rm mkdir chmod ls basename wc lockfile stat [ OK ] </code> As you can see, we're missing lockfile. Lets install it. First lets find out what package provides it. <code> # yum --enablerepo base whatprovides "*/lockfile" Loaded plugins: dellsysid, fastestmirror Loading mirror speeds from cached hostfile * base: hpc.arc.georgetown.edu Excluding Packages from CentOS-5 - Base Finished base/filelists_db | 3.4 MB 00:00 citrix/filelists | 236 B 00:00 dell-omsa-indep/filelists | 124 kB 00:00 dell-omsa-specific/filelists | 1.2 kB 00:00 procmail-3.22-17.1.el5.centos.i386 : The procmail mail processing program. Repo : base Matched from: Filename : /usr/bin/lockfile </code> It's in the package procmail. Lets install it. <code> # yum --enablerepo base install procmail Loaded plugins: dellsysid, fastestmirror Loading mirror speeds from cached hostfile * base: hpc.arc.georgetown.edu Excluding Packages from CentOS-5 - Base Finished Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package procmail.i386 0:3.22-17.1.el5.centos set to be updated --> Finished Dependency Resolution Dependencies Resolved =============================================================================================================================================================================================================== Package Arch Version Repository Size =============================================================================================================================================================================================================== Installing: procmail i386 3.22-17.1.el5.centos base 166 k Transaction Summary =============================================================================================================================================================================================================== Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 166 k Is this ok [y/N]: y Downloading Packages: procmail-3.22-17.1.el5.centos.i386.rpm | 166 kB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : procmail 1/1 Installed: procmail.i386 0:3.22-17.1.el5.centos Complete! </code> Now lets start the services again: <code> # /opt/dell/srvadmin/sbin/srvadmin-services.sh start Stopping Systems Management Data Engine: Stopping dsm_sa_snmpd: [ OK ] Stopping dsm_sa_eventmgrd: [ OK ] Stopping dsm_sa_datamgrd: [ OK ] Starting Systems Management Device Drivers: Starting dell_rbu: Already started [ OK ] Starting ipmi driver: [ OK ] Starting Systems Management Device Drivers: Starting dell_rbu: Already started [ OK ] Starting ipmi driver: [ OK ] Starting Systems Management Data Engine: Starting dsm_sa_datamgrd: [ OK ] Starting dsm_sa_eventmgrd: [ OK ] Starting dsm_sa_snmpd: [ OK ] Stopping Systems Management Data Engine: Stopping dsm_sa_snmpd: [ OK ] Stopping dsm_sa_eventmgrd: [ OK ] Stopping dsm_sa_datamgrd: [ OK ] Starting Systems Management Device Drivers: Starting dell_rbu: Already started [ OK ] Starting ipmi driver: [ OK ] Starting Systems Management Device Drivers: Starting dell_rbu: Already started [ OK ] Starting ipmi driver: [ OK ] Starting Systems Management Data Engine: Starting dsm_sa_datamgrd: [ OK ] Starting dsm_sa_eventmgrd: [ OK ] Starting dsm_sa_snmpd: [ OK ] Starting Systems Management Data Engine: Starting dsm_sa_datamgrd: Already started [ OK ] Starting dsm_sa_eventmgrd: Already started [ OK ] Starting dsm_sa_snmpd: Already started [ OK ] DSM SA Shared Services is already started DSM SA Connection Service is already started </code> Now we follow the <a href="http://support.dell.com/support/edocs/software/smitasst/8.6/en/index.htm">Dell IT Assistant User's Guide</a> to set up the SNMP alerts. For this guide, I will assume that you already have a working Dell ITA installation. Following the instructions on page 252 of the PDF: <code> # vi /etc/snmp/snmpd.conf </code> You should see the following file: <code> ############################################################################### # Access Control ############################################################################### # As shipped, the snmpd demon will only respond to queries on the # system mib group until this file is replaced or modified for # security purposes. #### # First, map the community name "public" into a "security name" # sec.name source community com2sec notConfigUser default public #### # Second, map the security name into a group name: # groupName securityModel securityName group notConfigGroup v1 notConfigUser group notConfigGroup v2c notConfigUser #### # Third, create a view for us to let the group have rights to: # name incl/excl subtree mask(optional) view systemview included system view systemview included interfaces view systemview included at view systemview included ip view systemview included icmp view systemview included tcp view systemview included udp view systemview included snmp #### # XenServer control domain does not support IPv6. # view systemview excluded ipv6InterfaceTableLastChange view systemview excluded icmpStatsInErrors.ipv6 view systemview excluded icmpStatsInMsgs.ipv6 view systemview excluded icmpStatsOutErrors.ipv6 view systemview excluded icmpStatsOutMsgs.ipv6 view systemview excluded icmpMsgStatsInPkts.ipv6 view systemview excluded icmpMsgStatsOutPkts.ipv6 #### # Finally, grant the group read-only access to the systemview view. # group context sec.model sec.level prefix read write notif access notConfigGroup "" any noauth exact systemview none none ############################################################################### # System contact information # syslocation Unknown (edit /etc/snmp/snmpd.conf) syscontact Root <root@localhost> (edit /etc/snmp/snmpd.conf) </code> First we follow step one and add a community name. Community name is like a password. Lets use a random password generator to create one: Change the line that says: <code> # sec.name source community com2sec notConfigUser default public </code> to something like this <code> # sec.name source community com2sec notConfigUser default 6bs2m9j-ZwUvdq?x@HyFq2Fapt!CUQX@ </code> At the end of the file add <code> trapsink 192.168.1.88 6bs2m9j-ZwUvdq?x@HyFq2Fapt!CUQX@ </code> Now we enable the SNMPd service and start it <code> # chkconfig snmpd on # service snmpd start Starting snmpd: [ OK ] </code> Replace 192.168.1.88 with the IP address of your Dell ITA Server and 6bs2m9j-ZwUvdq?x@HyFq2Fapt!CUQX@ with the community string you set up earlier. Now we will are going to follow <a href="http://support.citrix.com/article/CTX122337">Citrix KB Article CTX122337</a> to add the proper firewall rules. <code> # vi /etc/sysconfig/iptables </code> You should see something like the following: <code> # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -p 50 -j ACCEPT -A RH-Firewall-1-INPUT -p 51 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 694 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited COMMIT </code> Add the following right after "-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT". Unlike the XenServer document, dell ITA requires port 162 to be open in addition to 161. It also needs port 1311 open if you are have install System Administrator. <code> -A RH-Firewall-1-INPUT -p udp --dport 161 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 162 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 1311 --tcp-flags SYN,RST,ACK SYN -j ACCEPT </code> The whole file should now look like: <code> # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -p 50 -j ACCEPT -A RH-Firewall-1-INPUT -p 51 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 161 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 162 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 1311 --tcp-flags SYN,RST,ACK SYN -j ACCEPT -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 694 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited COMMIT </code> Now we refresh the firewall rules: <code> # service iptables restart Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: filter [ OK ] Unloading iptables modules: [ OK ] Applying iptables firewall rules: [ OK ] </code> Now log into Dell ITA server and test the connectivity. Go to Tools->Troubleshooting tool and put in the IP Address (or Host Name) of your Xen Server and click "Get Text Configuration". Now select SNMP Connectivity and click "Configure". Put in "6bs2m9j-ZwUvdq?x@HyFq2Fapt!CUQX@" for the Get Community and keep the Set Community blank and click "OK". Now click "Run Selected Test(s)". You should see something like the following: <code> Result of SNMP Connectivity test IP Address Used : 192.168.1.188 Result :  Connected using the Get Community Names - 6bs2m9j-ZwUvdq?x@HyFq2Fapt!CUQX@  Connected to the agent software(s) - [mib2, NA] Time of Execution : Thursday, June 17, 2010 2:51:03 PM EDT </code> Now lets add the IP of this server to the ranges (if it's not already covered by an existing range). Click on "Discovery and Monitoring->Ranges". If the range is not already covered, right click on "Include Ranges" and then select "New Include Range". Put in the IP address of your Xen server and "255.255.255.255" for the subnet mask, if you just want to add just the specific IP of this server. Click "Next", and then again click "Next" and put in "6bs2m9j-ZwUvdq?x@HyFq2Fapt!CUQX@" or the community string you set up earlier under "Get Community". Click "Next" a bunch of times until you get to step 7 and then change the option to "Perform both Discovery and Inventory". Click "Next" and "Finish". Now right click on the IP that we've just added under the "Include Ranges" and click "Perform Discovery and Inventory Now". Pick the "View Progress" from the dialog box that pops up. Once you see that the current task is 100% complete, click on "View->View Devices" and the server should show up under "Servers". XenServer Wed, 23 Jun 2010 23:52:00 -0400 http://www.ruslansivak.com/2010/6/23/XenServer-56- http://www.ruslansivak.com/2010/6/10/XenServer-56--Converting-Local-Storage-to-ext3-and-thereby-enabling-sparse-provisioning Since XenServer 5.6 has some sort of bug which won't let it boot when you have linux raid partition, and I haven't found a way around it, I'm going to make this short and sweet. We will just delete the existing LVM SR and recreate it as ext3. This will allow us to do sparse provisioning. First we will need to delete the current Local Storage, which involves quite a few steps. <code> # xe pbd-list uuid ( RO) : 4960a8ab-d46f-270c-645d-c697263972c4 host-uuid ( RO): d805a419-6dab-437a-ab3c-abba07209574 sr-uuid ( RO): e768c14b-e452-78fa-4fc6-7b2bbafd3fd4 device-config (MRO): location: /opt/xensource/packages/iso; legacy_mode: true currently-attached ( RO): true uuid ( RO) : a71c0a52-4d5a-fb22-01f7-63924ce0066f host-uuid ( RO): d805a419-6dab-437a-ab3c-abba07209574 sr-uuid ( RO): 01655c83-5668-c05b-7031-c33c032d7af0 device-config (MRO): device: /dev/disk/by-id/scsi-3600137206653cb001394e1bf5e3adfc5-part3 currently-attached ( RO): true uuid ( RO) : c00deda7-a064-903e-19cc-657a16eb1a1a host-uuid ( RO): d805a419-6dab-437a-ab3c-abba07209574 sr-uuid ( RO): cf8f5d45-2c85-e4c4-49bf-c6dab40a1e29 device-config (MRO): location: /dev/xapi/block currently-attached ( RO): true uuid ( RO) : e2e20fa4-0d5b-acf9-2f22-5d3a3cd89593 host-uuid ( RO): d805a419-6dab-437a-ab3c-abba07209574 sr-uuid ( RO): 9cb77bf4-1ccf-53bb-0a8b-ddc8ec9c3ee4 device-config (MRO): location: /dev/xapi/cd currently-attached ( RO): true </code> As you can see it's the second one on the list (the one that start with /dev/disk/by-id). Now we unplug it and destroy it. <code> # xe pbd-unplug uuid=a71c0a52-4d5a-fb22-01f7-63924ce0066f # xe pbd-destroy uuid=a71c0a52-4d5a-fb22-01f7-63924ce0066f </code> Now lets destroy the storage repository attached to it. First we get a list of the repositories. <code> # xe sr-list # xe sr-list uuid ( RO) : 01655c83-5668-c05b-7031-c33c032d7af0 name-label ( RW): Local storage name-description ( RW): host ( RO): <not in database> type ( RO): lvm content-type ( RO): user uuid ( RO) : 9cb77bf4-1ccf-53bb-0a8b-ddc8ec9c3ee4 name-label ( RW): DVD drives name-description ( RW): Physical DVD drives host ( RO): xen2 type ( RO): udev content-type ( RO): iso uuid ( RO) : cf8f5d45-2c85-e4c4-49bf-c6dab40a1e29 name-label ( RW): Removable storage name-description ( RW): host ( RO): xen2 type ( RO): udev content-type ( RO): disk uuid ( RO) : e768c14b-e452-78fa-4fc6-7b2bbafd3fd4 name-label ( RW): XenServer Tools name-description ( RW): XenServer Tools ISOs host ( RO): xen2 type ( RO): iso content-type ( RO): iso </code> We will delete the one called local storage. <code> # xe sr-forget uuid=01655c83-5668-c05b-7031-c33c032d7af0 </code> At this point it will be forgotten and disappear from XenCenter. Now, lets delete it from LVM. <code> # vgdisplay --- Volume group --- VG Name VG_XenStorage-01655c83-5668-c05b-7031-c33c032d7af0 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 1.81 TB PE Size 4.00 MB Total PE 474747 Alloc PE / Size 1 / 4.00 MB Free PE / Size 474746 / 1.81 TB VG UUID sR7JWl-k6sF-QU0Z-2Tkh-XNX5-mfuE-Pr7uKF </code> Now lets remove it. <code> # vgremove VG_XenStorage-01655c83-5668-c05b-7031-c33c032d7af0 Do you really want to remove volume group "VG_XenStorage-01655c83-5668-c05b-7031-c33c032d7af0" containing 1 logical volumes? [y/n]: y Logical volume "MGT" successfully removed Volume group "VG_XenStorage-01655c83-5668-c05b-7031-c33c032d7af0" successfully removed </code> Now we remove the physical volume. <code> # pvdisplay "/dev/sda3" is a new physical volume of "1.81 TB" --- NEW Physical volume --- PV Name /dev/sda3 VG Name PV Size 1.81 TB Allocatable NO PE Size (KByte) 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID 3KA4t0-rX04-0aa9-mP6c-EkOr-rPmg-BiGncU </code> <code> # pvremove /dev/sda3 Labels on physical volume "/dev/sda3" successfully wiped </code> Now we change the partition type to Linux. <code> # fdisk /dev/sda The number of cylinders for this disk is set to 243133. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 523 4194304 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 523 1045 4194304 83 Linux /dev/sda3 1045 243133 1944577183 8e Linux LVM Command (m for help): t Partition number (1-4): 3 Hex code (type L to list codes): L 0 Empty 1e Hidden W95 FAT1 80 Old Minix bf Solaris 1 FAT12 24 NEC DOS 81 Minix / old Lin c1 DRDOS/sec (FAT- 2 XENIX root 39 Plan 9 82 Linux swap / So c4 DRDOS/sec (FAT- 3 XENIX usr 3c PartitionMagic 83 Linux c6 DRDOS/sec (FAT- 4 FAT16 <32M 40 Venix 80286 84 OS/2 hidden C: c7 Syrinx 5 Extended 41 PPC PReP Boot 85 Linux extended da Non-FS data 6 FAT16 42 SFS 86 NTFS volume set db CP/M / CTOS / . 7 HPFS/NTFS 4d QNX4.x 87 NTFS volume set de Dell Utility 8 AIX 4e QNX4.x 2nd part 88 Linux plaintext df BootIt 9 AIX bootable 4f QNX4.x 3rd part 8e Linux LVM e1 DOS access a OS/2 Boot Manag 50 OnTrack DM 93 Amoeba e3 DOS R/O b W95 FAT32 51 OnTrack DM6 Aux 94 Amoeba BBT e4 SpeedStor c W95 FAT32 (LBA) 52 CP/M 9f BSD/OS eb BeOS fs e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi ee EFI GPT f W95 Ext'd (LBA) 54 OnTrackDM6 a5 FreeBSD ef EFI (FAT-12/16/ 10 OPUS 55 EZ-Drive a6 OpenBSD f0 Linux/PA-RISC b 11 Hidden FAT12 56 Golden Bow a7 NeXTSTEP f1 SpeedStor 12 Compaq diagnost 5c Priam Edisk a8 Darwin UFS f4 SpeedStor 14 Hidden FAT16 <3 61 SpeedStor a9 NetBSD f2 DOS secondary 16 Hidden FAT16 63 GNU HURD or Sys ab Darwin boot fb VMware VMFS 17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fc VMware VMKCORE 18 AST SmartSleep 65 Novell Netware b8 BSDI swap fd Linux raid auto 1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid fe LANstep 1c Hidden W95 FAT3 75 PC/IX be Solaris boot ff BBT Hex code (type L to list codes): 83 Changed system type of partition 3 to 83 (Linux) Command (m for help): p Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 523 4194304 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 523 1045 4194304 83 Linux /dev/sda3 1045 243133 1944577183 83 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot. Syncing disks. </code> Now we reboot to make sure that the kernel picks up our changes. <code> #reboot </code> Now lets add it to XenServer. <code> # xe sr-create host-uuid=d805a419-6dab-437a-ab3c-abba07209574 content-type=user name-label="Local SR" shared=false device-config:device=/dev/sda3 type=ext fece93d6-503e-991c-2076-ac4e148f8630 </code> Now we reboot and everything should come up fine. XenServer Thu, 10 Jun 2010 23:29:00 -0400 http://www.ruslansivak.com/2010/6/10/XenServer-56--Converting-Local-Storage-to-ext3-and-thereby-enabling-sparse-provisioning http://www.ruslansivak.com/2010/5/11/Get-rid-of-the-temp-files-generated-by-ColdFusion-Builder When opening an html file with CFBuilder, it was generating a temp file in my workspace - that wasn't going away when you closed the file. Digging into the issue, it turns out that Aptana - which is CFBuilder's HTML editor, does this. To get rid of this behavior, uncheck the following option: <code> Window->Preferences->HTML->Editors->HTML->Preview->Generate temporary files for browser previews. </code> ColdFusion CFBuilder Tue, 11 May 2010 19:23:00 -0400 http://www.ruslansivak.com/2010/5/11/Get-rid-of-the-temp-files-generated-by-ColdFusion-Builder http://www.ruslansivak.com/2010/4/7/Urchin-5-on-CentOS-5-RHEL-5--ERROR-7066211368 After installing Urchin, I got the following error when trying to update _domaindb. <code> ERROR: (7066-211-368) Domain DB update failed DETAIL: (6) Couldn't resolve host 'download.urchin.com' </code> Now the DNS was configured properly and download.urchin.com was pinging normally. Turns out that urchin needs the nscd service enabled. <code> #yum install nscd #chkconfig nscd on #service nscd start #ln -s /var/run/nscd/socket /var/run/.nscd_socket </code> After doing this, the update should work fine. Urchin Wed, 07 Apr 2010 09:34:00 -0400 http://www.ruslansivak.com/2010/4/7/Urchin-5-on-CentOS-5-RHEL-5--ERROR-7066211368 http://www.ruslansivak.com/2010/3/29/XenServer-55--Converting-Local-Storage-to-ext3-and-thereby-enabling-sparse-provisioning After I wrote my earlier post about setting up local NFS and enabling sparse provisioning, I was having some performance issues with NFS. It turns out that you can still have sparse provisioning with local storage when it's set up as ext, instead of lvm. XenServer will create sparse disks for your VMs only on NFS based volumes or locally formatted ext volumes. If you are using ISCSI or lvm based local storage, it will fully allocate each disk. This is less of a problem when you have a thinly provisioned ISCSI volume which is also compressed (such as those provided by Nexenta/OpenSolaris), but when you have a limited amount of local storage, it's unfortunate that XenServer doesn't give you the option to create sparse disks out of the box. Luckily, we can convert the storage to ext3 and enable thin provisioning. First we will need to delete the current Local Storage, which involves quite a few steps. <code> #lvdisplay --- Logical volume --- LV Name /dev/VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2/MGT VG Name VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 LV UUID HlifV3-7B6J-rVCp-pAxP-Rc7e-viEQ-Tt819a LV Write Access read/write LV Status NOT available LV Size 4.00 MB Current LE 1 Segments 1 Allocation inherit Read ahead sectors auto </code> Now we run xe pbd-list and find the one that matches our local SR. <code> #xe pbd-list uuid ( RO) : e06a37a5-e1e6-4415-134e-f5ae4f7f7c17 host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): fc8c8fc5-4a06-18b9-517d-f19a18e50820 device-config (MRO): location: /dev/xapi/cd currently-attached ( RO): true uuid ( RO) : 7a75d1b9-9aa5-d5f7-6b85-50d1175054c8 host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): a6db482a-5446-3fc3-6513-6933eb9d7915 device-config (MRO): location: /dev/xapi/block currently-attached ( RO): true uuid ( RO) : 6c1eeeb0-3c05-fbee-4dca-e7490e007504 host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): f663b0ec-56b0-72dc-d546-4e0fc9be7ef6 device-config (MRO): location: /opt/xensource/packages/iso; legacy_mode: true currently-attached ( RO): true uuid ( RO) : 825bc0eb-8ec9-01ab-e249-21146d66dd9a host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): 877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 device-config (MRO): device: /dev/disk/by-id/scsi-SATA_WDC_WD800JD-75M_WD-WMAM9AJ38489-part3 currently-attached ( RO): true </code> As we can see, it's the last one. Now we unplug it and destroy it. <code> #xe pbd-unplug uuid=825bc0eb-8ec9-01ab-e249-21146d66dd9a #xe pbd-destroy uuid=825bc0eb-8ec9-01ab-e249-21146d66dd9a </code> Now lets destroy the storage repository attached to it. First we get a list of the repositories. <code> #xe sr-list uuid ( RO) : a6db482a-5446-3fc3-6513-6933eb9d7915 name-label ( RW): Removable storage name-description ( RW): host ( RO): xenserver-ueyqfddq type ( RO): udev content-type ( RO): disk uuid ( RO) : fc8c8fc5-4a06-18b9-517d-f19a18e50820 name-label ( RW): DVD drives name-description ( RW): Physical DVD drives host ( RO): xenserver-ueyqfddq type ( RO): udev content-type ( RO): iso uuid ( RO) : 877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 name-label ( RW): Local storage name-description ( RW): host ( RO): <not in database> type ( RO): lvm content-type ( RO): user uuid ( RO) : f663b0ec-56b0-72dc-d546-4e0fc9be7ef6 name-label ( RW): XenServer Tools name-description ( RW): XenServer Tools ISOs host ( RO): xenserver-ueyqfddq type ( RO): iso content-type ( RO): iso </code> We will delete the one called local storage. <code> #xe sr-forget uuid=877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 </code> At this point it will be forgotten and disappear from XenCenter. Now, lets delete it from LVM. <code> #vgdisplay --- Volume group --- VG Name VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 66.85 GB PE Size 4.00 MB Total PE 17113 Alloc PE / Size 1 / 4.00 MB Free PE / Size 17112 / 66.84 GB VG UUID 2PJJkR-ULpa-1F6f-8H65-N22A-o11C-f0KkGa </code> Now lets remove it. <code> #vgremove VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 Do you really want to remove volume group "VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2" containing 1 logical volumes? [y/n]: y Logical volume "MGT" successfully removed Volume group "VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2" successfully removed </code> <code> #pvdisplay "/dev/sda3" is a new physical volume of "66.86 GB" --- NEW Physical volume --- PV Name /dev/sda3 VG Name PV Size 66.86 GB Allocatable NO PE Size (KByte) 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID ZK23c0-UvDg-A4MB-TWKi-YfNW-hWUK-uoyqdo </code> Now we remove the physical volume from LVM. <code> #pvremove /dev/sda3 Labels on physical volume "/dev/sda3" successfully wiped </code> The instructions that follow use a different system, and a different hard disk. I am using a 2TB disk and will create 2 888GB partitions for local storage and one 200GB for ISOs. Since XenServer will only allow a single SR on a drive, we'll need to create a fake raid array on the second data partition. To this end we need to change the type of the partition to "Linux raid autodetect", so that it's automounted on boot. <code> # fdisk /dev/sda The number of cylinders for this disk is set to 243133. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): m Command action a toggle a bootable flag b edit bsd disklabel c toggle the dos compatibility flag d delete a partition l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit without saving changes s create a new empty Sun disklabel t change a partition's system id u change display/entry units v verify the partition table w write table to disk and exit x extra functionality (experts only) Command (m for help): p Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 499 4008186 83 Linux /dev/sda2 500 998 4008217+ 83 Linux /dev/sda3 999 243133 1944949387+ 83 Linux Command (m for help): d Partition number (1-4): 3 Command (m for help): p Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 499 4008186 83 Linux /dev/sda2 500 998 4008217+ 83 Linux Command (m for help): n Command action e extended p primary partition (1-4) e Partition number (1-4): 3 First cylinder (999-243133, default 999): Using default value 999 Last cylinder or +size or +sizeM or +sizeK (999-243133, default 243133): Using default value 243133 Command (m for help): p Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 499 4008186 83 Linux /dev/sda2 500 998 4008217+ 83 Linux /dev/sda3 999 243133 1944949387+ 5 Extended Command (m for help): n Command action l logical (5 or over) p primary partition (1-4) l First cylinder (999-243133, default 999): Using default value 999 Last cylinder or +size or +sizeM or +sizeK (999-243133, default 243133): +888G Command (m for help): n Command action l logical (5 or over) p primary partition (1-4) l First cylinder (108960-243133, default 108960): Using default value 108960 Last cylinder or +size or +sizeM or +sizeK (108960-243133, default 243133): 888G Value out of range. Last cylinder or +size or +sizeM or +sizeK (108960-243133, default 243133): +888G Command (m for help): n Command action l logical (5 or over) p primary partition (1-4) l First cylinder (216921-243133, default 216921): Using default value 216921 Last cylinder or +size or +sizeM or +sizeK (216921-243133, default 243133): Using default value 243133 Command (m for help): p Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 499 4008186 83 Linux /dev/sda2 500 998 4008217+ 83 Linux /dev/sda3 999 243133 1944949387+ 5 Extended /dev/sda5 999 108959 867196701 83 Linux /dev/sda6 108960 216920 867196701 83 Linux /dev/sda7 216921 243133 210555891 83 Linux Command (m for help): t Partition number (1-7): 6 Hex code (type L to list codes): fd Changed system type of partition 6 to fd (Linux raid autodetect) Command (m for help): p Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 499 4008186 83 Linux /dev/sda2 500 998 4008217+ 83 Linux /dev/sda3 999 243133 1944949387+ 5 Extended /dev/sda5 999 108959 867196701 83 Linux /dev/sda6 108960 216920 867196701 fd Linux raid autodetect /dev/sda7 216921 243133 210555891 83 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot. Syncing disks. </code> At this point I had to reboot the server because of the warning above. You may or may not get this warning and need to reboot before proceeding. First lets set up our ISO repository. <code> # mkfs.ext3 -m 0 /dev/sda7 mke2fs 1.39 (29-May-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 26329088 inodes, 52638972 blocks 0 blocks (0.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 1607 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 36 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. </code> Now lets set up a folder for it and make sure it gets mounted at boot time. <code> #mkdir /data </code> <code> #vi /etc/fstab LABEL=root-cjfffcbq /ext3 defaults 1 1 /var/swap/swap.001swap swap defaults 0 0 none/dev/pts devpts defaults 0 0 none/dev/shm tmpfs defaults 0 0 none/proc proc defaults 0 0 none/sys sysfs defaults 0 0 </code> We need to add our directory to automatically mount at boot time. Lets add this entry <code> /dev/sda7 /data ext3 defaults 1 2 </code> This is how my file looked like at the end. <code> /ext3 defaults 1 1 /var/swap/swap.001swap swap defaults 0 0 none/dev/pts devpts defaults 0 0 none/dev/shm tmpfs defaults 0 0 none/proc proc defaults 0 0 none/sys sysfs defaults 0 0 /dev/sda7 /data ext3 defaults 1 2 </code> Now lets try mounting it. <code> #mount /data </code> If you get no output, that means it probably worked. Lets check that it mounted successfully. <code> #ls /data lost+found </code> Now lets create our directory that we will export. <code> #mkdir /data/iso </code> Lets edit the exports file. <code> #vi /etc/exports </code> The file should initially be empty. Lets add our entries. <code> /data/iso 127.0.0.1(ro,no_root_squash,sync) </code> Save the file, and now lets start the nfs and portmap services. <code> #service nfs start Starting NFS services: [ OK ] Starting NFS daemon: [ OK ] Starting NFS mountd: [ OK ] #service portmap start Starting portmap: [ OK ] </code> Lets make sure that the portmap and nfs services start at boot. <code> #chkconfig --level 345 nfs on #chkconfig --level 345 portmap on </code> Lets verify that our directory is being exported. <code> #exportfs /data/iso 127.0.0.1 </code> Lets add an ISO SR as well. Right click on the server in XenCenter, and click "New Storage Repository". Select "NFS ISO" as the type, and enter the following parameters. <code> Name: NFS Local ISO library Share Name: 127.0.0.1:/data/iso Click "Finish". </code> Now we will create the actual Storage Repositories to keep our VMs. I have decided to split mine in two as a way to short stroke the disk - I will try to use mostly the first SR, and maybe put in VMs that are not used often into the second SR, as the first SR should have slightly faster speed and better average seek time. You may choose to only have a single SR, so you'll need to modify your fdisk config earlier. <strike>First we create our ext3 filesystems. <code> # mkfs.ext3 -m 0 /dev/sda5 mke2fs 1.39 (29-May-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 108412928 inodes, 216799175 blocks 0 blocks (0.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 6617 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 22 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. </code> <code> # mkfs.ext3 -m 0 /dev/sda6 mke2fs 1.39 (29-May-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 108412928 inodes, 216799175 blocks 0 blocks (0.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 6617 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 30 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. </code> </strike> <b>Update (6/8/2010): Turns out it's not necessary to make the ext3 partitions yourself, as XenServer does it for you. </b><br/> Now we will create the storage repositories on these ext partitions. As I mentioned earlier, we need to create a fake raid on top of the second partition, otherwise XenServer won't us use it. <b>Update (6/10/2010): Looks like XenServer 5.6 has some sort of bug which prevents it from booting with any partitions set to type "fd". If you are using 5.6 - DO NOT CREATE an md device. Instead just partition it so that there is only a single data device. </b> <code> # mdadm --create /dev/md0 --level=1 --raid-devices=1 /dev/sda6 --force mdadm: array /dev/md0 started. </code> Now lets set up our Storage Repositories. This will take several minutes (about 15 minutes for me for a 1TB repo), so don't panic if you don't see any progress for a while. <code> # xe sr-create host-uuid=999847a4-d895-4e30-a703-1a20f9930cfd content-type=user name-label="Local SR1" shared=false device-config:device=/dev/sda5 type=ext 0414bfc6-bad9-81ed-ead9-9d3c42f19b61 </code> Now we set up a Storage Repository on top of the fake array. <code> #xe sr-create host-uuid=999847a4-d895-4e30-a703-1a20f9930cfd content-type=user name-label="Local SR2" shared=false device-config:device=/dev/md0 type=ext 037fb965-61c5-1345-4d73-b7f9736133ad </code> Now we reboot and if everything comes back up, we are done. Now when we create VMs, the Virtual Hard Disks will be allocated sparsely, and VMs created from templates, will all use the same base VHD and only store the changes in their own disk. XenServer Mon, 29 Mar 2010 20:07:00 -0400 http://www.ruslansivak.com/2010/3/29/XenServer-55--Converting-Local-Storage-to-ext3-and-thereby-enabling-sparse-provisioning http://www.ruslansivak.com/2009/12/3/Railo-on-Tomcat-on-Windows-x64--Part-IV Now that we've got Tomcat, Railo and Apache httpd up and running, lets connect Tomcat and Apache. For this we will need a mod_jk connector. The binary can be found <a href="http://www.trieuvan.com/apache/tomcat/tomcat-connectors/jk/binaries/">here</a>. There is no x64 connector as there is no x64 official release of Apache httpd, so we will be using the x32 connector. In my case I downloaded <a href="http://www.trieuvan.com/apache/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.28/mod_jk-1.2.28-httpd-2.2.3.so">mod_jk-1.2.28-httpd-2.2.3.so</a> from the win32 folder. Download this file and put it in C:\Apache2\modules. Now rename it to mod_jk.so Create a file in c:\Apache2\conf\extra called workers.properties and put this into the file <code> # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 </code> Now lets <a href="http://www.getrailo.org/index.cfm/download/">download Railo</a> and lets set it up. We want to get the custom one, the jars, in my case "railo-3.1.2.001-jars.zip (34 MB)". Create a Railo folder in the Tomcat folder, in my case "C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0". Now open up the railo zip file and put the jar files from the railo-3.1.2.001-jars into the railo folder we just created. Now edit the catalina.properties file that was in Tomcat conf folder, in my case "C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0\conf". Find the line that says "common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar" and edit it to say "common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home}/railo/*.jar" Now open tomcat-users.xml and change the encoding to utf-8. At the top where it says "&lt;?xml version='1.0' encoding='cp1252'?&gt;" and change it to "&lt;?xml version='1.0' encoding='utf-8'?&gt;" This is needed due to some weird Tomcat bug on windows. Now lets open web.xml in the Tomcat's conf directory. Just before the "Built In Servlet Mappings" add the following: <code> <servlet> <servlet-name>RailoCFMLServlet</servlet-name> <description>CFML runtime Engine</description> <servlet-class>railo.loader.servlet.CFMLServlet</servlet-class> <init-param> <param-name>configuration</param-name> <param-value>/WEB-INF/railo</param-value> <description>Configuration directory</description> </init-param> <!-- init-param> <param-name>railo-server-root</param-name> <param-value>.</param-value> <description>directory where railo root directory is stored</description> </init-param --> <load-on-startup>1</load-on-startup> </servlet> <servlet> <servlet-name>RailoAMFServlet</servlet-name> <description>AMF Servlet for flash remoting</description> <servlet-class>railo.loader.servlet.AMFServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet> <servlet-name>RailoFileServlet</servlet-name> <description>File Servlet for simple files</description> <servlet-class>railo.loader.servlet.FileServlet</servlet-class> <load-on-startup>2</load-on-startup> </servlet> </code> Now at the end of the servlet mapping section, add the following <code> <servlet-mapping> <servlet-name>RailoCFMLServlet</servlet-name> <url-pattern>*.cfm</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>RailoCFMLServlet</servlet-name> <url-pattern>*.cfml</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>RailoCFMLServlet</servlet-name> <url-pattern>*.cfc</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>RailoAMFServlet</servlet-name> <url-pattern>/flashservices/gateway/*</url-pattern> </servlet-mapping> <servlet-mapping> <!-- could be RailoFileServlet --> <servlet-name>default</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping> </code> Now open up server.xml and at the end of the file inside the Engine tag, we'll add a new host definition. <code> <Host name="railotest" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false"> <Context path="" docBase="c:/websites/railotest" /> </Host> </code> Now lets go back to our httpd-vhosts.conf Apache file. We need to add the following (I do this outside of any virtualhost definitions. <code> # Load mod_jk module LoadModule jk_module modules/mod_jk.so # Where to find workers.properties JkWorkersFile conf/extra/workers.properties # Where to put jk shared memory JkShmFile logs/mod_jk.shm # Where to put jk logs JkLogFile logs/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel info # Select the timestamp log format JkLogStampFormat "[%a %b %d %H:%M:%S %Y] " </code> We also need to add the following to the VirtualHost definition <code> # Send requests for cfm files to worker named worker1 JkMount /*.cfm worker1 </code> The full virtualhost definition should look like <code> <VirtualHost *:80> DocumentRoot "C:/websites/railotest" ServerName railotest ErrorLog "logs/railotest.com-error.log" CustomLog "logs/railotest-access.log" common # Send requests for cfm files to worker named worker1 JkMount /*.cfm worker1 </VirtualHost> </code> Now if we restart Tomcat and Apache we should be able to hit http://railotest in our browser and see the debugging info. We will also see a WEB-INF folder created inside c:\websites\railotest. Now lets put in an alias for the railo-context so that we can get to the admin. Inside the virtual host add <code> Alias /railo-context C:\websites\railotest\WEB-INF\railo\context </code> Now restart Apache and we should be able to get to the Web Administrator for this host by going to http://railotest/railo-context/admin.cfm Windows x64 Windows 2003 ColdFusion Railo Thu, 03 Dec 2009 21:58:00 -0400 http://www.ruslansivak.com/2009/12/3/Railo-on-Tomcat-on-Windows-x64--Part-IV http://www.ruslansivak.com/2009/12/2/Railo-on-Tomcat-on-Windows-x64--Part-III In the previous two parts we installed Tomcat. Now lets set up Apache httpd server. I suggest downloading Apache from <a href="http://www.apachelounge.com/download/">Apache Lounge</a>. The nice thing about Apache Lounge's builds is that they include mod_rewrite and mod_ssl. The latest version at the time of this writing is 2.2.14. Download httpd-2.2.14-win32-x86-ssl.zip and open it in your favorite archiver (mine is <a href="http://www.rarlab.com/download.htm">WinRar</a>). I recommend taking the Apache2 folder inside the zip file and placing it on c:\. After you've done this you should have a c:\Apache2 folder with many files and subfolders in it. Open c:\Apache2\conf\httpd.conf file in your favorite text editor. I recommend <a href="http://www.textpad.com/download/index.html">Textpad</a>. I usually change a few things from the defaults. Your configuration may differ. Change <code>ServerAdmin admin@example.com</code> to your email address. Uncomment the following modules: <code> #LoadModule proxy_module modules/mod_proxy.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule rewrite_module modules/mod_rewrite.so </code> by removing the # sign in front of the line. Find the line that says <code><Directory "c:/Apache2/htdocs"></code> After closing directory tag lets add one allowing access to our web root. I usually set up a folder or a new drive for it. Lets say we set up a webroot of "c:\websites". Create a folder websites on c: and then inside it create another folder called railotest. We will use this to set up our test site. After the closing </directory> tag, add a new one allowing access to our web root. <code> <Directory "c:/websites"> Options Indexes FollowSymLinks AllowOverride None Order allow,deny Allow from all </Directory> </code> This will allow Apache to serve from anywhere inside c:\websites. Alternatively, you can set up a new directory entry for every site that you create, but I find that this makes things easier without significantly impacting security. Find the line that says <code> DirectoryIndex index.html </code> and add index.cfm to that list <code> DirectoryIndex index.html index.cfm </code> Uncomment the line that says <code>#Include conf/extra/httpd-vhosts.conf</code> by removing the # sign. Now open up httpd-vhosts.conf file that is located in "C:\Apache2\conf\extra". There are two sample virtual hosts defined. Lets comment them both out. Alternatively you can just delete them. <code> <VirtualHost *:80> ServerAdmin webmaster@dummy-host.example.com DocumentRoot "c:/Apache2/docs/dummy-host.example.com" ServerName dummy-host.example.com ServerAlias www.dummy-host.example.com ErrorLog "logs/dummy-host.example.com-error.log" CustomLog "logs/dummy-host.example.com-access.log" common </VirtualHost> <VirtualHost *:80> ServerAdmin webmaster@dummy-host2.example.com DocumentRoot "c:/Apache2/docs/dummy-host2.example.com" ServerName dummy-host2.example.com ErrorLog "logs/dummy-host2.example.com-error.log" CustomLog "logs/dummy-host2.example.com-access.log" common </VirtualHost> </code> should look like this: <code> #<VirtualHost *:80> # ServerAdmin webmaster@dummy-host.example.com # DocumentRoot "c:/Apache2/docs/dummy-host.example.com" # ServerName dummy-host.example.com # ServerAlias www.dummy-host.example.com # ErrorLog "logs/dummy-host.example.com-error.log" # CustomLog "logs/dummy-host.example.com-access.log" common #</VirtualHost> # #<VirtualHost *:80> # ServerAdmin webmaster@dummy-host2.example.com # DocumentRoot "c:/Apache2/docs/dummy-host2.example.com" # ServerName dummy-host2.example.com # ErrorLog "logs/dummy-host2.example.com-error.log" # CustomLog "logs/dummy-host2.example.com-access.log" common #</VirtualHost> </code> Now lets add a new entry for our test server <code> <VirtualHost *:80> DocumentRoot "C:/websites/railotest" ServerName railotest ErrorLog "logs/railotest.com-error.log" CustomLog "logs/railotest-access.log" common </VirtualHost> </code> Now save the files and lets try running apache and see if it worked. Open up command prompt (Start -> Run -> cmd.exe) <code> Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>cd \apache2\bin C:\Apache2\bin>httpd httpd: Could not reliably determine the server's fully qualified domain name, using xxx.xxx.xxx.xxx for ServerName </code> We can ignore that warning since we don't care about the default configuration. Now we will need to define a host called railotest using windows hosts file. Open up "C:\windows\system32\drivers\etc\hosts" file in your favorite text editor. After a bunch of comments, you should see <code> 127.0.0.1 localhost </code> Lets add an entry for railotest <code> 127.0.0.1 railotest </code> Now this computer knows that railotest points to 127.0.0.1. Lets put a test cfm file in the webroot for railotest. Create a new file called index.cfm and put it in c:\websites\railotest. Inside the file lets put some basic cf code <code> <cfdump var="#server#"> </code> If you still have apache running and put in http://railotest in your browser you should see the code being output. It is not being interpreted yet because we have not hooked up Apache httpd to Railo. We will do this in Part IV. For now lets set up apache to run as a service. First stop the httpd that you ran earlier by entering ctrl-c and do the following. <code> C:\Apache2\bin>httpd -k install Installing the Apache2.2 service The Apache2.2 service is successfully installed. Testing httpd.conf.... Errors reported here must be corrected before the service can be started. httpd: Could not reliably determine the server's fully qualified domain name, using xxx.xxx.xxx.xxx for ServerName </code> The Apache service is now installed. I recommend also adding the "Apache Monitor" app to your startup folder. Click Start->All Programs and right click on Startup. Now click "Explore All Users". In another explorer window open up C:\Apache2\Bin and right drag ApacheMonitor.exe to the Startup folder. Let go of the right mouse button and select "Create shortcut here". Double click on the shortcut and the monitor App should appear in your taskbar next to the clock and next to Tomcat's icon. Double click it to open it and click start. Now you have a working Apache installation that will start as a service. If you enter http://railotest in your browser, you should see the code we wrote earlier. This will persist across reboots. In the next part, we'll hook it up to Railo and be able to actually execute this code. Windows x64 Windows 2003 ColdFusion Tomcat Railo Wed, 02 Dec 2009 17:47:00 -0400 http://www.ruslansivak.com/2009/12/2/Railo-on-Tomcat-on-Windows-x64--Part-III http://www.ruslansivak.com/2009/12/2/Railo-on-Tomcat-on-Windows-x64 I tried following <a href="http://corfield.org/blog/index.cfm/do/blog.entry/entry/Railo_for_Dummies_Part_III">Sean Corfield's excellent post</a> on how to get Railo running on Tomcat, but ran into a few snags on my x64 windows system. First download <a href="http://tomcat.apache.org/download-60.cgi">Tomcat 6</a> from the Apache Foundation. I picked the "Windows Service Installer" of the Core. Start up the installer and hit next a few times until you get to the "Choose Components" section. Select Full install and then uncheck the Examples item as we won't be needing it. Pick the installation folder, and the default port, and set a password for the administrator. At the next step it will ask for a path to a J2SE 5.0 JRE installation. Finding this on Sun's site is a bit of a pain, so here is a link to the <a href="http://java.sun.com/javase/downloads/5u22/jre">J2SE 5.0 Update 22</a>, which is the latest as of this writing. Download it, install it and make a note of what folder it installs in. In my case it was "C:\Program Files\Java\jre1.5.0_22". This is the path I provided to Tomcat installer. Finish the tomcat installation and you will see that the service is installed, but will not start. This is because we need the <a href="https://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/res/procrun/amd64/">64bit service wrapper</a> The only file that should be in there is tomcat6.exe. Download it and replace the one in your tomcat's installation bin folder. In my case that folder is "C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0\bin". Now if you go to "http://localhost:8080/", you should see The Tomcat default start page. In part II, we will cover getting setting up Apache. Windows x64 ColdFusion Railo Wed, 02 Dec 2009 16:15:00 -0400 http://www.ruslansivak.com/2009/12/2/Railo-on-Tomcat-on-Windows-x64 http://www.ruslansivak.com/2009/8/4/Windows-Server-2003-SP2-with-Firefox-35--downloads-Cancelled It seems that the new versions of Firefox have started to respect the server's security policy. I would usually use firefox to download things on a server to avoid having to deal with IE's enhanced security. The solution is to change the Internet zone to medium instead of high. This option, however, is disabled by default if you have "Internet Explorer Enhanced Security" installed. This option can be uninstalled from the control panel "Add/Remove Programs'" Add Remove Windows Components option. After uninstalling, restart firefox and you should be able to download again. Windows 2003 Tue, 04 Aug 2009 13:56:00 -0400 http://www.ruslansivak.com/2009/8/4/Windows-Server-2003-SP2-with-Firefox-35--downloads-Cancelled http://www.ruslansivak.com/2009/7/30/XenServer-Converting-Local-Storage-to-NFS-and-thereby-enabling-sparse-provisioning XenServer will create sparse disks for your VMs only on NFS based volumes. If you are using ISCSI or local storage, it will fully allocate each disk. This is less of a problem when you have a thinly provisioned ISCSI volume which is also compressed (such as those provided by Nexenta/OpenSolaris), but when you have a limited amount of local storage, it's unfortunate that XenServer doesn't give you the option to create sparse disks. Luckily, XenServer is just CentOS 5 under the hood, and we can turn the local storage into an NFS volume. First we will need to delete the current Local Storage, which involves quite a few steps. <code> #lvdisplay --- Logical volume --- LV Name /dev/VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2/MGT VG Name VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 LV UUID HlifV3-7B6J-rVCp-pAxP-Rc7e-viEQ-Tt819a LV Write Access read/write LV Status NOT available LV Size 4.00 MB Current LE 1 Segments 1 Allocation inherit Read ahead sectors auto </code> Now we run xe pbd-list and find the one that matches our local SR. <code> #xe pbd-list uuid ( RO) : e06a37a5-e1e6-4415-134e-f5ae4f7f7c17 host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): fc8c8fc5-4a06-18b9-517d-f19a18e50820 device-config (MRO): location: /dev/xapi/cd currently-attached ( RO): true uuid ( RO) : 7a75d1b9-9aa5-d5f7-6b85-50d1175054c8 host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): a6db482a-5446-3fc3-6513-6933eb9d7915 device-config (MRO): location: /dev/xapi/block currently-attached ( RO): true uuid ( RO) : 6c1eeeb0-3c05-fbee-4dca-e7490e007504 host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): f663b0ec-56b0-72dc-d546-4e0fc9be7ef6 device-config (MRO): location: /opt/xensource/packages/iso; legacy_mode: true currently-attached ( RO): true uuid ( RO) : 825bc0eb-8ec9-01ab-e249-21146d66dd9a host-uuid ( RO): 99ae2c2e-b992-4b4d-a09d-15cba5483225 sr-uuid ( RO): 877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 device-config (MRO): device: /dev/disk/by-id/scsi-SATA_WDC_WD800JD-75M_WD-WMAM9AJ38489-part3 currently-attached ( RO): true </code> As we can see, it's the last one. Now we unplug it and destroy it. <code> #xe pbd-unplug uuid=825bc0eb-8ec9-01ab-e249-21146d66dd9a #xe pbd-destroy uuid=825bc0eb-8ec9-01ab-e249-21146d66dd9a </code> Now lets destroy the storage repository attached to it. First we get a list of the repositories. <code> #xe sr-list uuid ( RO) : a6db482a-5446-3fc3-6513-6933eb9d7915 name-label ( RW): Removable storage name-description ( RW): host ( RO): xenserver-ueyqfddq type ( RO): udev content-type ( RO): disk uuid ( RO) : fc8c8fc5-4a06-18b9-517d-f19a18e50820 name-label ( RW): DVD drives name-description ( RW): Physical DVD drives host ( RO): xenserver-ueyqfddq type ( RO): udev content-type ( RO): iso uuid ( RO) : 877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 name-label ( RW): Local storage name-description ( RW): host ( RO): <not in database> type ( RO): lvm content-type ( RO): user uuid ( RO) : f663b0ec-56b0-72dc-d546-4e0fc9be7ef6 name-label ( RW): XenServer Tools name-description ( RW): XenServer Tools ISOs host ( RO): xenserver-ueyqfddq type ( RO): iso content-type ( RO): iso </code> We will delete the one called local storage. <code> #xe sr-forget uuid=877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 </code> At this point it will be forgotten and disappear from XenCenter. Now, lets delete it from LVM. <code> #vgdisplay --- Volume group --- VG Name VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 66.85 GB PE Size 4.00 MB Total PE 17113 Alloc PE / Size 1 / 4.00 MB Free PE / Size 17112 / 66.84 GB VG UUID 2PJJkR-ULpa-1F6f-8H65-N22A-o11C-f0KkGa </code> Now lets remove it. <code> #vgremove VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2 Do you really want to remove volume group "VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2" containing 1 logical volumes? [y/n]: y Logical volume "MGT" successfully removed Volume group "VG_XenStorage-877a1f66-59dd-b1ba-0de3-d8a753d0a0b2" successfully removed </code> <code> #pvdisplay "/dev/sda3" is a new physical volume of "66.86 GB" --- NEW Physical volume --- PV Name /dev/sda3 VG Name PV Size 66.86 GB Allocatable NO PE Size (KByte) 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID ZK23c0-UvDg-A4MB-TWKi-YfNW-hWUK-uoyqdo </code> Now we remove the physical volume from LVM. <code> #pvremove /dev/sda3 Labels on physical volume "/dev/sda3" successfully wiped </code> Now lets create a filesystem for us to use. <code> mkfs.ext3 -m 0 /dev/sda3 mke2fs 1.39 (29-May-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 8765440 inodes, 17526915 blocks 0 blocks (0.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 535 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 33 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. </code> Now lets set up a folder for it and make sure it gets mounted at boot time. <code> #mkdir /data </code> <code> #vi /etc/fstab LABEL=root-cjfffcbq /ext3 defaults 1 1 /var/swap/swap.001swap swap defaults 0 0 none/dev/pts devpts defaults 0 0 none/dev/shm tmpfs defaults 0 0 none/proc proc defaults 0 0 none/sys sysfs defaults 0 0 </code> We need to add our directory to automatically mount at boot time. Lets add this entry <code> /dev/sda3 /data ext3 defaults 1 2 </code> This is how my file looked like at the end. <code> /ext3 defaults 1 1 /var/swap/swap.001swap swap defaults 0 0 none/dev/pts devpts defaults 0 0 none/dev/shm tmpfs defaults 0 0 none/proc proc defaults 0 0 none/sys sysfs defaults 0 0 /dev/sda3 /data ext3 defaults 1 2 </code> Now lets try mounting it. <code> #mount /data </code> If you get no output, that means it probably worked. Lets check that it mounted successfully. <code> #ls /data lost+found </code> Now lets create our directories that we will export. <code> #mkdir /data/vm #mkdir /data/iso </code> Lets edit the exports file. <code> #vi /etc/exports </code> The file should initially be empty. Lets add our entries. <code> /data/vm 127.0.0.1(rw,no_root_squash,sync) /data/iso 127.0.0.1(ro,no_root_squash,sync) </code> Save the file, and now lets start the nfs and portmap services. <code> #service nfs start Starting NFS services: [ OK ] Starting NFS daemon: [ OK ] Starting NFS mountd: [ OK ] #service portmap start Starting portmap: [ OK ] </code> Lets make sure that the portmap and nfs services start at boot. <code> #chkconfig --level 345 nfs on #chkconfig --level 345 portmap on </code> Lets verify that our directories are being exported. <code> #exportfs /data/iso 127.0.0.1 /data/vm 127.0.0.1 </code> Now we can add the Storage Repository. We can do it through XenCenter. Right click on the server in XenCenter, and click "New Storage Repository". Select "NFS VHD" as the type, and enter the following parameters. <code> Name: NFS Local Storage Share Name: 127.0.0.1:/data/vm Leave the checkbox on "Create a New SR" and click "Finish". </code> Lets add an ISO SR as well. Right click on the server in XenCenter, and click "New Storage Repository". Select "NFS ISO" as the type, and enter the following parameters. <code> Name: NFS Local Storage Share Name: 127.0.0.1:/data/iso Leave the checkbox on "Create a New SR" and click "Finish". </code> Now we reboot and if everything comes back up, we are done. Now when we create VMs, the Virtual Hard Disks will be allocated sparsely, and VMs created from templates, will all use the same base VHD and only store the changes in their own disk. XenServer Thu, 30 Jul 2009 11:24:00 -0400 http://www.ruslansivak.com/2009/7/30/XenServer-Converting-Local-Storage-to-NFS-and-thereby-enabling-sparse-provisioning http://www.ruslansivak.com/2009/7/29/Jumbo-Frames-with-XenServer-55 There doesn't seem to be any way to configure jumbo frames with XenServer 5.5, and I'm sure this is unsupported, but it can be done by hacking the XenServer 5.5 config files. <code> #vi /opt/xensource/libexec/interface-reconfigure +879 </code> You will see something like this <code> f.write('"\n') return f </code> We are going to add our MTU information there: <code> f.write('"\n') #add MTU f.write('MTU=9212\n'); return f </code> 9212 is the MTU I chose, make sure you choose one that's appropriate for your network, and make sure to test it first. This will only change the MTU on the bonded interfaces, I believe. XenServer Wed, 29 Jul 2009 23:37:00 -0400 http://www.ruslansivak.com/2009/7/29/Jumbo-Frames-with-XenServer-55 http://www.ruslansivak.com/2009/7/22/Webmin-on-OpenSolaris After installing webmin from the package manager, you will need to run <code> webminsetup </code> to generate the appropriate config files. OpenSolaris Wed, 22 Jul 2009 14:01:00 -0400 http://www.ruslansivak.com/2009/7/22/Webmin-on-OpenSolaris http://www.ruslansivak.com/2009/7/22/locate-on-OpenSolaris Solaris has an alternate version of locate, called slocate. updatedb is still called the same, just instead of locate, you would call slocate. OpenSolaris Wed, 22 Jul 2009 13:52:00 -0400 http://www.ruslansivak.com/2009/7/22/locate-on-OpenSolaris http://www.ruslansivak.com/2009/7/15/CentOS-53-on-XenServer-55-Graphical-Install In order to do a graphical install (which lets you customize your LVM volumes) you just need to add the vnc option to the "OS Boot Parameters" when creating the VM. It should look like this: <code> graphical utf8 vnc </code> Once you start up your VM, it will go through a short text based configuration wizard, configuring your NIC and such, after which it will prompt you to log in using VNC. Virtualization XenServer CentOS Wed, 15 Jul 2009 22:45:00 -0400 http://www.ruslansivak.com/2009/7/15/CentOS-53-on-XenServer-55-Graphical-Install http://www.ruslansivak.com/2009/7/15/Urchin-5--Opening-reports-in-the-same-window By default Urchin 5 seems to want to open reports in a new window. This can be a little annoying. To change this, we just need to update the javascript function that gets run when you click on the "View Report" link. <code> vi /usr/local/urchin/htdocs/ujs/admin.js +434 </code> You should see the following code: <code> mywin = window.open('',myname); mywin.location.href = url; mywin.focus(); </code> We're going to comment it out and add our own code: <code> //mywin = window.open('',myname); //mywin.location.href = url; //mywin.focus(); window.location.href=url; </code> After clearing our cache, the reports open in the same window. Urchin Wed, 15 Jul 2009 13:54:00 -0400 http://www.ruslansivak.com/2009/7/15/Urchin-5--Opening-reports-in-the-same-window