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
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
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
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
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
LEARN ABOUT DEBIAN
vzsplit
vzsplit(8) Containers vzsplit(8)
NAME
vzsplit - generate a sample container configuration file
SYNOPSIS
vzsplit [-n numve] [-f conf_name] [-s swapsize] [-v yes|no]
DESCRIPTION
The vzsplit utility is used to split the Hardware Node into equal parts. It generates a full set of system resource control parameters for
the given number of containers. The values are calculated from the total physical memory of the Hardware Node the utility runs on, and the
number of containers the Hardware Node shall be able to run even if the given number of containers consume all the resources available.
Without any option given, vzsplit prompts for the desired number of containers and outputs the resulting resource control parameters to
stdout.
If there are not enough system resources to run the specified number of containers, an appropriate message is shown and the sample configu-
ration file is not generated.
OPTIONS
-n numve
Specify the number of containers.
-f conf_name
Specify the configuration sample name to write configuration to, instead of standard output. The file created will be named
/etc/vz/conf/ve-conf_name.conf-sample.
-s swapsize
Specify the swap size in Kbytes. If this option is not given, the swap size is read from /proc/meminfo.
-v yes|no
Whether to generate VSwap enabled configuration. Default is auto-detect by checking if running kernel is VSwap capable; this option
overrides auto-detection.
EXIT STATUS
vzsplit returns 0 upon a successful execution. If anything goes wrong, it returns 1.
SEE ALSO
ctid.conf(5).
LICENSE
Copyright (C) 2000-2011, Parallels, Inc. Licensed under GNU GPL.
OpenVZ 6 Jun 2011 vzsplit(8)