06-19-2019
Ldom guest volumen problem t8 Solaris 11
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 with other systems online
How Can i mount this volume in Control Domain?
The configuration in the guest domain is:
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
sys sys@primary-vds0 0 disk@0 primary
The configuration in Control Domain is:
rpool/ldoms 10G 38G 3K none
rpool/ldoms/sys 51G 4G 3G -
system disk of ldom guest are volumen of rpool:
/dev/zvol/dsk/rpool/ldoms/sys
Thank u for all.
8 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
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
3. Solaris
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)
Discussion started by: tommyq
4 Replies
4. Solaris
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)
Discussion started by: bstring
8 Replies
5. Solaris
Hi People,
I have been trying to learn solaris ldoms, have created one on a T2000 and get the following error when try to install it off DVD
WARNING: /virtual-devices@100/channel-devices@200/disk@1: Communication error with Virtual Disk Server using Port 0. Retrying
If anyone could help... (8 Replies)
Discussion started by: callmebob
8 Replies
6. Solaris
Hi,
There is LDOM Guest where I need to expand /u02 file systems on it.
It is residing on a Solaris 11 Hypervisor (Primary Domain).
The storage is expanded on vdisk presented to Hypervisor.
I need steps to expand the /u02 on LDOM Guest. (2 Replies)
Discussion started by: vidya_sagar2003
2 Replies
7. 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
8. Solaris
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
xbdback
XBDBACK(4) BSD/xen Kernel Interfaces Manual XBDBACK(4)
NAME
xbdback -- Xen backend paravirtualized block device interface
SYNOPSIS
pseudo-device xbdback
DESCRIPTION
The xbdback interface forms the backend part of the paravirtualized drivers used by Xen domains to offer a block device interface, similar to
a hard disk. xbdback interfaces are backed either by a physical device directly, or an image file mounted through vnd(4).
All xbdback interfaces follow the ``xbdbackXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary
identifier. This identifier is usually associated to the device node as seen by the guest using major(3) and minor(3) numbers. For example,
identifier ``769'' (0x301) means major 3 and minor 1, identified as ``hda1'' under Linux convention. For NetBSD, the guest device name spec-
ified in the guest configuration file does not matter, and can be chosen arbitrarily.
A xbdback interface will appear as a xbd(4) block device inside a NetBSD guest domain. In the XenStore, xbd and xbdback are identified by
``vbd'' (virtual block device) entries.
DIAGNOSTICS
xbd backend: attach device %s (size %d) for domain %d Gives the device used as xbdback interface for the given guest domain, and its size,
in bytes.
xbd backend 0x%x for domain %d using event channel %d, protocol %s Gives the backend identifier, guest domain ID, event channel ID, and pro-
tocol used for block level communication.
xbdback %s: can't VOP_OPEN device 0x%x: %d When this message appears in the system message buffer with error 16 (EBUSY), the device is
likely to be already mounted. It must be unmounted first, as the system will refuse to open it a second time.
SEE ALSO
vnd(4), xbd(4), xenbus(4)
HISTORY
The xbdback driver first appeared in NetBSD 4.0.
AUTHORS
The xbdback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.
BSD
June 7, 2011 BSD