TipsAndTricks/RunningQemuOnMacOSX - Revision history

Stephano at 18:40, 19 July 2019

2019-07-19T18:40:22Z

← Older revision		Revision as of 18:40, 19 July 2019
Line 9:		Line 9:
	2. for images without a GUI, you can also use the 'nographic' option: $runqemu nographic qemux86 core-image-minimal		2. for images without a GUI, you can also use the 'nographic' option: $runqemu nographic qemux86 core-image-minimal

	Also, when running a ~~forwarding~~ X11 qemu graphical display over the network, especially over WiFi, the output of the serial port and graphics may be painfully slow to respond. One way to fix this is to use is to use QEMU's vnc option:		Also, when running a forwarded X11 qemu graphical display over the network, especially over WiFi, the output of the serial port and graphics may be painfully slow to respond. One way to fix this is to use is to use QEMU's vnc option:

	- $runqemu qemux86 core-image-sato qemuparams="-vnc :66"		- $runqemu qemux86 core-image-sato qemuparams="-vnc :66"

Stephano at 18:37, 19 July 2019

2019-07-19T18:37:07Z

← Older revision		Revision as of 18:37, 19 July 2019
Line 1:		Line 1:
	If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install [https://www.xquartz.org/ XQuartz].		If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install [https://www.xquartz.org/ XQuartz].

	Sadly the keyboard mapping ~~will~~ be incorrect. To solve this simply add these qemu params to your runqemu command:		Sadly the keyboard mapping may be incorrect. To solve this simply add these qemu params to your runqemu command:

	runqemu ~~'''~~qemuparams="-k en-us"~~''' qemux86~~		- $runqemu qemux86 core-image-sato qemuparams="-k en-us"

	A couple of notes:		A couple of notes:
			1. keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)
			2. for images without a GUI, you can also use the 'nographic' option: $runqemu nographic qemux86 core-image-minimal

	- ~~keyboard mapping will be incorrect for all builds (~~core-image-~~minimal, core~~-~~image-sato)~~		Also, when running a forwarding X11 qemu graphical display over the network, especially over WiFi, the output of the serial port and graphics may be painfully slow to respond. One way to fix this is to use is to use QEMU's vnc option:
	~~- for images without~~ a ~~GUI~~, you ~~can also use the 'nographic' option~~:
	runqemu ~~nographic~~ qemux86 core-image-~~minimal~~		- $runqemu qemux86 core-image-sato qemuparams="-vnc :66"

			This will start a vnc server at 127.0.0.1 on display 66. You can then use an X11 forwarded vncviewer. Of course, you could connect remotely without X11 forwarding using:

			- $runqemu qemux86 core-image-sato qemuparams="-vnc 192.168.0.123:66"

			Where the IP matches that of your build machine.

Stephano at 20:39, 27 September 2016

2016-09-27T20:39:39Z

← Older revision		Revision as of 20:39, 27 September 2016
Line 8:		Line 8:

	- keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)		- keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)
	- for images without a GUI, you can also use the 'nographic' option		- for images without a GUI, you can also use the 'nographic' option:
	runqemu nographic qemux86 core-image-minimal		runqemu nographic qemux86 core-image-minimal

Stephano at 20:39, 27 September 2016

2016-09-27T20:39:25Z

← Older revision		Revision as of 20:39, 27 September 2016
Line 9:		Line 9:
	- keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)		- keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)
	- for images without a GUI, you can also use the 'nographic' option		- for images without a GUI, you can also use the 'nographic' option
	- runqemu nographic qemux86 core-image-minimal		runqemu nographic qemux86 core-image-minimal

Stephano at 20:39, 27 September 2016

2016-09-27T20:39:08Z

← Older revision		Revision as of 20:39, 27 September 2016
Line 7:		Line 7:
	A couple of notes:		A couple of notes:

	-keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)		- keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)
	-for images without a GUI, you can also use the 'nographic' option		- for images without a GUI, you can also use the 'nographic' option
	- runqemu nographic qemux86 core-image-minimal		- runqemu nographic qemux86 core-image-minimal

Stephano at 20:37, 27 September 2016

2016-09-27T20:37:55Z

← Older revision		Revision as of 20:37, 27 September 2016
Line 7:		Line 7:
	A couple of notes:		A couple of notes:

	-keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)		-keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)
	-for images without a GUI, you can also use the 'nographic' option - runqemu nographic qemux86 core-image-minimal		-for images without a GUI, you can also use the 'nographic' option
			- runqemu nographic qemux86 core-image-minimal

Stephano at 20:37, 27 September 2016

2016-09-27T20:37:37Z

← Older revision		Revision as of 20:37, 27 September 2016
Line 4:		Line 4:

	runqemu '''qemuparams="-k en-us"''' qemux86		runqemu '''qemuparams="-k en-us"''' qemux86

			A couple of notes:

			-keyboard mapping will be incorrect for all builds (core-image-minimal, core-image-sato)
			-for images without a GUI, you can also use the 'nographic' option - runqemu nographic qemux86 core-image-minimal

Stephano at 20:35, 27 September 2016

2016-09-27T20:35:33Z

← Older revision		Revision as of 20:35, 27 September 2016
Line 1:		Line 1:
	If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install [https://www.xquartz.org/ XQuartz]. Sadly the keyboard mapping will be incorrect. To solve this simply add these qemu params to your runqemu command:		If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install [https://www.xquartz.org/ XQuartz].

			Sadly the keyboard mapping will be incorrect. To solve this simply add these qemu params to your runqemu command:

	runqemu '''qemuparams="-k en-us"''' qemux86		runqemu '''qemuparams="-k en-us"''' qemux86

Stephano: Created page with "If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install [https://www.xquartz.org/ XQuartz]. Sadly the keyboard mapping will be incor..."

2016-09-27T20:34:58Z

Created page with "If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install [https://www.xquartz.org/ XQuartz]. Sadly the keyboard mapping will be incor..."

New page

If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install [https://www.xquartz.org/ XQuartz]. Sadly the keyboard mapping will be incorrect. To solve this simply add these qemu params to your runqemu command:

runqemu '''qemuparams="-k en-us"''' qemux86