From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Dov Murik <dovmurik@linux.vnet.ibm.com>
Cc: anthony.perard@citrix.com, sstabellini@kernel.org,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH] migration: Truncate state file in xen-save-devices-state
Date: Mon, 21 Sep 2020 18:56:39 +0100 [thread overview]
Message-ID: <20200921175639.GP3221@work-vm> (raw)
In-Reply-To: <f1ae6a96-322d-faaf-7ab8-1481cffa7aa7@linux.vnet.ibm.com>
* Dov Murik (dovmurik@linux.vnet.ibm.com) wrote:
>
>
> On 21/09/2020 14:17, Dr. David Alan Gilbert wrote:
> > * Dov Murik (dovmurik@linux.vnet.ibm.com) wrote:
> > > When running the xen-save-devices-state QMP command, if the filename
> > > already exists it will be truncated before dumping the devices' state
> > > into it.
> > >
> > > Signed-off-by: Dov Murik <dovmurik@linux.vnet.ibm.com>
> > > ---
> >
> > OK, that looks fine to me, so:
> >
> > Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >
> > >
> > > Note that I found the above issue while trying to debug
> > > xen-load-devices-state which simply fails (prints "Configuration section
> > > missing" to stderr) directly after xen-save-devices-state (in the same
> > > VM). I wonder if I should file a bug report as-is or investigate some
> > > more. Advice welcome.
> >
> > I don't try the xen-* commands normally; I've cc'ing in Stefano and
> > Anthony.
>
> Thanks Dave. Just to be clear, I'm running this without Xen at all; but
> these commands seem to work OK for dumping/restoring guest's devices
> state (without RAM) -- if I modify the code to circumvent the mentioned
> problem.
Yeh, although you can't rely on them not doing something Xen in the
future. There are a few other similar ways of doing what you want; eg.
if your RAM is 'shared' then you can set the x-ignore-shared migration
capability.
Dave
> Dov
>
> >
> > Dave
> >
> > >
> > > -Dov
> > >
> > > ---
> > > migration/savevm.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/migration/savevm.c b/migration/savevm.c
> > > index 304d98ff78..e1b26672cc 100644
> > > --- a/migration/savevm.c
> > > +++ b/migration/savevm.c
> > > @@ -2803,7 +2803,8 @@ void qmp_xen_save_devices_state(const char *filename, bool has_live, bool live,
> > > vm_stop(RUN_STATE_SAVE_VM);
> > > global_state_store_running();
> > > - ioc = qio_channel_file_new_path(filename, O_WRONLY | O_CREAT, 0660, errp);
> > > + ioc = qio_channel_file_new_path(filename, O_WRONLY | O_CREAT | O_TRUNC,
> > > + 0660, errp);
> > > if (!ioc) {
> > > goto the_end;
> > > }
> > > --
> > > 2.20.1
> > >
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-09-21 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 9:48 [PATCH] migration: Truncate state file in xen-save-devices-state Dov Murik
2020-09-21 11:17 ` Dr. David Alan Gilbert
2020-09-21 12:28 ` Dov Murik
2020-09-21 17:56 ` Dr. David Alan Gilbert [this message]
2020-09-21 23:46 ` Stefano Stabellini
2020-09-23 18:59 ` Dr. David Alan Gilbert
2020-09-28 16:46 ` Anthony PERARD via
2020-09-28 22:47 ` Marek Marczykowski-Górecki
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=20200921175639.GP3221@work-vm \
--to=dgilbert@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=dovmurik@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=sstabellini@kernel.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 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).