Tuesday, November 20, 2007


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