Changes between Version 11 and Version 12 of qemu
- Timestamp:
- 04/21/2022 08:42:05 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified qemu
v11 v12 7 7 qemu can be built without any graphical environment and run on a server, where the display will be made available by the integrated vnc server. 8 8 9 Building qemu without any graphical environment on a system that has a graphical environment installed seems to be a bit tricky. I was successful lwith the following commands:9 Building qemu without any graphical environment on a system that has a graphical environment installed seems to be a bit tricky. I was successful with the following commands: 10 10 {{{ 11 11 pathremove $XORG_PREFIX/bin PATH … … 40 40 41 41 42 The port bit of vnc is a bit funny, as the vnc port that you specify on the server is then increased by 5900 by qemu. 42 Vnc ports usually start at 5900, so when you define your vnc port for your virtual machine, qemu adds 5900 to it for the real port number. 43 43 44 44 The following will work: … … 50 50 QEMU_LOG_FILE=/tmp/myvm.log 51 51 QEMU_SERVER_VNC_ADDR=192.168.219.5 52 QEMU_SERVER_VNC_PORT= 594252 QEMU_SERVER_VNC_PORT=1 53 53 54 54 nohup /usr/bin/qemu $ALL_YOUR_USUAL_QEMU_OPTIONS_FOR_THIS_VM -vnc $QEMU_SERVER_VNC_ADDR:$QEMU_SERVER_VNC_PORT > $QEMU_LOG_FILE 2>&1 & 55 55 }}} 56 56 57 qemu will then make the display of the vm available on 192.168.219.5: 1184257 qemu will then make the display of the vm available on 192.168.219.5:5901 58 58 59 59 So, on your client desktop, you can then connect to it by: 60 60 61 61 {{{ 62 vncviewer 192.168.219.5:11842 63 }}} 64 65 On hindsight, maybe it would be more clever to specify "2" as the vnc server port and the just call it on 5902.... 66 67 Anyway, this works quite well for me, of course I have a couple of scripts to manage this easier. 62 vncviewer 192.168.219.5:5901 63 }}} 64 65 68 66 69 67