There are other open bugs for qemu+cirrus, so I will close this one for
qemu to mirror the linux status.
** No longer affects: qemu-kvm (Ubuntu Quantal)
** No longer affects: qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Closing Fix Released per comments #24 and #26. Thanks.
** Changed in: linux (Ubuntu Quantal)
Status: Incomplete = Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Sorry for the delay. I tried this with quantal-latest (host) on the
quantal-server-amd64 release iso and everything worked fine without
having to specify vga
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
I had seen this issue alot with automated iscsi root testing so had
switched to using the vga qemu-kvm option; I just switched back and did
some installs and a load of reboots and I can't reproduce this issue any
longer on latest quantal images.
--
You received this bug notification because you
@Paul,
Can you also confirm this bug no longer exists in the latest quantal
images? If so, please mark this bug as Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
@Paul, were you able to test the kernel mentioned in comment #22 ? The
3.5.0-17 kernel is now available as well.
** Changed in: linux (Ubuntu Quantal)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: linux (Ubuntu Quantal)
Importance: Medium
Status: Confirmed
** Also affects: qemu-kvm (Ubuntu Quantal)
Importance: Medium
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm
It might be worth re-testing with the 3.5.0-16.24 kernel once it lands
in the quantal release pocket, it's currently sitting in quantal-
proposed. It disables the cirrus driver as it was causing issues on
other systems as well. See the following for more information. Thanks.
Quoting Joseph Salisbury (joseph.salisb...@canonical.com):
Thanks, Serge. It would be good to know if the bug goes away if you
boot the precise kernel in the quantal vm. That will tell us if this is
a regression. If it is, we can perform a kernel bisect to identify the
commit in Quantal
Not likely to happen this week, as I'm swamped with beta2 stuff at the
moment, but I'll try to get to it as soon as I can
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1054129
Thanks, Serge. It would be good to know if the bug goes away if you
boot the precise kernel in the quantal vm. That will tell us if this is
a regression. If it is, we can perform a kernel bisect to identify the
commit in Quantal that introduced the regression.
--
You received this bug
Quoting Paul Larson (paul.lar...@canonical.com):
Not sure what you mean... I basically worked around the issue long
I assume he meant install the precise kernel in the quantal vm?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
apport information
** Tags added: apport-collected quantal
** Description changed:
plars discovered that after doing do-release-upgrade -d from a precise
server image can result in what appears to be a frozen system. Input to
the console works fine (you can log in and do things, and you
I'd like to complement the launchpad and apport folks for greatly
improving the command-line-server usage of apport-collect (since lucid
times).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
The above information is collect using apport in the qemu-kvm quantal
guest.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1054129
Title:
reboot with -vga cirrus can result in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.6 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
Once you've tested the
I'm still able to reproduce this problem after updating to the kernel at
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc6-quantal/
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: needs-upstream-testing
--
You received this bug notification because
Does this issue go away if you boot into the kernel prior to the
upgrade?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1054129
Title:
reboot with -vga cirrus can result in
Not sure what you mean... I basically worked around the issue long
enough to do the upgrade by booting with -vga std, upgraded to the new
upstream kernel, rebooted to make sure the new kernel works with -vga
std, then rebooted without -vga std and was able to reproduce it.
--
You received this
20 matches
Mail list logo
