Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Best performance UNIX just for HOST Virtualization? Post 303011906 by drysdalk on Thursday 25th of January 2018 09:44:51 AM
Old 01-25-2018
Hi,

I think OpenVZ 7 (the latest release) does support Windows, though only running in a KVM VM and not in a container. OpenVZ 7 added the option to create VMs that was previously only available in Virtuozzo, and so you can create containers for Linux guests and VMs for all non-Linux guests on OpenVZ 7 (or you should be able to at least, according to the documentation I can see). So if you're familiar with OpenVZ, then OpenVZ 7 is probably the best way to go, since you can use both containers and full-blown real VMs on the same host.

However, if the issue here is that you are actually wanting to make day-to-day use of your own PC whilst being able to run containers and VMs on it (which I think might be what your comments about SmartOS imply), then your options are a bit more limited. Things like OpenVZ/SmartOS/ESX are meant to run on a dedicated server that does nothing but host containers and VMs. You then connect remotely to those containers and VMs to use them in whatever way you see fit (SSH, rdesktop, etc), and can also connect remotely to the hardware node to manage it.

If you're looking to be setting up VMs or containers on your own PC, then running a normal desktop-oriented Linux distro locally and using KVM/QEMU to run VMs on it might be a good way forward. Similarly you could run Windows 10 or Windows Server locally and add the Hyper-V role, and create VMs that way whilst still having a usable "real" desktop OS too. Or just use VirtualBox or something like that if your needs are simpler.
 

4 More Discussions You Might Find Interesting

1. Solaris

ILOM to unix host

Hello- On Solaris 10g x86 - I had two IP addresses , one for unix host (connecting through putty) and one for ILOM (connecting through CLI and web). I had to perform some changes in FS sizes etc, did that on unix host and executed command 'init 6' remotely for them to take place. But, the unix host... (30 Replies)
Discussion started by: panchpan
30 Replies

2. Red Hat

Red Hat and Intel: Smart processors, virtualization boost efficiency and performance

On Monday March 30, Intel announced the availability of their much anticipated new line of processors, the Intel® Xeon® Processor 5500 series–nicknamed Nehalem. Red Hat, a long-time partner of the market-leading chip maker , collaborated on the chip’s debut, testing and optimizing the... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. UNIX for Dummies Questions & Answers

Virtualization of Global Namespace in UNIX

Hi all, I have a small Question here in Unix File System.I am unable to get a proper answer in Internet. Hope someone can get back to me soon. A Unix file system can mount filesystem of several disk partitions to form a single global space. Suppose that you wish to virtualize this global... (1 Reply)
Discussion started by: Pavan Kumar
1 Replies

4. Red Hat

Virt-install: ERROR Host does not support any virtualization

Hello guys! First of all sorry about my english. I am using KVM to virtualizate. But when i run the virt-install command, it shows the next error: ERROR Host does not support any virtualization options.My server had virtualisation extensions enabled in the bios. It is my first time using... (7 Replies)
Discussion started by: morrison71
7 Replies
vz.conf(5)							    Containers								vz.conf(5)

NAME
vz.conf - global OpenVZ configuration file SYNOPSIS
/etc/vz/vz.conf DESCRIPTION
This is the global configuration file for OpenVZ. It consists of lines in the form PARAMETER="value" All parameter names and values are case-sensitive. Quotes surrounding value are required if value contains spaces, and are optional other- wise. Extra spaces are not allowed. All unrecognized lines will be ignored. Global parameters VIRTUOZZO=yes|no This parameter can be set to yes or no, and used by the vz init script. In case it is not set to yes, nothing will be done to boot up OpenVZ on this node. LOCKDIR=directory Set the directory to put lock files to. VE0CPUUNITS=number Value of this parameter sets cpuunits for CT0 (host system). LOGGING=yes|no Enables or disables logging. This parameter can be set to yes or no, default is yes. LOGFILE=file Set location of log file, default is /var/log/vzctl.log. LOG_LEVEL=number Set the logging level for the log file (does not affect console output). The greater the number is, the more information will be logged to the LOGFILE. Default is 0, which means to log normal messages and errors. If set to -1, only errors will be logged. VERBOSE=number Set the logging level for console/terminal output (does not affect log file). Default is 0, which means to log normal messages and errors. Increasing the number makes vzctl(8) more verbose. MODULES_DISABLED=yes|no If the value of this parameter is set to yes, no attempt to load kernel modules is made by the vz initscript. This is helpful on systems which have OpenVZ-specific features compiled into the kernel (i. e. not as modules). IPTABLES_MODULES="module module ..." List of iptables kernel modules to be loaded by vz initscript before loading OpenVZ modules (which is required for iptables to work inside containers). If not set, value of IPTABLES is used. VZFASTBOOT=yes|no If the value of this parameter is set to yes, vz initscript called with start argument will start the containers with uncleanly shutdown quota state without performing quota reinitialization (which is usually a time-consuming process). After all the containers are started, the initscript when restarts those containers with unclean quota in a normal way (to recalculate/fix quotas). TEMPLATE=directory Value of this parameter is a directory in which all container template data are stored. Network interface parameters VE_ROUTE_SRC_DEV="device" This parameter specifies the network device name which IP address will be used as the source IP. This is helpful in case more than one network interface is configured on HN and there is a need to specify the source IP address. Default is the first device in the network device list. NEIGHBOUR_DEVS="detect" Controls on which interfaces to add/remove ARP records for a container IP, also which interfaces to use to query/announce ARP. If this is set to detect, the right network interface (the one which is in the same subnet as a CT IP) will be chosen automatically. Any other value restores old (as of vzctl 3.0.19 or older) behavior, when all the possible interfaces were used. ERROR_ON_ARPFAIL=yes|no In case the value of this parameter is set to yes, vzctl will fail to start a container if there is another host with the same IP in the subnet. The value of no makes vzctl to only print the warning. Defaults for containers Below parameters are defaults for containers, and can be overwritten by parameters in ctid.conf(5) per-container configuration file. DISK_QUOTA=yes|no In case the value of this parameter is set to no, all disk quota operations are disabled. VE_ROOT=directory Value of this parameter is the directory which serves as container root mount point. Value must contain literal string $VEID, which will be substituted with the actual numeric CT ID. VE_PRIVATE=directory Value of this parameter is the directory in which all the files and directories specific to that container are stored. Value must contain literal string $VEID, which will be substituted with the actual numeric CT ID. CONFIGFILE=name Default configuration file for create action, corresponds to --config option. IPTABLES="module module ..." List of iptables modules to be enabled for containers, corresponds to --iptables option. Most of the other parameters that appear in per-container configuration files ctid.conf(5) can be also set here. Still, it is recommended to keep TEMPLATE, VE_PRIVATE and VE_ROOT in this configuration file, and all the other container related parameters in per-container con- figuration files. SEE ALSO
vzctl(8), ctid.conf(5). LICENSE
Copyright (C) 2000-2011, Parallels, Inc. Licensed under GNU GPL. OpenVZ 28 Jun 2011 vz.conf(5)
All times are GMT -4. The time now is 06:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy