Difference between pages "Property:Summary" and "Linux on KVM"

(Difference between pages)
(Created page with "This is a property of type Has type::String.")
 
(Created page with "== Starting your first KVM virtual machine == To start your first KVM virtual machine, first download SysRescueCD and save it to systemrescuecd.iso. Then use the following co...")
 
Line 1: Line 1:
This is a property of type [[Has type::String]].
+
== Starting your first KVM virtual machine ==
 +
 
 +
To start your first KVM virtual machine, first download SysRescueCD and save it to systemrescuecd.iso. Then use the following commands, which will create a 10GB qcow disk image to use for the first disk, and then the next command will start your virtual machine, booting from the CD:
 +
 
 +
<console>
 +
# ##i##qemu-img create -f qcow2 vdisk.qcow2 10
 +
# ##i##qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd.iso  -vnc 127.0.0.1:1 -cpu host -net nic -net user
 +
VNC server running on `127.0.0.1:5900'
 +
</console>
 +
 
 +
Now you should be able to use a VNC client to connect to 127.0.0.1:5901 (VNC session 1) and access your virtual machine.
 +
 
 +
== Networking Options ==
 +
 
 +
Above, networking will be enabled but will be on its own private LAN, and ping will not work. If you have a local bridge that you use for networking, the following steps will allow you use your existing bridge to provide higher-performance and full-featured network access to your virtual machine.
 +
 
 +
First, create <tt>/etc/qemu-ifup</tt> and add the following to it. Replace <tt>brlan</tt> with the name of your bridge:
 +
 
 +
<syntaxhighlight lang="bash">
 +
#!/bin/bash
 +
ifconfig $1 0.0.0.0 promisc up
 +
brctl addif brlan $1
 +
sleep 2
 +
</syntaxhighlight>
 +
 
 +
Make it executable:
 +
 
 +
<console>
 +
# ##i##chmod +x /etc/qemu-ifup
 +
</console>
 +
 
 +
Start the virtual machine as follows:
 +
 
 +
<console>
 +
# ##i##qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 -net nic -net tap,id=foo
 +
</console>
 +
 
 +
== Tweaking KVM ==
 +
 
 +
=== VNC Output ===
 +
 
 +
If you wanted to have VNC listen on a different IP address or port, you can use the format <tt>-vnc IP:vncnum</tt> which will cause VNC to listen on the IP specified, and the TCP port 5900+vncnum.
 +
 
 +
=== CPU Settings ===
 +
 
 +
By default, the KVM guest will have one CPU with one core. To change this, use <tt>-cpu host</tt> (to export all of the host's CPU features) and <tt>-smp cores=X,threads=Y</tt>, where X is the number of cores, and Y is the number of threads on each core. You can emulate more CPUs and cores than you actually have.
 +
[[Category:Virtualization]][[Category:KVM]]

Latest revision as of 07:38, 4 March 2014

Starting your first KVM virtual machine

To start your first KVM virtual machine, first download SysRescueCD and save it to systemrescuecd.iso. Then use the following commands, which will create a 10GB qcow disk image to use for the first disk, and then the next command will start your virtual machine, booting from the CD:

# qemu-img create -f qcow2 vdisk.qcow2 10
# qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd.iso  -vnc 127.0.0.1:1 -cpu host -net nic -net user
VNC server running on `127.0.0.1:5900'

Now you should be able to use a VNC client to connect to 127.0.0.1:5901 (VNC session 1) and access your virtual machine.

Networking Options

Above, networking will be enabled but will be on its own private LAN, and ping will not work. If you have a local bridge that you use for networking, the following steps will allow you use your existing bridge to provide higher-performance and full-featured network access to your virtual machine.

First, create /etc/qemu-ifup and add the following to it. Replace brlan with the name of your bridge:

#!/bin/bash
ifconfig $1 0.0.0.0 promisc up
brctl addif brlan $1
sleep 2

Make it executable:

# chmod +x /etc/qemu-ifup

Start the virtual machine as follows:

# qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 -net nic -net tap,id=foo

Tweaking KVM

VNC Output

If you wanted to have VNC listen on a different IP address or port, you can use the format -vnc IP:vncnum which will cause VNC to listen on the IP specified, and the TCP port 5900+vncnum.

CPU Settings

By default, the KVM guest will have one CPU with one core. To change this, use -cpu host (to export all of the host's CPU features) and -smp cores=X,threads=Y, where X is the number of cores, and Y is the number of threads on each core. You can emulate more CPUs and cores than you actually have.


Pages using the property "Summary"

Showing 25 pages using this property.

(previous 25) (next 25)

3

389 Directory Server +This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the graphical management capabilities, too.  +
389 Directory Server Admin Server +The 389 Directory Server Admin Server is an Apache-based application server that can optionally be deployed alongside 389 Directory Server. It allows for remote Java-based management of your 389 Directory Server deployment.  +
389 Directory Server AdminUtil +AdminUtil is a set of utility functions written in C, and a dependency of 389 Directory Server.  +
389 Directory Server Console +This is the Java-based remote management console that is used for managing 389 Directory Server (administration as well as the server app itself.)  +

A

ACPI Daemon +Daemon for Advanced Configuration and Power Interface  +
AMD Catalyst Video Drivers +Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.  +
APC UPS Daemon +APC UPS daemon with integrated network-based remote shutdown  +
Apache +The Apache Web Server  +
Automatic FS Snapshots +Present proposal pretends to be the "big picture" of integrating snapshotting capabilities of modern CoW filesystems like BTRFS/ZFS in portage. Such an integration will enable sysamdins to easily recover from a disaster coming from a clunky update (or worse, a silent and catastrophic libpng-like update).  +
Awesome (Window Manager) +A dynamic floating and tiling window manager.  +

B

BSF Bean Scripting Framework +A framework that allows many scripting languages to be plugged into a Java application.  +
Bash +The standard GNU Bourne-again shell.  +
Batik +Java-based SVG toolkit.  +
Boo +A wrist-friendly language for the CLI.  +
Boot-Update +Funtoo Core Boot Framework for global boot loader configuration  +
Boot-Update Redesign +This page describes a proposed rewrite of boot-update.  +

C

CA Certificates +This package contains SSL certificates in PEM format that are used to validate the authenticity of remote systems, using the certificate authority system.  +
CCache +CCACHE is an application that caches compilation results and reuses it in future compilations in order to achieve faster compile times.  +
Chromium +Chromium is the Open Source Web browser that serves as the foundation for Google Chrome.  +
Cx Oracle +Python interface to Oracle.  +

D

DeaDBeeF +A foobar2000-like music player  +
Dictd Moby Thesaurus +This package contains the Moby Thesaurus, produced as part of the Moby Project. It is designed to work with dictd dictionary server.  +
Drupal +PHP-based open-source platform and content management system  +

E

Ebuild Ecosystem +This FLOP describes new wiki-based infrastructure to allow users to identify ebuilds that are important to them, and collect docs for these ebuilds.  +
Eclipse +A powerful integrated development environment (IDE) written in Java.  +
(previous 25) (next 25)