I found a solution that worked in my upgrade. I spent the weekend upgrading:
7.04 -- 7.10 -- 8.04 -- 10.04 (Yes it was quite the adventure!)
I saw a few messages about using the old menu.lst file during the final
upgrade to 10.04 with no
options other than keeping the old file as I recall.
Here are the promis
Thanks go to Bryce Harrington in comment #3 for giving a way around this
but it would be good if I could find a permanent way around this. Lucky
me for using a PS/2 keyboard ;-)
uname -a gives:
Linux klimrek 2.6.24-27-server #1 SMP Wed Mar 24 10:39:18 UTC 2010 i686
GNU/Linux
Dear me, that is the cause of my problem: I'm still running a kernel
that is not upstart friendly: 2.6.24-27-server But I cannot use the new
kernels as they hang during boot. (Even the 386 version, as opposed to
x86) The saga continues, will keep you posted, if I may.
--
After upgrade from
I encounter the same problem when I upgrade my Hardy to Lucid on my
(bare hardware) AMD Athlon. Will try to add more details later.
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification because you are a member
Same problem here. If the newer kernel is required, then why isn't it a
dependency when going from Hardy - Lucid?
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification because you are a member of Ubuntu
Bugs,
I found a way getting a working 10.04 domU with a hardy dom0.
I used this howto: http://www.agileweboperations.com/xen-debian-lenny-
dom0-with-ubuntu-lucid-guest/
The only differences I did in my $DOMU.cfg. This is my config:
bootloader=/usr/bin/pygrub
#kernel =
I am having the same problem, i am not using any virtualization, I
upgraded from 8.04 to 10.04 and now can start my machine. I get error
libudev: udev_monitor_new_from_netlink: error getting socket: Invalid
argument segfault
and after that my USB keyboard also doesn't work.
--
After upgrade
I am having the exact same problem as Steve Deery. However, it's much
worse for me, because as soon as it can't find udev, my USB keyboard is
rendered useless. No big deal? Well, it's a Dell PowerEdge 1950 and
the only port it supports for the keyboard is USB. urg, so now I can't
get into the
Canonical doesn't make it easy for one to stand behind them, if again
and again you get a Knife in your back.
Upstart is not a solution aimed at Servers, hence it should be removed
from the serveredition. It renders it totally unusable in Virtualized
environments, where more dependencies exist..
I have upgraded from 8.04 to 10.04, I had a problem with ureadahead: init:
ureadahead main process (2603) terminated with status 5
libudev: udev_monitor_new_from_netlink: error getting socket:Invalid argument.
Mountall: mountall.c:3204: Assertion failed in main: udev_monitor =
There are quite a number of people on the Ubuntu Forums reporting the
same problem but no solution yet. I have been informed that my problem
is a duplicate of this bug. Can anyone point me in the right direction,
I am keen to gather more info if someone will tell me how. I don't have
a VM running
Steven, can you explain what you did to get it working? I'd like to
replicate it if possible.
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ive hit the same issue upgrading an Ubuntu 8.04 Xen VM to Lucid 10.04.
The host is running Centos 5.3 and I have a mix of Centos, Debian and
Ubuntu VMs. The Debian VMs upgraded to Lenny without incident but It
appears I can't run a paravirt Lucid VM on top of Centos.
If I try to boot with a
Ok upgrading the Xen VM didn't install a Xen compatible kernel and it
reverted to older 8.04 kernels.
Install linux-image-virtual and I'm now up and working
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification
dear scott, can you please explain to my xen hosting provider why they
need to upgrade their stable dom0 in order to support ubuntu with new
domu kernels? their e-mail is ad...@funkfeuer.at
I have just replaced upstart, mountall, ureadahead, plymouth,... by a
very simple script that does what
Hi, just ran into this myself. Upgraded a vm on a Lenny dom0 from hardy
to lucid. I only have paravirtualization at my disposal (4 servers, none
with hvm support). Does this mean I'm out of luck and need to use an
older release when running Ubuntu in a paravirtualized situation? Also,
I read
Ubuntu 10.04, sorry =)
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
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.ubuntu.com
I do not think this was a request to support an older kernel, I think
this is a request to examine the possibility of using Ubuntu 10.05 with
bare metal virtualization technologies such as Xen, Openvz, Vserver,
etc. I believe there is an interest in using Ubuntu at least as a guest
OS if not on
On Thu, 2010-04-22 at 14:55 +, bodhi.zazen wrote:
I do not think this was a request to support an older kernel, I think
this is a request to examine the possibility of using Ubuntu 10.05 with
bare metal virtualization technologies such as Xen, Openvz, Vserver,
etc. I believe there is an
Ubuntu works just fine in such virtualisation environments, provided the
host and guest are using the correct kernel versions.
Well, that means that Lucid will be a whole lot less relevant on the
server side than previous Ubuntu versions.
I'm sure you know that Xen is still not fully
On Thu, 2010-04-22 at 18:59 +, ward wrote:
What kernel version is required, actually? Is it really *that*
impossible to fix this mountall call?
2.6.32 is required; it's not just mountall, there are dependencies on
this kernel version in upstart, mountall, ureadahead, udev, plymouth, X,
Sorry, we simply do not support earlier kernel versions. The plumbing
layer is now tightly integrated with the kernel; we had an option to
either support kernel upgrades or downgrades, we chose to support
upgrades since updating a kernel is common
** Changed in: mountall (Ubuntu)
Status:
Yup. Real problem!
Especially in virtualized environments.
I'd love to test fixes!
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I second that this is a real problem.
Anyone running Lucid on a virtualized system, as a guest, will run into
this if their hypervisor runs a kernel that's a little older.
Say, Debian Lenny on the bare metal with its 2.6.26-xen kernel, and a
Lucid domU.
Can we please get a fix in for this
I ran into this as well. I think it actually is a legitimate issue
because if you run into a problem with the lucid kernel, it is entirely
sensible that you'd want to boot an earlier kernel version and have it
work. I ran into this in a Hardy - Lucid upgrade.
You can workaround it by issuing
With latest kernel this problem dissapears. Please close this.
** Changed in: mountall (Ubuntu)
Status: New = Invalid
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification because you are a member of
Forgot to mention not im running 2.6.18-3-686 because im not able to
boot with -27 included in lucid, the boot stops with a loading bar and
stays there.
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification
27 matches
Mail list logo
