All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as migration
Date: Tue, 6 Feb 2018 16:24:33 +0100	[thread overview]
Message-ID: <20180206162433.09922904@redhat.com> (raw)
In-Reply-To: <20180205183630.GD2317@work-vm>

On Mon, 5 Feb 2018 18:36:31 +0000
"Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:

> * Tan, Jianfeng (jianfeng.tan@intel.com) wrote:
> > 
> > 
> > On 2/6/2018 12:29 AM, Igor Mammedov wrote:  
> > > On Mon,  5 Feb 2018 14:58:55 +0000
> > > Jianfeng Tan <jianfeng.tan@intel.com> wrote:
> > >   
> > > > Existing VMs with virtio devices and vhost-kernel as the backend
> > > > are always started with mem config:
> > > > 
> > > >    "-m xG"
> > > >    (with a ram block named "pc.ram")
> > > > 
> > > > while new VMs with virtio devices and vhost-user as the backend
> > > > are always started with mem config:
> > > > 
> > > >    "-m xG -numa node,memdev=pc.ram -object memory-backend-file,id=pc.ram,..."
> > > >    (with a ram block named "/object/pc.ram")  
> > > could you elaborate more on what src command line migrating to what dst command line?  
> > 
> > The src cmdline:
> >     $QEMU -enable-kvm -cpu host -smp 4 /path/to/img \
> >       -m 2G \
> >       -netdev tap,id=mynet1,vhost=on \
> >       -device virtio-net-pci,netdev=mynet1,mac=52:54:00:12:34:58 ...
> > 
> > The dst cmdline:
> >     $QEMU -enable-kvm -cpu host -smp 4 /path/to/img \
> >       -m 2G -numa node,memdev=pc.ram -mem-prealloc \
> >       -object
> > memory-backend-file,id=pc.ram,size=2G,mem-path=/dev/hugepages,share=on \
> >       -chardev socket,id=char0,path=/tmp/sock0 \
> >       -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
> >       -device virtio-net-pci,netdev=mynet1,mac=52:54:00:12:34:58 \
> >       -incoming tcp:0:4444 ...  
> 
> I'm surprised that it's safe to -numa node  the destination, even with
> the hack to the RAMBlock naming.  I'd expect it to have other effects
> as well.
it supposed to be 2 mutually exclusive configurations,
but migration stream doesn't have that information explicitly
(different id naming/mapping could fail migration).


> Dave
> 
> > Thanks,
> > Jianfeng
> >   
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

      reply	other threads:[~2018-02-06 15:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 14:58 [Qemu-devel] [RFC] exec: eliminate ram naming issue as migration Jianfeng Tan
2018-02-05 15:45 ` no-reply
2018-02-05 15:53 ` Paolo Bonzini
2018-02-05 16:12   ` Tan, Jianfeng
2018-02-05 16:19     ` Paolo Bonzini
2018-02-05 16:44       ` Tan, Jianfeng
2018-02-05 16:53         ` Paolo Bonzini
2018-02-05 17:15       ` Igor Mammedov
2018-02-05 17:31         ` Paolo Bonzini
2018-02-07  7:49           ` Tan, Jianfeng
2018-02-07 12:06             ` Igor Mammedov
2018-02-08  1:20               ` Tan, Jianfeng
2018-02-08  9:51                 ` Igor Mammedov
2018-02-08 10:18                   ` Tan, Jianfeng
2018-02-08 11:30                     ` Igor Mammedov
2018-02-24  3:08                       ` Tan, Jianfeng
2018-02-24  3:11                       ` Tan, Jianfeng
2018-02-26 12:55                         ` Igor Mammedov
2018-02-26 14:43                           ` Paolo Bonzini
2018-02-27  4:55                             ` Tan, Jianfeng
2018-02-27  4:36                           ` Tan, Jianfeng
2018-02-28 15:40                             ` Igor Mammedov
2018-02-05 18:44         ` Dr. David Alan Gilbert
2018-02-05 16:12 ` no-reply
2018-02-05 16:29 ` Igor Mammedov
2018-02-05 16:51   ` Tan, Jianfeng
2018-02-05 18:36     ` Dr. David Alan Gilbert
2018-02-06 15:24       ` Igor Mammedov [this message]

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=20180206162433.09922904@redhat.com \
    --to=imammedo@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jianfeng.tan@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.