Showing headlines posted by dba477

Due to known bug virt-install was broken on Ubuntu 8.04 since day of it’s GA and never has been fixed as far as to my knowledge. However, xen-enabled ISO’s like RH’s ones allow to perform PV Guest install via pygrub and repository placed on Apache Server running at Dom0. Notice, that virtual frame buffer would work fine for CentOS PV at Ubuntu Hardy Dom0 (2.6.24-21-xen).

The procedure down here has been developed due to virt-install failure to handle OpenSuse 11 PV DomU install at Xen 3.3 (3.2),(3.1) CentOS 5.2 Dom0 either via NFS or HTTP shared directory. Perform initial connect to Apache Server running at Dom0 , deployment and configuration (until first DomU reboot) via profile openSUSE11PV.cfg When OpenSuse DomU first time goes down for reboot, shutdown Suse DomU via “xm” and switch to pygrub profile for loading scp'ed images created via vm-install at OpenSuse 11 Dom0.

It’s well known that OpenSuse’s utility vm-install fails to perform RH PV guests install via NFS shares. Install from Internet repositories requires software download about 4GB of data for any CentOS 5.X of Fedora PV DomU. Corresponding ISO images have been copied to CentOS 5.2 box running Apache HTTP Server and located on same LAN. Then this images were loop mounted to corresponding folders under /var/www/html. This procedure provided an option for vm-install (via http) RH PV Guests at Xen 3.2.1 OpenSuse 11 Dom0 in pretty short time frame about 40-50 minutes for every DomU been installed.

Posting bellow describes setup Ubuntu Hardy PV DomU via attacment block device to Ubuntu Hardy HVM DomU at the same CentOS 5.2 Dom0. Standard debootstrap procedure has been used to create initial image on this device. This step allows to avoid “scp” image files from remote Ubuntu HH box to Dom0 and use /dev/sda(X) with prepared image immediately on the same box,referencing the same device from Ubuntu Hardy PV profile.

Port Xen 3.3 to CentOS 5.2 has been done via http://www.gitco.de/repo/xen3.3.0 . Install CentOS 5.2 PV DomU via virt-install utilizing NFS share with mounted loop DVD ISO image. Create profile PV DomU as follows not using vfb at this time and setup “vnc” at DomU afterwords.

Debian Etch install took about 2 hr on the box with C2D E8400, 8 GB RAM built up on P5K Premium/WIFI board. South Bridge ICH9R has been setup to AHCI mode with 2×250 SATA drives attached. dom0_mem was set to 4GB in /boot/grub/grub.conf. Debian HVM allocated 2 GB memory , Ubuntu 8.04.1 HVM 2.5 -3 GB memory . In case Ubuntu HH Desktop stub domain install it’s important to have enough memory on the box for Dom0 and DomU.

Working through weekend brought some positive results. However, kernel = “/usr/lib/xen/boot/ioemu-stubdom.gz” and device_model = ‘/usr/lib/xen/bin/stubdom-dm’ for HVM Domains show slow performance vs traditional approach for HVM DomUs creating at Xen 3.3 Linux Dom0s.

We use the most recent Xen 3.3 port to CentOS 5.2 via http://www.gitco.de/repo/xen3.3.0. Prepare grub's /boot/grub/menu.lst at DomU side for pv-grub booting.

Due to known issue attempt to virt-install OpenSuse 11 PV DomU at Xen 3.3 CentOS 5.2 Dom0 from nfs share fails immediately at startup. Approved procedure via Internet repositories for OpenSuse 10.3 requires internet connection speed at least 700 Kbit/sec to take reasonable time. OpenSuse 11.1 (with pygrub implemented) is due only in December 2008.However, pygrub coming along with current Xen Release 3.3(3.2.1) does allow to load OpenSuse 11 DomUs at CentOS 5.2 (RHEL 5.2) Dom0 with no problems.

This posting follows up the recent one Vncserver on SNV97 DomU at Xen 3.3 CentOS 5.2 Dom0 (64-bit) and is targeting enabling Sun's Java Web Start in FireFox 3.0.1 Web Browser with 32-bit JRE 6.0 plugin installed on 64-bit Linux. First of all install 32-bit Sun JRE 6.0 for Linux by running ./jre-6u-linux-i586-rpm.bin.Then install FireFox 3.0.1 into folder /usr/tmp/firefox for instance Create following symlink to make firefox aware of JRE.

Sun Xvnc implementation for Nevada, committed in build 76 provides 3 options in general. Third one is to start vncserver by hands. It allocates two ports 580(X) and 590(X), where (X) is available display number.Port 580(X) may be used for http://IP-DomU:580(X) connection to DomU , port 590(X) may be used by vncviewer IP-DomU:(X) connection. Both ways initiate loading Java Applets from DomU into Dom0. Connection via vncviewer has been selected on CentOS 5.2 Dom0 due to issue with Java Web Start and FireFox on 64-bit Linux. By some reasons first and second options provided by official Sun Xvnc failed on SNV97 DomU, successfully installed via pygrub in text mode as usual

Mentioned Xen port to CentOS 5.2 (64-bit) brought up daemons libvirtd and dnsmasq at Dom0. It makes patching of libvirt,libvirt-devel,libvirt-python packages and brings utility virt-install along with Xen 3.3 Hypervisor to system at a time.

Technical exercise bellow is targeting testing Jboss-Seam 2.0.2 SP1 with NetBeans 6.1 (JDK 6.0) to deploy Brian Leonard's Sample to Jboss 4.2.3 on Solaris Nevada ( build 96) with xVM kernel.Hibernate has been selected as persistence provider. Oracle 10gR2 database instance has been installed on SNV93 DomU for performance evaluation.

CentOS 5.2/RHEL 5.2 comes with a very highly modified Xen 3.03 which if I'm correct is in fact Xen 3.1 backported. If you wan to use the latest Xen 3.2.1 you need to update the hypervisor. This tutorial is for x86_64 because that's what I'm running on grantmcwilliams.com. If you want the 32 bit version modify the appropriate paths and file names.

ASUS P5K Premium/WIFI, P5K3 Deluxe,P5K Deluxe P5E3 Deluxe,Abit IP35 Pro,Gigabyte GA-P35-DQ6,MSI P35 Platinum have integrated on the board Realtek's NICs RTL8110SC/RTL8111B. RTL8110SC/RTL8111B (vs Marvell 88E8056 first NIC integrated on ASUS boards) are GLDv3 NICs and may be used for Solaris xVM PV and HVM DomUs creation at Solaris (Nevada) Dom0. However, disabling checksum offloading on Linux DomU front end network driver (eth0) is required to get network on DomU.

Following bellow is step by step procedure of SNV93 PV DomU install at SNV93 Dom0. Actually, all work to be done was performed at SolatisPV Serial Console, ending up with Sun Xvnc setup to provide graphical interface to SNV93 PV DomU. ZFS file system has been used as root image, installation source was set to a local path to SNV93 DVD ISO image.

Mentioned Xen port to CentOS 5.2 (64-bit) brought up daemons libvirtd and dnsmasq at Dom0, providing network bridging and NAT forwarding between Dom0 and DomUs. It also installs on the system command line utility virt-install.

The sample bellow briefly demonstrates attaching SXDE ISO images to SNV_93 DomU as a block oriented device which could be mounted afterwards on /mnt folder at DomU to support Sun Studio 12 Express install on PV DomU via graphical interface provided by Sun Xvnc implementation.

ASUS boards P5K Premium/WIFI, P5K3 Deluxe, P5E3 Deluxe have as second NIC integrated on the board RTL8110SC. RTL8110SC (vs Marvell Yukon) is GLDv3 NIC and may be used for Solaris xVM PV and HVM DomUs creation at Solaris (Nevada) Dom0. However, straight forward attempt to install SNV DomU in DHCP mode will time out at DHCP request phase due to failure checksum offloading on Realtek 8110SC.

Procedure described bellow installs packages mercurial, dev86, python-virtinst, virt-viewer. Virt-install as well as pygrub and hvmloader appear to be completely functional on Xen 3.2.1 F8 Dom0 and allow to create PV and HVM guests like on enterprise class system. Commands like xm start/stop/shutdown/reboot DomainName provide ability to manage created domains as on native Xen 3.1 F8 Dom0.