** Tags added: kernel-stable-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100386
Title:
Raring server installations on VMs fail to reboot after the
installations
To manage notifications
FYI, this is still a problem in 13.04 release. I installed 13.04 amd64
server and could not get a login prompt. Adding 'nomodeset' works fine.
I imagine I could also use the 'vmvga' driver instead of 'cirrus'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
Raring server installations with both amd64 and i386 fail to reboot
normally after the installations on VMs. This occurs with both amd64 and
i386 images when installing VMs, (using libvirt and virt-manager and
also using VirtBox).
+
+ This appears to be a
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100386
Title:
Raring server installations on VMs fail to reboot after
I have managed to reproduce the apparent hangs, the recovery mode issues
I have not; if they still exist they should be filed under a different
bug.
For the apparent hangs, I have managed to confirm they are not hangs at
all. What has happened is that we have lost the console completely.
The
The hang started on images with kernel version of Ubuntu
3.7.0-6-generic. This could be reproduced on the raring server i386
image of 20121213 and later
The hang can not be seen with images that contain kernel version
3.7.0-5-generic and earlier. Tested with raring server i386 images of
20121212
** Description changed:
Raring server installations with both amd64 and i386 fail to reboot
normally after the installations on VMs. This occurs with both amd64 and
i386 images when installing VMs, (using libvirt and virt-manager and
also using VirtBox).
- 1. Install raring server on a
Preseed file for automatic installation using utah
** Attachment added: virtual-host.preseed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494533/+files/virtual-host.preseed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The .run file used to run the test using utah.
** Description changed:
Raring server installations with both amd64 and i386 fail to reboot
normally after the installations on VMs. This occurs with both amd64 and
i386 images when installing VMs, (using libvirt and virt-manager and
also
The preseed file
** Attachment added: virtual-host.preseed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494539/+files/virtual-host.preseed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Utah runlist
** Attachment added: virtual-host.run
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494544/+files/virtual-host.run
** Description changed:
Raring server installations with both amd64 and i386 fail to reboot
normally after the installations on
This is bug 1096531 - looks like a standard job is behaving slightly
differently under raring and exposing the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100386
Title:
Raring server
*** This bug is a duplicate of bug 1096531 ***
https://bugs.launchpad.net/bugs/1096531
** Tags removed: kernel-key
** This bug has been marked a duplicate of bug 1096531
After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed
--
You received this bug notification
*** This bug is a duplicate of bug 1096531 ***
https://bugs.launchpad.net/bugs/1096531
We think this may actually be modeset related. Is it possible to preseed
the installation (or change it for the failing installed VMs) to have
nomodeset on the grub commandline?
--
You received this bug
*** This bug is a duplicate of bug 1096531 ***
https://bugs.launchpad.net/bugs/1096531
So I installed an i386 server with nomodeset option selected and the
normal reboots are working fine ( although the recovery mode path I
tried out of curiosity still leads to the kernel panic) - The host is
** This bug is no longer a duplicate of bug 1096531
After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100386
Title:
Raring
This occurred during a virtual-host preseeded installation of amd64
raring server image. The VM hanged when booting normally and threw a
kernel panic when booting via recovery mode.
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-virtual-host/60/
is
** Summary changed:
- Raring server installations on KVM fail to reboot after the installations
+ Raring server installations on VMs fail to reboot after the installations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried with 20130117 image of i386 on VBox and the kernel panic occurred when
booting on recovery mode. Please see the attached screenshot.
On VBox the normal booting succeeds most of the time though as opposed to
almost never on virt-manager.
The contents of /var/log on the i386 server
Contents of /var/log/ in an i386 server installation on VBox
** Attachment added: i386_vbox_log.tar.gz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3486081/+files/i386_vbox_log.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Raring server installations with both amd64 and i386 fail to reboot
- normally after the installations on KVM. This occurs with both amd64 and
- i386 images when installing on KVM, (using libvirt and virt-manager).
+ normally after the installations on VMs. This occurs
21 matches
Mail list logo
