Showing headlines posted by dba477

The next major production release of Ubuntu — version 8.04 LTS, codenamed Hardy Heron — will ship with KVM as its virtualization package. This choice is surprising to those of us who have been watching the Xen virtualization package become the darling of Virtual Machine world. So let’s try to make sense out of the KVM virtual machine and this recent choice by Ubuntu.

In all prior Fedora releases fullyvirtualized Xen guests had to boot via the QEMU BIOS. This means booting from a CDROM, harddisk, or Network PXE. Paravirtualized guests could always boot directly from a kernel and initrd. This allowed for fully automated guest installation since it allowed the tools to pass arguments straight into anaconda. KVM fullyvirtualized guests also support direct kernel booting.

What’s this pv_ops business all about? Well, as Dan explained, for a long time we’ve been forward-porting Xensource’s (now 2.6.18 based) kernel tree in an effort to try and have our Xen kernel not lag behind Fedora’s bare-metal kernel. Now that the upstream kernel has gained the ability to run on Xen using pv_ops (but only as i386 DomU, currently) we’ve taken the decision to stop wasting our time forward porting Xensource’s tree and put all our focus into improving the feature set of pv_ops based Xen.

This posting follows up the recent one regarding same problems on F8. Xen implementation on CentOS 5.1 is not 3.1 all around as on F8 and doesn't allow to create Solaris DomUs with "pygrub". Here we need "xen manager" utility for original DomU creating.However, we can still benefit from "pygrub" power and flexibility creating runtime profiles for Solaris DomUs at CentOS 5.1 Dom0.

Procedure descibed bellow attaches Solaris DomU to libvirtd's daemon subnet 192.168.122.0 (netmask 255.255.255.0) utilizing interface virbr0 and dnsmasq service as DHCP server. It doesn't require DHCP bridge and external DHCP Server to turn on old fashion xen-bridging on F8 Dom0.

Recent posting by Jürgen Keil at OpenSolaris xen-discuss forum briefly states, that mentioned install runs without problems if disk entry of installation profile is referencing ISO image of SNV75A DVD. However, install Xen from Internet Repositories on Ubuntu 7.10 (x86_64) appears to be not quite trivial and was described by Bob Mertz in his blog .

After finding how-to upon how-to that said to use "apt-get install ubuntu-xen-server" and repeatedly banging my head against the wall because it kept telling me the package wasnt found, I finally found the Xen page at the Ubuntu Community site that explained the situation.

We are pleased to announce the immediate availability of CentOS-5.1 for the i386 and x86_64 Architectures. CentOS-5.1 is based on the upstream release 5.1, and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. And the option to further enable external repositories at install time is now available in the installer.

Originally SXDE 76 has been installed on second partition of first 160 GB SATA drive. First partition of this drive was used by Windows. Attempt to create third partition of type "Solaris2" by Solaris "fdisk" appeared to be useless for creating ZFS pool on x86 system. "format" kept showing two SATA drives ( 2x160 GB) been installed on PC at the time of assembling

The article "Installing Xen On CentOS 5.0 (i386)" by Falko Timme silently presume that you have at least ADSL Internet connection 700 Kb/sec due to following instruction for virt-install command line utility..

Starting with Solaris Express build 75(75a) xVM/Xen are included as a standard part of Solaris Express for x86/x64. Oracle's installation procedure seems to be a kind of evaluation performance and reliability for next generation Solaris Xen Drops running as DomUs on top of Linux Dom 0. Preferably CentOS 5 (RHEL 5) or Debian Etch 4.X .

Command "ipcs -m" appears to be almost useless for getting Oracle 11g shared memory allocation maps. The basic steps for shared memory monitoring and tuning /dev/shm to handle instances with MEMORY_TARGET more then 1024M had been explained in Tanel Poder’s blog. Posting bellow follows advices from Tanel Poder’s blog to build Oracle 11g (64 bit) ASM database with MEMORY_TARGET size 1.2 GB on CentOS 5.

The author shows how to install Windows on a Solaris system.

Installing OpenSUSE 10.3 on the box I selected Xen entry into Grub menu after first phase was completed and system rebooted for final configuration.It brought me into text mode setup very similar graphical one when you select ordinary kernel.

I just have decided , that snapshots of the most recent posts at OpenSolaris Xen Discuss forum would be the best form of advertising regarding upcoming Solaris Xen Drop.

This installation has been done to evaluate OUI (disk I/O) performance on OpenSolaris DomU versus OUI performance on Linux (CentOS 4.5,5.0) HVM VMs on the same box. Difference appears to be very noticeable.

This posting follows up “Install Xen 3.1 Solaris domU (64 bit) at CentOS 5 dom0 (64 bit)” at Lxer.com and gives step by step instruction how to set up VNC on OpenSolaris DomU. In general , everything seems to be already told in OpenSolaris documents.However, I believe that detailed instructions won't be useless at mean time.

In general installation bellow went the same way as in TardisWiki, considering Xen 3.0.3-1 Solaris domU under Debian Etch dom0 (32 bit).
However, several things happened different from described in TardisWiki.
1. Installation didn't hang all way through.
2. To preserve "bootadm update-archive -R /a" work i had to force "umount /a"

I come from a MySQL background, and I have been given the challenge of learning Oracle. I can’t just play around with our customers’ databases.So I decided to install my own Oracle database, which I’ll be free to destroy in every way I can think of… and of course, free to bring it back to life.

Installation has been done to evaluate HVM VM performance. CentOS 5 VM has been tuned exactly as advised at oracle-base.com. 1 GB memory was allocated for VM and it was installed on 16 GB partion (/dev/sdbX) of SATA HDD Seagate Barracuda 160 GB