Almost forgot about this one now. I think I brought this up on irc and
the outcome was rather not to touch Maverick as long as there is the
easy work-around of not using device names. So I just close this as
won't fix.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You re
Cool. Though I leave it open for a bit. Although Maverick may be oldish,
maybe we want to get the behaviour in line with later releases (if only
to make it simpler for people to convert). Not sure, but I'll update the
report with whatever comes out of it.
--
You received this bug notification bec
Yes, excellent call, and much thanks for your help. This now works:
# cat /etc/fstab
proc/proc procdefaults0 0
LABEL=MYROOT / ext3 defaults,errors=remount-ro,noatime0 1
UUID=b9f62618-9dff-4bb4-9f58-3c2c5a95625d none swap sw 0 0
# cat /boot/grub/menu
root=LABEL=myroot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/821466
Title:
Lucid kernel works on Rackspace cloud server, Maverick kernel does not
To manage notifications about this bug go to:
ht
Ah, ok. So pretty sure this is the result of one patch we carried for
EC2. This renames the block devices to sd* even in PV mode. This has
been dropped in Natty and maybe can be dropped in Maverick, too. Though
generally (since the device name has not been that stable in history),
if you can avoid
Stefan,
You asked for /proc/partitions and /proc/device after the broken boot.
There is no /proc/device, but:
(initramfs) cat /proc/partitions
major minor #blocks name
apport information
** Tags added: apport-collected
** Description changed:
I have a Rackspace cloud server which started its life as Lucid.
Recently, Rackspace offered to turn over control of the kernel to users
via pv-grub per
http://www.rackspace.com/knowledge_center/linux_kernel_manag
Hm, ok. I was asking because both the example of the grub config and the
attached dmesg were showing a -server kernel for 2.6.32. And yes, both
/proc/partitions and /proc/device would be interesting if possible in the
broken case.
At least (not familiar with the interfaces rackspace provides) a
On Wed, 10 Aug 2011 22:09:20 -
Stefan Bader wrote:
> Can you confirm that you are running a virtual kernel flavour? This is
> not immediately visible from the messages here. The difference would
> be that for -server the xen_blkfront driver is built as a module while
> -virtual got it built-i
Can you confirm that you are running a virtual kernel flavour? This is
not immediately visible from the messages here. The difference would be
that for -server the xen_blkfront driver is built as a module while
-virtual got it built-in. So when booting a -virtual kernel, you will
see no module load
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/821466
Title:
Lucid kernel works on Rackspace cloud server, Maverick kernel does not
To manage notifications about this bug go to:
https://bugs.launchpa
11 matches
Mail list logo
