Sponsored Content
Full Discussion: VXVM on Linux desktop
Operating Systems Linux Red Hat VXVM on Linux desktop Post 302864009 by blackrageous on Tuesday 15th of October 2013 03:46:30 PM
Old 10-15-2013
I agree with VerdePollo you should have plenty of power; however, i would suggest getting familiar with the levels of virtualization support available in your specific processor (different generations of the i5 also have differences). Look up your specific processor. Also, since you are interested in doing i/o (virtual disks) it might help if you look up Intel Vt-d and see if that is a supported extension in your current cpu. See...Hardware-assisted Virtualization Technology
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Linux desktop connection via web

Hello all, I woud like to know if anyone has setup or know of a way (configure or product) to get a remote session form a windows box to linux box via the web browser. I'm looking for something like windows Remote desk top web connection, but for linux. VNC is what I want but via the web... (1 Reply)
Discussion started by: larryase
1 Replies

2. Linux

Desktop of linux server

Hi, How to get desktop of linux server in windows using putty or any other software (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. Linux

Best Linux desktop distro

I hate the fact that my first post is this. Anyhow, I've been using Linux distros such as Ubuntu, Fedora, Debian, openSUSE, and a few others for quite some time now. I've never had a problem with any distro, thus saying that they were all good in my opinion. I've been reading a lot on different... (2 Replies)
Discussion started by: Vex
2 Replies

4. UNIX Desktop Questions & Answers

Unix/Linux as a client desktop

Hi Does someone using unix or linux as a productive client desktop in your company? Which Desktop Environment/Windows Manager and which Workstation Management software? (2 Replies)
Discussion started by: ccc
2 Replies

5. What is on Your Mind?

Linux Desktop vs Windows 8

Any comments on this Windows 8 OEM specs may block Linux booting | ITworld (16 Replies)
Discussion started by: jgt
16 Replies

6. Fedora

Build Linux Desktop ?

Hi, Just trying to make a plan as to if this doable or not? Currently in the company all the desktop are Windows, users get MS-Word, some kind of Virus program. and all connected to Windows domain. If I want to do the same thiing on Linux? How would I do that? First I need to create... (3 Replies)
Discussion started by: samnyc
3 Replies

7. Linux

Linux Desktop OS

Right, I know this topic has more or less been done to death, however, I'm bringing it up again. I'm planning on moving to Linux as a full time desktop OS for my home system. I don't want to run a security distro, or anything that runs as root and just use my Windows OS in a VM when I need to use... (11 Replies)
Discussion started by: 3therk1ll
11 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:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy