On Sat, Mar 27, 2010 at 11:56:25AM +0100, Josip Rodin wrote: > If I try to boot 2.6.32-4-xen-amd64 on a 2.6.26-2-xen-amd64 (lenny) dom0, > it gets stuck at:
What was the last known working version? > [ 0.120653] XENBUS: Device with no driver: device/vbd/769 > [ 0.120658] XENBUS: Device with no driver: device/vif/0 > [ 0.120663] XENBUS: Device with no driver: device/console/0 > [ 0.120679] > /build/mattems-linux-2.6_2.6.32-10-amd64-Ff7Wwa/linux-2.6-2.6.32-10/debian/build/source_amd64_xen/drivers/rtc/hctosys.c: > unable to open rtc device (rtc0) > [ 0.120822] Freeing unused kernel memory: 588k freed > [ 0.121088] Write protecting the kernel read-only data: 4264k > Loading, please wait... > Begin: Loading essential drivers ... done. > Begin: Running /scripts/init-premount ... FATAL: Error inserting fan > (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/fan.ko): No such device > FATAL: Error inserting thermal > (/lib/modules/2.6.32-4-xen-amd64/kernel/drivers/acpi/thermal.ko): No such > device > [ 0.610445] blkfront: xvda1: barriers enabled > done. > Begin: Mounting root file system ... Begin: Running /scripts/local-top ... > done. > Begin: Waiting for root file system ... You are supposed to provide the complete log. There are several possible pitfalls. If you are upgrading from an old-style image and followed old documentation it is most likely a wrong root device. > Can anything be done? I thought the domUs were supposed to be a safe > upgrade? It is: | $ cat /sys/hypervisor/type | xen | $ cat /proc/version | Linux version 2.6.32-4-amd64 (Debian 2.6.32-10) ([email protected]) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Mar 17 03:23:53 UTC 2010 Bastian -- Only a fool fights in a burning house. -- Kank the Klingon, "Day of the Dove", stardate unknown -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
