[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] porting vmware's vmdk to domU
- To: Ernst Bachmann <e.bachmann@xxxxxxxx>, uebelacker@xxxxxxx
- From: Sharath Babu <sharathx@xxxxxxxxx>
- Date: Sat, 1 Oct 2005 04:10:49 +0530
- Cc: xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Fri, 30 Sep 2005 22:38:30 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hJKVitE95Q7tBNkhwORv5uCopZ1W8+tzkNUU2tXqDuPmACRX+GlDr4vUcO9uP6YobOuijoPBR0jqmwGthU8VLi/iL+sdEiYpJ9DN6s2b3vSOS1+NxH0TMsZBVfs5aqGqsX8ISAw9f9rzwd14cvrlZogR1F5KCBi3uajEChMcGzk=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
I have never seen vmware-mount.pl or vmware-loop working properly,
Everytime you try to mount, you would get "Unable to invoke
vmware-loop", this seems to support older version(version 2) of vmdk
files and not the newer ones.
if you try to use vmware-loop(vmdk to NBD mapper) directly, it might give you "Unable to open the vmdk file" or something....
But give it a try,
I believe qemu-img works better in this case and much more easier to use.
#qemu-img convert -f vmdk /path/filename.vmdk -O raw /path/filename.raw
# fdisk -l /path/filename.raw
will give you the list of partitions...... showing that the conversion was good.
Make sure to peel off the required partition from this image to a new
image, because you cannot mount a disk, you can only mount a partition.
supports vmware 3 and 4 images
check:
http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC18
--
Sharath
On 10/1/05, Ernst Bachmann <e.bachmann@xxxxxxxx> wrote:
On Friday 30 September 2005 18:57, Aaron // LT wrote:
> Lately I have been creating xen domU images using vmware. But what i
> usually do is do a basic install in vmware, then do something like:
>
> dd if=/dev/zero of=/osname bs=1024k count=size_megabytes
> mkfs.ext3 /osname
> mount -o loop /osnname /mnt
> cp -ax /mnt/{root,dev,var,etc,usr,bin,sbin,lib} /mnt
> mkdir /mnt/{proc,sys,home,tmp}
> chmod 777 /mnt/tmp
A bit offtopic, but I hope you don't create your /tmp dir that way on a
multiuser system, it is missing the sticky / "tempdir" flag.
chmod 1777 /mnt/tmp
would be better.
For the original question:
There's a tool to loopback-mount the vmware images into the host os, have a
look at:
http://www.vmware.com/support/reference/linux/loopback_linux.html#what
/Ernst
_______________________________________________
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
|
