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@lists.xensource.com http://lists.xensource.com/xen-users
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@texnet.com> 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@texnet.com> 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@lists.xensource.com >> 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@lists.xensource.com http://lists.xensource.com/xen-users
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@texnet.com> 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@texnet.com> 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@lists.xensource.com >> >> 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@lists.xensource.com >> 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@lists.xensource.com http://lists.xensource.com/xen-users
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@texnet.com> 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@texnet.com>
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@texnet.com> 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@lists.xensource.com
>> >> >> 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@lists.xensource.com
>> >> 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@lists.xensource.com
>> 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@lists.xensource.com
http://lists.xensource.com/xen-users
Hello, We consider to use Xen as VPS hosting platform but have some questions about securing traffic between domUs. I read the following article: http://www.standingonthebrink.com/index.php/ipv6-ipv4-and-arp-on-xen-for-vps/ and it seems that traffic securing if we in domUs subnet which is bridged to Internet is not quite good. It is very important for me to not allow to sniff/spoof traffic between domUs. Is it possible in Xen? We are using Xen 3.3.1 for now. What do you think about using approach in this article in production VPS enviroment? With regards, Andrey. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
mount -o loop /var/xen/domains/xen_compat/xen_compatible.img
/var/xen/domains/mnt
mount: you must specify the filesystem type
xenhost xen # fdisk -lu /var/xen/domains/xen_compat/xen_compatible.img
You must set cylinders.
You can do this from the extra functions menu.
Disk /var/xen/domains/xen_compat/xen_compatible.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders, total 0 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x000be14d
Device Boot Start
End Blocks Id System
/var/xen/domains/xen_compat/xen_compatible.img1 * 63
15952544 7976241 83 Linux
/var/xen/domains/xen_compat/xen_compatible.img2 15952545
16771859 409657+ 5 Extended
Partition 2 has different physical/logical endings:
phys=(1023, 254, 63) logical=(1043, 254, 63)
/var/xen/domains/xen_compat/xen_compatible.img5 15952608
16771859 409626 82 Linux swap / Solaris
Need an offset - 63x512=32,256
mount -o loop,offset=32256 /var/xen/domains/xen_compat/xen_compatible.img
/var/xen/domains/mnt
cat /var/xen/domains/mnt/etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options>
<dump> <pass>
proc /proc proc defaults 0 0
/dev/sda1 / ext3 errors=remount-ro 0 1
/dev/sda5 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
# Beginning of the block added by the VMware software
.host:/ /mnt/hgfs vmhgfs defaults,ttl=5
0 0
# End of the block added by the VMware software
/etc/xen/xen_compat.cfg:
root = ''/dev/sda1 ro''
disk = [
''file:/var/xen/domains/xen_compat/xen_compatible.img,sda1,w''
]
xm create -c xen_compat.cfg
Begin: Waiting for root file system ...
Same thing.
<sigh>
> Brian,
>
> Please try mounting the xen.img file using a command like this.
>
> mount -o loop /xen-images/guest_base.img /xen-images/mnt
> *
> *
> *then in /xen-images/mnt/etc/fstab you may be able to see the disk names.*
> *
> *
> *Then give the right disk partition name*
> *
> *
> *for the *
> *
> *
> *root= ''/dev/xxxxx ro''*
> *disk=
''''file:/var/xen/domains/xen_compat/xen_compatible.img,xxxxx,w''*
> *
> *
> This should work.
>
>
> On Thu, Feb 25, 2010 at 11:01 PM, Brian <brian@texnet.com> wrote:
>
>> 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''
>> ]
>>
>
> You have mismatch above in disk name and root.
>
>
>
>>
>> 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''
>> ]
>>
>>
> Here the disk name in fstab and root/disk variables do not match.
>
>
>> 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
>> >
>> >
>>
>
> I think if you do the following steps you will have a working setup:
>
> 1. Convert the disks from vmdk to xen using the commands in earlier mail
> for
> each of the disks.
> 2. Mount the image file which had root file system and check the
> /etc/fstab
> 3. Give the correct device names for root and disk variables in xen config
> as in fstab. (In disk variable specify both image files with their right
> name as in fstab).
>
> Thanks
> Ramachandran
>
>
>
>> > On Tue, Feb 23, 2010 at 10:34 PM, Brian <brian@texnet.com>
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@texnet.com> 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@texnet.com>
>> 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@lists.xensource.com
>> >> >> >> 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@lists.xensource.com
>> >> >> 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@lists.xensource.com
>> >> 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@lists.xensource.com
>> 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@lists.xensource.com
http://lists.xensource.com/xen-users