TipsAndTricks/RunningQemuOnMacOSX: Difference between revisions

From Yocto Project
Jump to navigationJump to search
mNo edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
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 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:
- 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.

Latest revision as of 18:40, 19 July 2019

If you'd like to forward X11 from a build machine to a machine running OSX, you'll need to install XQuartz.

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

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

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

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"

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.