Hallo Dustin,
i reported this bug too for Hardy. Its gone with karmic.
Reagrds, Kurt
Am 02.03.2010 00:36, schrieb Dustin Kirkland:
> Daniel-
>
> You opened this bug... Have you experienced this problem on Lucid (or
> Karmic) or any time recently?
>
> Thierry-
>
> You originally confirmed it. C
Sorry, read a bit further down and I see that both Thierry and Daniel
are reporting Success with recent Ubuntu. Closing for now. Please
reopen if this is still an issue. Thanks!
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: qemu
Status: Confirm
Daniel-
You opened this bug... Have you experienced this problem on Lucid (or
Karmic) or any time recently?
Thierry-
You originally confirmed it. Can you confirm it again against Lucid?
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/
I'm unassigning myself this bug, as I haven't found the time to fix it,
and I personally haven't hit this bug in a very long time. Leaving the
bug open, and I would be happy to review/sponsor/upload a fix if someone
else submits a patch.
** Changed in: qemu-kvm (Ubuntu Jaunty)
Assignee: Dust
** Package changed: kvm (Ubuntu) => qemu-kvm (Ubuntu)
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I am marking this as 'confirmed' as I can reproduce the problem with the
latest qemu-kvm package. Turning off cpu frequency scaling is a valid
workaround for me, but the clock on the guests drift a lot whenever I
forget to change the governor.
$ LANG=C apt-cache policy qemu-kvm
qemu-kvm:
Install
** Tags added: iso-testing
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Thanks, Daniel.
Thierry, I'm marking 'fix released'. Please reopen with 'confirmed', if
you can reproduce this on the latest Karmic qemu-kvm.
:-Dustin
** Changed in: kvm (Ubuntu)
Status: Incomplete => Fix Released
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues
AFAICT it's all good now.
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
My recent karmic ISO testings (using default kernel parameters) didn't
hang... I'll disable no-kvmclock in my guests and let you know if I can
reproduce it with current qemu-kvm.
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You r
Thierry, Daniel, can you reproduce this?
:-Dustin
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Changed in: kvm (Ubuntu)
Importance: High => Medium
** Changed in: kvm (Ubuntu)
Importance: Medium => Low
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a member of Ubunt
Can anyone reproduce this problem in karmic's qemu-kvm-0.11? Marking
incomplete. Please confirm if you still experience this issue there.
I'm marking won't fix against Jaunty. I don't think this rises to SRU,
since there are multiple workarounds.
:-Dustin
** Changed in: kvm (Ubuntu)
St
On Wed, Jun 24, 2009 at 10:38 AM, Anthony Liguori wrote:
> Assuming it worked? Potentially greater time drift in the guest.
Can that be helped with NTP in the guest?
:-Dustin
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You re
Dustin Kirkland wrote:
> On Tue, Jun 23, 2009 at 7:30 PM, Anthony Liguori wrote:
>
>> If no-kvmclock helps, it's possible to disable this in the host kernel.
>>
>
> Anthony-
>
> What's the downside of no-kvmclock, if we decided to make this a
> default in the Ubuntu server kernel?
>
> :-Dus
http://patchwork.kernel.org/patch/19007/
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
On Tue, Jun 23, 2009 at 7:30 PM, Anthony Liguori wrote:
> If no-kvmclock helps, it's possible to disable this in the host kernel.
Anthony-
What's the downside of no-kvmclock, if we decided to make this a
default in the Ubuntu server kernel?
:-Dustin
--
guest needs to boot with clock=acpi_pm (o
If no-kvmclock helps, it's possible to disable this in the host kernel.
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thierry-
Yes, I agree (as I'm the owner of 4+ effected AMD cpu's on which I
don't want to lose frequency scaling)...
:-Dustin
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you are a mem
\o/ cpu family : 15
FYI running with no-kvmclock (as suggested by Anthony in comment 2) also seems
to work around the issue.
Dustin: running guests with clocksource=acpi_pm is also a valid solution
for those who don't want to throw out freqscaling completely (I am one
of those), so I suggest the
** Summary changed:
- guest needs to boot with clock=acpi_pm
+ guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
--
guest needs to boot with clock=acpi_pm (older AMD freq scaling issues)
https://bugs.launchpad.net/bugs/361754
You received this bug notification because you ar
21 matches
Mail list logo
