09-19-2016
That's not much information...
You will need to create a vdsdev in your vds service. this vdsdev can be used as a vdisk for your ldom. within the ldom you will need to add this disk to the volume(s) for your /u02... and that will depend on your volume manager... ZFS? VxVM?
gP
9 More Discussions You Might Find Interesting
1. Solaris
Hi Folks,
I am used to writing scripts to get info by running commands at local zones level from their respective global zone by using zlogin <localzone> "command>" while remaining at the global zone level.
Can the same be done with Guest LDoms while remaining at the control LDOM level?
... (4 Replies)
Discussion started by: momin
4 Replies
2. Solaris
I have viewed a few previous posts regarding this, but none of them quite described or worked with my issue.
I am out of local disk space on my LDOM Manager but still have plenty of SAN vCPU and Memory available so I am trying to install a new LDOM OS on SAN.
I have exposed the SAN to the... (0 Replies)
Discussion started by: MobileGSP
0 Replies
3. Solaris
Solaris for Sparc 11.1 with the latest patches. Created a Guest LDOM with two vnet's net0 and net1, installed a guest whole root, ip exclusive zone that I want to be able to utilize DHCP. I have been able to create the zone but unable to get it to boot because I am unable to assign an anet to it.... (4 Replies)
Discussion started by: os2mac
4 Replies
4. Solaris
Host System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. running Solaris 11.3.
Last login: Tue Sep 19 14:42:42 2017 from xxx.xxx.xxx
Oracle Corporation SunOS 5.11 11.3 June 2017
$ uname -a
SunOS sog01 5.11 11.3 sun4v sparc sun4v
$
Original physical systems: Sun... (0 Replies)
Discussion started by: apmcd47
0 Replies
5. Solaris
Generally, this is what we do:-
On primary, export 2 LUNs (add-vdsdev).
On primary, assign these disks to the ldom in question (add-vdisk).
On ldom, created mirrored zpool from these two disks.
On one server (which is older) we have:-
On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
6. Solaris
Hi! Quick background for the question...
I have Solaris 11.4 control/primary zone with some LDOM's on top of it. I have some raw iSCSI LUN's presented to the control zone/primary zone from a NetApp, which I then pass up to the LDOM's via the VDS/vdisk. So basically the LDOM VM's see the disk as... (1 Reply)
Discussion started by: rtmg
1 Replies
7. Solaris
hello to everyone. im new member here.
i have a problem with a guest ldom on solaris 11 sparc in a T8. I need to access to disk vds assigned to guest domain but from control domain.
I want to modify a parameter in inittab of the guest domain because start guest domain give me problems... (2 Replies)
Discussion started by: Liam_
2 Replies
8. UNIX for Beginners Questions & Answers
I'm really stuck here. I've created an LDOM on a SPARC T4-1 with Solaris 11.4 to run a copy of Linux for SPARC. I got the Linux ISO installed and Linux itself installed and booted OK. The only thing is is that there's no networking available in the Linux guest.
This question is basically the... (7 Replies)
Discussion started by: Michele31416
7 Replies
9. Solaris
I have a guest LDOM running Solaris 10U11 on a Sun T4-1 host running Solaris 11.4. The host has a disk named bkpool that I'd like to share with the LDOM so both can read and write it. The host is hemlock, the guest is sol10.
root@hemlock:~# zpool list
NAME SIZE ALLOC FREE CAP DEDUP ... (3 Replies)
Discussion started by: Michele31416
3 Replies
lvmpvg(4) Kernel Interfaces Manual lvmpvg(4)
NAME
lvmpvg - LVM physical volume group information file
SYNOPSIS
DESCRIPTION
is an ASCII file that stores the volume-group information for all of the physical volume groups in the system. The information is stored
in a hierarchical format.
First, it starts with a volume group under which multiple physical volume groups can exist. Under each physical volume group, a list of
physical volumes can be specified. There must be at least one physical volume group in each volume group that appears in this file. The
physical-volume-group name must be unique within the corresponding volume group, although it is permissible to use a common physical volume
group name across different volume groups. There can be as many volume groups in this file as there are in the system.
Instead of using the and commands, the administrator can edit this file to create and extend physical volume groups. However, care must be
taken to ensure that all physical volumes to be included in the file have already been defined in their respective volume groups by previ-
ous use of or
The file format has the following structure. and are keywords that introduce the names of the volume group and physical volume group,
respectively.
pv_path
...
pv_path
...
pv_path
...
The variables are defined as follows:
pv_path The block device path name of a physical volume within the volume group.
pvg_name The name of the physical volume group. It must be unique within the volume group.
vg_name The path name of the volume group.
EXAMPLES
The following example shows an file containing two volume groups: the first containing two physical volume groups, each with two physical
volumes defined in it; the second containing three physical volume groups, each with one physical volume defined in it.
SEE ALSO
vgcreate(1M), vgextend(1M), vgreduce(1M), vgremove(1M), intro(7), lvm(7).
lvmpvg(4)