qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: libvir-list@redhat.com, QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ipv6 slirp network
Date: Mon, 21 Jul 2014 22:13:58 +0200	[thread overview]
Message-ID: <20140721201358.GK5496@type.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <CACaajQunVPZJHE2XodbUDJU7h9CYvAR4aC77zc1Z5uLbXFVKUw@mail.gmail.com>

Vasiliy Tolstov, le Tue 22 Jul 2014 00:12:23 +0400, a écrit :
> 2014-07-21 23:49 GMT+04:00 Samuel Thibault <samuel.thibault@gnu.org>:
> > There's no current support for this, but that could be useful to add
> > indeed.
> 
> 
> I hit another issue, but may be not related to the patch. In centos 7
> (test another boxes) i have running qemu with:
> /usr/bin/qemu-system-x86_64 -device virtio-scsi-pci,id=scsi0 -device
> scsi-hd,bus=scsi0.0,drive=drive0 -device virtio-net,netdev=user.0
> -drive if=none,cache=unsafe,id=drive0,discard=unmap,file=output/centos-7-x86_64-qemu/centos-7-x86_64.raw
> -display none -netdev user,id=user.0 -boot once=d -redir tcp:3213::22
> -m size=1024Mib -name centos-7-x86_64 -machine type=pc-1.0,accel=kvm
> -cdrom /home/vtolstov/devel/vtolstov/packer-builder/templates/centos/packer_cache/cffdc67bdc73fef02507fdcaff2d9fb7cbc8780ac3c17e862a5451ddbf8bf39d.iso
> -vnc 0.0.0.0:47
> 
> and try to ssh to localhost -p 3213, but get timeout. in tcpdump i
> have send packets but not recieved. inside qemu vm listen for 22 port
> on ipv4 and ipv6. Inside vm i see in tcpdump incoming packets but not
> outcoming.

It is related to the patch.  I have fixed it, and pushed a newer
tosubmit branch.

Samuel

  reply	other threads:[~2014-07-21 20:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 11:34 [Qemu-devel] ipv6 slirp network Vasiliy Tolstov
2014-07-21 11:41 ` Samuel Thibault
2014-07-21 11:42   ` Vasiliy Tolstov
2014-07-21 11:49     ` Samuel Thibault
2014-07-21 11:55       ` Vasiliy Tolstov
2014-07-21 11:59         ` Vasiliy Tolstov
2014-07-21 12:06           ` Samuel Thibault
2014-07-21 12:10             ` Vasiliy Tolstov
2014-07-21 14:19             ` Vasiliy Tolstov
2014-07-21 14:29               ` Samuel Thibault
2014-07-21 14:36                 ` Vasiliy Tolstov
2014-07-21 14:47                 ` Vasiliy Tolstov
2014-07-21 14:52                   ` Samuel Thibault
2014-07-21 19:22                     ` Vasiliy Tolstov
2014-07-21 19:49                       ` Samuel Thibault
2014-07-21 20:12                         ` Vasiliy Tolstov
2014-07-21 20:13                           ` Samuel Thibault [this message]
2014-07-21 20:19                             ` Vasiliy Tolstov
2014-07-21 20:30                               ` Samuel Thibault
2014-07-21 20:49                                 ` Samuel Thibault
2014-07-22 10:54                                   ` Vasiliy Tolstov
2014-07-21 14:47                 ` Samuel Thibault
2014-07-21 14:51                   ` Samuel Thibault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140721201358.GK5496@type.youpi.perso.aquilenet.fr \
    --to=samuel.thibault@gnu.org \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=v.tolstov@selfip.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).