http://www.opensolaris.org/os/downloads/on/The docs for xVM are here: http://opensolaris.org/os/community/xen/docs/
| Every paragraph is marked with a stamp like this: | [24.07.07 Xen 07_2007] |
| Every link is marked with a stamp like this: | [19.01.06] |
| Infos from other sources (like Blogs or Mailing lists) are marked with a stamp like this: | (Source: Casper Dik, 14.01.06 [19.01.06]) |
| This text was taken from another
source |
| Date |
Adapter |
Chipset,
Manufacturer |
Device
driver in Solaris |
Comment |
| 05.08.07 |
Broadcom |
bge | own experiences, Project nemo home page [06.08.07] | |
| 06.08.07 |
Intel |
e1000g |
Project
nemo home page [06.08.07]
|
|
| 06.08.07 |
Neterion |
xge |
Project nemo home page [06.08.07] | |
| 06.08.07 |
nVidia |
nge |
Project nemo home page [06.08.07] | |
| 06.08.07 |
Realtek |
rge |
Project nemo home page [06.08.07] | |
| 06.08.07 |
Intel |
ixgb |
Project nemo home page [06.08.07] | |
| 24.12.07 |
Marvell Yukon gigabit ethernet adapter and the skge driver from SysKonnect | Works with the driver
from Masayuki Murayama [24.12.07] compiled for GLDv3 ; see this blog
entry [24.12.07] for comile instructions. |
Network adapter from Sun that can be used:
X7286A Sun PCI-X GigE MMF Low Profile Intel 1x Fiber PCI-X NIC (PLC 5667)
X7285A Sun PCI-X Dual GigE UTP Low Profile Intel 2x UTP PCI-X NIC (PLC 5666)
X7281A-2 Dual Gigabit Ethernet MMF Intel 2x Fiber PCIe NIC (Northstar MMF)
X7280A-2 Dual Gigabit Ethernet UTP Intel 2x UTP PCIe NIC (Northstar UTP)
X9273A Quad Ethernet Controller Intel 4x UTP PCI-X GBE NIC
X9271A Single Ethernet Controller Intel 1x UTP PCI-X GBE NIC
| Date |
Adapter |
Chipset |
Device driver in Solaris | Comment |
| 05.08.07 |
Intel Pro/100 (?) | iprb | Source: Xen
Discussion [05.08.07] |
| File/Directory
name |
Type |
content
(guess only!) |
comment |
| /usr/lib/xen/bin |
Directory |
internal Xen binaries |
|
| /usr/lib/xen/scripts |
Directory |
Scripts for the backend device
configuration |
|
| /var/log/xen |
Directory |
Xen Logfiles |
|
| /var/lib/xend/domains |
Directory |
directory used for suspended
Domains and for the configuration of Managed Domains |
check the size of this directory
on a regular base! |
| /var/lib/xend/storage |
Directory |
||
| /var/lib/xen |
Directory |
Directory used by virt-install |
|
| /var/lib/xenstored |
Directory |
||
| /var/xen/dump |
Directory |
Directory for DomU core dumps |
check the size of this directory on a regular base! |
| /usr/share/xen/qemu/keymaps |
Directory |
keymaps used |
|
| /var/run/xenstore.pid |
file |
pidfile for xenstored |
|
| /var/lib/xenstored/tdb |
file |
xenstored Database |
persistent until build 78; in
build 79 and newer this database is not persistent anymore |
| /lib/svc/share/xvm_include.sh |
file |
include file for shell scripts |
In Solaris snv81 this script
definese the following functions: not_dom0 disable_xvm In addition this script includes the general include file for SMF start/stop scripts /lib/svc/share/smf_include.sh Update: 04.02.08 : Note that this script is not a public interface - use it at your own risk. Update 15.11.08: In Solaris snv_101 the scripts defines the functions: is_dom0 xvm_init |
| /usr/include/xen |
directory |
header files for Xen / xVM |
|
Source: see this thread [11.02.08] on the OpenSolaris Discussion list
The following packages are required for dom0 support.
SUNWvirtinst
SUNWurlgrabber
SUNWlibvirt
SUNWxvmhvm
SUNWxvmdom
SUNWxvm
SUNWgccruntime
SUNWgnutls
SUNWlibsdl
FSWxwpft
FSWxwrtl
| Image |
32/64
Bit? |
Dom0 |
Status |
Date |
| Solaris snv_85 created with the Solaris installation program running in a Domu # uname -a SunOS snv85domU001 5.11 snv_85 i86pc i386 i86xpv Note: The checksum disabling in the DomU is again neccessary; therefor install the DomU without name service configuration and add set xnf:xnf_cksum_offload = 0 to the /etc/system after the installation |
32 Bit |
Solaris snv_85 |
works |
06.04.2008 |
| Solaris
snv_81 created with the Solaris installation program running in a DomU virt-install -n solarisPV --paravirt -r 1024 \bash-3.2# uname -a SunOS sol10nv81002 5.11 snv_81 i86pc i386 i86xpv Note: Disable TCP checksums in the DomU to get the complete network functionality if the Dom0 and the DomU are running Solaris snv_81. |
32 Bit |
Solaris snv_78 |
works |
03.02.2008 |
Solaris snv_75 (Cluster SUNWCrnet + xVM packages)created with the Solaris installation program running in a DomU; see herebash-3.2# uname -a SunOS dhcppc0 5.11 snv_75 i86pc i386 i86xpv |
32Bit |
Solaris snv_75 |
works |
26.10.2007 |
Solaris snv_75 created with the Solaris installation program running in a DomUbash-3.2# uname -a SunOS dhcppc0 5.11 snv_75 i86pc i386 i86xpv |
32Bit |
Ubuntu 7.10 with Xen 3.1; see here |
works |
24.10.2007 |
Solaris with Xen 07/07 DomUsee here [07.08.07] for how to create a Solaris DomU running in a Solaris Dom0 |
32Bit |
Xen 07/07 Solaris snv_75 |
works works |
25.07.2007 27.10.2007 |
Ubuntu Feisty 7.04 with PAE kernelroot@ubuntu_v001:~# uname -a Linux ubuntu_v001 2.6.19-4-server #2 SMP Thu Apr 5 06:07:34 UTC 2007 i686 GNU/Linux The DomU image was created on a Ubuntu Feisty Dom0 with debootstrap |
32 Bit |
Xen 07/07 Solaris snv_75 Solaris snv_85 |
works works works |
27.07.2007 27.10.2007 05.04.2008 |
Centos 4 Image from the Xen Demo CD[root@dhcpppc2 ~] uname -a Linux dhcppc2 2.6.16.29-xen #1 SMP Mon Oct 16 12:11:52 BST 2006 i686 athlon i386 GNU/Linux see Xen - a Linux Dom without Linux [28.07.07] for how to extract the image from the CDROM. see also Centos 5, network installation via http |
32 Bit |
Xen 07/07 Solaris snv_75 |
works works |
25.07.2007 27.10.2007 |
Centos 5 Image from jailtime-bash-3.1# uname -a Linux centos_pristine 2.6.19-4-server #2 SMP Thu Apr 5 06:07:34 UTC 2007 i686 athlon i386 GNU/Linux The default root password is "password". DHCP does not work in the default configuration but assigning an IP address manually for the network interface works. The config file used for this DomU is: kernel = "/export/xen-images/centos5/vmlinuz-2.6.19-4-server" memory = 256 name = "centos.5-0" vif = [ '' ] disk = ['file:/export/xen-images/centos5/centos.5-0.img,sda1,w', 'file:/export/xen-images/centos5/centos.swap,sda2,w'] root = "/dev/sda1 ro" ramdisk = "/export/xen-images/ubuntu_feisty/initrd.img-2.6.19-4-server" The kernel and the ramdisk are from Xen 3.0.4. see also Centos 5, network installation via http |
32 Bit |
Xen 07/07 Solaris snv_75 |
works works |
29.07.2007 27.10.2007 |
Xenoppix 5.1.1(see the download links)To boot the Xenoppix 5.1.1 CD in a Solaris DomU do the following: - download the ISO image for the CDROM - mount the ISO image via lofiadm: bash-3.00# lofiadm -a /export/incoming/knoppix_v5.1.1CD_20070104_xen3.1.0_vbox-20070620+IPAFont.iso /dev/lofi/1 bash-3.00# mount -o ro -F hsfs /dev/lofi/1 /mnt - copy the files miniroot-xen.gz and vmlinuz-2.6.18-xen to the harddisk bash-3.00# cp /mnt/boot/xen/miniroot-xen.gz . bash-3.00# cp /mnt/boot/xen/vmlinuz-2.6.18-xen . - umount the ISO image bash-3.00# umount /mnt - remove the lofi device bash-3.00# lofiadm -d /dev/lofi/1 - create a DomU config file for the ISO image named xenoppix.py. The file should look like: name = "xenoppix" memory = "368" vcpus = "1" disk = [ 'file:/export/incoming/knoppix_v5.1.1CD_20070104_xen3.1.0_vbox-20070620+IPAFont.iso,hdc,r' ] vif = [ 'mac=00:16:3e:00:00:20' ] ramdisk = "/export/xen-images/xenoppix/miniroot-xen.gz" kernel = "/export/xen-images/xenoppix/vmlinuz-2.6.18-xen" extra = " ramdisk_size=100000 init=/etc/init lang=de apm=power-off nomce xserver=Xvnc_xen nosound noapic noacpi pnpbios=off acpi=off nofstab noscsi nodma noapm nousb nopcmcia nofirewire noagp noswap nohwsetup" - create the DomU bash-2.05# xm create -c xenoppix.py - connect to the DomU with the vncviewer bash-2.05# vncviewer 192.168.1.35 Note: If using DHCP for the IP configuration you should use a fix mac address for the DomU and configure a fix IP address for the DomU on the DHCP server. |
32 Bit |
Xen 07/07 |
works |
29.07.2007 |
Foresight Linux 1.3(see the link section below)[root@localhost rc.d]# uname -a Linux localhost.localdomain 2.6.19-4-server #2 SMP Thu Apr 5 06:07:34 UTC 2007 i686 athlon i386 GNU/Linux DHCP does not work in the default configuration but assigning an IP address manually to the network interface works. The config file used for this DomU is: kernel = "/export/xen-images/foresight/vmlinuz-2.6.19-4-server" memory = 256 name = "foresight" vif = [ '' ] disk = ['file:/export/xen-images/foresight/foresight-2.18.3-x86.img,sda1,w'] root = "/dev/sda1 ro" ramdisk = "/export/xen-images/foresight/initrd.img-2.6.19-4-server" The kernel and the ramdisk are from Xen 3.0.4. |
32 Bit |
Xen 07/07 |
works |
03.08.2007 |
Fedora 7 (FC7)(see the link section below)[root@dhcppc12 ~]# uname -a Linux dhcppc12 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 athlon i386 GNU/Linux The Fedora 7 Installation DVD ISO Image already contains a Xen DomU kernel that can be used to install Fedora 7 in a DomU; Instructions: Download the DVD ISO image for Fedora 7: F-7-i386-DVD.iso (see below) # mount the image using lofiadm # bash-3.00# mount -o ro -F hsfs $( lofiadm -a /export/xen-images/fc7/F-7-i386-DVD.iso ) /mnt # check the result: # bash-3.00# df -k /mnt Filesystem kbytes used avail capacity Mounted on /dev/lofi/1 2832620 2832620 0 100% /mnt # copy the initrd image and the kernel # bash-3.00# mkdir /export/xen-images/fc7 bash-3.00# cp /mnt/images/xen/initrd.img /export/xen-images/fc7 bash-3.00# cp /mnt/images/xen/vmlinuz /export/xen-images/fc7 # create an NFS share for the directory with the mounted ISO image # bash-3.00# share -o ro,anon=0 /mnt # check the result # bash-3.00# dfshares RESOURCE SERVER ACCESS TRANSPORT dhcppc1:/mnt dhcppc1 - - dhcppc1:/export dhcppc1 - - # create a harddisk image for the DomU # bash-3.00# qemu-img create -f raw /export/xen-images/fc7/fc7.img 10G Formating '/export/xen-images/fc7/fc7.img', fmt=raw, size=10485760 kB # create the DomU config file # bash-3.00# cat <<EOT >>/export/xen-images/fc7/fc7_install.cfg kernel = "/export/xen-images/fc7/vmlinuz" vcpus = 1 memory = "384" name = "fc7" vif = [ '' ] disk = [ 'file:/export/xen-images/fc7/fc7.img,hda,w'] ramdisk = "/export/xen-images/fc7/initrd.img" extra = "headless ip=dhcp vnc vncpassword=wibble method=nfs:192.168.1.21:/mnt/ lang=en_US keymap=de ksdevice=eth0" vfb=[ "type=sdl" ] EOT # create the DomU # bash-3.00# xm create -c /export/xen-images/fc7/fc7_install.cfg # wait for the VNC Server start message in the framebuffer window # The message looks like # Please connect to 192.168.1.27:1 to begin the install # Now start the VNC viewer (no user necessary; the password is the # password used in the DomU config file ("wibble" in this example) # bash-3.00# vncviewer 192.168.1.27:1 # After the installation finished, shutdown the DomU and create a new config file for # running the Domu: bash-3.00# cat <<EOT >/export/xen-images/fc7/fc7_running.cfg vcpus = 1 memory = "384" name = "fc7" vif = [ '' ] disk = [ 'file:/export/xen-images/fc7/fc7.img,hda,w'] EOT # and start the DomU # xm create -c /export/xen-images/fc7/fc7_running.cfg Notes: The messages Could not get identity of device /dev/hda - invalid argumentCould not get identity of device /tmp/hda - invalid argumentwhile installing the DomU can be ignored You should only use the PV framebuffer for the installation of the DomU because it's very fragile at this time. Install a VNC server in the DomU if you need a graphical display. see also How to install a fedora Guest on Solaris Dom0 [07.08.07]. |
32 Bit |
Xen 07/07 Solaris snv_75 Solaris snv_85 |
works works works |
07.08.2007 27.10.2007 05.04.2008 |
Fedora 8 (FC8)(see the link section below)The installation of Fedora 8 in a DomU works (see Fedora 7 (FC) for the necessary steps to install FC8). Notes: After the installation the DomU did not boot from the disk image created due to a corrupted Xen kernel in the disk image. After copying the kernel used for the installation into the disk image the DomU booted fine. The installation of FC8 did not work in a Dom0 running Solaris snv_78: The installation starts and after the IP configuration was done the DomU hung. But I could boot the FC8 DomU from the disk image created in a Solaris snv_81 Dom0 in a DomU running in a Solaris snv_78 Dom0. Update 04.04.08 Solaris snv_85 To change the kernel in the disk image for FC8 either attach the disk image to another DomU running Linux and correct the kernel from within this Linux DomU or boot the FC8 DomU with a cfg like this one: vcpus = 1 |
32 Bit |
Solaris snv_81 Solaris snv_85 |
works the DomU works (Installation not tested) |
05.02.2008 03.04.2008 |
NetBSD 4.0 from the ISO image(see the link section below)# uname -a NetBSD 4.99.46 NetBSD 4.99.46 (XEN3_DOMU) #0: Sun Dec 30 11:11:09 PST 2007 builds@wb28:/home/builds/ab/HEAD/amd64/200712300002Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/XEN3_DOMU amd64 Note: There's no non-PAE Xen kernel for NetBSD 4.0; you can only run a NetBSD 4.0 64 Bit DomU in a 64 Bit Dom0. You can also install NetBSD 4.0 direct from the NetBSD ftp server (see below). Instructions Download the NetBSD 4.0 64 Bit ISO image ( amd64cd-4.0.iso) and the two NetBSD Xen DomU kernels (they are not in the ISO image); see the link section below. # create the DomU config file for the installation # bash-3.2# cat netbsd40_install.cfg name = "netbsd40_64" memory = "368" vcpus = "1" kernel = "/export/xen-images/netbsd40_64/netbsd-INSTALL_XEN3_DOMU.gz" disk = [ 'file:/export/xen-images/netbsd40_64/netbsd40_64.img,0x1,w', 'file:/export/xen-images/netbsd40_64/amd64cd-4.0.iso,0x2,r' ] vif = [ '' ] # start the DomU for installing NetBSD # bash-3.2# xm create -c netbsd40_install.cfg Notes for the installation In the dialog to choose the packages to install select custom In the following dialog select the package sets for the installation: The following is the list of distribution sets that will be used. Distribution set Selected ------------------------ -------- a: Kernel (GENERIC) Yes b: Base Yes c: System (/etc) Yes d: Compiler Tools Yes e: Games No f: Online Manual Pages Yes g: Miscellaneous No h: Test programs No i: Text Processing Tools Yes j: X11 sets All The X11 sets to install are: The following is the list of distribution sets that will be used. Distribution set Selected ------------------------ -------- a: Kernel (GENERIC) Yes b: Base Yes c: System (/etc) Yes d: Compiler Tools Yes e: Games No f: Online Manual Pa+-------------------------------------+ g: Miscellaneous | a: X11 base and clients Yes | h: Test programs | b: X11 programming Yes | i: Text Processing | c: X11 configuration Yes | >j: X11 sets | d: X11 fonts Yes | x: Install selected| e: X11 servers Yes | | f: Select all the above sets | | g: Deselect all the above sets | |>x: Install selected sets | +-------------------------------------+ In the dialog to select the CD/DVD drive with the installation media change the CD/DVD device to xbd1d. Change Enter the CDROM device to be used and directory on the CDROM where the distribution is located. Remember, the directory should contain the .tgz files. a: Device cd0a >b: Set directory /amd64/binary/sets x: Continue to Enter the CDROM device to be used and directory on the CDROM where the distribution is located. Remember, the directory should contain the .tgz files. a: Device xbd1d b: Set directory /amd64/binary/sets >x: Continue Now the installation should run. If the installation of one or more packages fails you can check the packages in the CD/DVD ISO image (/mnt is mounted on the ISO image in the example below): xtrnaw7@t30:/data/download$ ls /mnt/amd64/binary/sets/ base.tgz CKSUM etc.tgz kern-GENERIC.MP.tgz man.tgz misc.tgz SYSVSUM xbase.tgz xetc.tgz xserver.tgz BSDSUM comp.tgz games.tgz kern-GENERIC.tgz MD5 SHA512 text.tgz xcomp.tgz xfont.tgz After the installation is finished do not reboot immediately - instead go back to the main menu and run a shell: Choose the Utility menue and then a: Run /bin/sh Then mount the disk with the installed NetBSD and check if the device nodes for the Xen harddisks are created: # mount /dev/xbd0a /mnt # ls /mnt/dev/xbd* ls: /mnt/dev/xbd*: No such file or directory If not, create the device nodes: Open-BSD # MINOR1=0 ; MINOR2=16 # for i in a b c d e f g h i j k l m n o p ; do mknod /mnt/dev/xbd0${i} b 142 ${MINOR1} ; mknod /mnt/dev/rxbd0${i} c 142 ${MINOR1} mknod /mnt/dev/xbd1${i} b 142 ${MINOR2} ; mknod /mnt/dev/rxbd1${i} c 142 ${MINOR2} MINOR1=`let $MINOR1+1` ; MINOR2=`let $MINOR2+1` done # ls -l /mnt/dev/xbd0* brw-r--r-- 1 root wheel 142, 0 Jan 1 16:20 /mnt/dev/xbd0a brw-r--r-- 1 root wheel 142, 1 Jan 1 16:20 /mnt/dev/xbd0b brw-r--r-- 1 root wheel 142, 2 Jan 1 16:20 /mnt/dev/xbd0c brw-r--r-- 1 root wheel 142, 3 Jan 1 16:20 /mnt/dev/xbd0d brw-r--r-- 1 root wheel 142, 4 Jan 1 16:20 /mnt/dev/xbd0e brw-r--r-- 1 root wheel 142, 5 Jan 1 16:20 /mnt/dev/xbd0f brw-r--r-- 1 root wheel 142, 6 Jan 1 16:20 /mnt/dev/xbd0g brw-r--r-- 1 root wheel 142, 7 Jan 1 16:20 /mnt/dev/xbd0h brw-r--r-- 1 root wheel 142, 8 Jan 1 16:20 /mnt/dev/xbd0i brw-r--r-- 1 root wheel 142, 9 Jan 1 16:20 /mnt/dev/xbd0j brw-r--r-- 1 root wheel 142, 10 Jan 1 16:20 /mnt/dev/xbd0k brw-r--r-- 1 root wheel 142, 11 Jan 1 16:20 /mnt/dev/xbd0l brw-r--r-- 1 root wheel 142, 12 Jan 1 16:20 /mnt/dev/xbd0m brw-r--r-- 1 root wheel 142, 13 Jan 1 16:20 /mnt/dev/xbd0n brw-r--r-- 1 root wheel 142, 14 Jan 1 16:20 /mnt/dev/xbd0o brw-r--r-- 1 root wheel 142, 15 Jan 1 16:20 /mnt/dev/xbd0p # ls -l /mnt/dev/rxbd0* crw-r--r-- 1 root wheel 142, 0 Jan 1 16:20 /mnt/dev/rxbd0a crw-r--r-- 1 root wheel 142, 1 Jan 1 16:20 /mnt/dev/rxbd0b crw-r--r-- 1 root wheel 142, 2 Jan 1 16:20 /mnt/dev/rxbd0c crw-r--r-- 1 root wheel 142, 3 Jan 1 16:20 /mnt/dev/rxbd0d crw-r--r-- 1 root wheel 142, 4 Jan 1 16:20 /mnt/dev/rxbd0e crw-r--r-- 1 root wheel 142, 5 Jan 1 16:20 /mnt/dev/rxbd0f crw-r--r-- 1 root wheel 142, 6 Jan 1 16:20 /mnt/dev/rxbd0g crw-r--r-- 1 root wheel 142, 7 Jan 1 16:20 /mnt/dev/rxbd0h crw-r--r-- 1 root wheel 142, 8 Jan 1 16:20 /mnt/dev/rxbd0i crw-r--r-- 1 root wheel 142, 9 Jan 1 16:20 /mnt/dev/rxbd0j crw-r--r-- 1 root wheel 142, 10 Jan 1 16:20 /mnt/dev/rxbd0k crw-r--r-- 1 root wheel 142, 11 Jan 1 16:20 /mnt/dev/rxbd0l crw-r--r-- 1 root wheel 142, 12 Jan 1 16:20 /mnt/dev/rxbd0m crw-r--r-- 1 root wheel 142, 13 Jan 1 16:20 /mnt/dev/rxbd0n crw-r--r-- 1 root wheel 142, 14 Jan 1 16:20 /mnt/dev/rxbd0o crw-r--r-- 1 root wheel 142, 15 Jan 1 16:20 /mnt/dev/rxbd0p # ls -l /mnt/dev/xbd1* brw-r--r-- 1 root wheel 142, 16 Jan 1 16:20 /mnt/dev/xbd1a brw-r--r-- 1 root wheel 142, 17 Jan 1 16:20 /mnt/dev/xbd1b brw-r--r-- 1 root wheel 142, 18 Jan 1 16:20 /mnt/dev/xbd1c brw-r--r-- 1 root wheel 142, 19 Jan 1 16:20 /mnt/dev/xbd1d brw-r--r-- 1 root wheel 142, 20 Jan 1 16:20 /mnt/dev/xbd1e brw-r--r-- 1 root wheel 142, 21 Jan 1 16:20 /mnt/dev/xbd1f brw-r--r-- 1 root wheel 142, 22 Jan 1 16:20 /mnt/dev/xbd1g brw-r--r-- 1 root wheel 142, 23 Jan 1 16:20 /mnt/dev/xbd1h brw-r--r-- 1 root wheel 142, 24 Jan 1 16:20 /mnt/dev/xbd1i brw-r--r-- 1 root wheel 142, 25 Jan 1 16:20 /mnt/dev/xbd1j brw-r--r-- 1 root wheel 142, 26 Jan 1 16:20 /mnt/dev/xbd1k brw-r--r-- 1 root wheel 142, 27 Jan 1 16:20 /mnt/dev/xbd1l brw-r--r-- 1 root wheel 142, 28 Jan 1 16:20 /mnt/dev/xbd1m brw-r--r-- 1 root wheel 142, 29 Jan 1 16:20 /mnt/dev/xbd1n brw-r--r-- 1 root wheel 142, 30 Jan 1 16:20 /mnt/dev/xbd1o brw-r--r-- 1 root wheel 142, 31 Jan 1 16:20 /mnt/dev/xbd1p # ls -l /mnt/dev/rxbd1* crw-r--r-- 1 root wheel 142, 16 Jan 1 16:20 /mnt/dev/rxbd1a crw-r--r-- 1 root wheel 142, 17 Jan 1 16:20 /mnt/dev/rxbd1b crw-r--r-- 1 root wheel 142, 18 Jan 1 16:20 /mnt/dev/rxbd1c crw-r--r-- 1 root wheel 142, 19 Jan 1 16:20 /mnt/dev/rxbd1d crw-r--r-- 1 root wheel 142, 20 Jan 1 16:20 /mnt/dev/rxbd1e crw-r--r-- 1 root wheel 142, 21 Jan 1 16:20 /mnt/dev/rxbd1f crw-r--r-- 1 root wheel 142, 22 Jan 1 16:20 /mnt/dev/rxbd1g crw-r--r-- 1 root wheel 142, 23 Jan 1 16:20 /mnt/dev/rxbd1h crw-r--r-- 1 root wheel 142, 24 Jan 1 16:20 /mnt/dev/rxbd1i crw-r--r-- 1 root wheel 142, 25 Jan 1 16:20 /mnt/dev/rxbd1j crw-r--r-- 1 root wheel 142, 26 Jan 1 16:20 /mnt/dev/rxbd1k crw-r--r-- 1 root wheel 142, 27 Jan 1 16:20 /mnt/dev/rxbd1l crw-r--r-- 1 root wheel 142, 28 Jan 1 16:20 /mnt/dev/rxbd1m crw-r--r-- 1 root wheel 142, 29 Jan 1 16:20 /mnt/dev/rxbd1n crw-r--r-- 1 root wheel 142, 30 Jan 1 16:20 /mnt/dev/rxbd1o crw-r--r-- 1 root wheel 142, 31 Jan 1 16:20 /mnt/dev/rxbd1p # # cd / # umount /mnt Now you can shutdown the DomU and restart it using the config file for running a NetBSD DomU: # create the DomU file for running the NetBSD 4.0 DomU # bash-3.2# cat netbsd40_run.cfg name = "netbsd40_64" memory = "368" vcpus = "1" kernel = "/export/xen-images/netbsd40_64/netbsd-XEN3_DOMU.gz" disk = [ 'file:/export/xen-images/netbsd40_64/netbsd40_64.img,0x1,w' ] vif = [ '' ] root = "xbd0a" # start the NetBSD 4.0 DomU # bash-3.2# xm create -c netbsd40_run.cfg After booting the NetBSD DomU the last final step is to configure the network in the DomU. Note: You might use the installation via ftp server described below to install NetBSD because using that method less manual steps are necessary to install the DomU. Additional notes from http://www.netbsd.org/ports/xen/howto.html [01.01.08]: When the new domain is booting you'll see some warnings about wscons and the pseudo-terminals,
these can be fixed by editing the files console "/usr/libexec/getty Pc" vt100 on secure Finally, all screens must be commented out from It is also desireable to add powerd=YES in rc.conf. This way, the domain will be properly shut down if 'xm shutdown -R' or 'xm shutdown -H' is used on the domain0. |
64 Bit |
Solaris snv_78 |
works |
01.01.2008 |
NetBSD 4.0 from the ftp server(see the link section below)dhcppc11# uname -a NetBSD dhcppc11 4.99.46 NetBSD 4.99.46 (XEN3_DOMU) #0: Sun Dec 30 11:11:09 PST 2007 builds@wb28:/home/builds/ab/HEAD/amd64/200712300002Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/XEN3_DOMU amd64 Note: There's no non-PAE Xen kernel for NetBSD 4.0; you can only run a NetBSD 4.0 64 Bit DomU in a 64 Bit Dom0. Instructions Download the two NetBSD 4.0 Xen DomU kernels; see the link section below. # create the DomU config file for the installation # bash-3.2# cat netbsd40_install_net.cfg name = "netbsd40_64" memory = "368" vcpus = "1" kernel = "/export/xen-images/netbsd40_64/netbsd-INSTALL_XEN3_DOMU.gz"/usr/lib/xen/bin/pygrub disk = [ 'file:/export/xen-images/netbsd40_64/netbsd40_64.img,0x1,w' ] vif = [ '' ] # start the installation of the DomU # bash-3.2# xm create -c netbsd40_install_net.cfg In the dialog to select the distribution to install you can choose Full installation. In the dialog to choose the installation media select ftp: Your disk is now ready for installing the kernel and the distribution sets. As noted in your INSTALL notes, you have several options. For ftp or nfs, you must be connected to a network with access to the proper machines. Sets selected 14, processed 0, Next set kern-GENERIC. ┌─────────────────────────┐ │ Install from │ │ │ │ a: CD-ROM / DVD │ │>b: FTP │ │ c: HTTP │ │ d: NFS │ │ e: Floppy │ │ f: Unmounted fs │ │ g: Local directory │ │ h: Skip set │ │ i: Skip set group │ │ j: Abandon installation │ └─────────────────────────┘ In the dialog with the details for the ftp server change the the base directory so that it matches the Xen kernel used: e.g. for the kernel ftp://iso2.de.netbsd.org/pub/NetBSD-daily/HEAD/200712300002Z/amd64/binary/kernel/netbsd-INSTALL_XEN3_DOMU.gz change the Base directory to pub/NetBSD/NetBSD-daily/HEAD/200712300002Z The following are the ftp site, directory, user, and password that will be used. If "user" is "ftp", then the password is not needed. a: Host ftp.NetBSD.org >b: Base directory /pub/NetBSD/NetBSD-daily/HEAD/200712300002Z c: Set directory /amd64/binary/sets d: User ftp e: Password f: Proxy g: Transfer directory /usr/INSTALL h: Delete after install No x: Get Distribution Now the rest of the installation should run without an error. No further configuration steps are necessary - the installation will create the required device nodes for the disk images and also configure the network for the running DomU. After the installation is finished shutdown the DomU and restart it using the config file for running a NetBSD DomU: bash-3.2# cat netbsd40_run_net.cfg name = "netbsd40_64" memory = "368" vcpus = "1" kernel = "/export/xen-images/netbsd40_64/netbsd-XEN3_DOMU.gz" disk = [ 'file:/export/xen-images/netbsd40_64/netbsd40_64.img,0x1,w' ] vif = [ '' ] root = "xbd0a" bash-3.2# xm create -c netbsd40_run_net.cfg See also the NetBSD DomU Notes above |
64 Bit |
Solaris snv_78 |
works |
01.01.2008 |
Netware 6.5(v) Novell Open Enterprise Server, NetWare 6.5 Support Pack Revision 07 (C) Copyright 1983-2007 Novell Inc. All Rights Reserved. Patent Pending. Server Version 5.70.07 September 18, 2007 Saturday, March 29, 2008 12:47:26 pm <<NO TIME ZONE>> : Download the ISO image NW65SP7_OVL_DVD.iso from the Netware download page. Then extract the file XNLOADER.SYS from the ISO image: bash-3.2# lofiadm -a /pool/xen-images/netware/NW65SP7_OVL_DVD.iso /dev/lofi/1 bash-3.2# mount -o ro -F hsfs /dev/lofi/1 /mnt bash-3.2# ls /mnt AUTORUN.INF INSTALL.BAT NLSFUNC.EXE NWINST.TMP READ_ME.TXT CONFIG LICENSE NW65OS POSTINST.NI STARTUP DRIVERS MODE.COM NW65PROD PRODUCT.NI SYS EGA.CPI NETMAIN.ILS NWDEPLOY.EXE PRODUCTS INSTALL NI NWDeployNoBrowser.exe READ_ME.HTM bash-3.2# cp /mnt/STARTUP/XNLOADER.SYS . bash-3.2# umount /mnt bash-3.2# lofiadm -d /pool/xen-images/netware/NW65SP7_OVL_DVD.iso Create the cfg file for installing the Netware DomU: bash-3.2# cat netware_install.cfg kernel = "/pool/xen-images/netware/XNLOADER.SYS" vcpus = 1 memory = "512" name = "netware" vif = [ '' ] disk = [ 'file:/pool/xen-images/netware/netware.iso,xvdb,r', 'file:/pool/xen-images/netware/netware_empty.img,xvda,w' ] vfb=[ "type=sdl" ] And then start the installation xm create -c netware_install.cfg Create the cfg file for running the Netware DomU: bash-3.2# cat netware_run.cfg kernel = "/pool/xen-images/netware/XNLOADER.SYS" vcpus = 1 memory = "512" name = "netware" vif = [ '' ] disk = [ 'file:/pool/xen-images/netware/netware_empty.img,xvda,w' ] vfb=[ "type=sdl" ] And then start the installation xm create -c netware_run.cfg Notes:
|
64 Bit 32 Bit |
snv_85 |
works but crashes frequently |
29.03.08 |
VMKnoppix Livecd with Xen 3.2root@Knoppix:~# uname -a Linux Knoppix 2.6.18.8-xen #1 SMP Tue Jan 22 16:04:36 JST 2008 i686 GNU/Linux Download the iso image knoppix_v5.1.1CD_20070104_xen3.2.0_vbox-20080213.iso # mount the ISO image and copy the Xen kernel and ramdisk # bash-3.2# lofiadm -a /pool/iso/knoppix_v5.1.1CD_20070104_xen3.2.0_vbox-20080213.iso /dev/lofi/1 bash-3.2# mount -o ro -F hsfs /dev/lofi/1 /mnt bash-3.2# cd /pool/xen-images/vmknoppix bash-3.2# cp /mnt/miniroot-xen.gz . bash-3.2# cp /mnt/vmlinuz-2.6.18.8-xen ./vmlinuz-xen bash-3.2# umount /mnt bash-3.2# lofiadm -d /pool/iso/knoppix_v5.1.1CD_20070104_xen3.2.0_vbox-20080213.iso # create the DomU config file: # lofbash-3.2# cat vmknoppix.cfg name = "vmknoppix" memory = "512" vcpus = "1" disk = [ 'file:/pool/iso/knoppix_v5.1.1CD_20070104_xen3.2.0_vbox-20080213.iso,hdc,r' ] vif = [ '' ] ramdisk = "/pool/xen-images/vmknoppix/miniroot-xen.gz" kernel = "/pool/xen-images/vmknoppix/vmlinuz-xen" extra = " ramdisk_size=100000 init=/etc/init lang=de apm=power-off nomce xserver=Xvnc_xen nosound noapic noacpi pnpbios=off acpi=off nofstab noscsi nodma noapm nousb nopcmcia nofirewire noagp noswap nohwsetup" vfb=[ "type=sdl" ] # start the DomU # bash-3.2# xm create -c vmknoppix.cfg Wait for message "Starting the X Windwow System" . Then, issue root@Knoppix:~# ifconfig eth0 eth0 Protokoll:Ethernet Hardware Adresse 00:16:3E:44:F5:19 inet Adresse:192.168.1.177 Bcast:192.168.1.255 Maske:255.255.255.0 inet6 Adresse: fe80::216:3eff:fe44:f519/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1422 errors:0 dropped:0 overruns:0 frame:0 TX packets:2173 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:164229 (160.3 KiB) TX bytes:2511057 (2.3 MiB) root@Knoppix:~# in the DomU to get the IP address of the DomU. Open another session and start the vncviewer: bash-3.2# vncviewer 192.168.1.177:0 |
64 Bit 32 Bit |
Solaris snv_85 |
works |
13.04.2008 |
Centos 5, network installation via http[root@localhost ~]# uname -a Linux localhost.localdomain 2.6.18-53.el5xen #1 SMP Mon Nov 12 03:26:12 EST 2007 i686 athlon i386 GNU/Linux ### Download the kernel and the ramdisk for the installation: # bash-3.2# wget http://mirror.centos.org/centos/5/os/i386/images/xen/initrd.img --09:56:02-- http://mirror.centos.org/centos/5/os/i386/images/xen/initrd.img => `initrd.img' Resolving mirror.centos.org... 88.208.217.170 Connecting to mirror.centos.org|88.208.217.170|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 5,285,268 (5.0M) [application/octet-stream] 100%[========================================================================>] 5,285,268 238.71K/s ETA 00:00 09:56:27 (211.28 KB/s) - `initrd.img' saved [5285268/5285268] bash-3.2# wget http://mirror.centos.org/centos/5/os/i386/images/xen/vmlinuz --09:56:37-- http://mirror.centos.org/centos/5/os/i386/images/xen/vmlinuz => `vmlinuz' Resolving mirror.centos.org... 88.208.217.170 Connecting to mirror.centos.org|88.208.217.170|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2,106,541 (2.0M) [text/plain] 100%[========================================================================>] 2,106,541 527.66K/s ETA 00:00 09:56:41 (532.29 KB/s) - `vmlinuz' saved [2106541/2106541] ### rename the kernel and the ramdisk image (not necessary but makes life easier) # bash-3.2# mv vmlinuz vmlinuz-xen-install bash-3.2# mv initrd.img initrd-xen-install #### create the disk image for the DomU # bash-3.2# /pool/install/root/opt/tools/qemu/CURRENT/qemu-img create domu-test.img 10G Formating 'domu-test.img', fmt=raw, size=10485760 kB ### create the DomU configuration file for the DomU # bash-3.2# cat centos5.cfg kernel = "/pool/xen-images/centos5_1/vmlinuz-xen-install" ramdisk = "/pool/xen-images/centos5_1/initrd-xen-install" name = "domu-test" memory = "256" disk = [ 'file:/pool/xen-images/centos5_1/domu-test.img,hda,w', ] vif = [ '' ] vcpus=1 ### and finally start the DomU # bash-3.2# xm create -c centos5.cfg ### select the language for the installation of the DomU # ------------------------ Welcome to CentOS +---------+ Choose a Language +---------+ | | | What language would you like to use | | during the installation process? | | | | Finnish ^ | | French : | | German : | | Greek # | | Gujarati : | | Hindi : | | Hungarian : | | Icelandic v | | | | +----+ | | | OK | | | +----+ | | | | | +---------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ### In the next screen select "HTTP" as installation source Welcome to CentOS +------+ Installation Method +------+ | | | What type of media contains the | | packages to be installed? | | | | Local CDROM | | Hard drive | | NFS image | | FTP | | HTTP | | | | +----+ +------+ | | | OK | | Back | | | +----+ +------+ | | | | | +-----------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ### Disable IPv6 support: Welcome to CentOS +----------------+ Configure TCP/IP +----------------+ | | | [*] Enable IPv4 support | | (*) Dynamic IP configuration (DHCP) | | ( ) Manual configuration | | | | [ ] Enable IPv6 support | | (*) Automatic neighbor discovery (RFC 2461) | | ( ) Dynamic IP configuration (DHCP) | | ( ) Manual configuration | | | | +----+ +------+ | | | OK | | Back | | | +----+ +------+ | | | | | +----------------------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ### enter the webserver name and the name of the directory with the installation image: Web site name : mirror.centos.org Centos directory: /centos/5/os/i386 Welcome to CentOS +-----------------+ HTTP Setup +------------------+ | | | Please enter the following information: | | | | o the name or IP number of your Web server | | o the directory on that server containing | | CentOS for your architecture | | | | Web site name: mirror.centos.org_______ | | CentOS directory: /centos/5/os/i386_______ | | | | +----+ +------+ | | | OK | | Back | | | +----+ +------+ | | | | | +-------------------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ### Now Centos Downloads the root image for the installation (this may take a while ...) Welcome to CentOS +----------------------------+ Retrieving +----------------------------+ | | | Retrieving images/minstg2.img... | | | +----------------------------------------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ### After that the installation starts: Welcome to CentOS +------------------+ CentOS +-------------------+ | | | Welcome to CentOS! | | | | | | +----+ | | | OK | | | +----+ | | | | | +-----------------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen Note: While configuring the installation the installation program prints warning messages about /dev/hda and /tmp/hda like this multiple times: Welcome to CentOS +-------------+ Warning +-------------+ | | | Could not get identity of device | | /dev/hda - Invalid argument | | | | +--------+ +--------+ | | | Ignore | | Cancel | | | +--------+ +--------+ | | | | | +-------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen Welcome to CentOS +-------------+ Warning +-------------+ | | | Could not get identity of device | | /tmp/hda - Invalid argument | | | | +--------+ +--------+ | | | Ignore | | Cancel | | | +--------+ +--------+ | | | | | +-------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ### You can simply ignore these messages. ### Just continue with the configuration ----------------------- Welcome to CentOS +---------------+ Warning +---------------+ | | | The partition table on device hda was | | unreadable. To create new partitions | | it must be initialized, causing the | | loss of ALL DATA on this drive. | | | | This operation will override any | | previous installation choices about | | which drives to ignore. | | | | Would you like to initialize this | | drive, erasing ALL DATA? | | | | +-----+ +----+ | | | Yes | | No | | | +-----+ +----+ | | | | | +-----------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ### and so on ... Welcome to CentOS +------------------+ Package Installation +------------------+ | | | Name : gtk2-2.10.4-19.el5-i386 | | Size : 19086k | | Summary: The GIMP ToolKit (GTK+), a library for | | creating GUIs for X | | | | Status: | | | | 0% | | | | Packages Bytes Time | | Total : 748 1818M 2:52:54 | | Completed: 288 412M 0:39:14 | | Remaining: 460 1406M 2:13:39 | | | | 22% | | | +------------------------------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen ... Welcome to CentOS +------------------+ Package Installation +------------------+ | | | Name : xorg-x11-drv-mga-1.4.2-6.el5-i386 | | Size : 161k | | Summary: Xorg X11 mga video driver | | | | | | Status: | | | | 0% | | | | Packages Bytes Time | | Total : 748 1818M 3:15:29 | | Completed: 703 1813M 3:14:53 | | Remaining: 45 5M 0:00:36 | | | | 99% | | | +------------------------------------------------------------+ <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen .. until it's finished: Welcome to CentOS +----------------------+ Complete +-----------------------+ | | | Congratulations, your CentOS installation is complete. | | | | Remove any media used during the installation process | | and press <Enter> to reboot your system. | | | | | | +--------+ | | | Reboot | | | +--------+ | | | | | +---------------------------------------------------------+ <Enter> to reboot Now shutdown the DomU by executing bash-3.2# xm shutdown domu-test in another session in the Dom0. The DomU should do a graceful shutdown: sending termination signals...done sending kill signals...done disabling swap... /dev/mapper/VolGroup00-LogVol01 unmounting filesystems... /mnt/runtime done disabling /dev/loop0 /proc done /dev/pts done /sys done /tmp/ramfs done /selinux done /mnt/sysimage/boot done /mnt/sysimage/sys done /mnt/sysimage/proc done /mnt/sysimage/selinux done /mnt/sysimage/dev done /mnt/sysimage done powering off system System halted. bash-3.2# Create a DomU config file to run the DomU: bash-3.2# cat centos5_run.cfg name = "domu-test" memory = "256" disk = [ 'file:/pool/xen-images/centos5_1/domu-test.img,hda,w', ] vif = [ '' ] vcpus=1 bash-3.2# ### and start the DomU bash-3.2# xm create -c centos5_run.cfg pyGRUB version 0.6 ┌────────────────────────────────────────────────────────────────────────┐ │ CentOS (2.6.18-53.el5xen) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────┘ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS. 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command line. [root@localhost ~]# uname -a Linux localhost.localdomain 2.6.18-53.el5xen #1 SMP Mon Nov 12 03:26:12 EST 2007 i686 athlon i386 GNU/Linux [root@localhost ~]# Note: The intructions above are based on the instructions from this web site: http://sysadminman.net/blog/archives/39 [23.05.08] |
32 Bit | Solaris snv_89 |
works |
|
Centos 5.1, network installation via httpUse the instructions for Centos 5, network installation via http to install Centos 5.1 via http. Change only the path to the ramdisk, the boot kernel, and the installation directory: Path to the ramdisk for Centos 5.1: http://mirror.centos.org/centos/5.1/os/i386/images/xen/initrd.img Path to the install kernel for Centos 5.1: http://mirror.centos.org/centos/5/os/i386/images/xen/vmlinuz Path to the installation directory on the webserver for Centos 5.1: centos-5/5.1/os/i386 |
32 Bit |
Solaris snv_78 |
works |
| NetWare 6.5 SP7 can run
paravirtualized on Xen, with the xnloader.sys bootloader and the included xennet.cad, xenblk.ham and xenmp.psm modules for device support. I haven't tried it on OpenSolaris yet, but it installs fine (without HVM) on a Linux Dom0. Just specify xnloader.sys as kernel and make sure the installation ISO is accessible as a block device and it should work. |
VirtualBox kernel driver not installed.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
Result Code: 0x80004005
Component: Console
Interface: IConsole
{d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}| Bernd Schemmer: >>looks
like the powernowd does not run under Xen: ... Bernd Schemmer: >> Is this correct? Casper Dik: >>Possibly; powernow needs to have access to ACPI and all the machine Casper Dik: >>specific registers controlling powernow. Right. There has been some discussion in the xen community on how to make this happen. I haven't followed the details of these conversations, but I don't expect a quick resolution. In addition, if you try frkit on our version of i86pc (i.e. a hardware boot, not under Xen), a couple of the modules will fail to install. We have moved a lot of the kernel modules to new locations, and we have yet to update frkit to look in both places. For now, you can work around these problems by running: # ln -s /platform/i86pc/kernel/mach/pcplusmp /kernel/mach/ # ln -s /platform/i86pc/kernel/mach/amd64/pcplusmp /kernel/mach/amd64/ |
| The blktap mechanism for providing disk access from dom0 is not currently supported on Solaris |
disk = [ 'tap:aio:/xen/images/c5-Services-1.img,xvda,w' ]do not work yet.
| We've recently added support for
blktap along with support for managing virtual disks (disk file images). There are some difference from a linux dom0. This is available in b101 @ http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ This allows you to create and manage vmdk and vdi (Virtual Box) disk files. By default, virt-install will now use a vmdk vdisk when a non existing disk file is passed in. |
xm list to check for a zombie domU:| The
Solaris Express build 75 release will be the first Solaris Express
build to include the Solaris xVM bits. There is a pretty serious bug in dom0 and potentially domU due to some bits that were integrated around the same time.. It's recommended that you use the "set softcall_delay=0x100000" workaround documented in 6612343 for both dom0 and domU. This bug should be fixed in b76. http://bugs.opensolaris.org/view_bug.do?bug_id=6612343 |
By default, the hypervisor will not use a serial console itself. To
enable
it (allowing debugging information and access), you will need to modify
/boot/grub/menu.lst as follows. If your serial console is
on ttya in
Solaris (check eeprom if you're not sure), then add an
entry similar
to the following:
title Solaris xVM with serial console
kernel$ /boot/$ISADIR/xen.gz console=com1 com1=auto
module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix
module$ /platform/i86pc/$ISADIR/boot_archiveIf the console is on ttyb in Solaris, then use com2
appropriately.
See 6593895 install does not set Xen console settings.
Boot the machine into the Xen Dom0title Solaris xVM with serial console-B console=ttya
kernel$ /boot/$ISADIR/xen.gz console=com1 com1=auto
module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix-kv
module$ /platform/i86pc/$ISADIR/boot_archive
>If I understand this correct, I can not run the older DomUs with Solaris |
I do see these messages in my log file:
xnb: [ID 873713 kern.warning] WARNING: xnb_alloc_page: Cannot allocate memory to transfer packets to peer
Until build 81 is available the Solaris network backend uses "page |
"/usr/lib/xen/bin/xenstore-read device-misc/vif/default-nic".If the value from the xenstore is wrong change it with
syseventadm list
class=EC_xendev /usr/lib/xen/scripts/xpvd-event action=$subclass domain=$domain vdev=$vdev device=$device devclass=$devclass febe=$fob
class=EC_xpvsys /usr/lib/xen/scripts/xpvsys-event subclass=$subclass shutdown=$shutdown
BASEDIR=${BASEDIR:-/}
/usr/sbin/syseventadm list -R $BASEDIR -c EC_xendev > /dev/null 2>&1
if [ $? -ne 0 ]
then
/usr/sbin/syseventadm add -R $BASEDIR -c EC_xendev \
/usr/lib/xen/scripts/xpvd-event 'action=$subclass' \
'domain=$domain' 'vdev=$vdev' 'device=$device' \
'devclass=$devclass' 'febe=$fob'
fi
/usr/sbin/syseventadm list -R $BASEDIR -c EC_xpvsys > /dev/null 2>&1
if [ $? -ne 0 ]
then
/usr/sbin/syseventadm add -R $BASEDIR -c EC_xpvsys \
/usr/lib/xen/scripts/xpvsys-event 'subclass=$subclass' \
'shutdown=$shutdown'
fi
# restart daemon if the package is being added to the running system
if [ "$BASEDIR" = "/" -a $? -eq 0 ]
then
/usr/sbin/syseventadm restart
fi
bash-3.2# lucreate -n "sol10snv87" -A "solaris 10 snv87" -m
/:/dev/dsk/c1d0s4:ufs -l test.log
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
ERROR: The system must be rebooted after applying required patches.
Please reboot and try again.
bash-3.2# cat test.log
new request cannot find provider for service=<getLogicalDeviceList>
| The
realtek device emulated in the qemu included in the Xen 3.0.4 source
does not work with vista. It works fine with WinXP.. For Vista and 3.0.4, you need to use ne2k_pci. vif = ['type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci'] I believe this is fixed in 3.1.2, but I haven't tried it to verify it yet. |
> I set /etc/system's zfs:zfs_arc_max = 0x10000000 and it seems better now. |
zfs:zfs_arc_max = 0x10000000to the /etc/system to set zfs_arc_max (0x10000000 is the size of the zfs cache)
When you use zfs and Xen together, there's some tuning |
| Hi, is there a way to define VLAN tags on VNICs for xVM? I thought there is a way to plumb a "VLAN-NIC" within Dom0 (eg. e1000g155000 for VLAN ID 155 on the physical NIC e1000g0), and use that VLAN-NIC when creating a DomU with virt-install (--bridge="e1000g155000"). I've tried this with Opensolaris b76 using virt-install, but within the debug messages /usr/lib/vna claims that it could not create the VNIC900. Is there an other way to accomplish VLAN tagged NICs within DomUs?? Best regards, Tobi ------- On 7 Dec 2007, at 09:06, Tobias Esser wrote: > is there a way to define VLAN tags on VNICs for xVM? It doesn't work. See 6637143. dme. |
while trying to boot a Solaris xVM Dom0 check which type of interrupt controller is used. To do this boot the machine into Solaris on bare metal (without xVM) and issue the command
This version of Solaris xVM does not support this hardware
extra = '/platform/i86xpv/kernel/unix -kd - nowin -B install_media=cdrom'
# xm create /tmp/solaris-exp -c
Using config file "/tmp/solaris-exp".
Loading kmdb...
Started domain solaris-exp
Welcome to kmdb
Loaded modules: [ unix krtld genunix ]
[0]> gnttab_init+0xa2:b <esp/W 403
[0]> ,5000:c
"It's annoying and poorly documented but it now seems necessary to use "tap:aio" instead of "file".
i.e. for your example:
disk = [ 'tap:aio:
'tap:aio:
This should work."
"Ensure that /bin/sh leads to /bin/bash (i.e. readlink /bin/sh ).. ifSource: http://lists.xensource.com/archives/html/xen-users/2007-01/msg00446.html [08.11.08]
not, ln -s -f /bin/bash /bin/sh
Its quite possible on your system /bin/sh leads to dash, which isn't
capable of parsing the hotplug scripts in /etc/xen/scripts, which is the
cause of this error."
"If you have the “loop” driver compiled into your kernel, you need to add
“max_loop=64” to your kernel boot arguments (the “append=” line in lilo.conf,
or to the end of the “kernel” line in grub’s menu.lst), and reboot."
If you have the “loop” driver compiled as a module, you need to insmod it with
“max_loop=64” added to its options. On Debian systems, you
edit /etc/modules.conf and add “options loop max_loop=64”, and “rmmod loop”
“modprobe loop”.
If you’re using devfs, then stop here. The new /dev/loop* will appear
automatically. If not, you’ll need to edit and run MAKEDEV:
Change:
loop)
for part in 0 1 2 3 4 5 6 7
do
makedev loop$part b 7 $part $disk
done
;;
To:
loop)
for part in `seq 0 63`
do
makedev loop$part b 7 $part $disk
done
;;
And run “MAKEDEV loop”.
| All xm opperations rely upon the
Xen control daemon, aka xend. For any
xm commands to run xend must also be running. For this reason you
should start xend as a service when your system first boots using xen. Most xm commands require root privileges to run due to the communications channels used to talk to the hypervisor. Running as non root will return an error. Most xm commands act asynchronously, so just because the xm command returned, doesn't mean the action is complete. This is important, as many operations on domains, like create and shutdown, can take considerable time (30 seconds or more) to bring the machine into a fully compliant state. If you want to know when one of these actions has finished you must poll through xm list periodically. |
online 10:51:04 svc:/system/xctl/store:defaultNote that the Xen services are disabled by default - you must manually enable them (but only once; enabling the services is persistent).
online 10:51:11 svc:/system/xctl/xend:default
online 10:51:11 svc:/system/xctl/console:default
online 10:51:16 svc:/system/xctl/domains:default
e.g.
bash-3.00# svcprop -p config xctl/xend
config/default-nic astring ""
config/dom0-cpus integer 0
config/dom0-min-mem integer 196
config/enable-dump boolean true
config/stability astring Unstable
config/xend-relocation-address astring 127.0.0.1
config/xend-relocation-hosts-allow astring \^localhost$
config/xend-relocation-server boolean true
config/xend-unix-server boolean true
See the xend
man page [28.07.07] for a
description of these properties.
Examples for changing the config values (copied from the xend
man page [28.07.07])
EXAMPLE 1 Modifying an Existing Property
Use the following sequence of commands to modify an existing xend
property.
# svccfg -s xctl/xend listprop
# svccfg -s xctl/xend setprop config/dom0-cpus = 1
# svcadm refresh xctl/xend
EXAMPLE 2 Creating a New Property
The following sequence creates a new property.
# svccfg -s xctl/xend setprop config/testprop = astring:
\"TestProperty\"
# svcadm refresh xctl/xend
# svcadm restart xend
# svcprop xctl/xend
[25.10.07 Solaris snv_75]
In Solaris snv_75 the name of the SMF services for Xen changed to
"svc:/system/xvm/<service>:default". Therefor the Xen properties
are now
bash-3.2# svcprop -p config xvm/xend
config/default-nic astring ""
config/dom0-cpus integer 0
config/dom0-min-mem integer 196
config/enable-dump boolean true
config/stability astring Unstable
config/xend-relocation-address astring 127.0.0.1
config/xend-relocation-hosts-allow astring \^localhost$
config/xend-relocation-server boolean true
config/xend-unix-server boolean true
| LogFile |
Content |
Comment |
| xend.log |
logging and back traces from the
long running daemon |
|
| xpvd-event.log |
logs from the backend device
creation and removal, etc |
|
| xend-debug.log |
||
| domain-builder-ng.log |
[06.04.08]
found in snv_85 |
|
| qemu-dm.$$.log |
log of the qemu part of xVM
(which is only used for HVM DomUs) |
$$ is unique number |
# uname -i
i86xpv
| By default Solaris detects what xen is using for it's console device and uses the same thing (you can of course override that with the -B or an entry in bootenv.rc, if you want the console to go to different devices. |
vncview 192.168.178.18:5900| If you don't have a vncviewer
installed, you can use the one which is
part of vino (remote desktop). Here's what I have on some of my systems. $ cat `which vncviewer` #!/bin/sh exec java -jar /usr/share/gnome/vino/vino-client.jar ${1+"$@"} |
xm pause" and "xm unpause" to pause or
resume a DomU, e.g.:|
By default, xend listens only on the loopback address for requests from the localhost. If you want to allow other machines to live migrate to the machine, you must do the following:
|
xm domid" and "xm domname" to convert a
DomID to a DomName and vice versa, e.g.xm network-list <domname>" to list the
currently attached network adapter of a DomU, e.g.network-attach domain-id [script=scriptname] [ip=ipaddr]
[mac=macaddr] [bridge=bridge-name] [backend=bedomain-id] network-detach domain-id devid xm block-attach mydomU1
pyh://vol/dev/rdsk/c1t0d0/ubuntu6.06i386 c3 r
If you need to use pygrub, an alternative is to convert 2008.05 to UFS: |
ethttool -K eth0 tx off
/etc/init.d/volmgt stopxm block-attach xen-centos1 phy://dev/rdsk/c1t0d0s0 /dev/sda3 rmount -o ro /dev/sda3 /mntumount /mntxm block-detach xen-centos1 /dev/sda3xm block-attach xen-centos1
pyh://vol/dev/rdsk/c1t0d0/ubuntu6.06i386 /dev/sda3 r| File |
Description |
|
| centos1.phy |
Xen configuration file for the
Centos image from the Xen Demo Disk: kernel = "/export/xen-images/centos1/vmlinuz-2.6.16.13-xen" memory = 128 name = "xen-centos1" disk = ['file:/export/xen-images/centos1/rootfs.img,sda1,w'] vif = [ 'mac=00:16:3E:00:00:15' ] root = "/dev/sda1 ro" |
[27.07.06 snv_43 Xen 07_2006] |
| start_xen_centos1.sh |
Sample script to start a Xen
DomU with the Centos image from the Xen
Demo Disk: sol9:/export/install/sol-nv-b89-x86-dvd #!/usr/bin/ksh |
[27.07.06 snv_43 Xen 07_2006] |
| start_xen.sh |
General kornshell script to
start a Xen DomU and/or attach a console and/or run the vncviewer for
the DomU. There's no documentation for the script right now - so please
check the source code. The important part is the part with the
configuration variables at the start of the script |
[14.09.06
snv_46 Xen 08_2006] |
| solaris10_0707_inst_on_SolarisDom0.phy | Xen configuration file for installing a Solaris 10 Xen 07/07
Solaris DomU on Solaris 10 Xen 07/07 Dom0 name = "solaris_10_July_07" memory = "368" vcpus = "1" disk = [ 'file:/data/cdtemp/sol10_xen.iso,6:cdrom,r','file:/test/Solaris10_xen0707.raw,0,w' ] vif = [ 'mac=00:0e:0c:3e:18:cd' ] on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' |
|
| solaris10_0707_run_on_SolarisDom0.phy |
Xen configuration file for running a Solaris 10 Xen 07/07
Solaris DomU on Solaris 10 Xen 07/07 Dom0 name = "solaris_10_July_07" memory = "368" vcpus = "1" disk = [ 'file:/export/xen-images/Solaris10_xen0707.raw,0,w' ] root = "/dev/dsk/c0d0s0" vif = [ 'mac=00:0e:0c:3e:18:cd' ] on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' |
|
| Solaris10_0707_inst_on_LinuxDom0.phy |
Xen configuration file for installing Solaris 10 Xen 07/07 DomU
on a Linux Dom0: name = "solaris_10_July_07_install" memory = "368" vcpus = "1" disk = [ 'file:/data/cdtemp/sol10_xen.iso,6:cdrom,r','file:/data/xen/Solaris10_xen0707_1.raw,0,w' ] vif = [ 'mac=00:0e:0c:3e:18:cd' ] on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' kernel = "/data/xen/Solaris10_xen0707.kernel" ramdisk = "/data/xen/x86.miniroot" rootdisk = "/dev/dsk/c0d0s0" extra = '/platform/i86xpv/kernel/unix -B install_media=cdrom' |
|
| Solaris10_0707_run_on_LinuxDom0.phy |
Xen configuration file for running Solaris 10 Xen 07/07 DomU on
a Linux Dom0: name = "solaris_10_July_07" memory = "368" vcpus = "1" disk = [ 'file:/data/xen/Solaris10_xen0707.raw,0,w' ] vif = [ 'mac=00:0e:0c:3e:18:cd' ] on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' kernel = "/data/xen/Solaris10_xen0707.kernel" ramdisk = "/data/xen/boot_archive1" rootdisk = "/dev/dsk/c0d0s0" extra = '/platform/i86xpv/kernel/unix -B bootpath=/xpvd/xdf@0:a' |
|
| xen_explorer.sh | Script to collect Xen related
informations for trouble shooting, see below |
 FedoraCore3.tar.bz2 |
289639 KB | 13/06/05 | 00:00:00 |
| FedoraCore3.tar.bz2.md5 |
1 KB | 14/06/05 | 00:00:00 |
| debian-31.tar.bz2 |
37010 KB | 09/06/05 | 00:00:00 |
| debian-31.tar.bz2.md5 |
1 KB | 14/06/05 | 00:00:00 |
| gentoo.tar.bz2 |
233783 KB | 15/11/05 | 00:00:00 |
| gentoo.tar.bz2.md5 |
1 KB | 15/11/05 | 00:00:00 |
| ttylinux-dns.tar.bz2 |
13120 KB | 17/06/05 | 00:00:00 |
| ttylinux-dns.tar.bz2.md5 |
1 KB | 17/06/05 | 00:00:00 |
| ttylinux-mysql-full.tar.bz2 |
10610 KB | 24/06/05 | 00:00:00 |
| ttylinux-mysql-full.tar.bz2.md5 |
1 KB | 24/06/05 | 00:00:00 |
| ttylinux-mysql-light.tar.bz2 |
3845 KB | 24/06/05 | 00:00:00 |
| ttylinux-mysql-light.tar.bz2.md5 |
1 KB | 24/06/05 | 00:00:00 |
| ubuntu-hoary.tar.bz2 |
109883 KB | 15/11/05 | 00:00:00 |
| ubuntu-hoary.tar.bz2.md5 |
1 KB | 15/11/05 | 00:00:00 |
| ubuntu-warty.tar.bz2 |
125786 KB | 15/11/05 | 00:00:00 |
| ubuntu-warty.tar.bz2.md5 |
ttylinux-5.1.tar.gz 03-Sep-2006 23:55 1.8M GZIP compressed docume>
ttylinux.image 12-Oct-2005 10:18 32.0M
ttylinux.tgz 11-Oct-2005 17:14 1.7M GZIP compressed tar ar>
http://cdprojekte.mattiasschlenker.de/Public/Xen-Images/ [01.01.08]
opensuse101-desktop-i386-20060514.tbz 14-May-2006 14:34 904M
opensuse101-minimal-amd64-20061106.tbz 06-Nov-2006 10:18 180M
opensuse101-minimal-i386-20061106.tbz 06-Nov-2006 13:18 185M
ubuntu606-desktop-i386-20060603.tbz 03-Jun-2006 13:07 562M
ubuntu606-minimal-amd64-20060723.tbz 23-Jul-2006 23:56 55M
ubuntu606-minimal-i386-20060723.tbz 24-Jul-2006 00:11 55M
ubuntu610-minimal-i386-20070330.tbz 30-Mar-2007 21:20 109M
ubuntu704-minimal-i386-20070331.tbz 31-Mar-2007 11:01 170M
uclibcroot-i386-20060515.tbz 15-May-2006 08:55 28M
Note: The descriptions of the images (in German) are here http://news.mattiasschlenker.de/2006/07/27/neue-tutorials-und-xen-images/ [01.01.08]