Testing patch for "6633784 checksum offload with Linux dom0 produces invalid checksum" on SNV76 DomU at CentOS 5.0 Dom0 per David Edmondson

Please, view description of original bug affecting SNV66,75A,76,77:-

6633784 checksum offload with Linux dom0 produces invalid checksum


Testing environment:- Xen 3.1 SNV76 DomU at CentOS 5.0 Dom0 (x86_64).
Patch has been applied when system rebooted the first time after
fresh install. File /etc/system has never been touched.
Original file layout:-

# mkdir /mnt/tmp
# mkdir /usr/lib/xen-solaris
# cd /usr/lib/xen-solaris/
# mount -o loop,ro snv76.iso /mnt/tmp
# cp /mnt/tmp/boot/amd64/x86.miniroot  /usr/lib/xen-solaris/x86.miniroot-76
# cp /mnt/tmp/boot/platform/i86xpv/kernel/amd64/unix  /usr/lib/xen-solaris/unix-76
# umount /mnt/tmp
 

Installation profile SolarisInstall.conf :-

name = 'Solaris76'
memory = '1024'
disk = [ 'file:/usr/lib/xen-solaris/snv76.iso,6:cdrom,r', 'phy:/dev/sdb3,0,w' ]
vif = [ '' ]
on_shutdown = 'destroy'
on_reboot = 'destroy'
on_crash = 'destroy'
kernel = '/usr/lib/xen-solaris/unix-76'
ramdisk = '/usr/lib/xen-solaris/x86.miniroot-76'
extra = '/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom'
  

# xm create -c SolarisInstall.conf
  

Runtime profile SolarisRunTime.conf:-

name = 'Solaris76'
memory = '1024'
disk = [ 'phy:/dev/sdb3,0,w' ]
vif = [ '' ]
on_shutdown = 'destroy'
on_reboot = 'destroy'
on_crash = 'destroy'
kernel = '/usr/lib/xen-solaris/unix-76'
ramdisk = '/usr/lib/xen-solaris/x86.miniroot-76'
extra = '/platform/i86xpv/kernel/amd64/unix -kd'
root = '/dev/dsk/c0d0s0'
  

  

# xm create -c SolarisRunTime.conf
  

Patching xnf driver during SNV76 DomU booting up:-

SSH connection from SNV DomU to CentOS 5 Dom0:-

Patched SNV76 DomU at CentOS 5 Dom0 has been tested to work
on Internet through proxy server on remote host.

SNV DomU still properly communicates with remote proxy server :-)

Querying Oracle 10gR2 Instance running on patched SNV76 DomU from Linux Dom0:-

Shutdown patched SNV76 DomU:-

Install Oracle 11g on Fedora 7 DomU at SXDE 76 Dom0 (x64/x86)

First install F7 DomU. Size of image file ( f7pvm.img ) should be
at least 15 GB in case when OUI 11g database folder would be located
on NFS share. If you intend upload linux.x64_11gR1_database.zip on DomU
filesystem increase image size up to 20 GB to install all packages at a time
and reduce number of additional packages required afterwards :-

# lofiadm -a /export/home/isos/f7.iso
# mount -o ro -F hsfs /dev/lofi/1   /mnt
# share -F nfs  /mnt
# virt-install -n F7pvm -p -r 1024 --nographics  -x "console=hvc0"  \
     -f /second_root/images/f7pvm.img -l nfs:<IP-ADDRESS Dom0>:/mnt
  

When installer brings you to "Software to be installed" customization screen,
select option customize for the set of the packages to be placed on the system
and mark all groups except "Clusters".
When install will be completed following additional rpms
will have be downloaded from the Net and installed on F7 DomU

# rpm -Uvh libaio-0.3.106-3.2.x86_64 \
   libaio-devel-0.3.106-3.2.x86_64
# rpm -Uvh unixODBC-devel-2.2.12-2.fc7.x86_64.rpm
# rpm -Uvh sysstat-7.0.4-3.fc7.x86_64.rpm
  

Tune F7 DomU for Oracle 11g install as advised in [1], except
adding lines to /etc/pam.d/login, otherwise console login to
F7 DomU will be lost and more over F7 DomU will start malfunction.
Enable SSH X11 forwarding on F7 DomU to perform remote Oracle
installation with Cygwin/X remote Windows XP desktop.
Start X-Server and open X-terminal on Windows desktop and issue:-

$ xhost +<IP-ADDRESS DomU>
$ ssh -X oracle@<IP-ADDRESS DomU>
$ /mnt/runIstaller &
  

In my case remote nfs share , containing OUI database folder,
was previously mounted on /mnt directory of F7 DomU

When done verify remote connections to Oracle Instance at F7 DomU,
launching windows Internet explorer to

https://<IP-ADDRESS DomU>:1158/em/
  

Shutdown oracle and F7 domU:-

oracle@ServerFDR7$ emctl stop dbconsole
oracle@ServerFDR7$ dbshut $ORACLE_HOME
oracle@ServerFDR7$ su -
password:
# shutdown -y -i0 -g0
 

Run "xm list" at SXDE 76 Dom0 and make sure F7 DomU
has been shutdown.

# xm start F7pvm
# xm console F7pvm
 

Login as root to DomU:-

# su - oracle
oracle@ServerFDR7$ dbstart $ORACLE_HOME
oracle@ServerFDR7$ emctl start console
  

Verify connections to Oracle instance from Solaris 76 Dom0 :-

References
1.http://oracle-base.com

Install Oracle 10.2.0.2 on Solaris 10 (08/07) HVM at SXDE 76 Dom0

Configure the vnc password and default nic for xend service.
Run "dladm show-link" to determine default nic for xend service.

 
# svccfg -s xvm/xend setprop config/vncpasswd = astring: \"secret\"
# svccfg -s xvm/xend setprop config/vnc-listen = astring: \"0.0.0.0\"
# svccfg -s xvm/xend setprop config/default-nic="rtls0"
# svcadm refresh xvm/xend
# svcadm restart xvm/xend
  

Copy by "dd" ISO image of Solaris 10 (08/07) to /export/home/isos/solaris0807.iso
at SXDE 76 Dom0 and proceed with virt-install Solaris 10 HVM:-

Booting Solaris HVM the first time:-

Now we have to install two additional packages from S10 U4 DVD.
Perform at SXDE 76 Dom0 side:-

#  lofiadm -a /export/home/isos/solaris0807.iso
#  mount -o ro -F hsfs /dev/lofi/1   /mnt
#  share -F nfs  /mnt
  

At Solaris 10 ( 08/07) HVM DomU:

# mount -F nfs <IP-ADDRESS Dom0>:/mnt /mnt
# pkgadd -d /mnt/Solaris_10/Product SUNWi1cs SUNWi15cs
  

Proceed with tuning Solaris 10 ( 08/07) HVM as advised in [1]
for Oracle 10.2.0.2 install on Solaris 10 (32 bit).

1.Run OUI in advanced mode and select option "Install Software Only"








2.Run dbca and create a database








3.Run netca to create LISTENER and perform Local Network Names configuration

Perform Oracle Instance verification connecting from SXDE 76 Dom0 side:-

References.
1. http://oracle-base.com

Virt-install Windows XP HVM on Solaris xVM (build 76)

Make sure you have selected "Solaris xVM" option from Grub menu and issue:-

# svcs -a | grep xvm
 

Four "xvm/xend" services should be in online state.
Next step is supposed to be : configuration the vnc password and
running "dladm show-link" to determine default nic for xend service.
The NIC must support the GLD v3
To determine if a NIC is GLDv3, run:

# dladm show-link
  

and look for links that are not of type 'legacy'

 
# svccfg -s xvm/xend setprop config/vncpasswd = astring: \"secret\"
# svccfg -s xvm/xend setprop config/vnc-listen = astring: \"0.0.0.0\"
# svccfg -s xvm/xend setprop config/default-nic="rtls0"
# svcadm refresh xvm/xend
# svcadm restart xvm/xend
  

Use virt-install to install the windows domain.

# virt-install -n Winds --hvm -r 512 --vnc -f /second_root/dsk/winxp-dsk \
  -s 7  -c /export/home/ISO/winxp.iso
# vncviewer :0
  

When text mode phase completed Windows HVM Guest system reboots the first time.
It causes path to installation ISO image to be lost by "virt-install" on Solaris xVM.
This "virt-install" behavior is considered to be normal.
To resolve the issue with Windows HVM rebooting behavior :-
1. Run "xm delete Windows-Domain-Name"
2. Restart "virt-install" with original command line

 
# virt-install -n Winds --hvm -r 512 --vnc -f /second_root/dsk/winxp-dsk \
  -s 7  -c /export/home/ISO/winxp.iso
  

This action will successfully restart installation exactly at the point of failure :- entering second installation phase.
Second Windows HVM Guest system's reboot requires again VNC authorization and brings Windows HVM into running state.


Start Winds DomU at SNV76 Dom0 after installation:-

# xm start Winds
# vncviewer :0
  

Stop Winds DomU at SNV76 Dom0

# xm shutdown Winds
  

Uploaded by ftp from Solaris Dom0 to Windows DomU and got installed Real VNC 4.1 :-

VNC connect to SNV76 PVM running at the same Dom0:-

Connecting to Oracle instance running on SNV76 PVM:-

Install Xvnc on Xen 3.1 SXDE 76 DomU at CentOS 5 Dom0 (64 bit)

Quote:-

It is high time that Solaris ships with a supported Xvnc binary. VNC is a widely-used remote desktop protocol and standard. Currently, Solaris users who wish to start a vnc server from the command line must seek out and download or compile their own binary from a 3rd party such as RealVNC, TightVNC, or UltraVNC.

Instead of integrating a 3rd party open source implementation based on outdated or insecure Xserver bits, we should leverage our own Xorg source and modify an existing Xorg VNC patch as needed.


Test these three common ways of configuring Xvnc to run:

1) Starting on demand from inetd, displaying dtlogin login screen:

# Enable XDMCP connections on dtlogin by removing "-udpport 0" from args
# Warning: restart will kill all current dtlogin sessions!
svccfg -s cde-login setprop 'dtlogin/args=""'
svcadm restart cde-login
# Add xvnc service to /etc/services if it isn't already
printf "vnc-server\t5900/tcp\t\t\t# VNC Server\n" >> /etc/services
# Enable Xvnc inetd service:
inetadm -e xvnc-inetd

Connect from another machine with:
vncviewer hostname:0
and verify you see the login screen and can login to a desktop session.

2) Starting at system boot from dtlogin, displaying dtlogin login screen:

# Add a display1 instance of x11-server service for configuration
# and configure it to run Xvnc
svccfg -s application/x11/x11-server add display1
svccfg -s application/x11/x11-server:display1 addpg options application
svccfg -s application/x11/x11-server:display1 addpropvalue options/server astring: "/usr/X11/bin/Xvnc"
svccfg -s application/x11/x11-server:display1 addpropvalue options/server_args astring: '"SecurityTypes=None"'

# Configure dtlogin to start it
mkdir -p /etc/dt/config
cp /usr/dt/config/Xservers /etc/dt/config/Xservers
echo " :1 Local local_uid@none root /usr/X11/bin/Xserver :1" >> /etc/dt/config/Xservers
pkill -HUP dtlogin

Connect from another machine with:
vncviewer hostname:1
and verify you see the login screen and can login to a desktop session.

3) Starting manually, displaying session of user who started it, requiring
VNC password (separate from Unix login password, not securely encoded on
disk or across the network, so don't use a valuable password):

/usr/bin/vncserver -httpd

From another machine, open a web browser and go to
http://hostname:5802/

(Assuming vncserver said it was starting on display :2 - if it listed
another display number, change :5802 to 5800 + the display id.)

Enter the password you provided to the vncserver script when it asked
and verify you see a simple desktop session in the viewer


Written by Alan Coopersmith (10/17/2007)


First set of instructions has been reproduced on SXDE 76 DomU at CentOS 5.0 Dom0

# svccfg -s cde-login setprop 'dtlogin/args=""'
# svcadm restart cde-login
# printf "vnc-server\t5900/tcp\t\t\t# VNC Server\n" >> /etc/services
# inetadm -e xvnc-inetd
  

Command "vncviewer <IP-address of Solaris DomU>:0" was issued from Linux Dom0 side.


Several snapshots follow bellow:-

Second set of instructions was reproduced as well:-

Sun Xvnc implementation on SXDE 76 DomU at SXDE 76 Dom0.

First option:-

Second option:-

VNC connections from remote Linux box for first option:-

VNC connections from remote Linux box for second option:-

References.
1.http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6572087