Technology nonprofit cools down, speeds up with HP Adaptive Infrastructure: TechSoup
TechSoup Global enabled the creation of a next-generation data center through server consolidation and virtualization by trading in old servers, install HP BladeSystem and VMware virtualization software, and integrate the entire solution with the storage area network.
HI
We have been asked by our IT department to move from our current physical solution to a VM environment. I am not that clued up on VM.
I looked from some benchmark tests to run so i can see a comparison between our live and new VM we have been presented. Please see below for results.
To me the... (3 Replies)
How can I get the upload and download speed of my pc, provided that my interface is wlan0?
I have though something like:
#!/bin/sh
ups=something
downs=somethingelse
echo "
Your current up speed is $ups
Your current down speed is $downs, but I have no idea how to get them?Are... (5 Replies)
Hello all,
We have a group of Solaris 8 machines that are having some real network performance issues, they all go through a switch which *should* be set at 100 mb full duplex on every port which goes back to a master switch. I have checked the machines and the NIC cards are all set at 100 full.... (9 Replies)
i recently purchased a dual ross sparc processor kit from someone.
the person listed these items as 133mhz processors, however, looking at bridgepoint's site, they do not make 133mhz processors.
so i was wondering, how can i check the processor speeds? (4 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 237SYSTEMD-DETECT-VIRT(1)