| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] debian Lenny -> Squeeze domU mdX software raid migration
Yes, my whatever.domain.cfg was insane, I fixed it by leaving:
root = /dev/xvda2
but had to update:
#kernel = '/boot/vmlinuz-2.6.26-1-xen-amd64'
#ramdisk = '/boot/initrd.img-2.6.26-1-xen-amd64'
kernel = '/boot/vmlinuz-2.6.32-5-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.32-5-xen-amd64'
after that it booted with errors, but allowed me to
vi /etc/apt/sources.lists in DomU and change lenny to squeeze and then
update/upgrade, and now my DomU Debian Lenny is Squeeze :)
No idea why the kernel mismatch would result in an md/sd/xvd error, but
hope this helps someone else!
Thx,
Cameron
On Wed, 2011-05-04 at 03:11 +1000, Joseph Glanville wrote:
> Hi Cameron
>
>
> Can you please post your domU xen configuration file, also at the
> initramfs prompt can you type and post output of:
> cat /proc/cmdline
>
>
> I think you have incorrectly configured the target of the root disk.
>
>
> Kind regards.
> Joseph.
>
> On 3 May 2011 03:12, Cameron Camp <cameron@xxxxxxxxxxxxx> wrote:
> I got the previous migration with standard /dev/sdX Dom0 to
> work by
> changing
>
> /dev/sda2
>
> to
>
> /dev/xvda2
>
> in /etc/xen/whatever.domain.com.cfg
>
> but now I'm migrating Lenny DomU VM to a Squeeze Dom0 which
> uses
> software raid filesystem like:
>
> /dev/md2
>
> but DomU
> uses /dev/sda2 /home/xen/domains/whatever.domain.com/disk.img
> still, and won't see the proper hdd, I get:
>
> mount: mounting none on /dev failed: No such device
> W: devtmpfs not available, falling back to tmpfs for /dev
> Couldnt get a file descriptor referring to the console
> KDGKBMODE: Bad file descriptor
> loadkeys: error reading keyboard mode
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin:
> Running /scripts/local-top ... Begin: Loading[ 1.304655]
> md: raid1
> personality registered for level 1
> Success: loaded module raid1.
> done.
> Begin: Assembling all MD arrays ... Failure: failed to
> assemble all
> arrays.
> done.
> done.
> Begin: Waiting for root file system ... done.
> Gave up waiting for root device. Common problems:
> - Boot args (cat /proc/cmdline)
> - Check rootdelay= (did the system wait long enough?)
> - Check root= (did the system wait for the right device?)
> - Missing modules (cat /proc/modules; ls /dev)
> ALERT! /dev/xvda2 does not exist. Dropping to a shell!
>
>
> BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /bin/sh: can't access tty; job control turned off
> (initramfs)
> =================================
> it seems like I somehow don't have the right "driver" loading
> in DomU to
> see Dom0 md2 filesystem, but couldn't find anything
> in /boot/whatever
> (or even /boot) in DomU where I could pass an argument to load
> whatever,
> is there something in the whatever.domain.com.cfg I can set to
> specify
> md2 on Dom0 filesystem to be recognized by DomU?
>
> Thanks,
> Cameron
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
>
> --
> Kind regards,
> Joseph.
>
>
> Founder | Director
>
> Orion Virtualisation Solutions | www.orionvm.com.au | Phone: 1300 56
> 99 52 | Mobile: 0428 754 846
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home