lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: qemu-kvm (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I installed the 2.6.32-32 kernel in https://launchpad.net/~serge-
hallyn/+archive/kernel and I see the same kvm guest crashes on my AMD
Opteron host (the system in bug 799166) that I observed with the stock
2.6.32-32 kernel.
wmldev@1p19l3j:~/standard_tests/test1$ aptitude show
linux-image-2.6.32-
I have had the opportunity to try this issue on an Intel based machine
(I have attached the output of lshw). The issues does appear to be the
same on this environment. i only have access to this for 1 day but I
would be able to try alternative kernel if required.
Regards
Roy
** Attachment added:
Serge - I will try it in the next couple of days and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790789
Title:
KVM Guest freezing following Ubuntu update
To manage notifications abou
@Seb,
Did you try the 2.6.32-32 kernel in https://launchpad.net/~serge-
hallyn/+archive/kernel ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790789
Title:
KVM Guest freezing following Ubuntu upda
>From bug 799166:
Current prerelease kernel 2.6.32-33 doesn't fix this issue for me.
This issue is restricted to AMD processors.
Falling back to 2.6.32-31 is an alternative work-around.
For me, modifying the Linux command line in our guests is an undesirable
workaround and I will be using 2.6.3
** Changed in: qemu-kvm (Ubuntu Lucid)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790789
Title:
KVM Guest freezing following Ubuntu update
To manage notific
@Roy,
understandable. I'm going to mark this bug 'fix released' as I assume
it is not found in oneiric. I'll mark it as wontfix for lucid. The
explanation for that is that (a) it has an effective workaround, which
makes it low priority by definition, and (b) low priority bugs don't get
SRU'd.
Seb,
I am afraid I shied away from trying the kernel that Serge
suggested. This is my main (and only) machine and I did ot feel
sufficiently confident with backing out the alternate kernel. I have a
workaround for the problem by adding kernel parameters to instruct the
guest to use clock=a
Did the 2.6.32-33 kernel provided by Serge solve the issue?
I see this report is for an AMD machine; it might possibly be related to
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/799166 although
in that case there was no "kvm-clocksource has been installed" message
in the logs prior to a
Marking low priority since there is a workaround. Please mark 'new'
when results from the test are in.
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a memb
Quoting Royston Carter (790...@bugs.launchpad.net):
> Serge,
> I will try this if there is a method by which I can revert to the
> normal kernel and thereby the normal update cycle?
What I usually do is revert by using
'dpkg -i /var/cache/apt/archives/linux-image-YYY*' where
linux-
Serge,
I will try this if there is a method by which I can revert to the
normal kernel and thereby the normal update cycle?
Regards
Roy
On 01/06/2011 14:23, Serge Hallyn wrote:
> Quoting Royston Carter (790...@bugs.launchpad.net):
>> Serge,
>> I will do this if there is a foolproof w
Quoting Royston Carter (790...@bugs.launchpad.net):
> Serge,
> I will do this if there is a foolproof way of doing so. This is my
> main machine that runs a number of VM's so I would need to know there is
> a sure fire method of testing this new kernel. Happy to follow a
> reliable link.
Serge,
I will do this if there is a foolproof way of doing so. This is my
main machine that runs a number of VM's so I would need to know there is
a sure fire method of testing this new kernel. Happy to follow a
reliable link.
By the way, other guests seem OK. Trixbox is Centos 5.5 I
@Royston,
would you mind testing the kernel (once it builds, probably later
tonight or tomorrow morning) at https://launchpad.net/~serge-
hallyn/+archive/kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I wonder if this could be due to
c7801430c930f490a0aa54dbd63be10e0a466cf5 in ubuntu-lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790789
Title:
KVM Guest freezing following Ubuntu update
--
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790789
Title:
KVM Guest freezing following Ubuntu update
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
18 matches
Mail list logo
