Hi,
Recently, as I run the qemu command to bring up windows guest, it
aborts with a vnc error
$ qemu -m 3000 -cpu Opteron_G5 -hda qemu-vm/win2xpsp3_32_c.img -hdb
qemu-vm/win2xpsp3_32_d.img -boot c -usbdevice tablet -enable-kvm
-device e1000,netdev=host_files -netdev
user,net=10.0.2.0/24,id=host_f
you can run ps -eaf |grep vnc to see whcih all ports being reserved . or
netstat comand netstat -tln|grep :59
On Sun, Jan 22, 2017 at 6:21 PM, Mahmood Naderan
wrote:
> Hi,
> Recently, as I run the qemu command to bring up windows guest, it
> aborts with a vnc error
>
> $ qemu -m 3000 -cpu Optero
>you can run ps -eaf |grep vnc to see whcih all ports being reserved
Isn't there any easier way? Users are not expert, so do not expect to use
ps command and see which vnc port is free...
If I don't use vnc, the qemu will bring up the screen. So, the question is
what is the benefit of using vnc?
This is how I addressed the need to try and select unique ports for the VNC and
Spice environments. This is from a Bash script used to start each VM.
#=#
# Spice and VNC Settings
I'm trying Qemu (2.8.0) on Slackware GNU Linux 14.2 (64-bit) host.
I've a Windows XP (guest) raw image which was working with Qemu times ago
(I used it on an older Slackware version as host system).
Now I launch qemu with the following command:
-
qemu-system-i386 \
-m 2G \
-net nic,model
Hi,
the vnc option can handle the port dynamicaly with -vnc :0,to=x where the
next open port is used from 5900 on to 5900+x.
You then can get the used port via monitor command info vnc or assign it to a
variable
VNC_PORT=$(echo "info vnc" | socat - UNIX-CONNECT:${FILE_MONITOR} | grep
address
Thanks for the suggestions. I will try them.
Regards,
Mahmood
