Hello mmn, Your problem is only slightly related to LDoms. The procedure you describe is generally valid. However, your guest definitions need to be sufficiently similar to allow the booting of your guest.
Your issue is this: Your guest system is stuck in the middle of the Solaris boot process. It is trying to (re-) mount the / filesystem from c0d1s0. This is obviously a UFS filesystem, and the device information is derived from /etc/vfstab on your boot disk. The boot disk is c0d0, and currently mounted read-only. The reason for this is probably that your original guest system had a second vdisk configured at one time, and the boot disk was c0d1s0. To recover, either reconfigure your guest in a way that makes the boot disk c0d1, or modify /etc/vfstab accordingly. Since what you are looking for is a golden boot image, I'd advise to do this: * configure exactly one disk for your guest * shut it down using "sys-unconfig" * add additional disks and system configuration after the copy of the golden image has been brought to production. Please also refer to Solaris and LDoms documentation, which covers this. hth stefan On 11.05.10 05:53, MMN wrote: > Hello folks, > > I am very new to LDOMS and have been playing around with it for a few days > now. I have been able to successfully bring up one of the ldoms guests and > have the required softwares installed on it. > > I know there is a ldoms migrate-domain provided in 1.2. However that would > require that the guest domain is kept on one of the solaris machines right? > And the machine to which it gets moved should have similar setup, I suppose. > I couldn't find much information from the documentation. > > What I tried to do hence is, to create the LDOMS guest with a virtual disk > which is a single file. After the guest was installed successfully, stopped > and unbound the guest. Now I transferred the virtual disk (the single) file > to the other machine. I gave all the RAM/CPU configurations on that one as > well and kept the file in the same hard disk and partition on the other > machine. However when I try to boot from that it throws > > r...@t512016g # telnet localhost 5000 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > > Connecting to console "ldg1" in group "ldg1" .... > Press ~? for control options .. > SunOS Release 5.10 Version Generic_141444-09 64-bit > Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > The / file system (/dev/rdsk/c0d1s0) is being checked. > > WARNING - Unable to repair the / filesystem. Run fsck > manually (fsck -F ufs /dev/rdsk/c0d1s0). > > May 11 08:54:05 svc.startd[7]: svc:/system/filesystem/usr:default: Method > "/lib/svc/method/fs-usr" failed with exit status 95. > May 11 08:54:05 svc.startd[7]: system/filesystem/usr:default failed fatally: > transitioned to maintenance (see 'svcs -xv' for details) > Requesting System Maintenance Mode > (See /lib/svc/share/README for more information.) > Console login service(s) cannot run > > Root password for system maintenance (control-d to bypass): Failed to > configure IPv4 DHCP interface(s): vnet0 > Hostname: unknown > Login incorrect > > Root password for system maintenance (control-d to bypass): > single-user privilege assigned to /dev/console. > Entering System Maintenance Mode > > May 11 08:56:41 su: 'su root' succeeded for LOGIN on /dev/console > Sun Microsystems Inc. SunOS 5.10 Generic January 2005 > # format > Searching for disks...done > > > AVAILABLE DISK SELECTIONS: > 0. c0d0 <SUN-DiskImage-70GB cyl 1989 alt 2 hd 96 sec 768> > /virtual-devi...@100/channel-devi...@200/d...@0 > Specify disk (enter its number): > > There is no c0d1 on this VM. The VM I brought it from has it as > r...@t512016g # telnet localhost 5000 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > > Connecting to console "ldg1" in group "ldg1" .... > Press ~? for control options .. > > unknown console login: > unknown console login: root > Password: > May 11 09:03:23 unknown login: ROOT LOGIN /dev/console > Last login: Mon May 10 16:18:23 on console > Sun Microsystems Inc. SunOS 5.10 Generic January 2005 > # format > Searching for disks...done > > > AVAILABLE DISK SELECTIONS: > 0. c0d1 <SUN-DiskImage-70GB cyl 1989 alt 2 hd 96 sec 768> > /virtual-devi...@100/channel-devi...@200/d...@1 > Specify disk (enter its number): > > I think this is causing the problem. So if I can fix this issue somehow, I > think I can have multiple LDOMS guests and save them in one location. > Whenever I need to use one, bring it over and just boot from that. > > Can anyone please help? > > I tried ldoms migration, but got stuck with > r...@t512016g # ldm migrate-domain ldg1 root@<host>:ldg1 > Failed to encode user name > Something to do with sasl_encode, I have to dig deeper for this one. But the > first thing I tried is my ideal solution. > > Thank you -- Stefan Hinker Systems LOB - Systems & Performance Sun Microsystems GmbH Tel: +49 6103 752-300 Brandenburger Str. 2-6 [email protected] D-40880 Ratingen http://www.sun.de/ http://blogs.sun.com/cmt http://blogs.sun.com/cmt/en --------------------------------------------------------------------------- Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht München: HRB 161028 Geschäftsführer: Jürgen Kunz
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
