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
LEARN ABOUT HPUX
vxvmboot
vxvmboot(1M) vxvmboot(1M)
NAME
vxvmboot - prepare Veritas Volume Manager volume as a root, boot, primary swap or dump volume
SYNOPSIS
/sbin/vxvmboot [-b|-d|-r|-s] [-v] -o offset -l length rawpath
/sbin/vxvmboot -v rawpath
/sbin/vxvmboot -c
DESCRIPTION
The vxvmboot command updates information in the LABEL file for the lif disk specified by the pathname of its character (raw) device node,
rawpath. The volume at the specified offset and length becomes the boot, root, primary swap or dump volume when the system is next booted.
This command is normally invoked by the vxbootsetup utility.
OPTIONS
-b Specifies the volume type as a boot volume with name standvol.
-c Is used to update the /stand/rootconf file with the offset and length of the rootvol. The usage is slightly different when the -c
argument is used. The rawpath argument is not used with this invocation. Instead the path of the boot device is extracted from
the /stand/bootconf file. Also, the -o and -l arguments are not used to specify the offset and length. Instead, the offset and
length of the rootvol are obtained from the LIF LABEL file on the boot device.
The -c option would normally be used in the sbin/ioinitrc script to update the /stand/rootconf file, when the boot disk is VxVM
rootable.
-d Specifies the volume type as a dump volume with name dumpvol.
If a dumpvol volume exists on the specified disk, the extent information from this volume is used. If no such volume exists, the
extent information of the swap volume is used instead, and swapvol performs the dual role of swap device and dump device.
-l length Specifies the length of the volume in units of 1024-byte blocks.
-o offset Specifies the start of the volume as the number of 1024-byte blocks from the beginning of the disk.
-r Specifies the volume type as a root volume with name rootvol.
-s Specifies the volume type as a swap volume with name swapvol.
-v When used with one of the options -b, -d, -r or -s, displays the contents of the updated LABEL file. Otherwise, this option may
be used to display the contents of the LABEL file on the specified lif disk.
Note: The -b, -c, -d, -r and -s options are mutually exclusive. If more than one of these options is specified, the vxvmboot com-
mand exits without performing any operation.
ARGUMENTS
rawpath Specifies the pathname of the character (raw) device node for the lif disk.
SEE ALSO
lif(4), mkboot(1M), vxbootsetup(1M)
VxVM 5.0.31.1 24 Mar 2008 vxvmboot(1M)