Sunday, February 24, 2008


Pygrub & install Solaris (build >75) DomU at CentOS 5.1 Dom0 (x86_64)



Procedure described 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. Standard Solaris DomU notation vif=[' ']
would work fine on CentOS 5.1 and specifying DHCP for xnf0 interface will
successfully obtain IP address from dnsmasq service during original SNV DomU
installation.


Xen implementation on CentOS 5.1 allows to utilize pygrub as bootloader for Solaris
DomUs, already created by "xm" utility , what significantly simplifies creating runtime profiles for SNV DomUs and also will work for any build of OpenSolaris (76,78,79) regardless of "Bug 633784 checksum offload with Linux dom0 produces invalid checksum", been fixed in build 81.


First of all "yum update" has been run on CentOS 5.1 box.











[root@ServerRHL51 vm]# xm info
host : ServerRHL51
release : 2.6.18-53.1.13.el5xen
version : #1 SMP Tue Feb 12 13:33:07 EST 2008
machine : x86_64
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2137
hw_caps : bfebfbff:20000800:00000000:00000140:0000e3bd:00000000:00000001
total_memory : 2047
free_memory : 1025
xen_major : 3
xen_minor : 1
xen_extra : .0-53.1.13.el5
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
cc_compile_by : mockbuild
cc_compile_domain :
cc_compile_date : Tue Feb 12 12:55:35 EST 2008
xend_config_format : 2




***********************
Installation profile :
***********************



name = "Solaris81PVM"
vcpus = 1
memory = "1024"
kernel = "/usr/lib/xen-solaris/unix-81"
ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81"
extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom"
disk = ['file:/usr/lib/xen-solaris/snv81.iso,6:cdrom,r','phy:/dev/sda8,0,w']
vif = ['']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"




Go through installation procedure as usual, specifying DHCP for
network interface at Solaris DomU (xnf0).











Then create runtime profile utilizing "pygrub" as follows:-


********************
RunTime profile :
********************



name = "Solaris81PVM"
vcpus = 1
memory = "1024"

bootloader = "/usr/bin/pygrub"
kernel = "/platform/i86xpv/kernel/amd64/unix"
ramdisk = "/platform/i86pc/amd64/boot_archive"
disk = ['phy:/dev/sda8,0,w']
vif = ['']
on_shutdown = "destroy"
on_reboot = "restart"
on_crash = "destroy"












DHCP config for xnf0 at Solaris DomU:-








Connection via ssh from Solaris DomU to CentOS 5.1 Dom0
and getting "xm list -l SNV_DomU_Name" report :-








********************************
# xm list -l Solaris81PVM
********************************



[root@ServerRHL51 vm]# xm list -l Solaris81PVM
(domain
(domid 4)
(uuid 7c114a8a-5831-f2e9-1d45-fe40af47c41f)
(vcpus 1)
(cpu_weight 1.0)
(memory 1024)
(shadow_memory 0)
(maxmem 1024)
(bootloader /usr/bin/pygrub)
(features )
(name Solaris81PVM)
(on_poweroff destroy)
(on_reboot restart)
(on_crash destroy)
(image
(linux
(ramdisk /var/lib/xen/boot_ramdisk.WIVYhW)
(kernel /var/lib/xen/boot_kernel.xe3nxA)
(args /platform/i86xpv/kernel/amd64/unix)
)
)
(device (vif (backend 0) (script vif-bridge) (mac 00:16:3e:16:55:29)))
(device (vbd (backend 0) (dev 0:disk) (uname phy:/dev/sda8) (mode w)))
(state -b----)
(shutdown_reason poweroff)
(cpu_time 88.801468943)
(online_vcpus 1)
(up_time 161.828547955)
(start_time 1203905988.7)
(store_mfn 449776)
(console_mfn 449775)
)


Thursday, February 21, 2008


Pygrub & install Solaris (build >75) DomU at Fedora 8 Dom0 (x86_64)



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,
as was suggested in xen-discuss forum at opensolaris.org:-

Re: Xen 3.1 Linux Dom0 (x86_64) & PYGRUB



Xen implementation on Fedora 8 allows to utilize pygrub as bootloader for Solaris
DomUs, what significantly simplifies creating installation and runtime profiles for SNV DomUs and also will work for any build of OpenSolaris (76,78,79) regardless of
"Bug 633784 checksum offload with Linux dom0 produces invalid checksum", been fixed
in build 81.
Fedora 8 Dom0 (64-bit) has been installed on the box with static IP address.
File /etc/xen/xend-config.sxp was modified to set up a isolated bridge + NAT forwarding:-



# (network-script network-bridge)
#### LAPTOP USERS ! #####
# For laptops, or machines where network interfaces come/go on-the-fly,
# or are otherwise managed by NetworkManager, comment out the above line.
# Then, uncomment the line below, and use libvirt's virtual networking
# capability which sets up a isolated bridge + NAT forwarding
(network-script /bin/true)




This changes requires daemon xend restart.



**********************
Installation profile
**********************
name = 'Solaris81F8X'
memory = '1024'
disk = [ 'file:/usr/lib/xen-solaris/snv81.iso,6:cdrom,r','phy:/dev/sdb14,0,w']
vif = [ 'bridge = virbr0' ]
bootloader = '/usr/bin/pygrub'
kernel = '/boot/platform/i86xpv/kernel/amd64/unix'
ramdisk = '/boot/amd64/x86.miniroot'
extra = '/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom'




Report "xm list -l Solaris81F8X" running in the backend window demonstrates,
that virtual interface for SNV DomU install is attached to virbr0, what
guarantees DHCP request from SNV DomU to dnsmasq service to succeed and does
allow to avoid creating DHCP bridge on F8 box, wich consequently requires
external DHCP Server on the LAN to turn on old fashioned xen-bridging on F8 Dom0.











****************
Runtime profile
****************
name = 'Solaris81F8X'
memory = '1024'
disk = [ 'phy:/dev/sdb14,0,w' ]
vif = [ 'bridge = virbr0' ]















SSH connection from SNV81 DomU to F8 Dom0 and getting "xm list -l SNV_DomU_Name"
report.








References.
Install SNV81 DomU at Fedora 7 Dom0 (x86_64)

Saturday, February 16, 2008


Solaris 08/07 (64-bit) VMWare (1.0.4) VM on CentOS 5.1 (x86_64)



Install VMWare Server 1.0.4 on CentOS 5.1








Configure and install Solaris 08/07 VM:-








Starting up Solaris VM:-











Verifying network config (DHCP with NAT forwarding):-








Internet working:-








Solaris VMWare VM is ptretty much alive with following hardware config:-


C2D6850
ASUS P5K Prenium/WIFI-AP
4GB RAM
2x250 GB SATA Drives (Seagate Barracuda)


SNV76 HVM (32-bit) DomU at CentOS 5.1 Dom0 on same box shows up
a bit better performance , but not enough to quit development
at Solaris 08/07 VMWare Server's (1.0.4) VM.

Friday, February 15, 2008


Install SNV81 DomU at Fedora 8 Dom0 (i386)



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,
as was suggested in xen-discuss forum at opensolaris.org:-

Re: Xen 3.1 Linux Dom0 (x86_64) & PYGRUB



Fedora 8 Dom0 (32 bit) has been installed on the box with static IP address.
File /etc/xen/xend-config.sxp was modified to set up a isolated bridge + NAT forwarding:-



# (network-script network-bridge)
#### LAPTOP USERS ! #####
# For laptops, or machines where network interfaces come/go on-the-fly,
# or are otherwise managed by NetworkManager, comment out the above line.
# Then, uncomment the line below, and use libvirt's virtual networking
# capability which sets up a isolated bridge + NAT forwarding
(network-script /bin/true)




and:-



# service xend restart




Both services libvirtd and dnsmasq were up and running.
Interface virbr0 actived 192.168.122.1
SNV81 DomU installed with DHCP option on libvirtd's (dnsmasq) subnet.


In case when vif=[' ']


[root@fedora8xen vm]# brctl show



bridge name bridge id STP enabled interfaces
tmpbridge 8000.feffffffffff no vif6.0
virbr0 8000.000000000000 no




DHCP request to libvirtd's subnet timed out


In case when vif=['bridge = virbr0']



[root@fedora8xen vm]# brctl show
bridge name bridge id STP enabled interfaces
tmpbridge 8000.000000000000 no
virbr0 8000.feffffffffff no vif5.0




DHCP request to libvirtd's subnet succeeded in 1-2 minutes


Installation profile:-



name = 'Solaris81PVM'
memory = '1024'
bootloader = '/usr/bin/pygrub'
disk = [ 'file:/usr/lib/xen-solaris/snv81.iso,6:cdrom,r','phy:/dev/sdb11,0,w']
vif = [ 'bridge = virbr0' ]
kernel = '/boot/platform/i86xpv/kernel/unix'
ramdisk = '/boot/x86.miniroot'
extra = '/platform/i86xpv/kernel/unix - nowin -B install_media=cdrom'
on_shutdown = 'destroy'
on_reboot = 'destroy'
on_crash = 'destroy'




Command "xm list -l Solaris81" been executed in backend window reported, that bridge
used during installation was virbr0.








Runtime profile:-



name = 'Solaris81PVM'
memory = '1024'
disk = [ 'phy:/dev/sdb11,0,w' ]
vif = [ 'bridge = virbr0' ]













Thursday, February 14, 2008


Install SNV81 DomU at Fedora 7 Dom0 (x86_64)



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. It doesn't require DHCP bridge and external DHCP
Server to turn on old fashion xen-bridging on F7(8), as was suggested
in xen-discuss forum at opensolaris.org:-

Re: Xen 3.1 Linux Dom0 (x86_64) & PYGRUB



Fedora 7 Dom0 (64 bit) has been installed on the box with static IP address.
File /etc/xen/xend-config.sxp was modified to set up a isolated bridge + NAT forwarding:-



# (network-script network-bridge)
#### LAPTOP USERS ! #####
# For laptops, or machines where network interfaces come/go on-the-fly,
# or are otherwise managed by NetworkManager, comment out the above line.
# Then, uncomment the line below, and use libvirt's virtual networking
# capability which sets up a isolated bridge + NAT forwarding
(network-script /bin/true)




Then daemon xend has been restarted :-



# service xend restart




Both services libvirtd and dnsmasq were up and running.
Interface virbr0 actived 192.168.122.1
SNV81 DomU has been installed with DHCP option on libvirtd's (dnsmasq) subnet
192.168.122.0 (netmask 255.255.255.0).


In case when vif=[' ']


[root@fedora7xen vm]# brctl show



bridge name bridge id STP enabled interfaces
tmpbridge 8000.feffffffffff no vif5.0
virbr0 8000.000000000000 no




DHCP request to libvirtd's dhcp server (dnsmasq service) timed out


In case when vif=['bridge = virbr0']



[root@fedora7xen vm]# brctl show
bridge name bridge id STP enabled interfaces
tmpbridge 8000.000000000000 no
virbr0 8000.feffffffffff no vif6.0




DHCP request to libvirtd's dhcp server (dnsmasq service) succeeded in 1-2 minutes


Installation profile:-



name = "Solaris81"
vcpus = 1
memory = "1024"
kernel = "/usr/lib/xen-solaris/unix-81"
ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81"
extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom"
disk = ['file:/usr/lib/xen-solaris/snv81.iso,6:cdrom,r','phy:/dev/sdb7,0,w']
vif = ['bridge = virbr0']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"




Command "xm list -l Solaris81" been executed in backend window reported, that bridge
used during installation was virbr0.








Runtime profile:-



name = "Solaris81"
vcpus = 1
memory = "1024"
kernel = "/usr/lib/xen-solaris/unix-81"
ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81"
extra = "/platform/i86xpv/kernel/amd64/unix"
disk = ['phy:/dev/sdb7,0,w']
vif = ['bridge = virbr0']
root= "/dev/dsk/c0d0s0"
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"




Runtime snapshots :-














View also :-
Install SNV81 DomU at Fedora 8 Dom0 (i386)
64-bit Fedora Dom0 will be tested shortly.




Wednesday, February 06, 2008


Deployment SNV81 DomU to ZFS filesystem at SNV81 Dom0 on ASUS P5K Premium/WIFI



SNV81 Dom0 was installed on second partition of first SATA drive.
ZFS filesystem would be created on second SATA Drive .
Detection second drive by SNV81:-








format>fdisk
Fourth partition on second drive of type "Other"
has been created with fdisk








# zpool create pool c1t5d0p4
# zfs create -V 23G pool/snv81-dsk




Now proceed with virt-install:-



# virt-install -n Solaris81ZFS --paravirt -r 1024 \
--nographics -f /dev/zvol/dsk/pool/snv81-dsk \
-l /export/home/isos/snv81.iso






Virt-install runs just fine :-














When SNV81 DomU reboots the first time.
Add to /etc/system line :-



set xnf:xnf_cksum_offload = 0




Configure Sun Xvnc and reboot DomU one more time.
Snapshots bellow demonstrate ssh connection
from DomU to Dom0 and running:-
# xm list -l Solaris81ZFS
at Solaris DomU graphical desktop









Tuesday, February 05, 2008


Linux Dom0 vs SNV81 Dom0 when running SNV81 DomU.



Installing SNV81 DomU at Linux Dom0 you don't have anymore modify
file /etc/system, run "bootadm update-archive" and copy boot_archive
to Linux Dom0. However, installing SNV81 DomU at SNV81 Dom0
you have to add the same line as before:-



set xnf:xnf_cksum_offload = 0




to /etc/system on SNV81 DomU side and reboot DomU one more time.
When it gets done network between SNV81 DomU and SNV81 Dom0
will work fine. Two samples of installation procedures follow bellow.



Install Solaris (SNV81) at CentOS 5.1 Dom0 (x86_64)



Installation and runtime profiles for SNV81 DomU.








Starting up SNV81 DomU.











Runtime snapshots.









SSH connection to CentOS 5.1 Dom0 and running:-
# xm list -l Solaris81PVM








Internet working through remote Proxy Server on SNV81 DomU at CentOS 5.1 Dom0:-








Install SNV81 DomU at SNV81 Dom0.


View also:-
Install SNV81 DomU on ZFS filesystem at SNV81 Dom0



Start virt-install to create SNV DomU:-



# virt-install -n Solaris81PV --paravirt -r 1024 \
--nographics -f /export/home/images/solaris81.img -s 16 \
-l /export/home/isos/snv81.iso












When istallation completes and guest reboots the first time
add to /etc/system:-



set xnf:xnf_cksum_offload = 0




Configure Solaris Xvnc ([1]) and reboot SNV81 DomU.











Internet working through remote Proxy Server on SNV81 DomU at SNV81 Dom0:-








References.
1.http://librenix.com/?inode=11382

Monday, February 04, 2008


Install Solaris (SNV81) at CentOS 5.1 Dom0 (x86_64)



Installation and runtime profiles for SNV81 DomU.








Starting up SNV81 DomU.











Runtime snapshots.









SSH connection to CentOS 5.1 Dom0 and running:-
# xm list -l Solaris81PVM








Internet working through remote Proxy Server on SNV81 DomU.