Difference between pages "Linux on KVM" and "User:Stac80"

(Difference between pages)
(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...")
 
(Created page with "{{Person |Full name=stac80 |Email=stac80+funtoo@gmail.com |Geoloc=51.0454620, -114.0836320 |Location name=Calgary, Alberta, Canada |Roles= |Maintains= |Blogs= }}")
 
Line 1: Line 1:
== Starting your first KVM virtual machine ==
+
{{Person
  
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:
+
|Full name=stac80
  
<console>
+
|Email=stac80+funtoo@gmail.com
# ##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.
+
|Geoloc=51.0454620, -114.0836320
  
== Networking Options ==
+
|Location name=Calgary, Alberta, Canada
  
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.
+
|Roles=
  
First, create <tt>/etc/qemu-ifup</tt> and add the following to it. Replace <tt>brlan</tt> with the name of your bridge:
+
|Maintains=
  
<syntaxhighlight lang="bash">
+
|Blogs=
#!/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 05:30, 10 March 2014

Stacy Pawlowich

Contact

stac80+funtoo@gmail.com

Location

Loading map...
Calgary, Alberta, Canada (51° 2' 43.6632", -114° 5' 1.0752")