Sponsored Content
Full Discussion: Tseries and zones
Operating Systems Solaris Tseries and zones Post 302544650 by cornsnap on Thursday 4th of August 2011 12:03:29 PM
Old 08-04-2011
Thanks. Here is the official answer from Oracle on my question which is exactly what you said.

"
Zones and LDOMs are completely different virtualization technologies. Anywhere you can run Solaris 10 or later, you can run zones, regardless of the hardware or even virtualization that Solaris is running on. LDOMs is a hardware based virtualization that uses the hypervisor built into our T-Series CPUs, and can only be used on T-Series servers, but has no restrictions in relation to zones, so you can run zones on any T-Series server with or without LDOMs, and you can run zones in the Solaris instance running on an LDOM. I don't think there will be anything written specifically to address the question, as they are separate, no-dependent technologies."
 

10 More Discussions You Might Find Interesting

1. Solaris

Zones

Hi, I want to wheather there is any command by using that we can reboot all the zones , Example : I have 10 zones, I can reboot all 10 zones by using one command (2 Replies)
Discussion started by: manoj.solaris
2 Replies

2. Solaris

Solaris Zones

I have a Solaris 10 box configured with a global zone and 3 non-global zones. All of the zones need to be configured so they can access and run an application in the global zone located at /export/home. How do i make this application and all of its accompanying files available to the 3 non-global... (3 Replies)
Discussion started by: goose25
3 Replies

3. Solaris

zones

what are the files related to dns zones database file management ? (1 Reply)
Discussion started by: tirupathi
1 Replies

4. Solaris

zones

Hi I need a help in creating a zones.I am trying to create zone in Sun fire T1000 server with single cpu / 8 gb Ram / 73 gb hdd.I am planning to install java based application on two different zones. iam planning to install solaris 10. Can some one suggest what is the best way to create two... (5 Replies)
Discussion started by: solaris8in
5 Replies

5. Solaris

Global Zones

I'm logged into a non-global zone server. How would I find out what the global zone server name is from there? (1 Reply)
Discussion started by: soupbone38
1 Replies

6. Solaris

Zones

Hi guys Im using VMware and ive installed solaris 10 in that..ive configured virtual disks in that n im using it..my question is if im gona configure zones in it do i need a seperate NIC card..my virtual interface name is pcn0 and if i create zones can i give pcn0:1 n allocate a seperate... (1 Reply)
Discussion started by: madanmeer
1 Replies

7. Solaris

Zones

Hi Everyone, I need the process of how to add a cpu to a non-global zone or how to add a resource to non-globalzone. Thanks & Regards Padmaja (2 Replies)
Discussion started by: padmaja
2 Replies

8. Solaris

Zones

Hi Everyone, How to create a loopback filesystem in a running non golbalzone? and how to share a diskgroup in veritas ? Thanks & Regards Padmaja (1 Reply)
Discussion started by: padmaja
1 Replies

9. Solaris

zones

how can we know zone is migrate and which files going to update (3 Replies)
Discussion started by: nsusheelgoud
3 Replies

10. UNIX for Beginners Questions & Answers

Zones

haven't work with zones in a while. when shutting down zones from solaris 10 I have to do it from the global zone, but can I just shutdown the global zone and all non global zones will shutdown or do I have to zoneadm -z zonename shutdown for all the non global zones ,then shutdown... (2 Replies)
Discussion started by: goya
2 Replies
SYSTEMD-DETECT-VIRT(1)						systemd-detect-virt					    SYSTEMD-DETECT-VIRT(1)

NAME
systemd-detect-virt - Detect execution in a virtualized environment SYNOPSIS
systemd-detect-virt [OPTIONS...] DESCRIPTION
systemd-detect-virt detects execution in a virtualized environment. It identifies the virtualization technology and can distinguish full machine virtualization from container virtualization. systemd-detect-virt exits with a return value of 0 (success) if a virtualization technology is detected, and non-zero (error) otherwise. By default, any type of virtualization is detected, and the options --container and --vm can be used to limit what types of virtualization are detected. When executed without --quiet will print a short identifier for the detected virtualization technology. The following technologies are currently identified: Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization) +----------+----------------+--------------------------------------+ |Type | ID | Product | +----------+----------------+--------------------------------------+ |VM | qemu | QEMU software virtualization, | | | | without KVM | | +----------------+--------------------------------------+ | | kvm | Linux KVM kernel virtual machine, | | | | with whatever software, except | | | | Oracle Virtualbox | | +----------------+--------------------------------------+ | | zvm | s390 z/VM | | +----------------+--------------------------------------+ | | vmware | VMware Workstation or Server, and | | | | related products | | +----------------+--------------------------------------+ | | microsoft | Hyper-V, also known as Viridian or | | | | Windows Server Virtualization | | +----------------+--------------------------------------+ | | oracle | Oracle VM VirtualBox (historically | | | | marketed by innotek and Sun | | | | Microsystems), | | | | for legacy and KVM | | | | hypervisor | | +----------------+--------------------------------------+ | | xen | Xen hypervisor (only domU, not dom0) | | +----------------+--------------------------------------+ | | bochs | Bochs Emulator | | +----------------+--------------------------------------+ | | uml | User-mode Linux | | +----------------+--------------------------------------+ | | parallels | Parallels Desktop, Parallels Server | | +----------------+--------------------------------------+ | | bhyve | bhyve, FreeBSD hypervisor | +----------+----------------+--------------------------------------+ |Container | openvz | OpenVZ/Virtuozzo | | +----------------+--------------------------------------+ | | lxc | Linux container implementation by | | | | LXC | | +----------------+--------------------------------------+ | | lxc-libvirt | Linux container implementation by | | | | libvirt | | +----------------+--------------------------------------+ | | systemd-nspawn | systemd's minimal container | | | | implementation, see systemd- | | | | nspawn(1) | | +----------------+--------------------------------------+ | | docker | Docker container manager | | +----------------+--------------------------------------+ | | rkt | rkt app container runtime | +----------+----------------+--------------------------------------+ If multiple virtualization solutions are used, only the "innermost" is detected and identified. That means if both machine and container virtualization are used in conjunction, only the latter will be identified (unless --vm is passed). OPTIONS
The following options are understood: -c, --container Only detects container virtualization (i.e. shared kernel virtualization). -v, --vm Only detects hardware virtualization). -r, --chroot Detect whether invoked in a chroot(2) environment. In this mode, no output is written, but the return value indicates whether the process was invoked in a chroot() environment or not. --private-users Detect whether invoked in a user namespace. In this mode, no output is written, but the return value indicates whether the process was invoked inside of a user namespace or not. See user_namespaces(7) for more information. -q, --quiet Suppress output of the virtualization technology identifier. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
If a virtualization technology is detected, 0 is returned, a non-zero code otherwise. SEE ALSO
systemd(1), systemd-nspawn(1), chroot(2), namespaces(7) systemd 237 SYSTEMD-DETECT-VIRT(1)
All times are GMT -4. The time now is 10:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy