From: "Daniel P. Berrange" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Ashijeet Acharya <ashijeetacharya@gmail.com>,
Juan Quintela <quintela@redhat.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] migration: QEMU aborts migration of "none" machine
Date: Wed, 25 Jan 2017 11:07:15 +0000 [thread overview]
Message-ID: <20170125110715.GB15529@redhat.com> (raw)
In-Reply-To: <c5202aa1-bf56-5d66-533a-a1e78a3eafa2@redhat.com>
On Wed, Jan 25, 2017 at 11:53:06AM +0100, Thomas Huth wrote:
> On 25.01.2017 11:01, Ashijeet Acharya wrote:
> > Hi Thomas,
> >
> > I was able to reproduce the bug you encountered while trying to migrate
> > a "none" machine.
> >
> > After digging deep and debugging the problem with gdb, I found that
> > bitmap_new() is the function that crashes qemu as it always has
> > zero bits being passed to it.
> >
> > I had a discussion with Dave on the IRC yesterday and he suggested the
> > reason of crash being the absence of RAM ( since machine is "none")
> > while attempting the migration.
> >
> > I am not sure what the ideal solution will be in this case; Do any of
> > the maintainers have any suggestions or even a starting point which I
> > can ponder upon?
>
> I'm not that familiar with the migration code either, but maybe you
> could simply check for last_ram_offset() == 0 at the beginning of
> ram_save_setup() and return with an error in that case?
Do we actually need/want migration to succeed when RAM is 0 or vCPU
count is 0 ? If not, then we could just register a migration blocker
during machine init
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2017-01-25 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 10:01 [Qemu-devel] migration: QEMU aborts migration of "none" machine Ashijeet Acharya
2017-01-25 10:53 ` Thomas Huth
2017-01-25 11:07 ` Daniel P. Berrange [this message]
2017-01-25 11:16 ` Juan Quintela
2017-01-25 12:58 ` Ashijeet Acharya
2017-01-25 16:10 ` Thomas Huth
2017-01-25 16:34 ` Ashijeet Acharya
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=20170125110715.GB15529@redhat.com \
--to=berrange@redhat.com \
--cc=ashijeetacharya@gmail.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.com \
/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.