Hi,
I've created a bootable DVD which works fine for earlier versions of Solaris 10 (6/06) and Solaris 9.
But now i've moved to Solaris 10 8/07 and I am getting the NFSv4 prompt at login.
Initially i thought i could surpress this by adding the line
nfs4_domain=dynamic
to my... (0 Replies)
Is there a way to install Solaris 10 x86 with an external DVD drive that connects through the USB port? I would think I would run GRUB off of a floppy disk and somehow use that to make it look to the USB port to boot from but I don't know how to do that. Can anyone help me out? (1 Reply)
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)
Apologies if this is the wrong forum..
I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Hello,
I am trying to install Solaris 10 on a newly created LDom. Here are the commands I ran to create the LDom:
ldm add-domain ldg2
ldm add-vcpu 8 ldg2
ldm add-memory 2g ldg2
ldm add-vnet vnet2 primary-vsw0 ldg2
ldm add-vdsdev /dev/dsk/c0t5000CCA01535E20Cd0s0 vol2@primary-vds0
ldm... (8 Replies)
Hi,
Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image.
Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch.
So, I am not sure how to achieve this because. If I remove the... (7 Replies)
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)
I have a Sun T4-1 running Solaris 11.4 with a static IP 192.168.0.183. On this machine is a Solaris 10 LDOM with a static IP of 192.168.0.78. The other day I had to stop the LDOM to do a memory reconfigure. When I rebooted it I got an error that the IP 192.168.0.78 was already in use and so... (4 Replies)
Discussion started by: Michele31416
4 Replies
LEARN ABOUT NETBSD
dm
DM(4) BSD Kernel Interfaces Manual DM(4)NAME
dm -- Device-mapper disk driver
SYNOPSIS
pseudo-device dm
DESCRIPTION
The dm driver provides the capability of creating one or more virtual disks based on the target mapping.
This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
figuration file, and how to partition disks. This driver is used by the Linux lvm2tools to create and manage lvm in NetBSD.
Currently, the linear, zero, and error targets are implemented. Each component partition should be offset at least 2 sectors from the begin-
ning of the component disk. This avoids potential conflicts between the component disk's disklabel and dm's disklabel. In i386 it is offset
by 65 sectors, where 63 sectors are the initial boot sectors and 2 sectors are used for the disklabel which is set to be read-only.
In order to compile in support for dm, you must add a line similar to the following to your kernel configuration file:
pseudo-device dm #device-mapper disk device
dm may create linear mapped devices, zero, and error block devices. Zero and error block devices are used mostly for testing. Linear
devices are used to create virtual disks with linearly mapped virtual blocks to blocks on real disk. dm Device-mapper devices are controlled
through the /dev/mapper/control device. For controlling this device ioctl(2) calls are used. For the implementation of the communication
channel, the proplib(3) library is used. The protocol channel is defined as a proplib dictionary with needed values. For more details, look
at sys/dev/dm/netbsd-dm.h. Before any device can be used, every device-mapper disk device must be initialized. For initialization one line
must be passed to the kernel driver in the form of a proplib dictionary. Every device can have more than one table active. An example for
such a line is:
0 10240 linear /dev/wd1a 384
dm The first parameter is the start sector for the table defined with this line, the second is the length in sectors which is described with
this table. The third parameter is the target name. All other parts of this line depend on the chosen target. dm For the linear target,
there are two additional parameters: The first parameter describes the disk device to which the device-mapper disk is mapped. The second
parameter is the offset on this disk from the start of the disk/partition.
SEE ALSO config(1), proplib(3), MAKEDEV(8), dmsetup(8), fsck(8), lvm(8), mount(8), newfs(8)HISTORY
The device-mapper disk driver first appeared in NetBSD 6.0.
AUTHORS
Adam Hamsik <haad@NetBSD.org> implemented the device-mapper driver for NetBSD.
Brett Lymn <blymn@NetBSD.org>,
Reinoud Zandijk <reinoud@NetBSD.org>, and
Bill Stouder-Studenmund <wrstuden@NetBSD.org> provided guidance and answered questions about the NetBSD implementation.
BUGS
This driver is still work-in-progress--there can be bugs.
BSD August 30, 2008 BSD