Hi,
If I understood correctly your guest dom boot's up until some point were
you get the error:
find: /lib/firmware/2.6.18-xen : No such file or directory
If this is the error you have to:
-shutdown the guest dom;
-mount the lvm partition on to a folder on the dom0, and then copy from
dom0 the /lib/firmware/"2.6.18-xen" directory to
/mounted_lvm/lib/firmware/"2.6.18-xen"
-umount the partition, and everthing should be ok know.
Best regards.
>> Hello,
>>
>> vgchange -a y
>>
>> works good - the 4 currently allocated volumes are found and than
>> also can be found in /dev/mapper/ folder.
>> In initramfs scripts I rallz doid not find anz scripts which would
>> initiate the lvm. Is this a bug of initramfs from Ubuntu?
>> The update of the ramfs brings nothing new - the error is still the
>> same. But one thing is interesting, after I start update-initramfs, there
>> comes more times the error message:
>>
>> find: /lib/firmware/2.6.18-xen : No such file or directory
>>
>> - could this mean something from Your point of view? The same
>> messages came also at the time I have created the first ramfs.
>> Do You have any idea what to do now? Is there any other tool for the
>> creation of the ramfs which could be used? In the previous version I used
>> yaird, but with Ubuntu 7.04 it reports some strange errors...
>>
>> Thank You very much for Your help, Diky Vladimire :-)
>>
>> Archie
>>
>> -----Original Message-----
>> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Vladislav Kurz
>> Sent: Wednesday, May 30, 2007 5:20 PM
>> To: xen-users@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM,which
>> is on RAID
>>
>> On Wednesday 30 May 2007 16:44, Artur Linhart - Linux communication wrote:
>>> Hello,
>>>
>>> Thanks for response :-)
>>>
>>> I verified the kernel configurations, they are different - sure - but in
>>> the area of the MD/LVM this is very similar (the only difference is, the
>>> Xen kernel has for CONFIG_BLK_DEV_MD the value "y", by the Ubuntu
>>> default
>>> kernel it is the value "m"), so it's looks for me like this is rather
>>> not
>>> the problem I have... Or what do You think?
>>
>> I think this should not be a problem.
>>
>>> In the /dev/mapper directory is only 1 character device with the name
>>> "control"
>>> After the system comes in the state described below, there is such a "
>>> prompt"
>>> (initramfs)
>>> And the cursor is blinking there, I can use some shell commands of the
>> xen.
>>> If I start lvm, I can by lvdisplay, vgdisplay, pvdisplay see the given
>>> entities like I have defined it and used in Ubuntu direct, but that is
>>> all
>>> - it looks like the device in /dev/mapper just would not be created and
>>> I
>>> do not have any Idea why or what should I do...
>>
>> Try this (in initramfs shell):
>>
>> vgchange -a y
>>
>> this should bring up all volume groups
>>
>> It seems that there is no script to bring up lvm in your initrd. Check the
>> contents of /script (in initramfs) or /usr/share/initramfs-tools/scripts
>> if
>> there is a script "lvm". Maybe regenerating the initrd might help. Try
>> this
>> (on normally booted system):
>>
>> update-initramfs -u -k 2.6.18-xen
>>
>> (At least this should work on debian, I expect ubuntu to be similar)
>>
>> --
>> Regards
>> Vladislav Kurz
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
>> __________ Informace od NOD32 2298 (20070530) __________
>>
>> Tato zprava byla proverena antivirovym systemem NOD32.
>> http://www.nod32.cz
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home