From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: aik@ozlabs.ru, pbonzini@redhat.com
Cc: amit.shah@redhat.com, kraxel@redhat.com, m.gibula@beyond.pl,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] Migration breakage from fe680d0 'exec: Limit translation limiting in address_space_translate to xen'
Date: Fri, 18 Jul 2014 19:05:28 +0100 [thread overview]
Message-ID: <20140718180527.GJ10517@work-vm> (raw)
In-Reply-To: <20140718173848.GF10517@work-vm>
Hi Alexey,
I've got a migration breakage that bisects back to fe680d0
'exec: Limit translation limiting in address_space_translate to xen'
I'm told this is unlikely, but it seems to be reliably reproducable
and if I comment out the 'xen_enabled() &&' it all works fine.
Test system:
x86-64 i7-3520M fedora 20
Test case:
It's a script from Kraxel that boots a guest with a live CD
and bounces it back and forward with a running VNC.
(Annoyingly every other test I've got doesn't seem to hit this;
virt-test, google stress app test - all happy).
Failure:
I'm seeing squashfs errors and then random app failures.
The command line is:
try/bin/qemu-system-x86_64 -m 2G -smp 2 -name migrate-loop -nodefaults -enable-kvm -boot menu=on -vga std -vnc localhost:6448 -drive if=none,id=live,readonly,media=cdrom,file=/home/vmimages/Fedora-Live-Desktop-x86_64-20-1.iso -drive if=none,id=disk,format=raw,cache=none,aio=native,file=/home/dgilbert/tmp/kraxel/migrate-loop.img -chardev socket,id=mon,path=/tmp/migrate-loop-12326/mon-12348-23459,server,nowait -mon chardev=mon -serial stdio -net user,bootfile=http://192.168.2.14/tftpboot/pxelinux.0 -net nic,model=virtio -device ide-hd,bus=ide.0,drive=disk,bootindex=1 -device ide-cd,bus=ide.1,drive=live,bootindex=2 -device AC97 -incoming tcp:0:23459
(Resend, I forgot to cc the list)
Dave (who is on holiday next week)
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
parent reply other threads:[~2014-07-18 18:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20140718173848.GF10517@work-vm>]
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=20140718180527.GJ10517@work-vm \
--to=dgilbert@redhat.com \
--cc=aik@ozlabs.ru \
--cc=amit.shah@redhat.com \
--cc=kraxel@redhat.com \
--cc=m.gibula@beyond.pl \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).