Sponsored Content
Full Discussion: Ldoms not booting from vdisk
Operating Systems Solaris Ldoms not booting from vdisk Post 302605673 by gull04 on Thursday 8th of March 2012 07:04:18 AM
Old 03-08-2012
If you do "ldm list-bindings domain_name" do you see the disks there?

Are the disks labled? In the case of the image file I think from memory that you had to create it with the -Z switch.

Have these disks worked in the past?

Which disk did you install the O/S on?
 

10 More Discussions You Might Find Interesting

1. Solaris

RAID1 and LDoms

I have a Netra T5220 Solaris 10 server with LDoms installed and enabled. RAID1 is enabled in the control domain with the following slices: d50 -m d51 d52 1 d51 1 1 c1t0d0s5 d52 1 1 c1t1d0s5 d10 -m d11 d12 1 d11 1 1 c1t0d0s0 d12 1 1 c1t1d0s0 d20 -m d21 d22 1 d21 1 1 c1t0d0s1 d22 1 1... (14 Replies)
Discussion started by: StarSol
14 Replies

2. Solaris

LDOMs on T5220

We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid? I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies

3. Solaris

LDoms can't ping each other

I've got Sun Fire T2000 with two LDoms - primary and ldom1, both being Solaris 10 u8. Both can be accessed over the network (ssh, ping), both can access the network, but they can't ping or ssh to each other. I only use e1000g0 interface on T2000, the primary ldom has an address on it, ldm has a... (1 Reply)
Discussion started by: mludvig
1 Replies

4. Solaris

LDOMS command

What command would i type to get a list of LDOMS running on a blade? (3 Replies)
Discussion started by: soupbone38
3 Replies

5. Solaris

Ldom Vdisk on NFS Share

Can any one tell me how to add a virtual disk from NFS share in Ldom .. i have one share /VMshare/boot.img file shared/exported from one server but i do now know how to add nfs based vdsdev as it gives primary domain cannot validate the disk. (1 Reply)
Discussion started by: fugitive
1 Replies

6. Solaris

Booting Solaris LDOMS Control Domains

We are having a discussion on what order LDOMS and control domains should be booted. I think it should be LDOMS first then Control. Can anyone tell me why I am wrong or why I am right. Thanks, :confused: (6 Replies)
Discussion started by: aeroforce
6 Replies

7. Solaris

Can not use zone in LDoms on T4-1

I have a T4-1 with Solaris 11.1, LDom ver 3.0.0.1 and I'm encountering two problems with zones. I'd greatly appreciate help on these, especially the first one. I have created multiple guest LDoms, all Solaris 11.1, and they all work fine. The first problem is that I can not boot any... (9 Replies)
Discussion started by: ad101
9 Replies

8. Solaris

LDOMS and memory (PA/RA)

If I do ldm ls l ldom1 the memory block is as follows:- MEMORY RA PA SIZE 0x20000000 0x20000000 64G 0x1420000000 0x1020000000 16G 0x1c20000000 0x1420000000 16G 0x2420000000 0x1820000000 16G 0x2c20000000... (1 Reply)
Discussion started by: psychocandy
1 Replies

9. Solaris

LDoms disappeared

System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. I have been experimenting on the above system, using ldmp2v to create "clones" of my physical systems as LDoms on the server when there was an unscheduled power outage. After the system came back up I had lost my LDoms, although... (7 Replies)
Discussion started by: apmcd47
7 Replies

10. UNIX for Advanced & Expert Users

Creating filesystem in LDOMs

Hi, I have a task of creating a UFS filesystem in an LDOM. It is located in a hypervisor (CDOM). The storage has been provisioned to the CDOM. How do I make it reflect to the LDOM, and then from there configure/set up the filesystem in the LDOM? Please help. (1 Reply)
Discussion started by: anaigini45
1 Replies
reboot(8)						      System Manager's Manual							 reboot(8)

Name
       reboot - automatic reboot procedures

Syntax
       /etc/reboot [ -n ] [ -q ]

Description
       The  ULTRIX  system is booted by loading a kernel image, usually into memory at location zero and transferring to zero.	Because the system
       is not reenterable, the kernel image must be read in from disk each time the system is bootstrapped.

       When the reboot of a running system is desired, is normally used.  If there are no users, can be used.  The command causes the disks to	be
       synced,	and  then  a multiuser reboot is initiated.  The system is booted and an automatic disk check is performed.  If the procedure suc-
       ceeds, the system is then brought up for the users.

       The system will reboot itself after a power failure or after a crash, provided auto-restart is enabled on your system.  A consistency check
       of the file systems will be performed and, unless the check fails, the system will resume multiuser operations.

Options
       -n   Prevents the disks from being synced.

       -q   Reboots quickly and ungracefully, without shutting down running processes first.

Files
       System code

See Also
       crash(8v), fsck(8), halt(8), init(8), newfs(8), rc(8), shutdown(8)

																	 reboot(8)
All times are GMT -4. The time now is 05:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy