FAQ - Revision history

Iggy: minor formatting fix

2020-12-20T20:44:46Z

minor formatting fix

← Older revision		Revision as of 16:44, 20 December 2020
Line 29:		Line 29:
	With a recent enough Linux kernel, run the command:		With a recent enough Linux kernel, run the command:

	. egrep '^flags.*(vmx\|svm)' /proc/cpuinfo		'''egrep '^flags.*(vmx\|svm)' /proc/cpuinfo'''

	If something shows up, you have VT. You can also check the processor model name (in `/proc/cpuinfo`) in the vendor's web site.		If something shows up, you have VT. You can also check the processor model name (in `/proc/cpuinfo`) in the vendor's web site.

2015-11-08T20:03:43Z

When connecting to a VNC terminal, a "rect too big" message appears and the VNC session disconnects

← Older revision		Revision as of 16:03, 8 November 2015
Line 152:		Line 152:
	kvm 159656 1 kvm_intel		kvm 159656 1 kvm_intel

	=== When connecting to a VNC ~~Terminal~~, a "rect too big" message appears and the VNC ~~Session~~ disconnects ===		=== When connecting to a VNC terminal, a "rect too big" message appears and the VNC session disconnects ===
	This happens because of a VNC protocol flaw on the way on-the-fly pixel format changes are handled (more info at [http://www.mail-archive.com/qemu-devel@nongnu.org/msg04879.html this thread]). If you are using TigerVNC, you can avoid this problem by disabling on-the-fly selection of pixel encoding, using the <tt>-AutoSelect=0</tt> command-line option of vncviewer. You may also want to check the encoding options on the vncviewer man page, as this will disable automatic selection of encoding based on connection speed.		This happens because of a VNC protocol flaw on the way on-the-fly pixel format changes are handled (more info at [http://www.mail-archive.com/qemu-devel@nongnu.org/msg04879.html this thread]). If you are using TigerVNC, you can avoid this problem by disabling on-the-fly selection of pixel encoding, using the <tt>-AutoSelect=0</tt> command-line option of vncviewer. You may also want to check the encoding options on the vncviewer man page, as this will disable automatic selection of encoding based on connection speed.

2015-11-08T20:01:57Z

When connecting to a VNC Terminal, a "rect too big" message appears and the VNC Session disconnects

← Older revision		Revision as of 16:01, 8 November 2015
Line 152:		Line 152:
	kvm 159656 1 kvm_intel		kvm 159656 1 kvm_intel

	=== ~~"rect too big" Message when using VNC Display ===~~		=== When connecting to a VNC Terminal, a "rect too big" message appears and the VNC Session disconnects ===
	When ~~connection~~ to a VNC Terminal, a "rect too big" message appears, and the VNC Session disconnects.

	This happens because of a VNC protocol flaw on the way on-the-fly pixel format changes are handled (more info at [http://www.mail-archive.com/qemu-devel@nongnu.org/msg04879.html this thread]). If you are using TigerVNC, you can avoid this problem by disabling on-the-fly selection of pixel encoding, using the <tt>-AutoSelect=0</tt> command-line option of vncviewer. You may also want to check the encoding options on the vncviewer man page, as this will disable automatic selection of encoding based on connection speed.		This happens because of a VNC protocol flaw on the way on-the-fly pixel format changes are handled (more info at [http://www.mail-archive.com/qemu-devel@nongnu.org/msg04879.html this thread]). If you are using TigerVNC, you can avoid this problem by disabling on-the-fly selection of pixel encoding, using the <tt>-AutoSelect=0</tt> command-line option of vncviewer. You may also want to check the encoding options on the vncviewer man page, as this will disable automatic selection of encoding based on connection speed.

2015-11-08T19:57:46Z

Is it possible to use a host's USB devices within a guest?

← Older revision		Revision as of 15:57, 8 November 2015
Line 290:		Line 290:
	----------		----------

	=== Is it possible to use USB devices ~~with~~ a guest OS? ===		=== Is it possible to use a host's USB devices within a guest? ===
	Yes, ~~look up how to do it with QEMU, it's the same way~~.		Yes, this method is described in detail [http://www.linux-kvm.org/page/USB_Host_Device_Assigned_to_Guest here].

	----------		----------

2015-11-08T19:51:50Z

I compiled a new kernel for my KVM client and the ethernet interface is not recognized

← Older revision		Revision as of 15:51, 8 November 2015
Line 319:		Line 319:
	----------		----------

	=== I compiled a new kernel for my KVM client, and the ethernet interface is not recognized ===		=== I compiled a new kernel for my KVM client and the ethernet interface is not recognized ===
	~~you~~ can ~~tell~~ qemu ~~to emulate e~~.~~g. the 8139 with~~ model=rtl8139		You can specify alternative network interfaces to qemu with the ''-net nic,model='' parameter. For example, ''-net nic,model=rtl8139'' would enable a device with the Realtek 8139 chipset.

	----------		----------

2015-11-08T19:39:13Z

I can't ping from guest to host or vice versa. How can I access the host?

← Older revision		Revision as of 15:39, 8 November 2015
Line 324:		Line 324:
	----------		----------

	=== I can't ping from host ~~to guest~~ or vice versa. How can I access the host ~~please~~? ===		=== I can't ping from guest to host or vice versa. How can I access the host? ===
	ping ~~does~~ not go through, but ~~I suppose~~ you ~~can~~ access the host in ~~some~~ way, ~~i.e.~~ you can ~~navigate for sure internet(e.g~~. ~~firefox) if host can~~		The ping command may not go through in this circumstance, but you may be able to access the host in another way. For example, you can access a host running Apache by entering its IP address into a browser within the guest.

	----------		----------

	[[Category:Docs]][[Category:HowTo]]		[[Category:Docs]][[Category:HowTo]]

2015-11-08T19:28:18Z

Are 64-bit processors supported under KVM?

← Older revision		Revision as of 15:28, 8 November 2015
Line 6:		Line 6:

	----------		----------
	=== Are ~~64bits~~ processors supported under KVM? ===		=== Are 64-bit processors supported under KVM? ===
	Yes they are supported and will allow you to run ~~32bits~~ and 64 ~~bits~~ guests.		Yes they are supported and will allow you to run 32-bit and 64-bit guests.

	See also '''Can KVM run a 32-bit guest on a 64-bit host? What about PAE?''' below.		See also '''Can KVM run a 32-bit guest on a 64-bit host? What about PAE?''' below.

2015-05-31T14:06:03Z

added categories

← Older revision		Revision as of 10:06, 31 May 2015
Line 328:		Line 328:

	----------		----------

			[[Category:Docs]][[Category:HowTo]]

2015-05-31T14:04:35Z

move orphan page content to faq

@@ Line 316: / Line 316: @@
 === Is the name 'KVM' trademarked? ===
 No.
 ----------

2014-12-30T22:17:46Z

Added some tea.

← Older revision		Revision as of 18:17, 30 December 2014
Line 128:		Line 128:
	=== How can I check that I'm not falling back to QEMU with no hardware acceleration? ===		=== How can I check that I'm not falling back to QEMU with no hardware acceleration? ===

	If you think that you might no be using the hardware acceleration provided by the KVM module, here are a few steps to help you check this.		If you think that you might not be using the hardware acceleration provided by the KVM module, here are a few steps to help you check this.

	First of all, check that you don't have messages such as:		First of all, check that you don't have messages such as: