similar to: Some initial experiences.

After BFU-ing my system to b75 I ended up with a panicing system when booting into Xen: grub> #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- grub> title Solaris on Xen grub> kernel$ /boot/$ISADIR/xen.gz grub> module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -B console=ttyb grub> module$ /platform/i86pc/$ISADIR/boot_archive grub>

Can you use a different zvol for dump and swap rather than using the swap and dump zvol created by liveupgrade? Casper

I''ve upgraded my system from ufs to zfs (root pool). By default, it creates a zvol for dump and swap. It''s a 4GB Ultra-45 and every late night/morning I run a job which takes around 2GB of memory. With a zvol swap, the system becomes unusable and the Sun Ray client often goes into "26B". So I removed the zvol swap and now I have a standard swap partition. The

I have one thing happening now at boot which must have happened during the migration to zfs boot. I get an error message about /dev/random: "No randomness provider enabled for /dev/random. Use cryptoadm to provide one." Does anyone know how to fix this? Another thing: Is it possible to upgrade to a higher build when using zfs boot? Is this what LiveUpgrade does? And is there a step by

After a liveupgrade and luactivate I can login to the -new- BE. My question is: do I have to luactive the -old- BE again if I want to chose that one from the grub menu or can I just run it if I want to. -- Dick Hoogendijk -- PGP/GnuPG key: 01D2433D + http://nagual.nl/ | SunOS sxce snv107 ++ + All that''s really worth doing is what we do for others (Lewis Carrol)

# lucreate -n B85 Analyzing system configuration. Hi, after typing # lucreate -n B85 I get the following error: No name for current boot environment. INFORMATION: The current boot environment is not named - assigning name <BE1>. Current boot environment is named <BE1>. Creating initial configuration for primary boot environment <BE1>. ERROR: Unable to determine major and

Hello ,,,, can liveupgrade be done zfs i am running snv_35 on sparc if so how tks art This message posted from opensolaris.org

Hello ,,,, can liveupgrade be done zfs i am running snv_35 on sparc if so how tks art This message posted from opensolaris.org

Author: vikram Repository: /hg/zfs-crypto/gate Revision: 713996eb2dc91bcfcc9abdc42346acdc09d25708 Log message: 6267174 "bootadm set-menu" should give more boundary check for the "default" option 6294234 bootadm silently fails to update archive 6294785 bootadm hangs during reboot with args 6299969 bootadm can''t update archive on alternate path 6300723 bootadm misbehaves

Using build 70, I followed the zfsboot instructions at http:// www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/ to the letter. I tried first with a mirror zfsroot, when I try to boot to zfsboot the screen is flooded with "init(1M) exited on fatal signal 9" Than I tried with a simple zfs pool (not mirrored) and it just reboots right away. If I try to setup grub

Hi, I have setup an old Compaq Proliant DL580 with 2 xeon @700MHz 2Gb RAM two SmartArray 5300 controllers and 12 drives in an array enclosure. I am running the latest opensolaris update bfu''ed from binaries since I could not build from source. I am controlling the drives with the cpqary3 driver (Solaris 10) from HP. Initially the array had 7 drives and I created a raidz zfs pool

Hi everyone! I''m planning to migrate a little firm''s Windows server to a HVM machine. The test setup woks fine (it''s basically an MSSQL server tied pack of programs for an accountancy office), all programs can reach the mssql from the outside on the hvm windows. If fact it turned out to be so good, that I''m even planning to simply copy the win image(s) to the

Hi All, I am running nevada 79 BFU''ed to 82. The machine is a Ultra 20 with 4GB memory. I have several Windows XP domU''s configured and registered. When ever I try to start the fourth domain I get an out of memory exception: Not enough memory is available, and dom0 cannot be shrunk any further Each of my domains only uses 256 so I thought there would be sufficient memory

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris

On Fri, Apr 11, 2008 at 06:39:00PM -0700, George Wilson wrote: > Solaris Installation Guide > System Administration Guide: Basic > ZFS Administration Guide > System Administration Guide: Devices and File Systems Where can I get the updated guides? > For further information, visit our OpenSolaris page at: > >

Hi all Opensolaris works perfectly, but I am not able to boot the xvm kernel on this hardware. I added the -k option in grub, but the system hangs before the hostname line without any debug info. I''ve tried snv from b94 to b99, with the same results. If I install Debian with xen kernel I am able to use pvm and hvm guests. What can I do ? thanks Giacomo -- This message posted from

Author: setje Repository: /hg/zfs-crypto/gate Revision: cc6c7f4cdc6315564dc66bc978503b27d8a4499f Log message: 6341178 bootadm refuses to check read-only alternate root Files: update: usr/src/cmd/boot/bootadm/bootadm.c

Hi, I''m searching for a tutorial to install correctly a xen domU on OpenSolaris domO. Please help me ... -- This message posted from opensolaris.org

Hi I have installed nevada77 in x4200. But i can''t use ''virt-install'' ro create guest domain. Do I need add more pkg? what''s wrong? #virt-install --name xmv-test-1 ram 1024 --nographics --file /export/home/xmv-test-1 --location /export/home/software/snv-solarisdvd-x86-77.iso Traceback (most recent call last): File "/usr/bin/virt-install", line 657,

Author: szhou Repository: /hg/zfs-crypto/gate Revision: c95d7672f710aa2a4b16724397ded8d464b123bd Log message: 6295108 When installing to second disk, grub defaults to hd0 instead of hd1 6322231 bootadm generates incorrect menu when boot partition and root are on separate disks 6322723 boot-file setting in bootenv.rc is not respected in snv_21 and later builds 6331385 adding nexus driver does not