I want to install OpenSolaris-based Dom0 onto a compact flash card and thus need to get the smallest install possible. [Note: the space for all the DomUs will come from iSCSI mounts and logs will be forwarded to a syslog server] I tried "Core System Support"and then added xVM and virt-install, but the dependencies had me installing Java, which itself needed XWindows...next thing I knew I was over 2GB (my target CF size) Anybody know what dependencies can be safely ignored - assuming I''m running only console access on Dom0 and all DomUs? Thanks! Kent
Kent Watsen wrote:> I want to install OpenSolaris-based Dom0 onto a compact flash card and > thus need to get the smallest install possible. [Note: the space for > all the DomUs will come from iSCSI mounts and logs will be forwarded to > a syslog server] > > I tried "Core System Support"and then added xVM and virt-install, but > the dependencies had me installing Java, which itself needed > XWindows...next thing I knew I was over 2GB (my target CF size) > > Anybody know what dependencies can be safely ignored - assuming I''m > running only console access on Dom0 and all DomUs? > > Thanks! > Kent > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >Java, it might beak some SMF services, deal with them by disabling. Known one off the top of my head would be webconsole, wbem, perhaps others. Java even tries pulling in CDE icons and "java extensions" which are indeed needed for Swing applications, but for console are not a big deal, in the instance you did want Java, as long as you didn''t need X11, most apps should work, but there''s no promise in saying that, who knows unless you try it. I believe the xVM console/viewer is in Java fwiw, so be aware, and there''s no remote option yet aside from VNC. You can safely remote webconsole, wbem, CDE, GNOME, StarOffice, gcc, Java help, Java demos, Java Desktop System stuff, some things may break, but you could extract the packages and fix the dependency issues with simple tools like ldd. James
Hi Kent, I only created a minimal Solaris DomU until now. That is documented on my web page http://home.arcor.de/bnsmb/public/htdocs/Xen_and_Solaris.html#mozTocId791059. I think that is a good starting point to create a minimal Dom0 for Solaris. There might be some packages missing but IMHO that shouldn''t be that much. IMHO you really don''t need Java in the Dom0. Just ignore the dependency if any and test your Dom0. regards Bernd tion cluster is necessary to install Xen? Kent Watsen wrote:> I want to install OpenSolaris-based Dom0 onto a compact flash card and > thus need to get the smallest install possible. [Note: the space for > all the DomUs will come from iSCSI mounts and logs will be forwarded to > a syslog server] > > I tried "Core System Support"and then added xVM and virt-install, but > the dependencies had me installing Java, which itself needed > XWindows...next thing I knew I was over 2GB (my target CF size) > > Anybody know what dependencies can be safely ignored - assuming I''m > running only console access on Dom0 and all DomUs? > > Thanks! > Kent > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org > >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Hi Bernd, Your site is great - I wish SUN''s xVM FAQ looked more like it... On your site you say "Note that you must disable the automatic reboot after installation and add the packages listed above manually if you''re installing in a DomU" - is this saying that you have to install the missing packages prior to reboot? - inside the installer wizard or after installation is complete? - isn''t it possible to reboot SUNWCrnet first and install the remaining packages afterwards? Thanks, Kent Bernd Schemmer wrote:> Hi Kent, > > I only created a minimal Solaris DomU until now. That is documented on > my web page > > http://home.arcor.de/bnsmb/public/htdocs/Xen_and_Solaris.html#mozTocId791059. > > > I think that is a good starting point to create a minimal Dom0 for > Solaris. There might be some packages missing but IMHO that shouldn''t > be that much. > > IMHO you really don''t need Java in the Dom0. Just ignore the > dependency if any and test your Dom0. > > regards > > Bernd > > > tion cluster is necessary to install Xen? > > Kent Watsen wrote: >> I want to install OpenSolaris-based Dom0 onto a compact flash card >> and thus need to get the smallest install possible. [Note: the space >> for all the DomUs will come from iSCSI mounts and logs will be >> forwarded to a syslog server] >> >> I tried "Core System Support"and then added xVM and virt-install, but >> the dependencies had me installing Java, which itself needed >> XWindows...next thing I knew I was over 2GB (my target CF size) >> >> Anybody know what dependencies can be safely ignored - assuming I''m >> running only console access on Dom0 and all DomUs? >> >> Thanks! >> Kent >> >> _______________________________________________ >> xen-discuss mailing list >> xen-discuss@opensolaris.org >> >> > >
On Wed, Jan 16, 2008 at 09:34:10AM -0500, Kent Watsen wrote:> Your site is great - I wish SUN''s xVM FAQ looked more like it...The FAQ is a little sparse, true. If you have suggestions for things you''d like to see documented on the opensolaris site let us know. We''re trying, wherever possible, to make the man pages self-explanatory though (and virt-manager will help a lot when it lands) regards john
Kent Watsen wrote:> I want to install OpenSolaris-based Dom0 onto a compact flash card and > thus need to get the smallest install possible. [Note: the space for > all the DomUs will come from iSCSI mounts and logs will be forwarded to > a syslog server] > > I tried "Core System Support"and then added xVM and virt-install, but > the dependencies had me installing Java, which itself needed > XWindows...next thing I knew I was over 2GB (my target CF size) > > Anybody know what dependencies can be safely ignored - assuming I''m > running only console access on Dom0 and all DomUs?I have been meaning to do a blog entry on how to do this but haven''t found the time yet... Here''s a quick way to build a minimal domU which can also be used for an embedded dom0. I have a dom0 which I run off of a ram disk booted from a USB flash and then can start multiple domUs using the same ramdisk used to boot dom0. I''ll just cover how to build the domU and then follow up how to build the ramdisk and put it on a USB flash in a later e-mail. Setup your domU disk, newfs it, and mount it. In this example I''m assuming you mounted it under /mnt. : alpha[1]#; dd if=/dev/zero of=./disk.img bs=1024k count=512 : alpha[1]#; lofiadm -a `pwd`/disk.img : alpha[1]#; newfs /dev/rlofi/1 : alpha[1]#; mount -F ufs /dev/lofi/1 /mnt then run the script below, unmount/lofiadm -d your disk, then boot your domU and configure it how you want. You may want to customize the packages to include any disk adapter/NIC drivers you need, etc.. I''m using the following py file to boot it. Make sure you umount /mnt and lofiadm -d first ;-) : alpha[1]#; cat embedded-disk.py name = "embedded-disk" vcpus = 1 memory = "512" root = "/dev/dsk/c0d0s0" disk = [''file:/export/guests/embedded/disk.img,0,w''] vif = [''''] This is a script that I''ve been hacking on. suggestions/improvements welcome. :-) Someday I''d like it to be command line based but don''t have time to do that right now. You need to modify the ROOTDIR, PROD, and PROD_OVERRIDE paths below. Also customize any packages you want/don''t want. I have a SMF service which I commented in my setup which brings up DHCP on all NICs reported by dladm. Probably better if you use NWAM. But I can send those out if someone is really interested. ---- : alpha[1]#; cat build-domU.sh #!/bin/ksh PKGADD=/usr/sbin/pkgadd PKGLOG=/tmp/packages.log PKGADMIN=/tmp/pkgadmin ROOTDIR=/mnt PROD=/export/install/i386/nevada/79/Solaris_11/Product PROD_OVERRIDE=/tank/ws/xvm-remote/packages-nondebug # # Minimum list of packages that boots to login prompt on text console. # Add additional packages to get more functionality (e.g. add SUNWmdbr # for kernel debugging via kmdb). # BASE=" SUNWcar.i SUNWcarx.i SUNWcakr.i SUNWcakrx.i SUNWkvm.i SUNWcsr SUNWcsd SUNWos86r SUNWrmodr SUNWpsdcr SUNWpsdir SUNWckr SUNWcnetr SUNWcsl SUNWcsu SUNWcslr SUNWesu SUNWkey SUNWlibms SUNWlibmsr SUNWusb SUNWpr SUNWtls SUNWlibsasl SUNWlxml SUNWopenssl-libraries SUNWusbs SUNWmdr SUNWmdu SUNWtecla SUNWzlib SUNWuprl SUNWsmapi SUNWkrbr SUNWkrbu SUNWgss SUNWbipr SUNWbip SUNWzfskr SUNWzfsr SUNWzfsu SUNWbash SUNWipfr SUNWipfu " SYSID=" SUNWadmap SUNWadmlib-sysid SUNWadmr " SSH=" SUNWsshcu SUNWsshdr SUNWsshdu SUNWsshr SUNWsshu " NFSCLIENT=" SUNWnfsckr SUNWnfscr SUNWnfscu " NFSSERVER=" SUNWnfsskr SUNWnfssr SUNWnfssu " NIS=" SUNWnisr SUNWnisu " AUTOFS=" SUNWatfsr SUNWatfsu " MDB=" SUNWmdb SUNWmdbr " DOM0=" SUNWPython SUNWPython-extra SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWxvmhvm SUNWxvmdomr SUNWxvmdomu SUNWxvmu SUNWxvmr SUNWgccruntime SUNWgnutls SUNWlibsdl SUNWxwplt SUNWxwrtl " NICS=" SUNWbge SUNWnge SUNWrge SUNWxge SUNWintgige " DISK_HBAS=" SUNWahci " # # Create a pkg admin file - see man admin(4) # sed ''s/ask/nocheck/'' /var/sadm/install/admin/default > $PKGADMIN echo "adding packages to $ROOTDIR" for pkg in $BASE $SYSID $SSH $MDB $NFSCLIENT $AUTOFS $DOM0 $NIS $DISK_HBAS; do if [ -d "$PROD_OVERRIDE/$pkg" ]; then $PKGADD -a $PKGADMIN -d $PROD_OVERRIDE -R $ROOTDIR $pkg \ > PKGLOG 2>&1 elif [ -d "$PROD/$pkg" ]; then $PKGADD -a $PKGADMIN -d $PROD -R $ROOTDIR $pkg \ > PKGLOG 2>&1 else echo " $pkg not found: skipped" fi done # seed the SMF repository /usr/bin/cp $ROOTDIR/lib/svc/seed/global.db $ROOTDIR/etc/svc/repository.db chmod 600 $ROOTDIR/etc/svc/repository.db cd $ROOTDIR/var/svc/profile/ rm -f generic.xml name_service.xml ln -s generic_limited_net.xml generic.xml ln -s ns_files.xml name_service.xml # # Setup DHCP on all NICs # #cp /tank/ws/embedded/devices-net $ROOTDIR/lib/svc/method/ #cp /tank/ws/embedded/devices-net.xml $ROOTDIR/var/svc/manifest/system/device/ # save away vfstab for domU and ramdisk /usr/bin/cp $ROOTDIR/etc/vfstab $ROOTDIR/etc/vfstab.disk /usr/bin/cp $ROOTDIR/etc/vfstab $ROOTDIR/etc/vfstab.ramdisk echo "/devices/ramdisk:a - / ufs - no nologging" >> $ROOTDIR/etc/vfstab.ramdisk echo "/dev/dsk/c0d0s0 /dev/rdsk/c0d0s0 / ufs 1 no -" >> $ROOTDIR/etc/vfstab.disk # build up /dev. This causes some minor problems but will self correct. # XXX - This would be better if we had a seed tarball. /usr/sbin/devfsadm -R $ROOTDIR # make the disk links for domU cd $ROOTDIR/dev/dsk rm -f c0d0s0 /usr/bin/ln -s ../../devices/xpvd/xdf@0:a c0d0s0 cd $ROOTDIR/dev/rdsk rm -f c0d0s0 /usr/bin/ln -s ../../devices/xpvd/xdf@0:a,raw c0d0s0 /usr/bin/cp $ROOTDIR/etc/vfstab.disk $ROOTDIR/etc/vfstab # spinkle a little magic sysconfig fairy dust echo "/lib/svc/method/sshd\n\ /usr/sbin/sysidkbd\n\ /usr/sbin/sysidpm\n\ /lib/svc/method/net-nwam\n\ /usr/lib/cc-ccr/bin/eraseCCRRepository" > $ROOTDIR/etc/.sysidconfig.apps # setup the image so we need to configure it on first boot # XXX: if we setup timezone, could we save the reboot?? /usr/sbin/sys-unconfig -R $ROOTDIR echo "build boot_archive" /usr/sbin/bootadm update-archive -R $ROOTDIR
Mark Johnson wrote:> I''ll just cover how to build the domU and then > follow up how to build the ramdisk and put it > on a USB flash in a later e-mail.The first problem is that program which builds a boot archive doesn''t handle the -s parameter correctly. e.g. /boot/solaris/bin/root_archive s) EXTRA_SPACE="$OPTARG" I am hacking that script right now, adding an extra 64M to my ramdisk.. Extra credit for anyone who would like to contribute a fix for this :-) : alpha[1]#; diff root_archive.new /boot/solaris/bin/root_archive 739,740c739 < END {print int((t + (64 * 1024 * 1024)) * 1.10 / 1024)}'') < --- > END {print int(t * 1.10 / 1024)}'') : alpha[1]#; To build a ramdisk, I make sure my disk based embedded domU is shutdown first!!! Make sure you''ve configured it how you want it to be, users, etc. Since this is a ramdisk, you won''t be able to make persistent changes to it. This is off the top of my head, so there could be some typos. : alpha[1]#; cp disk.img temp.img : alpha[1]#; lofiadm -a `pwd`/temp.img : alpha[1]#; mount /dev/lofi/1 /mnt : alpha[1]#; rm /mnt/platform/i86pc/boot_archive : alpha[1]#; rm /mnt/platform/i86pc/amd64/boot_archive : alpha[1]#; mkdir -p xvm/amd64 : alpha[1]#; root_archive.new pack ./xvm/solaris.ramdisk /mnt : alpha[1]#; cp /mnt/platform/i86xpv/kernel/unix xvm : alpha[1]#; cp /mnt/boot/xen.gz xvm/ : alpha[1]#; cp /mnt/platform/i86xpv/kernel/amd64/unix xvm/amd64/ : alpha[1]#; cp /mnt/boot/amd64/xen.gz xvm/amd64/ Now you should have a ramdisk that you can boot on domU and dom0. Here''s my domU py file. : alpha[1]#; cat ./xvm/guest.py name = "embedded" vcpus = 1 memory = "512" kernel = "/tank/guests/embedded/boot/xvm/amd64/unix" ramdisk = "/tank/guests/embedded/boot/xvm/solaris.ramdisk" extra = "/platform/i86xpv/kernel/amd64/unix -k" vif = [''''] Here''s my dom0 grub menu.lst entry -- title Embedded Solaris xVM (serial console) kernel$ /boot/xvm/$ISADIR/xen.gz com1=9600,8n1 console=com1 module$ /boot/xvm/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -k -B console=ttya module$ /boot/xvm/solaris.ramdisk Finally, you can put this on a USB or compact flash drive. This should work on FAT32, etc, since it''s just a ramdisk file. Right now install_grub expects a Solaris disk so the instructions below will just cover that. o list usb disks, note the /dev/dsk/c<yourdisk> # rmmount -l o unmount all the usb flash partitions, verify they are unmounted # rmumount <usbflash> # df -lk o partition the usb flash stick, delete all partitions and make 1 solaris 2 partition # fdisk /dev/rdsk/c<yourdisk>p0 o format the partition. Put all of the flash in s0. Save as SMI. # format -e o make it a UFS slice # newfs /dev/rdsk/c<yourdisk>s0 o install grub # installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c<yourdisk>s0 o install the embedded dom0 # mount /dev/dsk/c1t0d0s0 /mnt # cd /mnt # <copy your xvm files to /mnt, see my layout below> o Reboot off the USB flash (Exercise for the reader) o login as root o give it a spin, you can boot the same image your using as a dom0 as a domU. (NOTE: the current py file assumes you are booted in 64-bit) # xm list # <mount your usb disk over /boot> # xm create -c /boot/xvm/guest.py --- Here is the layout of my flash disk : alpha[1]#; ls -lR .: total 20 drwxr-xr-x 2 root root 512 Jan 16 10:37 grub/ drwx------ 2 root root 8192 Jan 11 09:11 lost+found/ drwxr-xr-x 3 root root 512 Jan 16 10:37 xvm/ ./grub: total 2 -rw-r--r-- 1 root root 461 Jan 16 10:38 menu.lst ./lost+found: total 0 ./xvm: total 197430 drwxr-xr-x 2 root root 512 Jan 11 08:35 amd64/ -rw-r--r-- 1 root root 244 Jan 11 16:56 guest.py -rwxr-xr-x 1 root root 99340669 Jan 11 07:29 solaris.ramdisk* -rwxr-xr-x 1 root root 1353352 Jan 11 07:29 unix* -rwxr-xr-x 1 root root 300119 Jan 11 07:29 xen.gz* ./xvm/amd64: total 4176 -rwxr-xr-x 1 root root 1780432 Jan 11 07:29 unix* -rwxr-xr-x 1 root root 328566 Jan 11 07:29 xen.gz* : alpha[1]#; where... : alpha[1]#; cat grub/menu.lst default 0 fallback 1 timeout 10 serial --unit=0 --speed=9600 terminal --timeout=10 console serial title Solaris xVM kernel$ /xvm/$ISADIR/xen.gz module$ /xvm/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -k -B console=text module$ /xvm/solaris.ramdisk title Solaris xVM (serial console) kernel$ /xvm/$ISADIR/xen.gz com1=9600,8n1 console=com1 module$ /xvm/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -k -B console=ttya module$ /xvm/solaris.ramdisk : alpha[1]#; I mount the USB stick over /boot, then run domUs with.... : alpha[1]#; cat xvm/guest.py name = "embedded" vcpus = 1 memory = "512" kernel = "/boot/xvm/amd64/unix" ramdisk = "/boot/xvm/solaris.ramdisk" extra = "/platform/i86xpv/kernel/amd64/unix -k" vif = ['''',''''] on_shutdown = "destroy" on_reboot = "restart" on_crash = "destroy"
John Levon wrote:> On Wed, Jan 16, 2008 at 09:34:10AM -0500, Kent Watsen wrote: > >> Your site is great - I wish SUN''s xVM FAQ looked more like it... > > The FAQ is a little sparse, true. If you have suggestions for things > you''d like to see documented on the opensolaris site let us know. We''re > trying, wherever possible, to make the man pages self-explanatory though > (and virt-manager will help a lot when it lands)Very recently an early version of virt-manager was made available here: http://opensolaris.org/os/project/jds/tasks/virt-manager/ Please share any feedback.
And one last dump of information.. You can also use a slight variation of the previous script to build a domU from the new packaging system too. This will be pretty cool in the future.. MRJ : alpha[1]#; cat pkg.sh #!/bin/ksh ROOTDIR=/export/pkg-test BASE=" SUNWcs SUNWcsd SUNWckr SUNWcar SUNWcarx SUNWcakr SUNWcakrx SUNWos86r SUNWkvm SUNWrmodr SUNWpsdcr SUNWpsdir SUNWckr SUNWcnetr SUNWcsl SUNWesu SUNWkey SUNWlibms SUNWusb SUNWpr SUNWtls SUNWlibsasl SUNWlxml SUNWopenssl SUNWusbs SUNWmd SUNWtecla SUNWzlib SUNWuprl SUNWsmapi SUNWkrb SUNWgss SUNWbip SUNWzfskr SUNWzfs SUNWbash SUNWipf SUNWbash SUNWfmd SUNWgrub SUNWperl584core SUNWtoo SUNWbind SUNWrcmdc " # NOTES: # perl needed for intrd # packaging system PKG=" SUNWPython SUNWPython-extra SUNWipkg " # needed for sys-unconfig, etc. SYSID=" SUNWadmap SUNWadmlib-sysid SUNWadmr " SSH=" SUNWsshcu SUNWsshd SUNWssh " NFSCLIENT=" SUNWnfsckr SUNWnfsc " NFSSERVER=" SUNWnfsskr SUNWnfss " NIS=" SUNWnis " AUTOFS=" SUNWatfs " MDB=" SUNWmdb " DOM0=" SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWxvmhvm SUNWxvmdom SUNWxvm SUNWgccruntime SUNWgnutls SUNWlibsdl FSWxwpft FSWxwrtl " # dom0 devices DEVS=" SUNWbge SUNWnge SUNWrge SUNWxge SUNWintgige SUNWahci SUNWmv88sx SUNWnvsata SUNWsi3124 " # create the packaging db /usr/bin/pkg image-create -F -a opensolaris.org=http://pkg.opensolaris.org $ROOTDIR #pkg image-create -F -a mrj=http://localhost:10000 $ROOTDIR cd $ROOTDIR echo "adding packages to `pwd`" for pkg in $BASE $PKG $SYSID $SSH $MDB $NFSCLIENT $AUTOFS $NIS; do /usr/bin/pkg install $pkg done # dom0 support #for pkg in $DOM0 $DEVS; do # /usr/bin/pkg install $pkg #done # seed the SMF repository /usr/bin/cp $ROOTDIR/lib/svc/seed/global.db $ROOTDIR/etc/svc/repository.db chmod 600 $ROOTDIR/etc/svc/repository.db cd $ROOTDIR/var/svc/profile/ ln -s generic_limited_net.xml generic.xml ln -s ns_files.xml name_service.xml # save away vfstab for domU and ramdisk /usr/bin/cp $ROOTDIR/etc/vfstab $ROOTDIR/etc/vfstab.disk /usr/bin/cp $ROOTDIR/etc/vfstab $ROOTDIR/etc/vfstab.ramdisk echo "/devices/ramdisk:a - / ufs - no nologging" >> $ROOTDIR/etc/vfstab.ramdisk echo "/dev/dsk/c0d0s0 /dev/rdsk/c0d0s0 / ufs 1 no -" >> $ROOTDIR/etc/vfstab.disk # build up /dev. This causes some minor problems but will self correct. # XXX - This would be better if we had a seed tarball. /usr/sbin/devfsadm -R $ROOTDIR # make the disk links for domU cd $ROOTDIR/dev/dsk rm -f c0d0s0 /usr/bin/ln -s ../../devices/xpvd/xdf@0:a c0d0s0 cd $ROOTDIR/dev/rdsk rm -f c0d0s0 /usr/bin/ln -s ../../devices/xpvd/xdf@0:a,raw c0d0s0 /usr/bin/cp $ROOTDIR/etc/vfstab.disk $ROOTDIR/etc/vfstab # spinkle a little magic sysconfig fairy dust echo "/lib/svc/method/sshd\n\ /usr/sbin/sysidkbd\n\ /usr/sbin/sysidpm\n\ /lib/svc/method/net-nwam\n\ /usr/lib/cc-ccr/bin/eraseCCRRepository" > $ROOTDIR/etc/.sysidconfig.apps # setup the image so we need to configure it on first boot # XXX: if we setup timezone, could we save the reboot?? /usr/sbin/sys-unconfig -R $ROOTDIR # remove some Indiana iso specific stuff cat $ROOTDIR/etc/passwd | sed ''/^jack/d'' > $ROOTDIR/etc/passwd.new;mv -f $ROOTDIR/etc/passwd.new $ROOTDIR/etc/passwd cat $ROOTDIR/etc/shadow | sed ''/^jack/d'' > $ROOTDIR/etc/shadow.new;mv -f $ROOTDIR/etc/shadow.new $ROOTDIR/etc/shadow cat $ROOTDIR/etc/user_attr | sed ''s/^root::::type=role;/root::::/g'' > $ROOTDIR/etc/user_attr.new;mv -f $ROOTDIR/etc/user_attr.new $ROOTDIR/etc/user_attr echo "build boot_archive" /usr/sbin/bootadm update-archive -R $ROOTDIR : alpha[1]#;
Missed a step. Mark Johnson wrote:> Mark Johnson wrote:> To build a ramdisk, I make sure my disk based embedded domU > is shutdown first!!! Make sure you''ve configured it how > you want it to be, users, etc. Since this is a ramdisk, > you won''t be able to make persistent changes to it. > > This is off the top of my head, so there could be some typos. > > > : alpha[1]#; cp disk.img temp.img > : alpha[1]#; lofiadm -a `pwd`/temp.img > : alpha[1]#; mount /dev/lofi/1 /mnt > : alpha[1]#; rm /mnt/platform/i86pc/boot_archive > : alpha[1]#; rm /mnt/platform/i86pc/amd64/boot_archive: alpha[1]#; cp /mnt/etc/vfstab.ramdisk /mnt/etc/vfstab MRJ
Kent Watsen wrote: Kent, >>On your site you say "Note that you must disable the automatic reboot after installation and add the packages listed above manually if you''re installing in a >>DomU" - is this saying that you have to install the missing packages prior to reboot? - inside the installer wizard or after installation is complete? - isn''t it possible >>to reboot SUNWCrnet first and install the remaining packages afterwards? That''s only necessary if you install the SUNWCrnet in a DomU; the DomU will not boot correct if the packages are missing (if I remember correct). I installed the packages after the installer finished manually If you''re installing a Dom0 you can reboot after the SUNWCrnet and install the missing packages after the reboot. regards Bernd> > Hi Bernd, > > Your site is great - I wish SUN''s xVM FAQ looked more like it... > > On your site you say "Note that you must disable the automatic reboot > after installation and add the packages listed above manually if > you''re installing in a DomU" - is this saying that you have to install > the missing packages prior to reboot? - inside the installer wizard > or after installation is complete? - isn''t it possible to reboot > SUNWCrnet first and install the remaining packages afterwards? > > Thanks, > Kent > > > > Bernd Schemmer wrote: >> Hi Kent, >> >> I only created a minimal Solaris DomU until now. That is documented >> on my web page >> >> http://home.arcor.de/bnsmb/public/htdocs/Xen_and_Solaris.html#mozTocId791059. >> >> >> I think that is a good starting point to create a minimal Dom0 for >> Solaris. There might be some packages missing but IMHO that shouldn''t >> be that much. >> >> IMHO you really don''t need Java in the Dom0. Just ignore the >> dependency if any and test your Dom0. >> >> regards >> >> Bernd >> >> >> tion cluster is necessary to install Xen? >> >> Kent Watsen wrote: >>> I want to install OpenSolaris-based Dom0 onto a compact flash card >>> and thus need to get the smallest install possible. [Note: the >>> space for all the DomUs will come from iSCSI mounts and logs will be >>> forwarded to a syslog server] >>> >>> I tried "Core System Support"and then added xVM and virt-install, >>> but the dependencies had me installing Java, which itself needed >>> XWindows...next thing I knew I was over 2GB (my target CF size) >>> >>> Anybody know what dependencies can be safely ignored - assuming I''m >>> running only console access on Dom0 and all DomUs? >>> >>> Thanks! >>> Kent >>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >>> >>> >> >> >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Hi Mark, I used or instructions to create a minimal Solaris DomU. I changed some minor things to get it work (see below) but in principle it worked very well (I did not test the use of a USB drive /compact flash card for the Dom0/DomU until now). I''ve documented my efforts here: http://home.arcor.de/bnsmb/public/htdocs/Xen_and_Solaris.html#How_to_create_a_minimal_Solaris_DomU_or and here http://home.arcor.de/bnsmb/public/htdocs/Xen_and_Solaris.html#How_to_create_a_Solaris_DomU_or_Dom0_that_boots_from_a_RAM_disk The script to create the minimal DomU is here http://home.arcor.de/bnsmb/public/solaris/xen/buildDomU.sh The script to create the ram disk is here: http://home.arcor.de/bnsmb/public/solaris/xen/buildDomU_ramdisk.sh There''s only one open issue with a failed SMF service in the DomU. And I could not start a Dom0 using the ramdisk until now. regards Bernd Tested in Solaris snv_78 ------------------------ Changes made to the script to create the minimal DomU/Dom0 ========================================================= 1. I changed "> PKGLOG" to ">> $PKGLOG" ---------------------------------------------------------- 2. Added mkdir $ROOTDIR/boot/grub before /usr/sbin/bootadm update-archive -R $ROOTDIR Without creating the directory the bootadm command fails: build boot_archive /mnt/: not a GRUB boot OS instance And the image is not bootable: bash-3.2# xm create -c embbed_solaris.cfg Using config file "./embbed_solaris.cfg". Error: Boot loader didn''t return any data! ---------------------------------------------------------- 3. Added the packages with mkisofs to the DomU disk image added SUNWmkcdr and SUNWmkcd to the packages to install reason: The update of the boot-archive failed most of the times in the minimal DomU because of not enough memory without mkisofs. If mksiofs does not exist bootadm creates a boot-archive with UFS and that process uses much more memory than creating a boot-archive with hsfs (using mkisofs). ---------------------------------------------------------- 3. Added some echo and check commands ---------------------------------------------------------- Changes to the Solaris configuration after booting the new DomU: bash-3.2# svcs -x svc:/system/intrd:default (interrupt balancer) State: maintenance since Fri Jan 18 23:14:17 2008 Reason: Restarting too quickly. See: http://sun.com/msg/SMF-8000-L5 See: intrd(1M) See: /var/svc/log/system-intrd:default.log Impact: This service is not running. svc:/system/fmd:default (Solaris Fault Manager) State: offline since Fri Jan 18 23:14:03 2008 Reason: Dependency file://localhost/usr/lib/fm/fmd/fmd is absent. See: http://sun.com/msg/SMF-8000-E2 See: fmd(1M) Impact: This service is not running. bash-3.2# Disabled both services before creating the ram disk svcadm disable svc:/system/intrd:default svcadm disable svc:/system/fmd:default Note: sys:/system/intrd:default is not running because the service needs Perl which is not installed in the Image. bash-3.2# tail /var/svc/log/system-intrd:default.log /lib/svc/method/svc-intrd: /usr/lib/intrd: not found [ Jan 18 23:14:17 Method "start" exited with status 0. ] [ Jan 18 23:14:17 Stopping because all processes in service exited. ] [ Jan 18 23:14:17 Executing stop method (:kill). ] [ Jan 18 23:14:17 Executing start method ("/lib/svc/method/svc-intrd"). ] /lib/svc/method/svc-intrd: /usr/lib/intrd: not found [ Jan 18 23:14:17 Method "start" exited with status 0. ] [ Jan 18 23:14:17 Stopping because all processes in service exited. ] [ Jan 18 23:14:17 Executing stop method (:kill). ] [ Jan 18 23:14:17 Restarting too quickly, changing state to maintenance. ] bash-3.2# file /usr/lib/intrd /usr/lib/intrd: executable /usr/perl5/bin/perl script Question: Do we need this service? If yes, Perl (and maybe other packages) must be added to the image. --------------------------------------------------------- In preparation for the creation of the ramdisk I disabled the service to update the boot-archive in the DomU image before creating the ramdisk: svcadm disable svc:/system/boot-archive-update:default --------------------------------------------------------- Changes made to the code to create a ramdisk for the minimal DomU/Dom0 ===================================================================== Corrected the links for the root device /dev/{r}dsk/c0d0s0 in the image file before creating the ramdisk: echo "Correcting the devices links for the root disk in the image ..." TMP_MOUNTPOINT="/mnt" ... mount ${LOFI_DEVICE} ${TMP_MOUNTPOINT} # new code: # change the root device in the image rm ${TMP_MOUNTPOINT}/dev/dsk/c0d0s0 rm ${TMP_MOUNTPOINT}/dev/rdsk/c0d0s0 ln -s ../../devices/ramdisk:a ${TMP_MOUNTPOINT}/dev/dsk/c0d0s0 ln -s ../../devices/ramdisk:a,raw ${TMP_MOUNTPOINT}/dev/rdsk/c0d0s0 Without these changes the DomU will always boot in the maintenance mode with root readonly mounted and no /tmp because the service to mount the local filesystem fails. Open Issues ========== I could not boot the ramdisk in a Dom0 until now, my grub menu entries are: title Embedded Solaris xVM 64 Bit (serial console) kernel$ /boot/$ISADIR/xen.gz com1=96008n1 console=com1 module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -k -B console=ttya module$ /boot/solaris.ramdisk title Embedded Solaris xVM 32 Bit (serial console) kernel$ /boot/xen.gz com1=9600,8n1 console=com1 module$ /platform/i86xpv/kernel/unix /platform/i86xpv/kernel/unix -k -B console=ttya module$ /boot/solaris.ramdisk title Embedded Solaris xVM 64 Bit (vga) kernel$ /boot/$ISADIR/xen.gz module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -k module$ /boot/solaris.ramdisk title Embedded Solaris xVM 32 Bit (vga) kernel$ /boot/xen.gz module$ /platform/i86xpv/kernel/unix /platform/i86xpv/kernel/unix -k module$ /boot/solaris.ramdisk Booting the 64 Bit kernel only loads the Xen kernel and then reboots immediately; booting the 32 Bit kernel stops with the error message saying there is "not enough memory for Dom0". My Ferrari has 1 GB memory --IMHO that should be enough to load the ramdisk and start a Dom0. The size of the ramdisk file is: bash-3.2# ls -l /boot/solaris.ramdisk -rw-r--r-- 1 root root 98759429 Jan 19 22:00 /boot/solaris.ramdisk The size of the unpacked ramdisk file is: bash-3.2# ls -l ./myramdisk -rw-r--r-- 1 root root 383283200 Jan 20 14:40 ./myramdisk The size of the filesystem in the ramdisk file is: bash-3.2# df -k /mnt1 Filesystem kbytes used avail capacity Mounted on /dev/lofi/2 350994 264939 50956 84% /mnt1 Mark Johnson wrote:> I have been meaning to do a blog entry on how to do > this but haven''t found the time yet... > > Here''s a quick way to build a minimal domU which > can also be used for an embedded dom0. > > I have a dom0 which I run off of a ram disk booted > >from a USB flash and then can start multiple domUs > using the same ramdisk used to boot dom0. > > I''ll just cover how to build the domU and then > follow up how to build the ramdisk and put it > on a USB flash in a later e-mail. > > >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Bernd Schemmer wrote:> Hi Mark, > > There''s only one open issue with a failed SMF service in the DomU.ah, right. I disable intrd and fmd? Sorry, forgot to put that down.. You are right, you can add in perl to get intrd to work (which I did in the pkg version of the script).> And I > could not start a Dom0 using the ramdisk until now. > > regards > > Bernd > > > > > Tested in Solaris snv_78 > ------------------------ > > > Changes made to the script to create the minimal DomU/Dom0 > =========================================================>thanks for all of the corrections.. I have been delaying sending it out because it was so raw.. But finally figured it would be better out there than not.> > > Open Issues > ==========> > I could not boot the ramdisk in a Dom0 until now, my grub menu entries are:>> title Embedded Solaris xVM 64 Bit (serial console) > kernel$ /boot/$ISADIR/xen.gz com1=96008n1 console=com1 > module$ /platform/i86xpv/kernel/$ISADIR/unix > /platform/i86xpv/kernel/$ISADIR/unix -k -B console=ttya > module$ /boot/solaris.ramdiskyou need to copy unix of out the ramdisk and use that. I separate all the embedded bits from the standard dom0 on my disk so I don''t get confused.. e.g. I would expect title Embedded Solaris xVM 64 Bit (serial console) kernel$ /boot/xvm/$ISADIR/xen.gz com1=96008n1 console=com1 module$ /boot/xvm/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -k -B console=ttya module$ /boot/xvm/solaris.ramdisk MRJ> title Embedded Solaris xVM 32 Bit (serial console) > kernel$ /boot/xen.gz com1=9600,8n1 console=com1 > module$ /platform/i86xpv/kernel/unix /platform/i86xpv/kernel/unix -k -B > console=ttya > module$ /boot/solaris.ramdisk > > title Embedded Solaris xVM 64 Bit (vga) > kernel$ /boot/$ISADIR/xen.gz > module$ /platform/i86xpv/kernel/$ISADIR/unix > /platform/i86xpv/kernel/$ISADIR/unix -k > module$ /boot/solaris.ramdisk > > title Embedded Solaris xVM 32 Bit (vga) > kernel$ /boot/xen.gz > module$ /platform/i86xpv/kernel/unix /platform/i86xpv/kernel/unix -k > module$ /boot/solaris.ramdisk > > > Booting the 64 Bit kernel only loads the Xen kernel and then reboots > immediately; booting the 32 Bit kernel stops with the error message > saying there is "not enough memory for Dom0". > > My Ferrari has 1 GB memory --IMHO that should be enough to load the > ramdisk and start a Dom0. > > The size of the ramdisk file is: > > bash-3.2# ls -l /boot/solaris.ramdisk > -rw-r--r-- 1 root root 98759429 Jan 19 22:00 > /boot/solaris.ramdisk > > The size of the unpacked ramdisk file is: > > bash-3.2# ls -l ./myramdisk > -rw-r--r-- 1 root root 383283200 Jan 20 14:40 ./myramdisk > > The size of the filesystem in the ramdisk file is: > > bash-3.2# df -k /mnt1 > Filesystem kbytes used avail capacity Mounted on > /dev/lofi/2 350994 264939 50956 84% /mnt1 > >
Mark, >>ah, right. I disable intrd and fmd? So both damoens are not necessary and can be disabled? I already disabled them and the DomU works - but I''m not sure if the intrd daemon is necessary. >>you need to copy unix of out the ramdisk and use that. >>I separate all the embedded bits from the standard >>dom0 on my disk so I don''t get confused.. The unix on the ramdisk is the same unix as in /platform/i86xpv/kernel/unix - or did I miss something? Anyway, I copied the file unix from the ramdisk into /boot/xvm/ and /boot/xvm/amd64 and the Dom0 still doesn''t boot. regards Bernd Mark Johnson wrote:> > > Bernd Schemmer wrote: >> Hi Mark, >> >> There''s only one open issue with a failed SMF service in the DomU. > > ah, right. I disable intrd and fmd? > Sorry, forgot to put that down.. You are right, > you can add in perl to get intrd to work (which > I did in the pkg version of the script). > > > >> And I could not start a Dom0 using the ramdisk until now. >> >> regards >> >> Bernd >> >> >> >> >> Tested in Solaris snv_78 >> ------------------------ >> >> >> Changes made to the script to create the minimal DomU/Dom0 >> =========================================================>> > > > thanks for all of the corrections.. I have been > delaying sending it out because it was so raw.. > But finally figured it would be better out there > than not. > > >> >> >> Open Issues >> ==========>> >> I could not boot the ramdisk in a Dom0 until now, my grub menu >> entries are: > > >> title Embedded Solaris xVM 64 Bit (serial console) >> kernel$ /boot/$ISADIR/xen.gz com1=96008n1 console=com1 >> module$ /platform/i86xpv/kernel/$ISADIR/unix >> /platform/i86xpv/kernel/$ISADIR/unix -k -B console=ttya >> module$ /boot/solaris.ramdisk > > > you need to copy unix of out the ramdisk and use that. > I separate all the embedded bits from the standard > dom0 on my disk so I don''t get confused.. > > e.g. I would expect > > title Embedded Solaris xVM 64 Bit (serial console) > kernel$ /boot/xvm/$ISADIR/xen.gz com1=96008n1 console=com1 > module$ /boot/xvm/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix > -k -B console=ttya > module$ /boot/xvm/solaris.ramdisk > > > > MRJ > > > >> title Embedded Solaris xVM 32 Bit (serial console) >> kernel$ /boot/xen.gz com1=9600,8n1 console=com1 >> module$ /platform/i86xpv/kernel/unix /platform/i86xpv/kernel/unix -k >> -B console=ttya >> module$ /boot/solaris.ramdisk >> >> title Embedded Solaris xVM 64 Bit (vga) >> kernel$ /boot/$ISADIR/xen.gz >> module$ /platform/i86xpv/kernel/$ISADIR/unix >> /platform/i86xpv/kernel/$ISADIR/unix -k >> module$ /boot/solaris.ramdisk >> >> title Embedded Solaris xVM 32 Bit (vga) >> kernel$ /boot/xen.gz >> module$ /platform/i86xpv/kernel/unix /platform/i86xpv/kernel/unix -k >> module$ /boot/solaris.ramdisk >> >> >> Booting the 64 Bit kernel only loads the Xen kernel and then reboots >> immediately; booting the 32 Bit kernel stops with the error message >> saying there is "not enough memory for Dom0". >> >> My Ferrari has 1 GB memory --IMHO that should be enough to load the >> ramdisk and start a Dom0. >> >> The size of the ramdisk file is: >> >> bash-3.2# ls -l /boot/solaris.ramdisk >> -rw-r--r-- 1 root root 98759429 Jan 19 22:00 >> /boot/solaris.ramdisk >> >> The size of the unpacked ramdisk file is: >> >> bash-3.2# ls -l ./myramdisk >> -rw-r--r-- 1 root root 383283200 Jan 20 14:40 ./myramdisk >> >> The size of the filesystem in the ramdisk file is: >> >> bash-3.2# df -k /mnt1 >> Filesystem kbytes used avail capacity Mounted on >> /dev/lofi/2 350994 264939 50956 84% /mnt1 >> >> >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Bernd Schemmer wrote:> Mark, > > >>ah, right. I disable intrd and fmd? > > So both damoens are not necessary and can be disabled?> I already disabled them and the DomU works - but I''m not sure if the > intrd daemon is necessary.intrd does dynamic interrupt distribution.. Don''t need that on a domU.> >>you need to copy unix of out the ramdisk and use that. > >>I separate all the embedded bits from the standard > >>dom0 on my disk so I don''t get confused.. > > The unix on the ramdisk is the same unix as in > /platform/i86xpv/kernel/unix - or did I miss something?Depends one what you have installed on your dom0 vs what Solaris install you used to build your domU. They don''t have to be the same.> Anyway, I copied the file unix from the ramdisk into /boot/xvm/ and > /boot/xvm/amd64 and the Dom0 still doesn''t boot.What happens when you try to boot? Did you copy the ramdisk version of vfstab to /etc/vfstab before building the ramdisk? Thanks, MRJ
Hi >>What happens when you try to boot? Booting the 32 Bit Version: The Xen Kernel boots and prints a message about "not enough ram for Domain 0 allocation" Booting the 64 Bit Version The Xen Kernel boots, prints some messages and immediately reboots (to fast to read the messages) The Ferrari does not have a serial port therefor I can not direct the output to com1. >>Did you copy the ramdisk >>version of vfstab to /etc/vfstab before building the ramdisk? The entry for the root filesystem in the /etc/vfstab is /dev/dsk/c0d0s0 /dev/rdsk/c0d0s0 / ufs - no nologging And I also tried this version /dev/dsk/c0d0s0 /dev/rdsk/c0d0s0 / ufs 1 no - /dev/{r}dsk/c0d0s0 are symbolic links to the ramdisk devices: [Sat Jan 26 22:10:24 root@dhcppc2 /mnt/dev] # ls -l *dsk/c0d0s0 lrwxrwxrwx 1 root root 23 Jan 19 19:58 dsk/c0d0s0 -> ../../devices/ramdisk:a lrwxrwxrwx 1 root root 27 Jan 19 19:58 rdsk/c0d0s0 -> ../../devices/ramdisk:a,raw I missed the line echo "/devices/ramdisk:a - / ufs - no nologging" >> $ROOTDIR/etc/vfstab.ramdisk in your message when I created the script but I think it will make no difference with that entry Tomorrow I can test the 32 Bit Dom0 on another machine that has a serial port (but that machine only has a 32 Bit CPU). regards Bernd Mark Johnson wrote:> > > Bernd Schemmer wrote: >> Mark, >> >> >>ah, right. I disable intrd and fmd? >> >> So both damoens are not necessary and can be disabled? > >> I already disabled them and the DomU works - but I''m not sure if the >> intrd daemon is necessary. > > intrd does dynamic interrupt distribution.. Don''t > need that on a domU. > > >> >>you need to copy unix of out the ramdisk and use that. >> >>I separate all the embedded bits from the standard >> >>dom0 on my disk so I don''t get confused.. >> >> The unix on the ramdisk is the same unix as in >> /platform/i86xpv/kernel/unix - or did I miss something? > > Depends one what you have installed on your dom0 > vs what Solaris install you used to build your > domU. They don''t have to be the same. > >> Anyway, I copied the file unix from the ramdisk into /boot/xvm/ and >> /boot/xvm/amd64 and the Dom0 still doesn''t boot. > > What happens when you try to boot? Did you copy the ramdisk > version of vfstab to /etc/vfstab before building the ramdisk? > > > > Thanks, > > > > > MRJ >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Hi, these are the messages on the serial console trying to boot the Dom0 with the RAM disk: xVM version 3.0.4-1-xvm Latest ChangeSet: Mon Nov 12 23:09:42 2007 -0800 13228:ed897008a4c9 (XEN) Command line: /boot/xen.gz com1=9600,8n1 console=com1 (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009fc00 (usable) (XEN) 000000000009fc00 - 00000000000a0000 (reserved) (XEN) 00000000000ce000 - 00000000000d2000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000003fff0000 (usable) (XEN) 000000003fff0000 - 000000003fff8000 (ACPI data) (XEN) 000000003fff8000 - 0000000040000000 (ACPI NVS) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000fff80000 - 0000000100000000 (reserved) (XEN) System RAM: 1023MB (1048124kB) (XEN) ACPI: RSDP (v000 AMI ) @ 0x000fabb0 (XEN) ACPI: RSDT (v001 AMIINT VIA_K7 0x00000011 MSFT 0x00000097) @ 0x3fff0000 (XEN) ACPI: FADT (v001 AMIINT VIA_K7 0x00000011 MSFT 0x00000097) @ 0x3fff0030 (XEN) ACPI: MADT (v001 AMIINT 0x00000009 MSFT 0x00000097) @ 0x3fff00b0 (XEN) ACPI: DSDT (v001 VIA VIA_K7 0x00001000 MSFT 0x0100000d) @ 0x00000000 (XEN) NUMA turned off (XEN) Faking a node at 0000000000000000-000000003fff0000 (XEN) Domain heap initialised: DMA width 30 bits (XEN) Xen heap: 9MB (10092kB) (XEN) PAE enabled, limit: 16 GB (XEN) found SMP MP-table at 000fbe40 (XEN) DMI 2.3 present. (XEN) Using APIC driver default (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 6:6 APIC version 16 (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 1333.348 MHz processor. (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 256K (64 bytes/line) (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: AMD Athlon(tm) XP 1500+ stepping 02 (XEN) Mapping cpu 0 to node 255 (XEN) Total of 1 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Platform timer is 1.193MHz PIT (XEN) Brought up 1 CPUs (XEN) Machine check exception polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Not enough RAM for domain 0 allocation. (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... The machine has 1 GB; the ramdisk OS boots fine in a DomU. regards Bernd Mark Johnson wrote:> > > Bernd Schemmer wrote: >> Mark, >> >> >>ah, right. I disable intrd and fmd? >> >> So both damoens are not necessary and can be disabled? > >> I already disabled them and the DomU works - but I''m not sure if the >> intrd daemon is necessary. > > intrd does dynamic interrupt distribution.. Don''t > need that on a domU. > > >> >>you need to copy unix of out the ramdisk and use that. >> >>I separate all the embedded bits from the standard >> >>dom0 on my disk so I don''t get confused.. >> >> The unix on the ramdisk is the same unix as in >> /platform/i86xpv/kernel/unix - or did I miss something? > > Depends one what you have installed on your dom0 > vs what Solaris install you used to build your > domU. They don''t have to be the same. > >> Anyway, I copied the file unix from the ramdisk into /boot/xvm/ and >> /boot/xvm/amd64 and the Dom0 still doesn''t boot. > > What happens when you try to boot? Did you copy the ramdisk > version of vfstab to /etc/vfstab before building the ramdisk? > > > > Thanks, > > > > > MRJ >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
Bernd Schemmer wrote:> Hi, > > these are the messages on the serial console trying to boot the Dom0 > with the RAM disk: > > xVM version 3.0.4-1-xvm > Latest ChangeSet: Mon Nov 12 23:09:42 2007 -0800 13228:ed897008a4c9 > (XEN) *** LOADING DOMAIN 0 *** > (XEN) > (XEN) **************************************** > (XEN) Panic on CPU 0: > (XEN) Not enough RAM for domain 0 allocation. > (XEN) **************************************** > (XEN) > (XEN) Reboot in five seconds... > > > The machine has 1 GB; the ramdisk OS boots fine in a DomU. >What does you menu.lst entry look like? Did you add 64M of extra space to the ramdisk? MRJ