* Marcus (shadow...@gmail.com) wrote:
Dang, I was hoping some ground was being made on this.
Can you answer the same questions I asked Marcin?
What's the latest version of QEMU you've seen this on, what CPU are you
using, what guest OS and what's your QEMU command line?
Dave
On Wed, Apr 2,
I can answer some of the questions. It's been 3 months or so since I
looked into it. I ended up disabling kvmclock from the qemu command
line and moving on. I saw it with CentOS 6.5 and Ubuntu 12.04 guests.
Sending the guest to the BIOS CLI or PXE would not reproduce the
issue. I didn't attempt an
* Marcus (shadow...@gmail.com) wrote:
I can answer some of the questions. It's been 3 months or so since I
looked into it. I ended up disabling kvmclock from the qemu command
line and moving on. I saw it with CentOS 6.5 and Ubuntu 12.04 guests.
Sending the guest to the BIOS CLI or PXE would
On 04/15/2014 02:53 PM, Dr. David Alan Gilbert wrote:
* Marcus (shadow...@gmail.com) wrote:
snip
As mentioned by others, the mode of reproduction is to launch the vm,
wait about an hour, and then try to migrate it
Here's are example qemu command lines (as generated from libvirt with
the
W dniu 2014-04-15 20:53, Dr. David Alan Gilbert pisze:
* Marcus (shadow...@gmail.com) wrote:
I can answer some of the questions. It's been 3 months or so since I
looked into it. I ended up disabling kvmclock from the qemu command
line and moving on. I saw it with CentOS 6.5 and Ubuntu 12.04
Dang, I was hoping some ground was being made on this.
On Wed, Apr 2, 2014 at 11:05 AM, Marcin Gibuła m.gib...@beyond.pl wrote:
Yes, that's where it gets weird. I've never seen this on fresh VM.
It needs to be idle for couple of hours at least. And even then it
doesn't always hang.
So your
It's looking good so far, after a few migrations (it takes a while to test
because I'm waiting at least 5 hours between migrations). I'll be happier
once I've done a couple of weeks of this without any failures!
Does anyone have any hints how to debug this thing? :(
I've tried to put hanged
* Marcin Gibu??a (m.gib...@beyond.pl) wrote:
It's looking good so far, after a few migrations (it takes a while to test
because I'm waiting at least 5 hours between migrations). I'll be happier
once I've done a couple of weeks of this without any failures!
Does anyone have any hints how to
Can you give:
1) A backtrace from the guest
thread apply all bt full
in gdb
You mean from gdb attached to hanged guest? I'll try to get it. From
what I remember it looks rather normal - busy executing guest code.
2) What's the earliest/newest qemu versions you've seen this
* Marcin Gibu??a (m.gib...@beyond.pl) wrote:
Can you give:
1) A backtrace from the guest
thread apply all bt full
in gdb
You mean from gdb attached to hanged guest? I'll try to get it. From
what I remember it looks rather normal - busy executing guest
code.
yes; if you can
On 02.04.2014 11:39, Dr. David Alan Gilbert wrote:
* Marcin Gibu??a (m.gib...@beyond.pl) wrote:
Can you give:
1) A backtrace from the guest
thread apply all bt full
in gdb
You mean from gdb attached to hanged guest? I'll try to get it. From
what I remember it looks rather
Yes, that's where it gets weird. I've never seen this on fresh VM.
It needs to be idle for couple of hours at least. And even then it
doesn't always hang.
So your OS is just sitting at a text console, running nothing special?
When you reboot after the migration what's the last thing you see
in
On Mon, Mar 31, 2014 at 10:39:47AM +0200, Marcin Gibuła wrote:
I've seen very similar problem on our installation. Have you tried to
run with kvm-clock explicitly disabled (either via no-kvmclock in
guest kernel or with -kvm-clock in qemu) ?
No, I haven't tried it yet (I've confirmed
I've seen very similar problem on our installation. Have you tried to
run with kvm-clock explicitly disabled (either via no-kvmclock in
guest kernel or with -kvm-clock in qemu) ?
No, I haven't tried it yet (I've confirmed kvm-clock is currently
being used). I'll have a look at it.
Did it help
Hi,
I have a problem where I migrate a linux guest VM, and on the
receiving side the guest goes to 100% cpu as seen by the host, and
the guest itself is unresponsive, e.g. not responding to ping etc.
The only way out I've found is to destroy the guest.
This seems to only happen if the guest has
W dniu 2014-03-27 23:52, Chris Dunlop pisze:
Hi,
I have a problem where I migrate a linux guest VM, and on the
receiving side the guest goes to 100% cpu as seen by the host, and
the guest itself is unresponsive, e.g. not responding to ping etc.
The only way out I've found is to destroy the
On Fri, Mar 28, 2014 at 12:29:18AM +0100, Marcin Gibuła wrote:
W dniu 2014-03-27 23:52, Chris Dunlop pisze:
Hi,
I have a problem where I migrate a linux guest VM, and on the
receiving side the guest goes to 100% cpu as seen by the host, and
the guest itself is unresponsive, e.g. not
17 matches
Mail list logo
