I have vmware server 2.0 vmdk that is using lvm within the vmware vmdk. I can i convert it so i can use it with xen, i been trying ever on the web but have found a solution that work. Here is the vmdk fstab runing centos 5.2 /dev/VolGroup00/LogVol03 / ext3 defaults 1 1 /dev/VolGroup00/LogVol00 /var ext3 defaults 1 2 /dev/VolGroup00/LogVol02 /tmp ext3 defaults 1 2 /dev/VolGroup00/LogVol04 /home ext3 grpquota,suid,dev,usrquota,exec 0 2 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>I have vmware server 2.0 vmdk that is using lvm within the vmware vmdk. I can i convert it so i can use it with xen, i been trying ever on the web but have found a solution that work.What is your target block device in xen, a file or lvm etc? Are both machines available at the same time, or do you have sufficient intermediate storage? jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Christopher, First, look into qemu-img that converts VMware .vmdk to Xen .img. I''ve been through a few iterations and found this to be the best for me. ** I use Centos as my domUs. Create a Xen domU with the desired settings. If you can, custom layout the partition and do it all in plain old ext3-no LVMs. I prefer to have just a / partition where both root and /boot live as my days of filling up / and killing the OS are over. ** Update both Xen domU and your VMware guest to the latest packages so they are in sync, just a precaution. Or at least make sure they are in sync. ** Remove any VMware drivers from your VMware guest. Once you have it all up and running, down it and then mount the disk image on your dom0 under what ever dir u like, something like /foo I guess (I use lomount for this). Now export /foo and mount that export on the VMware box as /foo. From your VMware guest, change to /foo and do; ** make sure you are in /foo 1 - mv all etc/sysconfig/network* to network*.o so for example, the file network becomes network.o, the dirs networking and networking- scripts each are renamed with a .o suffix. 2 - mv etc/sysconfig/grub to grub.o. 3 - mv etc/sysconfig/hwconf to hwconf.o 4 - mv etc/sysconfig/kernel to kernel.o 5 - mv etc/modprof.conf to modprobe.conf.o ** see the pattern here 6 - while still living in /foo, do dump -L 0 -f - / | restore -r -u -f - 7 - Once finished, remove the .o suffix, over writing the existing files/dirs. 8 - Adjust hostname, ip to taste and unmount the export. 9 - Now, back on your dom0, unexport /foo and unmount it. 10 - Fire up that domU up, all should be well. I''ve done this on about half a dozen boxs and all is well. ** While there are certainly better options and from more qualified ppl on this list as I am very green, this works for me. ** This is basically syncing 2 OS''s and then modifying the target back to what makes it a Xen OS. ** I think you went a little too far with separate mounts for /var, / tmp and /home so adjust the above to incorporate those mnt points. I don''t want to debate system design as you have a good reason for doing this but my professor emphasized the KISS principle, he was an ex marine. ** If you want to keep with the LVM theme, then read the below thread from a very knowledgeable and helpful comrad in arms on how to mount LVMs; Brian Krusic wrote:> Forgot, my conf files disk line of interest looks like this; > > disk = [ "tap:aio:/var/lib/xen/images/foo.img,xvda,w" ]First make sure your guest isn''t running unless you want to trash its file systems. losetup -f /var/lib/xen/images/foo.img losetup -a # Make a note of which device corresponds to /var/lib/images/foo.img, # ''ll call it /dev/loopN but it''s probably /dev/loop0 kpartx -va /dev/loopN You''ll get two new entries in /dev/mapper now: /dev/mapper/loopNp1 and /dev/mapper/loopNp2. loopNp1 is /boot (asume you have got a standard layout). loopNp2 is a volume group. You can just mount /dev/loopNp1 to poke around the /boot file system. Now vgscan This is where you might come unstuck. The default volume group for Red Hat and similar is "VolGroup00". If your dom0 is using LVM and so is the guest then you''ll have do VolGroup00''s and that''s bad. The best thing to do now is to boot a rescue image in a different domU and rename the guest''s volume group. You''ll need to undo the kpartx and losetup (see below first) and when you''ve all finished then you''ll need to either fix up the guest''s /boot/initrd*.img, /etc/fstab and / boot/grub/grub.conf to hold the new name or you''ll have to rename it back again in the rescue guest. Anyway, assuming you don''t get a clash: vgchange -ay VolGroup00 The guest''s file systems are now in /dev/VolGroup00 and you can mount them as normal. To undo everything: 1. umount any file systyems you mounted 2. vgchange -an VolGroup00 3. kpartx -d /dev/loopN 4. losetup -d /dev/loopN And next time you build a system, change the name of its volume group so you don''t wind up with two systems with the same volume group name! And I wish Red Hat had listened to me years ago when I said that "VolGroup00" was a really poor idea. jch - Brian On Mar 1, 2009, at 3:43 PM, christopher andrews wrote:> I have vmware server 2.0 vmdk that is using lvm within the vmware > vmdk. I can i convert it so i can use it with xen, i been trying > ever on the web but have found a solution that work. > > Here is the vmdk fstab runing centos 5.2 > /dev/VolGroup00/LogVol03 / ext3 > defaults 1 1 > /dev/VolGroup00/LogVol00 /var ext3 > defaults 1 2 > /dev/VolGroup00/LogVol02 /tmp ext3 > defaults 1 2 > /dev/VolGroup00/LogVol04 /home ext3 > grpquota,suid,dev,usrquota,exec 0 2 > LABEL=/boot /boot ext3 > defaults 1 2 > tmpfs /dev/shm tmpfs > defaults 0 0 > devpts /dev/pts devpts > gid=5,mode=620 0 0 > sysfs /sys sysfs > defaults 0 0 > proc /proc proc > defaults 0 0 > /dev/VolGroup00/LogVol01 swap swap > defaults 0 0 > > > _______________________________________________ > 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
Note that, depending on the type of VMDK file you''re using, it''s already in a state where you can use it in Xen. I''m not sure about VMware Server 2, but in VMware ESX/ESXi, there are two files for each disk - <diskname>.vmdk, the descriptor file, and <diskname>-flat.vmdk, the data. The -flat.vmdk file is essentially the same as a Xen RAW file, so you can use it directly with Xen. -Nick>>> christopher andrews <khris4@gmail.com> 2009/03/01 16:43 >>>I have vmware server 2.0 vmdk that is using lvm within the vmware vmdk. I can i convert it so i can use it with xen, i been trying ever on the web but have found a solution that work. Here is the vmdk fstab runing centos 5.2 /dev/VolGroup00/LogVol03 / ext3 defaults 1 1 /dev/VolGroup00/LogVol00 /var ext3 defaults 1 2 /dev/VolGroup00/LogVol02 /tmp ext3 defaults 1 2 /dev/VolGroup00/LogVol04 /home ext3 grpquota,suid,dev,usrquota,exec 0 2 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
If you execute the "file" command on the teamhalprin.com-flat_vm.vmdk
file, you should get the following output:
teamhalprin.com-flat_vm.vmdk: x86 boot sector, GRand Unified Bootloader,
code offset 0x48
If so, that file can be used directly with Xen. The config line for Xen
would look something like this:
disk=[ ''file:/path/to/teamhalprin.com-flat_vm.vmdk,hda,w'', ]
that''s assuming you''re using an HVM domU on Xen - if you want
to do a PV
domU, you''d probably do this, instead:
disk=[ ''file:/path/to/teamhalprin.com-flat_vm.vmdk,xvda,w'', ]
(the only difference is that hda from the first example changes to
xvda). I''ve never tried to use one of these in Xen and then go back
and
use it with the original descriptor file in VMware, so I don''t know if
that works. I would imagine so, but it''s possible that VMware does
some
sort of check to make sure that it hasn''t been modified without their
knowing.
-Nick
--
Nick Couchman
Manager, Information Technology
SEAKR Engineering, Inc
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Mon, 2 Mar 2009 00:04:48 -0500
This is what i have
Other Linux 2.6.x kernel.vmem Other Linux 2.6.x kernel.vmx
teamhalprin.com-flat_vm.vmdk.lck vmware.log
Other Linux 2.6.x kernel.vmsd Other Linux 2.6.x kernel.vmxf
teamhalprin_vm.vmdk
Other Linux 2.6.x kernel.vmss teamhalprin.com-flat_vm.vmdk
vmware-0.log
Would have an idea of what the config should look like for the vmdk in
xen? I know there are lot of way to include the image in xen config for
different type of setupz.
On Sun, Mar 1, 2009 at 11:59 PM, Nick Couchman <Nick.Couchman@seakr.com>
wrote:
Well, it only works if you have the right type of VMDK. If you
have a <diskname>-flat.vmdk file, it probably will work - you
can just point the Xen configuration at that file and Xen will
read the disk. If you have a multiple-slice disk, where you
have <diskname>-s001.vmdk, <diskname>-s002.vmdk, etc.,
you''ll
need to do the conversion - the easiest way, as has already been
mentioned, is using qemu-img to convert each of the -s00*.vmdk
files to raw format, then cat them all into a single file.
-Nick
>>> christopher andrews <khris4@gmail.com> 2009/03/01
21:56 >>>
Would you know how I can use my current vmdk file with xen? That
would be a easy way to get thing working.
On Sun, Mar 1, 2009 at 11:52 PM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
Note that, depending on the type of VMDK file you''re
using, it''s already in a state where you can use it in
Xen. I''m not sure about VMware Server 2, but in VMware
ESX/ESXi, there are two files for each disk -
<diskname>.vmdk, the descriptor file, and
<diskname>-flat.vmdk, the data. The -flat.vmdk file is
essentially the same as a Xen RAW file, so you can use
it directly with Xen.
-Nick
>>> christopher andrews <khris4@gmail.com>
2009/03/01
16:43 >>>
I have vmware server 2.0 vmdk that is using lvm within
the vmware vmdk. I can i convert it so i can use it with
xen, i been trying ever on the web but have found a
solution that work.
Here is the vmdk fstab runing centos 5.2
/dev/VolGroup00/LogVol03 / ext3 defaults 1 1
/dev/VolGroup00/LogVol00 /var ext3 defaults 1 2
/dev/VolGroup00/LogVol02 /tmp ext3 defaults 1 2
/dev/VolGroup00/LogVol04 /home ext3
grpquota,suid,dev,usrquota,exec 0 2
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
________________________________________________________
This e-mail may contain confidential and privileged
material for the sole use of the intended recipient. If
this email is not intended for you, or you are not
responsible for the delivery of this message to the
intended recipient, please note that this message may
contain SEAKR Engineering (SEAKR) Privileged/Proprietary
Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or
otherwise using this message, its contents or
attachments in any way. If you have received this
message in error, please notify us immediately by
replying to this e-mail and delete the message from your
mailbox. Information contained in this message that does
not relate to the business of SEAKR is neither endorsed
by nor attributable to SEAKR.
________________________________________________________________
This e-mail may contain confidential and privileged material for
the sole use of the intended recipient. If this email is not
intended for you, or you are not responsible for the delivery of
this message to the intended recipient, please note that this
message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are
strictly prohibited from downloading, photocopying, distributing
or otherwise using this message, its contents or attachments in
any way. If you have received this message in error, please
notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither
endorsed by nor attributable to SEAKR.
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient. If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Sounds like you may need to use qemu-img to convert it from VMDK to
RAW...
-Nick
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Tue, 3 Mar 2009 09:03:28 -0500
I guess I don''t have good luck because it''s come like this
file Virtual\ Machine.vmdk
Virtual Machine.vmdk: data
On Tue, Mar 3, 2009 at 8:29 AM, Nick Couchman <Nick.Couchman@seakr.com>
wrote:
If you execute the "file" command on the
teamhalprin.com-flat_vm.vmdk file, you should get the following
output:
teamhalprin.com-flat_vm.vmdk: x86 boot sector, GRand Unified
Bootloader, code offset 0x48
If so, that file can be used directly with Xen. The config line
for Xen would look something like this:
disk=[
''file:/path/to/teamhalprin.com-flat_vm.vmdk,hda,w'', ]
that''s assuming you''re using an HVM domU on Xen - if
you want to
do a PV domU, you''d probably do this, instead:
disk=[
''file:/path/to/teamhalprin.com-flat_vm.vmdk,xvda,w'', ]
(the only difference is that hda from the first example changes
to xvda). I''ve never tried to use one of these in Xen and then
go back and use it with the original descriptor file in VMware,
so I don''t know if that works. I would imagine so, but
it''s
possible that VMware does some sort of check to make sure that
it hasn''t been modified without their knowing.
-Nick
--
Nick Couchman
Manager, Information Technology
SEAKR Engineering, Inc
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Mon, 2 Mar 2009 00:04:48 -0500
This is what i have Other Linux 2.6.x kernel.vmem Other Linux
2.6.x kernel.vmx teamhalprin.com-flat_vm.vmdk.lck vmware.log
Other Linux 2.6.x kernel.vmsd Other Linux 2.6.x kernel.vmxf
teamhalprin_vm.vmdk Other Linux 2.6.x kernel.vmss
teamhalprin.com-flat_vm.vmdk vmware-0.log
Would have an idea of what the config should look like for the
vmdk in xen? I know there are lot of way to include the image
in xen config for different type of setupz.
On Sun, Mar 1, 2009 at 11:59 PM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
Well, it only works if you have the right type of VMDK.
If you have a <diskname>-flat.vmdk file, it probably
will work - you can just point the Xen configuration at
that file and Xen will read the disk. If you have a
multiple-slice disk, where you have
<diskname>-s001.vmdk, <diskname>-s002.vmdk, etc.,
you''ll
need to do the conversion - the easiest way, as has
already been mentioned, is using qemu-img to convert
each of the -s00*.vmdk files to raw format, then cat
them all into a single file.
-Nick
>>> christopher andrews <khris4@gmail.com>
2009/03/01
21:56 >>>
Would you know how I can use my current vmdk file with
xen? That would be a easy way to get thing working.
On Sun, Mar 1, 2009 at 11:52 PM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
Note that, depending on the type of VMDK file
you''re using, it''s already in a state
where you
can use it in Xen. I''m not sure about VMware
Server 2, but in VMware ESX/ESXi, there are two
files for each disk - <diskname>.vmdk, the
descriptor file, and <diskname>-flat.vmdk, the
data. The -flat.vmdk file is essentially the
same as a Xen RAW file, so you can use it
directly with Xen.
-Nick
>>> christopher andrews
<khris4@gmail.com>
2009/03/01 16:43 >>>
I have vmware server 2.0 vmdk that is using lvm
within the vmware vmdk. I can i convert it so i
can use it with xen, i been trying ever on the
web but have found a solution that work.
Here is the vmdk fstab runing centos 5.2
/dev/VolGroup00/LogVol03 / ext3 defaults 1 1
/dev/VolGroup00/LogVol00 /var ext3 defaults 1 2
/dev/VolGroup00/LogVol02 /tmp ext3 defaults 1 2
/dev/VolGroup00/LogVol04 /home ext3
grpquota,suid,dev,usrquota,exec 0 2
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
________________________________________________
This e-mail may contain confidential and
privileged material for the sole use of the
intended recipient. If this email is not
intended for you, or you are not responsible for
the delivery of this message to the intended
recipient, please note that this message may
contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a
case, you are strictly prohibited from
downloading, photocopying, distributing or
otherwise using this message, its contents or
attachments in any way. If you have received
this message in error, please notify us
immediately by replying to this e-mail and
delete the message from your mailbox.
Information contained in this message that does
not relate to the business of SEAKR is neither
endorsed by nor attributable to SEAKR.
________________________________________________________
This e-mail may contain confidential and privileged
material for the sole use of the intended recipient. If
this email is not intended for you, or you are not
responsible for the delivery of this message to the
intended recipient, please note that this message may
contain SEAKR Engineering (SEAKR) Privileged/Proprietary
Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or
otherwise using this message, its contents or
attachments in any way. If you have received this
message in error, please notify us immediately by
replying to this e-mail and delete the message from your
mailbox. Information contained in this message that does
not relate to the business of SEAKR is neither endorsed
by nor attributable to SEAKR.
________________________________________________________________
This e-mail may contain confidential and privileged material for
the sole use of the intended recipient. If this email is not
intended for you, or you are not responsible for the delivery of
this message to the intended recipient, please note that this
message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are
strictly prohibited from downloading, photocopying, distributing
or otherwise using this message, its contents or attachments in
any way. If you have received this message in error, please
notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither
endorsed by nor attributable to SEAKR.
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient. If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
You may need to add the following line to your Xen domU config:
root="/dev/hda1"
Replace "hda1" with whichever partition is your root device and see if
that works. Also, Xen HVM domUs only support the ata_piix disk
controller, so your kernel and initrd need to have support for that
included. If not, the kernel won''t be able to locate the hard drive
and
mount it.
-Nick
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Tue, 3 Mar 2009 09:20:07 -0500
when i convert it to a raw, xen vm won''t boot due to not being able to
mount partition and then a kernel panic. Just to let you know inside
the image the hard drive is partition the old fashion way with different
partition ( /,home,var,tmp,boot ). So i''m thinking maybe xen
can''t
handle the LVM partition plus the parittion scheme that inside the xen
image.
On Tue, Mar 3, 2009 at 9:05 AM, Nick Couchman <Nick.Couchman@seakr.com>
wrote:
Sounds like you may need to use qemu-img to convert it from VMDK
to RAW...
-Nick
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Tue, 3 Mar 2009 09:03:28 -0500
I guess I don''t have good luck because it''s come like
this file
Virtual\ Machine.vmdk Virtual Machine.vmdk: data
On Tue, Mar 3, 2009 at 8:29 AM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
If you execute the "file" command on the
teamhalprin.com-flat_vm.vmdk file, you should get the
following output:
teamhalprin.com-flat_vm.vmdk: x86 boot sector, GRand
Unified Bootloader, code offset 0x48
If so, that file can be used directly with Xen. The
config line for Xen would look something like this:
disk=[
''file:/path/to/teamhalprin.com-flat_vm.vmdk,hda,w'', ]
that''s assuming you''re using an HVM domU on
Xen - if you
want to do a PV domU, you''d probably do this, instead:
disk=[
''file:/path/to/teamhalprin.com-flat_vm.vmdk,xvda,w'', ]
(the only difference is that hda from the first example
changes to xvda). I''ve never tried to use one of these
in Xen and then go back and use it with the original
descriptor file in VMware, so I don''t know if that
works. I would imagine so, but it''s possible that
VMware does some sort of check to make sure that it
hasn''t been modified without their knowing.
-Nick
--
Nick Couchman
Manager, Information Technology
SEAKR Engineering, Inc
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Mon, 2 Mar 2009 00:04:48 -0500
This is what i have Other Linux 2.6.x kernel.vmem
Other Linux 2.6.x kernel.vmx
teamhalprin.com-flat_vm.vmdk.lck vmware.log Other Linux
2.6.x kernel.vmsd Other Linux 2.6.x kernel.vmxf
teamhalprin_vm.vmdk Other Linux 2.6.x kernel.vmss
teamhalprin.com-flat_vm.vmdk vmware-0.log
Would have an idea of what the config should look like
for the vmdk in xen? I know there are lot of way to
include the image in xen config for different type of
setupz.
On Sun, Mar 1, 2009 at 11:59 PM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
Well, it only works if you have the right type
of VMDK. If you have a <diskname>-flat.vmdk
file, it probably will work - you can just point
the Xen configuration at that file and Xen will
read the disk. If you have a multiple-slice
disk, where you have <diskname>-s001.vmdk,
<diskname>-s002.vmdk, etc., you''ll need
to do
the conversion - the easiest way, as has already
been mentioned, is using qemu-img to convert
each of the -s00*.vmdk files to raw format, then
cat them all into a single file.
-Nick
>>> christopher andrews
<khris4@gmail.com>
2009/03/01 21:56 >>>
Would you know how I can use my current vmdk
file with xen? That would be a easy way to get
thing working.
On Sun, Mar 1, 2009 at 11:52 PM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
Note that, depending on the type of VMDK
file you''re using, it''s
already in a
state where you can use it in Xen. I''m
not sure about VMware Server 2, but in
VMware ESX/ESXi, there are two files for
each disk - <diskname>.vmdk, the
descriptor file, and
<diskname>-flat.vmdk, the data. The
-flat.vmdk file is essentially the same
as a Xen RAW file, so you can use it
directly with Xen.
-Nick
>>> christopher andrews
<khris4@gmail.com> 2009/03/01 16:43
>>>
I have vmware server 2.0 vmdk that is
using lvm within the vmware vmdk. I can
i convert it so i can use it with xen, i
been trying ever on the web but have
found a solution that work.
Here is the vmdk fstab runing centos
5.2
/dev/VolGroup00/LogVol03 / ext3 defaults
1 1
/dev/VolGroup00/LogVol00 /var ext3
defaults 1 2
/dev/VolGroup00/LogVol02 /tmp ext3
defaults 1 2
/dev/VolGroup00/LogVol04 /home ext3
grpquota,suid,dev,usrquota,exec 0 2
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0
0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap
defaults 0 0
________________________________________
This e-mail may contain confidential and
privileged material for the sole use of
the intended recipient. If this email is
not intended for you, or you are not
responsible for the delivery of this
message to the intended recipient,
please note that this message may
contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In
such a case, you are strictly prohibited
from downloading, photocopying,
distributing or otherwise using this
message, its contents or attachments in
any way. If you have received this
message in error, please notify us
immediately by replying to this e-mail
and delete the message from your
mailbox. Information contained in this
message that does not relate to the
business of SEAKR is neither endorsed by
nor attributable to SEAKR.
________________________________________________
This e-mail may contain confidential and
privileged material for the sole use of the
intended recipient. If this email is not
intended for you, or you are not responsible for
the delivery of this message to the intended
recipient, please note that this message may
contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a
case, you are strictly prohibited from
downloading, photocopying, distributing or
otherwise using this message, its contents or
attachments in any way. If you have received
this message in error, please notify us
immediately by replying to this e-mail and
delete the message from your mailbox.
Information contained in this message that does
not relate to the business of SEAKR is neither
endorsed by nor attributable to SEAKR.
________________________________________________________
This e-mail may contain confidential and privileged
material for the sole use of the intended recipient. If
this email is not intended for you, or you are not
responsible for the delivery of this message to the
intended recipient, please note that this message may
contain SEAKR Engineering (SEAKR) Privileged/Proprietary
Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or
otherwise using this message, its contents or
attachments in any way. If you have received this
message in error, please notify us immediately by
replying to this e-mail and delete the message from your
mailbox. Information contained in this message that does
not relate to the business of SEAKR is neither endorsed
by nor attributable to SEAKR.
________________________________________________________________
This e-mail may contain confidential and privileged material for
the sole use of the intended recipient. If this email is not
intended for you, or you are not responsible for the delivery of
this message to the intended recipient, please note that this
message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are
strictly prohibited from downloading, photocopying, distributing
or otherwise using this message, its contents or attachments in
any way. If you have received this message in error, please
notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither
endorsed by nor attributable to SEAKR.
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient. If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I''m not sure I understand...is your domU using LVM or not? Earlier you
said it was partitioned "the old fashioned way" which makes me think
your domU is not using LVM. If your original VMware virtual machine was
using LVM, then you still need to use LVM. If your original VMware
virtual machine did not use LVM, you don''t need to use LVM. What
you''re
using in the dom0 does not matter for the configuration inside the domU.
-Nick
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Tue, 3 Mar 2009 09:27:19 -0500
do i need to make any changes to the fstab inside the domUs, since they
using LVM Labels?
On Tue, Mar 3, 2009 at 9:22 AM, Nick Couchman <Nick.Couchman@seakr.com>
wrote:
You may need to add the following line to your Xen domU config:
root="/dev/hda1"
Replace "hda1" with whichever partition is your root device
and
see if that works. Also, Xen HVM domUs only support the
ata_piix disk controller, so your kernel and initrd need to have
support for that included. If not, the kernel won''t be able to
locate the hard drive and mount it.
-Nick
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Tue, 3 Mar 2009 09:20:07 -0500
when i convert it to a raw, xen vm won''t boot due to not being
able to mount partition and then a kernel panic. Just to let
you know inside the image the hard drive is partition the
old fashion way with different partition
( /,home,var,tmp,boot ). So i''m thinking maybe xen
can''t handle
the LVM partition plus the parittion scheme that inside the xen
image.
On Tue, Mar 3, 2009 at 9:05 AM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
Sounds like you may need to use qemu-img to convert it
from VMDK to RAW...
-Nick
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to xen
Date: Tue, 3 Mar 2009 09:03:28 -0500
I guess I don''t have good luck because it''s
come like
this file Virtual\ Machine.vmdk Virtual Machine.vmdk:
data
On Tue, Mar 3, 2009 at 8:29 AM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
If you execute the "file" command on the
teamhalprin.com-flat_vm.vmdk file, you should
get the following output:
teamhalprin.com-flat_vm.vmdk: x86 boot sector,
GRand Unified Bootloader, code offset 0x48
If so, that file can be used directly with Xen.
The config line for Xen would look something
like this:
disk=[
''file:/path/to/teamhalprin.com-flat_vm.vmdk,hda,w'', ]
that''s assuming you''re using an HVM
domU on Xen
- if you want to do a PV domU, you''d probably
do
this, instead:
disk=[
''file:/path/to/teamhalprin.com-flat_vm.vmdk,xvda,w'', ]
(the only difference is that hda from the first
example changes to xvda). I''ve never tried to
use one of these in Xen and then go back and use
it with the original descriptor file in VMware,
so I don''t know if that works. I would imagine
so, but it''s possible that VMware does some
sort
of check to make sure that it hasn''t been
modified without their knowing.
-Nick
--
Nick Couchman
Manager, Information Technology
SEAKR Engineering, Inc
-----Original Message-----
From: christopher andrews <khris4@gmail.com>
To: Nick Couchman <Nick.Couchman@seakr.com>
Subject: Re: [Xen-users] help convert vmdk to
xen
Date: Mon, 2 Mar 2009 00:04:48 -0500
This is what i have Other Linux 2.6.x
kernel.vmem Other Linux 2.6.x kernel.vmx
teamhalprin.com-flat_vm.vmdk.lck vmware.log
Other Linux 2.6.x kernel.vmsd Other Linux 2.6.x
kernel.vmxf teamhalprin_vm.vmdk Other Linux
2.6.x kernel.vmss teamhalprin.com-flat_vm.vmdk
vmware-0.log
Would have an idea of what the config should
look like for the vmdk in xen? I know there are
lot of way to include the image in xen config
for different type of setupz.
On Sun, Mar 1, 2009 at 11:59 PM, Nick Couchman
<Nick.Couchman@seakr.com> wrote:
Well, it only works if you have the
right type of VMDK. If you have a
<diskname>-flat.vmdk file, it probably
will work - you can just point the Xen
configuration at that file and Xen will
read the disk. If you have a
multiple-slice disk, where you have
<diskname>-s001.vmdk,
<diskname>-s002.vmdk, etc.,
you''ll need
to do the conversion - the easiest way,
as has already been mentioned, is using
qemu-img to convert each of the
-s00*.vmdk files to raw format, then cat
them all into a single file.
-Nick
>>> christopher andrews
<khris4@gmail.com> 2009/03/01 21:56
>>>
Would you know how I can use my current
vmdk file with xen? That would be a easy
way to get thing working.
On Sun, Mar 1, 2009 at 11:52 PM, Nick
Couchman <Nick.Couchman@seakr.com>
wrote:
Note that, depending on the type
of VMDK file you''re using,
it''s
already in a state where you can
use it in Xen. I''m not sure
about VMware Server 2, but in
VMware ESX/ESXi, there are two
files for each disk -
<diskname>.vmdk, the descriptor
file, and <diskname>-flat.vmdk,
the data. The -flat.vmdk file is
essentially the same as a Xen
RAW file, so you can use it
directly with Xen.
-Nick
>>> christopher andrews
<khris4@gmail.com> 2009/03/01
16:43 >>>
I have vmware server 2.0 vmdk
that is using lvm within the
vmware vmdk. I can i convert it
so i can use it with xen, i been
trying ever on the web but have
found a solution that work.
Here is the vmdk fstab runing
centos 5.2
/dev/VolGroup00/LogVol03 / ext3
defaults 1 1
/dev/VolGroup00/LogVol00 /var
ext3 defaults 1 2
/dev/VolGroup00/LogVol02 /tmp
ext3 defaults 1 2
/dev/VolGroup00/LogVol04 /home
ext3
grpquota,suid,dev,usrquota,exec
0 2
LABEL=/boot /boot ext3 defaults
1 2
tmpfs /dev/shm tmpfs defaults 0
0
devpts /dev/pts devpts
gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap
swap defaults 0 0
________________________________
This e-mail may contain
confidential and privileged
material for the sole use of the
intended recipient. If this
email is not intended for you,
or you are not responsible for
the delivery of this message to
the intended recipient, please
note that this message may
contain SEAKR Engineering
(SEAKR) Privileged/Proprietary
Information. In such a case, you
are strictly prohibited from
downloading, photocopying,
distributing or otherwise using
this message, its contents or
attachments in any way. If you
have received this message in
error, please notify us
immediately by replying to this
e-mail and delete the message
from your mailbox. Information
contained in this message that
does not relate to the business
of SEAKR is neither endorsed by
nor attributable to SEAKR.
________________________________________
This e-mail may contain confidential and
privileged material for the sole use of
the intended recipient. If this email is
not intended for you, or you are not
responsible for the delivery of this
message to the intended recipient,
please note that this message may
contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In
such a case, you are strictly prohibited
from downloading, photocopying,
distributing or otherwise using this
message, its contents or attachments in
any way. If you have received this
message in error, please notify us
immediately by replying to this e-mail
and delete the message from your
mailbox. Information contained in this
message that does not relate to the
business of SEAKR is neither endorsed by
nor attributable to SEAKR.
________________________________________________
This e-mail may contain confidential and
privileged material for the sole use of the
intended recipient. If this email is not
intended for you, or you are not responsible for
the delivery of this message to the intended
recipient, please note that this message may
contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a
case, you are strictly prohibited from
downloading, photocopying, distributing or
otherwise using this message, its contents or
attachments in any way. If you have received
this message in error, please notify us
immediately by replying to this e-mail and
delete the message from your mailbox.
Information contained in this message that does
not relate to the business of SEAKR is neither
endorsed by nor attributable to SEAKR.
________________________________________________________
This e-mail may contain confidential and privileged
material for the sole use of the intended recipient. If
this email is not intended for you, or you are not
responsible for the delivery of this message to the
intended recipient, please note that this message may
contain SEAKR Engineering (SEAKR) Privileged/Proprietary
Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or
otherwise using this message, its contents or
attachments in any way. If you have received this
message in error, please notify us immediately by
replying to this e-mail and delete the message from your
mailbox. Information contained in this message that does
not relate to the business of SEAKR is neither endorsed
by nor attributable to SEAKR.
________________________________________________________________
This e-mail may contain confidential and privileged material for
the sole use of the intended recipient. If this email is not
intended for you, or you are not responsible for the delivery of
this message to the intended recipient, please note that this
message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are
strictly prohibited from downloading, photocopying, distributing
or otherwise using this message, its contents or attachments in
any way. If you have received this message in error, please
notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither
endorsed by nor attributable to SEAKR.
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient. If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way. If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox. Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users