diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 16:27:09 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 16:27:09 +0000 |
| commit | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (patch) | |
| tree | 4010d5fb3e8bc48c110a2c1ff2a16b8648cb86bb /results/classifier/accel-gemma3:12b/kvm/1388735 | |
| parent | 5541099586dbd6018574cb44e1934907c121526f (diff) | |
| download | qemu-analysis-4d9e26c0333abd39bdbd039dcdb30ed429c475ba.tar.gz qemu-analysis-4d9e26c0333abd39bdbd039dcdb30ed429c475ba.zip | |
add gemma accelerator classification results
Diffstat (limited to 'results/classifier/accel-gemma3:12b/kvm/1388735')
| -rw-r--r-- | results/classifier/accel-gemma3:12b/kvm/1388735 | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/results/classifier/accel-gemma3:12b/kvm/1388735 b/results/classifier/accel-gemma3:12b/kvm/1388735 new file mode 100644 index 000000000..4828e574e --- /dev/null +++ b/results/classifier/accel-gemma3:12b/kvm/1388735 @@ -0,0 +1,12 @@ + +QEMU no longer allows to use full TCP port range for VNC + +After upgrade to QEMU version 2.1.0 (Debian 2.1+dfsg-4ubuntu6), I am no longer able to use any TCP port for VNC display. +For example, if I need to assign VNC server a TCP port 443, I used to run: +# qemu-system-x86_64 -vnc :-5457 +qemu-system-x86_64: Failed to start VNC server on `:-1000': can't convert to a number:-5457 +expected behavior: as any VNC software, take port base of 5900, substract 5457 display number, and use TCP port 443 + +I ask to change vnc port conversion routine to allow input values in range of all TCP ports, from 1 to 65535. + +I really depend on ability to use full TCP range for VNC port numbers, and inablity to do so in new version of QEMU is very disappointing. \ No newline at end of file |