Showing headlines posted by dba477

This posting attempts to address several issues raised up during the recent discussion at Lxer.com. View:- OpenSolaris 2008/05 Live CD worked for me just now
Install on bare metal is quite simple if OpenSolaris HCL has been consulted before it began.
Create installation profile for OS200805 HVM Guest ...

Install Ubuntu 8.04 Xen Server (amd64) as was recently advised by Todd Deshane in his notes @LiveJournal.com. To configure startup profile for Solaris Nevada build 87 at Ubuntu 8.04 Server Dom0 perform losetup of ISO image of Solaris DVD and change disk entry ....

For details that I might be missing a good resource is: http://howtoforge.com/ubuntu-8.04-server-install-xen-from-ub...
I will clean this up and do more testing when I have time
Any problems, questions leave a comment or post to the xen-users mailing list.
Also, this is just proof of concept, in production I would recommend things like LVM and network storage solutions like AoE, iSCSI, and DRDB.

Install OpenSolaris 2008/05, based on Nevada build 86, requires workaround recently suggested by Jurgen Keil.It's runtime profile differs from reqular one due to utilizing ZFS filesystem (vs UFS for regular Nevada builds) as was noticed by Mark Jonson at xen-discuss forum @opensolaris.org. Place OpenSolaris 2008/05 DVD in drive, wait until gets mounted and run ..

Instal HVM FreeBSD 7 DomU as usual hangs at Xen 3.2 (Xen 3.1) Linux Dom0s, in case when box has been built up with Intel CPU.Workaround bellow is not required by Xen 3.2 Linux Dom0s running on AMD Dual Core Chips and is quite neccessary for Linux Dom0s running on Core2Duo E8X00,E6X50,...

Nevada build 85 id the first SNV build implementing Xen 3.1.2 bits. It's well known that straight forward attempt to install SNV85 DomU at Xen 3.2 Linux Dom0 immediatelly crashes due to broken by Xen 3.2 backward compatibility.

Build 85 is the first Nevada build with xen 3.1.2 bits implemented. Several issues have been inspired due to this changes : 1. Install SNV 85 DomU at Xen 3.2 Linux Dom0 (CentOS 5.1,Ubuntu 7.10) crashes immediately due to broken by Xen 3.2 backward compatibility...

This posting is targeting cloning Mercurial Repository for Xen 3.2 on Ubuntu 7.10 Desktop (64-bit) and creating 64-bit Xen 3.2 Ubuntu 7.10 Desktop Dom0. To verify Dom0 functionality Solaris (Nevada Build 84) has been installed and tested as DomU. Looks like same procedure at Ubuntu 7.10 Server (amd64) differs from described above.

This posting follows up "Install Solaris (SNV 84) DomU at Xen 3.2 CentOS 5.1 Dom0 (64 bit)" and provides brief description how to install 64-bit Solaris 01/08 HVM DomU at Xen 3.2 CentOS 5.1 Dom0 (64-bit as well) despite installer puts this HVM in 32-bit mode by default.

This posting is targeting cloning Mercurial Repository for Xen 3.2 on CentOS 5.1 and creating 64-bit Xen 3.2 CentOS 5.1 Dom0. To verify Dom0 functionality Solaris (Navada Build 84) has been installed as DomU. Xvnc has been set up per Sun manuals and it appeared that only CDE Desktop was functional on DomU. Gnome Desktop crashed immediately after logging in. However , that’s quite enough to perform Oracle 10g R2 installation at DomU and evaluate I/0 performance provided by new Xen Hypervisor for Solaris Paravirtual guests

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..