Had the vmware guest split into 2G chunks, converted to single growable,
verified bootable and network connectivity under VMWare. This is a good
vmdk. Here is the /etc/fstab of the VM:
/dev/sda1 / ext3 errors=remount-ro 0 1
/dev/sda5 none swap sw 0 0
Next:
vmware-vdiskmanager -r vmware_image.vmdk -t 0 temporary_image.vmdk (doubt
this really needed to be done as I already converted to single growable)
qemu-img convert -f vmdk temporary_image.vmdk -O raw xen_compatible.img
Copied a swap.img from another xen vm to /var/xen/domains/xen_compat/.
/etc/xen/xen_compat.cfg:
root = '/dev/xvda2 ro'
disk = [
'file:/var/xen/domains/xen_compat/swap.img,sda1,w',
'file:/var/xen/domains/xen_compat/xen_compatible.img,sda5,w'
]
also tried (copied from a working xen vm)
root = '/dev/xvda2 ro'
disk = [
'file:/var/xen/domains/xen_compat/swap.img,xvda1,w',
'file:/var/xen/domains/xen_compat/xen_compatible.img,xvda2,w'
]
xm create -c xen_compat.cfg results:
Begin: Waiting for root file system ...
Have no idea how to pass single to a non-bootable xen VM.
Where does "mount -o remount,rw /" go, surely not in a non-bootable VM
/etc/fstab?
"edit /etc/fstab sdb to hda or whatever as in xen.cfg." I created my
xen_compat.cfg by hand, no instructions for migrated VMs.
Thanks again for any insight.
> Brian,
>
> For me the following steps worked.
>
> vmware-vdiskmanager -r vmware_image.vmdk -t 0 temporary_image.vmdk
qemu-img convert -f vmdk temporary_image.vmdk -O raw xen_compatible.img
>
> Then using this disk I could boot the guest in which I could login as
root
> in single user mode
>
> mount -o remount,rw /
>
> edit /etc/fstab sdb to hda or whatever as in xen.cfg.
>
> Can you please post your /etc/fstab file in your vmware guest and the
xen
> cfg file.
>
> Are you reaching to a point where you are able to login in a single user
mode into the converted xen guest at all?
>
> Thanks
> Ramachandran
>
>
> On Tue, Feb 23, 2010 at 10:34 PM, Brian <brian@xxxxxxxxxx> wrote:
>
>> I got into the original VMWare guest and found sda1 as / and sda5 as
swap,
>> changed the disk lines in the .cfg, or did I not understand correctly
as
>> I
>> haven't read this anywhere?
>> Am I supposed to create a "blank" xen disk and dd the converted vmware
file to the blank??????
>> Some official docs would sure be nice if htere's more than the few
lines
>> in the wiki.
>> This is about a deal-breaker ;~(
>> > Brian,
>> >
>> > I guess you may be missing a step of renaming the device.
>> > Check if your /etc/fstab and rename sda or sdb etc to hda etc as the
>> case
>> > may be in xen vm config file.
>> >
>> > Thanks
>> > Ramachandran
>> >
>> > On Fri, Feb 19, 2010 at 11:58 PM, Brian <brian@xxxxxxxxxx> wrote:
>> >
>> >> Yep, read that one too ;~)>
>> >>
>> >> This is a debian vm.
>> >>
>> >> The new disk.img shows to be raw.
>> >>
>> >> Not sure where to go from here, thought it would just work.
>> >>
>> >>
>> >> > check this
>> >> > http://ian.blenke.com/vmware/vmdk/xen/hvm/qemu/vmware_to_xen_hvm.html
>> >> >
>> >> > On Fri, Feb 19, 2010 at 12:53 PM, Brian <brian@xxxxxxxxxx> wrote:
>> >> >
>> >> >> So I tried this:
>> >> >>
>> >> >> http://wiki.xensource.com/xenwiki/VMDKImage
>> >> >>
>> >> >> And get this:
>> >> >>
>> >> >> <bunch of stuff>
>> >> >> Begin: Waiting for root file system ...
>> >> >>
>> >> >> What am I missing, where are some docs?
>> >> >>
>> >> >> TIA
>> >> >>
>> >> >>
>> >> >> --
>> >> >> This message has been scanned for viruses and
>> >> >> dangerous content by MailScanner, and is
>> >> >> believed to be clean.
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Xen-users mailing list
>> >> >> Xen-users@xxxxxxxxxxxxxxxxxxx
>> >> >> http://lists.xensource.com/xen-users
>> >> >>
>> >> >
>> >> > --
>> >> > This message has been scanned for viruses and
>> >> > dangerous content by MailScanner, and is
>> >> > believed to be clean.
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> This message has been scanned for viruses and
>> >> dangerous content by MailScanner, and is
>> >> believed to be clean.
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-users mailing list
>> >> Xen-users@xxxxxxxxxxxxxxxxxxx
>> >> http://lists.xensource.com/xen-users
>> >>
>> >
>> > --
>> > This message has been scanned for viruses and
>> > dangerous content by MailScanner, and is
>> > believed to be clean.
>> >
>> >
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home