KvmOnGentoo

Xming — Thu, 09 May 2013 11:34:53 GMT

Revision as of 11:34, 9 May 2013		Current revision
Line 14:		Line 14:

	== Installing ==		== Installing ==
-	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/protage/make.conf	+	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/portage/make.conf
-	(If you haven't migrated /etc/make.conf to /etc/protage/make.conf yet, use /etc/portage instead or migrate it to /etc/protage/make.conf)	+	(If you haven't migrated /etc/make.conf to /etc/portage/make.conf yet, use /etc/make.conf instead or migrate it to /etc/portage/make.conf)
	* emerge app-emulation/qemu-kvm		* emerge app-emulation/qemu-kvm

HOWTO

Mjt — Thu, 09 May 2013 11:30:35 GMT

add link to gentoo wiki page, probably need to delete local KvmOnGentoo

Revision as of 11:30, 9 May 2013		Current revision
Line 52:		Line 52:

	=== Gentoo ===		=== Gentoo ===
		+	* Gentoo has [http://wiki.gentoo.org/wiki/QEMU good page about qemu/kvm in their wiki].
	* [[KvmOnGentoo\|KVM on Gentoo hosts]]		* [[KvmOnGentoo\|KVM on Gentoo hosts]]

KvmOnGentoo

Xming — Thu, 09 May 2013 11:29:59 GMT

Revision as of 11:29, 9 May 2013		Current revision
Line 14:		Line 14:

	== Installing ==		== Installing ==
-	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/make.conf	+	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/protage/make.conf
		+	(If you haven't migrated /etc/make.conf to /etc/protage/make.conf yet, use /etc/portage instead or migrate it to /etc/protage/make.conf)
	* emerge app-emulation/qemu-kvm		* emerge app-emulation/qemu-kvm

Networking

Mjt — Wed, 08 May 2013 10:27:17 GMT

Added "Compatibility" part

Revision as of 10:27, 8 May 2013		Current revision
Line 18:		Line 18:

	'''Solution:'''		'''Solution:'''
-	* simply run your guest with "-net nic -net user", e-g:	+	* simply run your guest without specifying network parameters, which by default will create user-lever (a.k.a slirp) networking:
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic -net user	+	qemu-system-x86_64 -hda /path/to/hda.img

	'''Notes:'''		'''Notes:'''
	* The IP address can be automatically assigned to the guest thanks to the DHCP service integrated in QEMU		* The IP address can be automatically assigned to the guest thanks to the DHCP service integrated in QEMU
	* If you run multiple guests on the host, you don't need to specify a different MAC address for each guest		* If you run multiple guests on the host, you don't need to specify a different MAC address for each guest
-	* You can still access one specific port on the guest using the "hostfwd" option. This means e.g. if you want to transport a file with scp from host to guest, start the guest with "-net nic -net user,hostfwd=tcp::5555-:22". Now you are forwarding the host port 5555 to the guest port 22. After starting up the guest, you can transport a file with e.g. "scp -P 5555 file.txt root@localhost:/tmp" from host to guest. Or you can also use other address of the host to connect to.	+	* The default is equivalent to this explicit setup:
		+	qemu-system-x86_64 -hda /path/to/hda.img -netdev user,id=user.0 -device e1000,netdev=user.0
		+	* user.0 identifier above is just to connect the two halves into one, you may use any identifier you wish, such as "n" or "net0".
		+	* Use rtl8139 instead of e1000 to get 8139-series NIC.
		+	* You can still access one specific port on the guest using the "hostfwd" option. This means e.g. if you want to transport a file with scp from host to guest, start the guest with "-device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::5555-:22". Now you are forwarding the host port 5555 to the guest port 22. After starting up the guest, you can transport a file with e.g. "scp -P 5555 file.txt root@localhost:/tmp" from host to guest. Or you can also use other address of the host to connect to.


Line 68:		Line 72:

	* Run each guest with the following, replacing $macaddress with the value from the previous step		* Run each guest with the following, replacing $macaddress with the value from the previous step
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0

	'''Notes:'''		'''Notes:'''
	* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use		* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use
	* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run		* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap,script=/path/to/qemu-ifup	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0,script=/path/to/qemu-ifup

	* Each guest on the private virtual network must have a different MAC address		* Each guest on the private virtual network must have a different MAC address
Line 182:		Line 186:

	* Run each guest with the following, replacing $macaddress with the value from the previous step		* Run each guest with the following, replacing $macaddress with the value from the previous step
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0

	'''Notes:'''		'''Notes:'''
	* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use		* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use
	* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run		* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap,script=/path/to/qemu-ifup	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0,script=/path/to/qemu-ifup

	* Each guest on the network must have a different MAC address		* Each guest on the network must have a different MAC address
Line 225:		Line 229:
	There's now a page dedicated to ideas for improving		There's now a page dedicated to ideas for improving
	[[Networking Performance]].		[[Networking Performance]].
		+
		+	== Compatibility ==
		+
		+	There's another, old and obsolete syntax of specifying network for virtual machines. Above examples uses -netdev..-device model, old way used -net..-net pairs. For example,
		+
		+	-netdev tap,id=net0 -device e1000,netdev=net0,mac=52:54:00:12:34:56
		+
		+	is about the same as old
		+
		+	-net tap,vlan=0 -net nic,vlan=0,model=e1000,macaddr=52:54:00:12:34:56
		+
		+	(note mac => macaddr parameter change as well; vlan=0 is the default).
		+
		+	Old way used the notion of "VLANs" - these are QEMU VLANS, which has nothing to do with 802.1q VLANs. Qemu VLANs are numbered starting with 0, and it's possible to connect one or more devices (either host side, like -net tap, or guest side, like -net nic) to each VLAN, and, in particular, it's possible to connect more than 2 devices to a VLAN. Each device in a VLAN gets all traffic received by every device in it. This model was very confusing for the user (especially when a guest has more than one NIC).
		+
		+	In new model, each host side correspond to just one guest side, forming a pair of devices based on -netdev id= and -device netdev= parameters. It is less confusing, it is faster (because it's always 1:1 pair), and it supports more parameters than old -net..-net way.
		+
		+	However, -net..-net is still supported, used widely, and mentioned in lots of various HOWTOs and guides around the world. It is also a bit shorter and so faster to type.

KVM - Recent changes [en]

KvmOnGentoo

HOWTO

KvmOnGentoo

Networking