I have had the same problem, I tried logging into a buildroot image that
was started using the following command line:
qemu-system-i386 -drive
file=output/images/disk.img,format=raw,index=0,media=disk -vga std -nic
user,ipv6=off,model=e1000,mac=10:10:10:10:10:10,hostfwd=tcp::4000-:22
The ssh
That's rather embarrassing, but the problem with my VM was that it was
lacking networking support. I turned this (too) minimal example of a
Guix System:
;;; file: os.scm
(use-modules (gnu services ssh)
(gnu system)
(gnu tests))
(simple-operating-system
(service
Here's what `tcpdump -i lo` reports during attempting the SSH access:
17:09:30.573545 IP localhost.55526 > localhost.: Flags [S], seq 1198531632,
win 65495, options [mss 65495,sackOK,TS val 1662149852 ecr 0,nop,wscale 7],
length 0
17:09:30.573569 IP localhost. > localhost.55526: Flags
Hello, I'm also experiencing such a problem, using qemu-system-x86_64
(hence the retitling of this issue). More information and output is
available at http://issues.guix.gnu.org/48739, but basically with the
following QEMU command used to run a VM:
** Summary changed:
- -net user,hostfwd=... is not working(qemu-system-aarch64)
+ -net user,hostfwd=... is not working
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1414466
Title:
-net
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1414466
Title:
-net
So is this now working for everybody with the correct ssh config (maybe
also check your firewall settings)? Could we close this ticket nowadays?
Or is somebody still having trouble?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are
Finally I found what was the issue. in the /etc/ssh/sshd_config after
commenting the below lines I am able to ssh to the vm.
# grep -i LISTEN /etc/ssh/sshd_config
#ListenAddress 127.0.0.1
#ListenAddress ::
#
check your sshd config.
--
You received this bug notification because you are a member
Is this issue resolved.?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1414466
Title:
-net user,hostfwd=... is not working(qemu-system-aarch64)
Status in QEMU:
Confirmed
Bug description:
Do we got any solution for this issue ?
I am seeing similar issue for qemu-system-arm, I have tried with "-nic
user,model=virtio-net-
pci,hostfwd=tcp:127.0.0.1:31258-:22,hostfwd=tcp:127.0.0.1:47175-:443,hostname=xxx.com"
and also with "-net nic -net
Redirect does happen, but no packets appear on guest interface: checked
by iptables rule for `NEW` on `tcpport 22` inside guest.
On host:
$ sudo lsof -itcp | grep 2851
packer24233 kit6u IPv4 1532725 0t0 TCP
localhost:52822->localhost:2851 (ESTABLISHED)
qemu-syst 24286
Doesn't work even with proper hostfwd
Doesn't work even with `-redir`
$ qemu-system-x86_64 -machine type=pc,accel=kvm -netdev
user,id=user.0,hostfwd=tcp::2851-:22 -display sdl -cpu host -smp cpus=2
-device rtl8139,netdev=user.0 -cdrom /home/kit/git/packer-
I think this is not a bug, but you are using the command line parameters
in a wrong way. When you use "-net user,hostfwd=tcp:127.0.0.1:1122-:22"
you are creating a *new*, second host network device which is not
connected to the guest NIC device that you specified. Please try to
avoid mixing "-net"
Also happens on Ubuntu 16.04.1 64-bit with QEMU 1:2.5+dfsg-5ubuntu10.4.
I have the following settings added to instance xml config:
It looks like forwarding does not happen at all. When I try to connect
to guest instance, I get exactly the same results regardless of whether
14 matches
Mail list logo
