Hi, I have a Solaris DomU in which only the 32 Bit version of Solaris is installed.
To start this DomU in a Solaris Dom0 that is also running in 32 Bit I can use this cfg file: In a Solaris xVM Dom0 booted in 64Bit mode the config file should look like name = "Milax" memory = "512" vcpus = "1" disk = [ 'file:/pool/xen/milax_with_xen.hdd,0,w' ] on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' To start the DomU in a Solaris xVM Dom0 that is running in 64 Bit I must copy the kernel and the ramdisk to the Dom0 and use this cfg file: name = "Milax" memory = "312" vcpus = "1" disk = [ 'file:/xen/milax_with_xen.hdd,0,w' ] vif = [ '' ] on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' kernel = "/xen/unix" ramdisk = "/xen/boot_archive_ufs" extra = "/platform/i86xpv/kernel/unix -r -B console=text,livemode=text" Using the cfg file without kernel and ramdisk entries leads to the error message: Using config file "./milax_on_ufs1.cfg". Error: Boot loader didn't return any data! The question is now: Can I avoid copying the kernel and ramdisk into the Dom0 so that I can use a cfg file like the one for the 32 Bit Dom0? (I'm running Solaris snv_89 and Solaris snv_101) regards Bernd -- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro _______________________________________________ xen-discuss mailing list [email protected]
