*** This bug is a duplicate of bug 361754 ***
https://bugs.launchpad.net/bugs/361754
The error "vcpu not ready for apic_round_robin" can also occur if a
guest is timing out for other reasons...like not enough RAM allocated. I
have examples of this occuring on a hardy 8.04 LTS system with KVM
*** This bug is a duplicate of bug 361754 ***
https://bugs.launchpad.net/bugs/361754
Parag,
Can you open a separate bug report for the error you saw on the Intel
system. An Intel processor would not suffer from this particular bug.
--
cpu frequency scaling causes multiple vcpu guests to pa
*** This bug is a duplicate of bug 361754 ***
https://bugs.launchpad.net/bugs/361754
** This bug has been marked a duplicate of bug 361754
guest needs to boot with clock=acpi_pm
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You receiv
Can someone give me some pointers?
- I would like to test different scaling governors, but due to bug 351159 this
is impossible. Is this important?
- How can I see the kvm version? (What's the version of kvm in kvm-source, and
if they are both installed, what version is in use?) It looks like th
Tried with 1 vcpu instead of 2. Same error (vcpu not ready for
apic_round_robin)
Is there someting else I can try without installing other packages?
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You received this bug notification because you
I no longer think the CPU model is relevant to this bug. I just copied
the virtual machine to another host. (Intel(R) Xeon(R) CPU E5335 @
2.00GHz). It didn't take long to panic.
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You received this
Just adding a different CPU to this bug:
$ sudo lshw -class cpu
*-cpu:0
description: CPU
product: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz
vendor: Intel Corp.
physical id: 4
bus info: c...@0
version: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz
That sounds like a good plan. If this is a solution to this bug I
suspect it's worth considering whether kvm should depend on kvm-source
instead of just suggesting it.
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You received this bug notif
agent-
Excellent! I'm going to leave the bug 'incomplete' for now, awaiting
feedback from in say, a week?
:-Dustin
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You received this bug notification because you are a member of Ubuntu
Bugs, w
Thanks Dustin, I'd say that's looking positive. I used kvm-source,
reloaded the modules, and switched the scaling governor to ondemand
(none of which required a reboot so it should be easy for others to test
as well). Before it was extremely rare for a virtual machine to make it
through boot. So
parag & agent 8131-
Could you perhaps try the kvm-source built modules, if you aren't
already?
If this is fixed in the upstream kernel, there's a good chance it's
fixed in the kvm-source built module, as it's quite a bit more modern
than the source in the Ubuntu jaunty kernel.
:-Dustin
--
cpu
This is a kernel panic I've seen at startup. I assume it's related to
this issue but it could be another bug. I've seen lots of errors using
libvirt and kvm under jaunty that make me think there might be multiple
bugs that need addressing before it can be considered ready for use.
** Attachment
Crashing randomly = kernel panics. My apologies for not being more
specific. I could turn frequency scaling back on to get the specific
messages if you think that would help.
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You received this b
Describe "crashing randomly"...
Is the guest kernel oopsing or panicing?
Is kvm on the host simply seg faulting?
I need a bit more information here to go on.
:-Dustin
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You received this bug not
I believe I have just run into this bug. I figured now that 9.04 has
entered RC status I would upgrade a test server to figure out what
problems I would run into if and when upgrading. All of my domains only
had 1 VPCU so I don't think that is an issue. The problem is frequency
scaling. When fr
Interesting, thanks for the report...
I'm going to keep my finger on the pulse of this.
I'm seeing some strange behavior on my Jaunty systems, when
cpu-freq-scaling is enabled. I'm still trying to nail it down ...
:-Dustin
--
cpu frequency scaling causes multiple vcpu guests to panic
https://
Mainline kernel 2.6.29 does not seem to have this problem - same VM runs
ok on 2.6.29 while it gets stuck with the "vcpu not ready for
apic_round_robin" error.
BTW, I am not using multiple VCPUs - single cpu Intrepid x86 vm.
--
cpu frequency scaling causes multiple vcpu guests to panic
https://
This happens to me with Jaunty on an Intel Xeon CPU - have never seen it before
with Intrepid kernel.
/proc/cpuinfo :
processor : 0
vendor_id : GenuineIntel
Hi,
Can you post the output of:
$ cat /proc/cpuinfo
$ lshw -class cpu
We think that your processor is an AMD rev F, which don't have a
constant tfc frequency, and guests can't see that the host processor
frequency has changed. This would be a hardware problem, not a software
problem.
:-Dustin
** Changed in: kvm (Ubuntu)
Importance: Undecided => Medium
--
cpu frequency scaling causes multiple vcpu guests to panic
https://bugs.launchpad.net/bugs/246175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
20 matches
Mail list logo
