On Fri, Jan 14, 2011 at 3:44 PM, GNUbie <gnubie@xxxxxxxxx> wrote:
> Hello Fajar,
> On Fri, Jan 14, 2011 at 3:47 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
>> Let me make this reaaaaaaly simple. You were able to captrure boot
>> log. That's good.
>> Your previous boot log shows these
>> [ 0.071713] XENBUS: Device with no driver: device/vbd/2050
>> [ 0.071718] XENBUS: Device with no driver: device/vbd/2064
>> [ 0.071722] XENBUS: Device with no driver: device/vbd/2051
>> whish should roughly mean you have three block devices on that domU.
>> Do you know what they are? If not, you need to find out (whether from
>> domU config file, some kind of Amazon EC2 config page, ask Amazon
>> support, whatever).
> Maybe that 3 block devices were from its original domU where
> previously (from where this domU came from), it comes with the
> following partitions:
> /dev/xvda1 => /
> /dev/xvda2 => /media/ephemeral0
> /dev/xvda3 => SWAP
There's no xvda1 detected on your boot log.
Find out what your actual disk mappings are (again, whether from domU
config file, some kind of Amazon EC2 config page, ask Amazon support,
whatever). Don't bother doing anything else unless you ABSOLUTELY know
what your disk mappings are.
> When you say "boot device", are you referring to the whole / or just
> the /boot? As I mentioned on my previous message that the /dev/xvda1
> or /dev/xvda contains the entire / filesystem including the /boot.
Since the fdisk output you show earlier show / and /boot on the same
disk, then simply assign that disk as xvda. Start from there. Don't
bother doing anything else unless you've succesfully done that (and
the boot log actually shows xvda is detected with the correct
Xen-users mailing list