On Wed, Dec 16, 2015 at 03:43:06PM +0300, Pavel Fedin wrote:
> rYR8N8f/ookveMRL7BfPnj5lw+EJZd+uG+v/lZnBuWidyQ4r
> g586/P1rPsQw8p6wT+M7LnqvMLZM9eWq2ht53Bd5liqxFGckGmoxFxUnAgC5sFKthAIAAA==
> Status: O
> Content-Length: 4853
> Lines: 66
>
> Hello!
>
> > However, I'm more curious about the pin
On Wed, Dec 16, 2015 at 02:57:15PM +0300, Pavel Fedin wrote:
> Hello!
>
> > I can reproduce your issue on my side with above patch (and only when
> > F_GUEST_ANNOUNCE is not set at DPDK vhost lib). TBH, I don't know
> > why that happened, the cause could be subtle, and I don't think it's
> > wort
Hello!
> However, I'm more curious about the ping loss? Did you still see
> that? And to be more specific, have the wireshark captured the
> GRAP from the guest?
Yes, everything is fine.
root at nfv_test_x86_64 /var/log/libvirt/qemu # tshark -i ovs-br0
Running as user "root" and group "root".
On Tue, Dec 15, 2015 at 05:58:28PM +0300, Pavel Fedin wrote:
> Hello!
>
> > No idea. Maybe you have changed some other configures (such as of ovs)
> > without notice? Or, the ovs bridge interface resets?
>
> I don't touch the ovs at all. Just shut down the guest, rebuild the qemu,
> reinstall
Hello!
> I can reproduce your issue on my side with above patch (and only when
> F_GUEST_ANNOUNCE is not set at DPDK vhost lib). TBH, I don't know
> why that happened, the cause could be subtle, and I don't think it's
> worthwhile to dig it, especially it's not the right way to do it.
May be no
On Wed, Dec 16, 2015 at 10:38:03AM +0800, Peter Xu wrote:
> On Tue, Dec 15, 2015 at 04:07:57PM +0100, Thibaut Collet wrote:
> > After a migration, to avoid netwotk outage, all interfaces of the guest
> > must send a packet to update switches mapping (ideally a GARP).
> > As some interfaces do not d
On Tue, Dec 15, 2015 at 04:07:57PM +0100, Thibaut Collet wrote:
> After a migration, to avoid netwotk outage, all interfaces of the guest
> must send a packet to update switches mapping (ideally a GARP).
> As some interfaces do not do it QEMU does it in behalf of the guest by
> sending a RARP (his
Hello!
> 1. if vhost-user backend (or say, DPDK) supports GUEST_ANNOUNCE, and
>send another RARP (or say, GARP, I will use RARP as example),
>then there will be two RARP later on the line, right? (since the
>QEMU one is sent unconditionally from qemu_announce_self).
qemu_announce_se
On Tue, Dec 15, 2015 at 04:48:12PM +0300, Pavel Fedin wrote:
> Hello!
>
> > > Wrong. I tried to unconditionally enforce it in qemu (my guest does
> > > support it), and the
> > link stopped working at all. I don't understand why.
> >
> > I'm wondering how did you do that? Why do you need enfor
On Tue, Dec 15, 2015 at 03:24:48PM +0300, Pavel Fedin wrote:
> Hello!
>
> > After a migration, to avoid network outage, the guest must announce its new
> > location to the L2 layer, typically with a GARP. Otherwise requests sent to
> > the guest arrive to the old host until a ARP request is sent
On Tue, Dec 15, 2015 at 12:47:47PM +0100, Thibaut Collet wrote:
> On Tue, Dec 15, 2015 at 12:43 PM, Thibaut Collet
> wrote:
>
> >
> >
> > On Tue, Dec 15, 2015 at 11:05 AM, Peter Xu wrote:
> >
> >> On Tue, Dec 15, 2015 at 11:45:56AM +0300, Pavel Fedin wrote:
> >> > To tell the truth, i don't kno
Hello!
> After a migration, to avoid netwotk outage, all interfaces of the guest must
> send a packet to update switches mapping (ideally a GARP).
> As some interfaces do not do it QEMU does it in behalf of the guest by
> sending a RARP (his RARP is not forged by the guest but by QEMU). This is
On Tue, Dec 15, 2015 at 11:45:56AM +0300, Pavel Fedin wrote:
> To tell the truth, i don't know. I am also learning qemu internals on the
> fly. Indeed, i see that it should announce itself. But
> this brings up a question: why do we need special announce procedure in
> vhost-user then?
I have t
Hello!
> No idea. Maybe you have changed some other configures (such as of ovs)
> without notice? Or, the ovs bridge interface resets?
I don't touch the ovs at all. Just shut down the guest, rebuild the qemu,
reinstall it, run the guest.
>
> BTW, would you please try my v1 patch set with abo
On Tue, Dec 15, 2015 at 04:23:24PM +0800, Yuanhan Liu wrote:
> On Mon, Dec 14, 2015 at 11:58:42AM +0800, Peter Xu wrote:
> > If ping to guest from outside, when the migration finishes on the
> > target side of qemu, qemu_self_announce() will be called.
>
> It's supposed to see some ARP requests if
On Tue, Dec 15, 2015 at 11:45:56AM +0300, Pavel Fedin wrote:
> Hello!
>
> > I mean I do find that qemu_annouce_self composes an ARP
> > broadcoast request, but it seems that I didn't catch it on
> > the target host.
> >
> > Something wrong, or someting I missed?
>
> To tell the truth, i don't
Hello!
> > Wrong. I tried to unconditionally enforce it in qemu (my guest does
> > support it), and the
> link stopped working at all. I don't understand why.
>
> I'm wondering how did you do that? Why do you need enforece it in QEMU?
> Isn't it already supported so far?
I mean - qemu first
On Mon, Dec 14, 2015 at 11:58:42AM +0800, Peter Xu wrote:
> On Fri, Dec 11, 2015 at 01:22:23PM +0300, Pavel Fedin wrote:
> > BTW, it works, and it was my bad. openvswitch was configured incorrectly
> > on the other side, vhost port number was different for
> > some reason, while ruleset was the s
On Tue, Dec 15, 2015 at 2:18 PM, Yuanhan Liu
wrote:
> On Tue, Dec 15, 2015 at 12:47:47PM +0100, Thibaut Collet wrote:
> > On Tue, Dec 15, 2015 at 12:43 PM, Thibaut Collet <
> thibaut.collet at 6wind.com>
> > wrote:
> >
> > >
> > >
> > > On Tue, Dec 15, 2015 at 11:05 AM, Peter Xu wrote:
> > >
> >
Hello!
> After a migration, to avoid network outage, the guest must announce its new
> location to the L2 layer, typically with a GARP. Otherwise requests sent to
> the guest arrive to the old host until a ARP request is sent (after 30
> seconds) or the guest sends some data.
> QEMU implementat
On Tue, Dec 15, 2015 at 12:43 PM, Thibaut Collet
wrote:
>
>
> On Tue, Dec 15, 2015 at 11:05 AM, Peter Xu wrote:
>
>> On Tue, Dec 15, 2015 at 11:45:56AM +0300, Pavel Fedin wrote:
>> > To tell the truth, i don't know. I am also learning qemu internals on
>> the fly. Indeed, i see that it should a
On Tue, Dec 15, 2015 at 11:05 AM, Peter Xu wrote:
> On Tue, Dec 15, 2015 at 11:45:56AM +0300, Pavel Fedin wrote:
> > To tell the truth, i don't know. I am also learning qemu internals on
> the fly. Indeed, i see that it should announce itself. But
> > this brings up a question: why do we need sp
Hello!
> Note quite sure. I found Thibaut submitted a patch to send
> VHOST_USER_SEND_RARP request after migration is done months
> ago. Thibaut, would you please elaborate it a bit more what
> should be done on vhost-user backend? To construct a gratuitous
> ARP request and broadcast it?
By th
Hello!
> I mean I do find that qemu_annouce_self composes an ARP
> broadcoast request, but it seems that I didn't catch it on
> the target host.
>
> Something wrong, or someting I missed?
To tell the truth, i don't know. I am also learning qemu internals on the fly.
Indeed, i see that it shou
On Mon, Dec 14, 2015 at 09:28:08PM +0800, Peter Xu wrote:
> On Mon, Dec 14, 2015 at 09:21:15PM +0800, Yuanhan Liu wrote:
> > Peter,
> >
> > Thanks for your input, and that sounds reasonable. You just reminded
> > me that the host1's NIC is indeed different with host2's NIC: the ovs
> > bridge mac
On Mon, Dec 14, 2015 at 09:21:15PM +0800, Yuanhan Liu wrote:
> Peter,
>
> Thanks for your input, and that sounds reasonable. You just reminded
> me that the host1's NIC is indeed different with host2's NIC: the ovs
> bridge mac address is different.
>
> I then had a quick try, setting the two ovs
On Mon, Dec 14, 2015 at 09:00:22PM +0800, Peter Xu wrote:
> On Mon, Dec 14, 2015 at 08:09:37PM +0800, Yuanhan Liu wrote:
> > It seems that we have exactly the same test environment set up: I have
> > one server (where I normally do vhost test there) and one desktop (my
> > dev box),
> >
> > On bo
On Mon, Dec 14, 2015 at 08:09:37PM +0800, Yuanhan Liu wrote:
> It seems that we have exactly the same test environment set up: I have
> one server (where I normally do vhost test there) and one desktop (my
> dev box),
>
> On both hosts, there is an ovs bridge, with IP address 192.168.100.1
> assi
On Mon, Dec 14, 2015 at 12:46:57PM +0300, Pavel Fedin wrote:
> Hello!
>
> > > Host<--->openVSwitch<--->guest
> > > LOCAL vhostuser
> > >
> > > So, in order to migrate the guest, i simply replicated this setup on
> > > both hosts, with the
> > same IPs on host sid
On Mon, Dec 14, 2015 at 12:46:57PM +0300, Pavel Fedin wrote:
> > Regarding to "with the same IPs on host side": do you mean that you
> > configured the same IP on two hosts in the intranet?
>
> No intranet. You can think of it as an isolated network between the host and
> guest, and that's all.
Hello!
> > I _guess_ the problem for ping might be: guest ARP entry for
> > 192.168.100.1 is not updated. Or say, after guest migrated to host2
> > from host1, guest is still trying to send packet to host1's NIC (no
> > one is telling it to update, right?), so no one is responding the
> > ping. W
On Mon, Dec 14, 2015 at 10:30:54AM +0300, Pavel Fedin wrote:
> Hello!
Hi, Pavel!
>
> > When doing the ping, was it from the guest (to another host) or to
> > the guest (from another host)?
> >
> > In any case, I still could not understand why the ping loss happened
> > in this test.
> >
> > I
Hello!
> > Host<--->openVSwitch<--->guest
> > LOCAL vhostuser
> >
> > So, in order to migrate the guest, i simply replicated this setup on both
> > hosts, with the
> same IPs on host side. And on both hosts i set up the following ruleset for
> openvswitch:
>
>
On Fri, Dec 11, 2015 at 01:22:23PM +0300, Pavel Fedin wrote:
> BTW, it works, and it was my bad. openvswitch was configured incorrectly on
> the other side, vhost port number was different for
> some reason, while ruleset was the same. I reconfigured it and now everything
> migrates correctly, e
Hello!
> When doing the ping, was it from the guest (to another host) or to
> the guest (from another host)?
>
> In any case, I still could not understand why the ping loss happened
> in this test.
>
> If ping from guest, no ARP refresh is required at all?
ping from guest to host.
Ok, my se
On Fri, Dec 11, 2015 at 11:26:55AM +0300, Pavel Fedin wrote:
> Hello!
>
> I am currently testing this patchset with qemu and have problems.
Hi,
Thanks for testing!
>
> The guest migrates correctly, but after the migration it cries in the log:
>
> Vhost user backend fails to broadcast fake R
Hello!
> On Fri, Dec 11, 2015 at 11:26:55AM +0300, Pavel Fedin wrote:
> > Hello!
> >
> > I am currently testing this patchset with qemu and have problems.
>
> Hi,
>
> Thanks for testing!
Not at all :)
BTW, it works, and it was my bad. openvswitch was configured incorrectly on
the other s
Hello!
I am currently testing this patchset with qemu and have problems.
The guest migrates correctly, but after the migration it cries in the log:
Vhost user backend fails to broadcast fake RARP
and pinging the (new) host doesn't work. When i migrate it back to the old
host, the network r
On 12/2/2015 11:40 AM, Yuanhan Liu wrote:
> This patch set adds the initial vhost-user live migration support.
>
> The major task behind that is to log pages we touched during
> live migration. So, this patch is basically about adding vhost
> log support, and using it.
>
> Patchset
>
> - P
On Wed, Dec 02, 2015 at 04:10:56PM +0200, Victor Kaplansky wrote:
...
> > Note: this patch set has mostly been based on Victor Kaplansk's demo
> > work (vhost-user-bridge) at QEMU project. I was thinking to add Victor
> > as the co-author. Victor, what do you think of that? :)
>
> Thanks for addin
On Wed, Dec 02, 2015 at 11:43:09AM +0800, Yuanhan Liu wrote:
> This patch set adds the initial vhost-user live migration support.
>
> The major task behind that is to log pages we touched during
> live migration. So, this patch is basically about adding vhost
> log support, and using it.
>
> Patc
This patch set adds the initial vhost-user live migration support.
The major task behind that is to log pages we touched during
live migration. So, this patch is basically about adding vhost
log support, and using it.
Patchset
- Patch 1 handles VHOST_USER_SET_LOG_BASE, which tells us whe
42 matches
Mail list logo
