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/1628971 | |
| 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/1628971')
| -rw-r--r-- | results/classifier/accel-gemma3:12b/kvm/1628971 | 58 |
1 files changed, 58 insertions, 0 deletions
diff --git a/results/classifier/accel-gemma3:12b/kvm/1628971 b/results/classifier/accel-gemma3:12b/kvm/1628971 new file mode 100644 index 000000000..b9cb36b46 --- /dev/null +++ b/results/classifier/accel-gemma3:12b/kvm/1628971 @@ -0,0 +1,58 @@ + +-netdev user: guestfwd doesn't work + +Hello! + +QEMU emulator version 2.6.1 (Debian 1:2.6.1+dfsg-0ubuntu4), Copyright (c) 2003-2008 Fabrice Bellard + +The IP address 192.168.1.46 is assigned to eth0. + +qemu-system-x86_64 \ + -no-hpet \ + -nodefconfig \ + -machine accel=kvm \ + -cpu host \ + -smp 2 \ + -drive if=virtio,file=yakkety-server-cloudimg-amd64.img \ + -device virtio-net-pci,netdev=net0 \ + -netdev 'user,id=net0,hostfwd=tcp::2222-:22,guestfwd=tcp:1.2.3.4:1234-cmd:nc 192.168.1.46 8842' \ + -m 1024 \ + -initrd yakkety-server-cloudimg-amd64-initrd-generic \ + -kernel yakkety-server-cloudimg-amd64-vmlinuz-generic \ + -append 'root=/dev/vda1 modprobe.blacklist=floppy systemd.log_level=debug systemd.journald.forward_to_console=1' + +Without the guestfwd=... part everything works nicely. With it I get the following message. + + +qemu-system-x86_64: -netdev user,id=net0,hostfwd=tcp::2222-:22,guestfwd=tcp:1.2.3.4:1234-cmd:nc 192.168.1.46 8842: conflicting/invalid host:port in guest forwarding rule 'tcp:1.2.3.4:1234-cmd:nc 192.168.1.46 8842' +qemu-system-x86_64: -netdev user,id=net0,hostfwd=tcp::2222-:22,guestfwd=tcp:1.2.3.4:1234-cmd:nc 192.168.1.46 8842: Device 'user' could not be initialized + + +But I just compiled c640f2849ee8775fe1bbd7a2772610aa77816f9f, and I get the same behavior. + +pas@strange:~/qemu/x86_64-softmmu$ ./qemu-system-x86_64 -net 'user,guestfwd=tcp:1.2.3.4:1234-cmd:nc 192.168.1.48 80' +qemu-system-x86_64: -net user,guestfwd=tcp:1.2.3.4:1234-cmd:nc 192.168.1.48 80: conflicting/invalid host:port in guest forwarding rule 'tcp:1.2.3.4:1234-cmd:nc 192.168.1.48 80' +qemu-system-x86_64: -net user,guestfwd=tcp:1.2.3.4:1234-cmd:nc 192.168.1.48 80: Device 'user' could not be initialized + + +After poking a bit around it seems that this check fails in slirp/slirp.c: (around line 1074) + + if ((guest_addr->s_addr & slirp->vnetwork_mask.s_addr) != + slirp->vnetwork_addr.s_addr || + guest_addr->s_addr == slirp->vhost_addr.s_addr || + guest_addr->s_addr == slirp->vnameserver_addr.s_addr) { + return -1; + } + +Because guest_addr, and slirp has equivalent s_addr values. + +x86_64-softmmu/qemu-system-x86_64 -net 'user,net=10.0.2.0/24,host=10.0.2.2,guestfwd=tcp:12.0.0.2:80-cmd:echo ok' + +guest_addr: 12.0.0.2 +vnetwork_mask: 12.0.0.2 +vhost_addr: 12.0.0.2 +vnameserver_addr: 12.0.0.2 +guest_addr & mask: 12.0.0.2 + + +Thanks in advance for looking into this! \ No newline at end of file |