[opensuse] Mounting an vmware virtual disk in Linux.

newer
[opensuse] Suse shuts down network...

Carlos E. R.

17 Feb 2008 17 Feb '08

14:05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm trying the script "vmware-mount.pl" (VMware-server-1.0.4-56528) thus: nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl -p Windows\ Me.vmdk -------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential -------------------------------------------- Nr Start Size Type Id Sytem -- ---------- ---------- ---- -- ------------------------ 1 63 16771797 BIOS C Win95 FAT32 (LBA) So, the disk is recognized. I try to mount it: nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl Windows\ Me.vmdk 1 ../mnt1/ -------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential -------------------------------------------- It has been reported that this program does not work correctly with 2.4+ Linux kernels in some cases, and you are currently running such a kernel. Do you really want to continue? [N] Y No Network Block Device detected. There is no Network Block Device defined on this machine. This script is about to create the /dev/nb0 Network Block Device. Continue? [Y] N Unable to continue. What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing? And wanting a kernel <= 2.4... Yicks! - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuD8ntTMYHG2NR9URAtOAAJ4tLt1bamhu2K0YhP99LP3slLQtdACgmJmv EqRG95BIIwF2gWl2F5idAug= =42Vt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Anders Johansson

17 Feb 17 Feb

14:10

On Sunday 17 February 2008 15:05:26 Carlos E. R. wrote:

...

Hi,

I'm trying the script "vmware-mount.pl" (VMware-server-1.0.4-56528) thus:

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl -p Windows\ Me.vmdk

-------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential --------------------------------------------

Nr Start Size Type Id Sytem -- ---------- ---------- ---- -- ------------------------ 1 63 16771797 BIOS C Win95 FAT32 (LBA)

So, the disk is recognized. I try to mount it:

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl Windows\ Me.vmdk 1 ../mnt1/

-------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential --------------------------------------------

It has been reported that this program does not work correctly with 2.4+ Linux kernels in some cases, and you are currently running such a kernel. Do you really want to continue? [N] Y

No Network Block Device detected.

There is no Network Block Device defined on this machine. This script is about to create the /dev/nb0 Network Block Device. Continue? [Y] N

Unable to continue.

What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

Why are you opposed to it? Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

16:09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 15:10 +0100, Anders Johansson wrote:

...

...
No Network Block Device detected.

There is no Network Block Device defined on this machine. This script is about to create the /dev/nb0 Network Block Device. Continue? [Y] N

Unable to continue.

What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

Why are you opposed to it?

Because an attempt to modify my network setup without proper explanation is unjustified and unnecessary. I do not see why creating a network device is needed to _mount_ a disk. It smells of virus or trojan. :-/ - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuFxVtTMYHG2NR9URAhrSAJ0VNSF5GOS04z8Mf1KRrkUsQCAGyACbBnaH T2UfOC7WlSX9Yu9LoWbUWhk= =ww+W -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

16:15

On Sunday 17 February 2008 17:09:57 Carlos E. R. wrote:

...

The Sunday 2008-02-17 at 15:10 +0100, Anders Johansson wrote:

...
...
No Network Block Device detected.

There is no Network Block Device defined on this machine. This script is about to create the /dev/nb0 Network Block Device. Continue? [Y] N

Unable to continue.

What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

Why are you opposed to it?

Because an attempt to modify my network setup without proper explanation is unjustified and unnecessary. I do not see why creating a network device is needed to _mount_ a disk.

It smells of virus or trojan. :-/

In other words, you don't know what a network block device is If it makes you feel any better, it only runs on the loopback device, you're not creating a new network *device*, you're starting a network *service*, and this service, as I said, only runs on the lo device Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

16:18

On Sunday 17 February 2008 17:09:57 Carlos E. R. wrote:

...

The Sunday 2008-02-17 at 15:10 +0100, Anders Johansson wrote:

...
...
No Network Block Device detected.

There is no Network Block Device defined on this machine. This script is about to create the /dev/nb0 Network Block Device. Continue? [Y] N

Unable to continue.

What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

Why are you opposed to it?

Because an attempt to modify my network setup without proper explanation is unjustified and unnecessary. I do not see why creating a network device is needed to _mount_ a disk.

It smells of virus or trojan. :-/

Just to make it clear: a network block device is not a network device, it is a way to access a block device (disk) over a network connection Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

kanenas＠hawaii.rr.com

19:53

On Sunday 17 February 2008 06:18:13 am Anders Johansson wrote:

...

On Sunday 17 February 2008 17:09:57 Carlos E. R. wrote:

...
The Sunday 2008-02-17 at 15:10 +0100, Anders Johansson wrote:

...
...
No Network Block Device detected.

There is no Network Block Device defined on this machine. This script is about to create the /dev/nb0 Network Block Device. Continue? [Y] N

Unable to continue.

What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

Why are you opposed to it?

Because an attempt to modify my network setup without proper explanation is unjustified and unnecessary. I do not see why creating a network device is needed to _mount_ a disk.

It smells of virus or trojan. :-/

Just to make it clear: a network block device is not a network device, it is a way to access a block device (disk) over a network connection

Anders -- Madness takes its toll

Carlos, if you get this resolved, can you please post the procedure? thanks, d. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

19:55

On Sunday 17 February 2008 20:53:46 kanenas@hawaii.rr.com wrote:

...

Carlos, if you get this resolved, can you please post the procedure? thanks, d.

There is nothing to resolve. Carlos just refuses to use the tools provided by vmware because he thinks they will install a virus on his machine. I explained that it isn't so, and that he should use them Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

22:08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 17:18 +0100, Anders Johansson wrote:

...

...
...
...
What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

Why are you opposed to it?

Because an attempt to modify my network setup without proper explanation is unjustified and unnecessary. I do not see why creating a network device is needed to _mount_ a disk.

It smells of virus or trojan. :-/

Just to make it clear: a network block device is not a network device, it is a way to access a block device (disk) over a network connection

Well, that's better. But I don't see why it needs a network connection to mount a local file. [...] Demonstration: nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # file /Reserva/vmware/Virtual\ Machines/Windows\ Me/Windows\ Me-flat.vmdk /Reserva/vmware/Virtual Machines/Windows Me/Windows Me-flat.vmdk: x86 boot sector nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl -p Windows\ Me.vmdk -------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential -------------------------------------------- Nr Start Size Type Id Sytem -- ---------- ---------- ---- -- ------------------------ 1 63 16771797 BIOS C Win95 FAT32 (LBA) Offset is 63*512. So: nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # losetup -o 32256 /dev/loop5 Windows\ Me-flat.vmdk nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # file -s /dev/loop5 /dev/loop5: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads 255, hidden sectors 63, sectors 16771792 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 16347, reserved3 0x800000, serial number 0x432917ea, label: "BOOT-VMWARE" nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # mount -o ro /dev/loop5 ../mnt1/ nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # ls ../mnt1/ .windows-label Data PropiedadesSistema.ps autoexec.bat config.bak netlog.txt ut .windows-serial Desinstalados PropiedadesSistemaPorConexion.ps bootlog.prv config.sys nvidia windows 0_Disco_C_hdc1_320.0_GB Images Recycled bootlog.txt gs scandisk.log 0_Notas_Midnight_Comander My Documents WUTemp cabs hp2P.ps setupxlg.txt See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuLBbtTMYHG2NR9URAkP5AKCSInvS/EgkHielAfLwr2YkHQX0NACfbje2 Lcf9EEfvXn7AUJlI22xuFX4= =Riyx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

22:40

On Sunday 17 February 2008 23:08:14 Carlos E. R. wrote:

...

See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup.

Sure, but that will only work when you haven't split the disks. losetup doesn't know about split disks I don't know why vmware chose to use nbd devices. My guess is that their magic needed to stream split and sparse disks together shouldn't go into a kernel module, and with the nbd it can all be done in user space. But that's just a guess. It was clearly done a long time ago My point was just that your talk of viruses and trojans was just so much twaddle. Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

23:25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 23:40 +0100, Anders Johansson wrote:

...

On Sunday 17 February 2008 23:08:14 Carlos E. R. wrote:

...
See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup.

Sure, but that will only work when you haven't split the disks. losetup doesn't know about split disks

Two disks on the same image, you mean? Yes, could be a problem. It should be solvable, though: the image even has a standard partition table with disk sizes et al. It could be a problem as well if the image has a snapshot point, I suppose.

...

I don't know why vmware chose to use nbd devices. My guess is that their magic needed to stream split and sparse disks together shouldn't go into a kernel module, and with the nbd it can all be done in user space. But that's just a guess. It was clearly done a long time ago

Yes, 1998.

...

My point was just that your talk of viruses and trojans was just so much twaddle.

I know that I exaggerated, and I did it on purpose, because it smells wrong to me. Surely there are other methods in linux to do that. It even complains that the kernel is too modern and thus the script can fail! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuMJVtTMYHG2NR9URApC+AJ9fosoQOQyt7y1fENtbZwbcU11r+ACggWvs U50qzPHVNRHsAFJn1fdz/xQ= =qejd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

23:29

On Monday 18 February 2008 00:25:08 Carlos E. R. wrote:

...

The Sunday 2008-02-17 at 23:40 +0100, Anders Johansson wrote:

...
On Sunday 17 February 2008 23:08:14 Carlos E. R. wrote:

...
See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup.

Sure, but that will only work when you haven't split the disks. losetup doesn't know about split disks

Two disks on the same image, you mean?

No, I mean multiple images for one disk When you create a disk image in vmware, the default is to split it up in 2GB chunks, and I think that would be tricky to handle with losetup Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

23:38

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-18 at 00:29 +0100, Anders Johansson wrote:

...

...
...
Sure, but that will only work when you haven't split the disks. losetup doesn't know about split disks

Two disks on the same image, you mean?

No, I mean multiple images for one disk

When you create a disk image in vmware, the default is to split it up in 2GB chunks, and I think that would be tricky to handle with losetup

Ah! Yes, I remember now that you say it. It make sense for windows vmware on vfat, but not for linux on ext3, so if it asked for that I'd say no, don't split. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuMVdtTMYHG2NR9URAu06AJ9t9CGO3NS7aX+IwOqrdqFD7awPLgCaAj+G DE+m8h58Ep9qbncLLYnFFTs= =mSdy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Greg Freemyer

22:50

On Feb 17, 2008 5:08 PM, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-02-17 at 17:18 +0100, Anders Johansson wrote:

...
...
...
...
What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

Why are you opposed to it?

Because an attempt to modify my network setup without proper explanation is unjustified and unnecessary. I do not see why creating a network device is needed to _mount_ a disk.

It smells of virus or trojan. :-/

Just to make it clear: a network block device is not a network device, it is a way to access a block device (disk) over a network connection

Well, that's better. But I don't see why it needs a network connection to mount a local file.

[...]

Demonstration:

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # file /Reserva/vmware/Virtual\ Machines/Windows\ Me/Windows\ Me-flat.vmdk /Reserva/vmware/Virtual Machines/Windows Me/Windows Me-flat.vmdk: x86 boot sector

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl -p Windows\ Me.vmdk

-------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential --------------------------------------------

Nr Start Size Type Id Sytem -- ---------- ---------- ---- -- ------------------------ 1 63 16771797 BIOS C Win95 FAT32 (LBA)

Offset is 63*512. So:

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # losetup -o 32256 /dev/loop5 Windows\ Me-flat.vmdk

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # file -s /dev/loop5 /dev/loop5: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads 255, hidden sectors 63, sectors 16771792 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 16347, reserved3 0x800000, serial number 0x432917ea, label: "BOOT-VMWARE"

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # mount -o ro /dev/loop5 ../mnt1/ nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # ls ../mnt1/ .windows-label Data PropiedadesSistema.ps autoexec.bat config.bak netlog.txt ut .windows-serial Desinstalados PropiedadesSistemaPorConexion.ps bootlog.prv config.sys nvidia windows 0_Disco_C_hdc1_320.0_GB Images Recycled bootlog.txt gs scandisk.log 0_Notas_Midnight_Comander My Documents WUTemp cabs hp2P.ps setupxlg.txt

See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup.

I think they call that "whistling to your grave", or something like that. Seriously, the above creates a situation where both vmware and suse think they own the drive and are maintaining there own caches, etc. This gets extremely dangerous if they both start making changes. ie. they both can claim an inode for different uses. lots of other issues. So _if_ you want direct access like this, you have to use a CFS (cluster file system). Those are typically implemented via a network!!!! And I don't know any that are multi-OS. I have not followed this thread, so I don't know what vmware is suggesting, but I would just share the drive out of the guest and use NFS or CIFS to mount it on the host. Those are layered protocols that live above the base local filesystem. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

23:12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 17:50 -0500, Greg Freemyer wrote:

...

...
See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup.

I think they call that "whistling to your grave", or something like that.

Seriously, the above creates a situation where both vmware and suse think they own the drive and are maintaining there own caches, etc. This gets extremely dangerous if they both start making changes. ie. they both can claim an inode for different uses. lots of other issues.

No! No, because I make certain that the virtual machine has been stopped first. I know very well I must not make use of the same file structure at the same time from vmware and linux.

...

So _if_ you want direct access like this, you have to use a CFS (cluster file system). Those are typically implemented via a network!!!! And I don't know any that are multi-OS.

I have not followed this thread, so I don't know what vmware is suggesting, but I would just share the drive out of the guest and use NFS or CIFS to mount it on the host. Those are layered protocols that live above the base local filesystem.

That's what I normally use, but it is very slow (in my machine the guest is real slow), and I wanted to run antivir on the disk image and not be waiting a whole day. So I wanted full direct access to the virtual disk - in read only mode, just in case. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuL9mtTMYHG2NR9URAq9cAJ4lmUy1ZdHzyCbIq/QaGgYv/qKFuQCeLfpL K9zyhDmmpe29lRgYPFLWBtc= =WW90 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Greg Freemyer

23:18

On Feb 17, 2008 6:12 PM, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-02-17 at 17:50 -0500, Greg Freemyer wrote:

...
...
See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup.

I think they call that "whistling to your grave", or something like that.

Seriously, the above creates a situation where both vmware and suse think they own the drive and are maintaining there own caches, etc. This gets extremely dangerous if they both start making changes. ie. they both can claim an inode for different uses. lots of other issues.

No! No, because I make certain that the virtual machine has been stopped first. I know very well I must not make use of the same file structure at the same time from vmware and linux.

...
So _if_ you want direct access like this, you have to use a CFS (cluster file system). Those are typically implemented via a network!!!! And I don't know any that are multi-OS.

I have not followed this thread, so I don't know what vmware is suggesting, but I would just share the drive out of the guest and use NFS or CIFS to mount it on the host. Those are layered protocols that live above the base local filesystem.

That's what I normally use, but it is very slow (in my machine the guest is real slow), and I wanted to run antivir on the disk image and not be waiting a whole day.

So I wanted full direct access to the virtual disk - in read only mode, just in case.

Are your vmware virtual drives fully allocated, or did you set them up to grow as needed? If fully allocated, I don't immediately see a problem with what your doing, especially if it is read-only. I have no idea how the"grow as needed" vmware drives are structured, but somehow I doubt a simple loopback device will work. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

23:35

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 18:18 -0500, Greg Freemyer wrote:

...

Are your vmware virtual drives fully allocated, or did you set them up to grow as needed?

This one is fully allocated, which was also a mistake, as I allocated 8GB and I can't reduce it now; at least I don't know if it is possible.

...

If fully allocated, I don't immediately see a problem with what your doing, especially if it is read-only.

I have no idea how the"grow as needed" vmware drives are structured, but somehow I doubt a simple loopback device will work.

Yes, I think so, too. I've been lucky, after all :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuMTPtTMYHG2NR9URAr9BAJ0adxVFJ1o/dbbkkAvbIGIC3k0eQACfXBg9 oULXYD5HJB27q/9CpB6toPw= =W1p0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Aaron Kulkis

18 Feb 18 Feb

00:11

Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

I'm trying the script "vmware-mount.pl" (VMware-server-1.0.4-56528) thus:

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl -p Windows\ Me.vmdk

-------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential ^^^^^^^^^^^^^^^^^^^^^^^^^^^ --------------------------------------------

Nr Start Size Type Id Sytem -- ---------- ---------- ---- -- ------------------------ 1 63 16771797 BIOS C Win95 FAT32 (LBA)

So, the disk is recognized. I try to mount it:

nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl Windows\ Me.vmdk 1 ../mnt1/

-------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential ^^^^^^^^^^^^^^^^^^^^^^^^^^^ --------------------------------------------

It has been reported that this program does not work correctly with 2.4+ Linux kernels in some cases, and you are currently running such a kernel. Do you really want to continue? [N] Y

No Network Block Device detected.

There is no Network Block Device defined on this machine. This script is about to create the /dev/nb0 Network Block Device. Continue? [Y] N

Unable to continue.

What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?

And wanting a kernel <= 2.4... Yicks!

Carlos E. R.

22:57

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 19:11 -0500, Aaron Kulkis wrote:

...

...
And wanting a kernel <= 2.4... Yicks!

Copyright 1998 says it all. Why don't you get a new version of this software?

Because, believe it or not, it is the newest! I downloaded it the same day I posted, upgrading to 1.0.4 from 1.0.3: nimrodel:~ # rpm -q -f `which vmware-config.pl` VMware-server-1.0.4-56528 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHug1rtTMYHG2NR9URAhz/AJ9AdHKFLrNCb67eHXHTNxx0ikK9xwCfffAe Jgaqse+E1HNMCUVz4v4f3Ew= =n2fJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kai Ponte

23:17

On Monday 18 February 2008 02:57:45 pm Carlos E. R. wrote:

...

The Sunday 2008-02-17 at 19:11 -0500, Aaron Kulkis wrote:

...
...
And wanting a kernel <= 2.4... Yicks!

Copyright 1998 says it all. Why don't you get a new version of this software?

Because, believe it or not, it is the newest!

I downloaded it the same day I posted, upgrading to 1.0.4 from 1.0.3:

nimrodel:~ # rpm -q -f `which vmware-config.pl` VMware-server-1.0.4-56528

I wouldn't be suprised if VMWare server wants a 2.4 kernel. Aren't many of the "enterprise" systems still on the 2.4 kernel even today? I know VMWare workstation and player work fine on the 2.6 kernel. I just used Player today to launch my corporate XP image to get some work done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

23:26

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-18 at 15:17 -0800, Kai Ponte wrote:

...

On Monday 18 February 2008 02:57:45 pm Carlos E. R. wrote:

...
The Sunday 2008-02-17 at 19:11 -0500, Aaron Kulkis wrote:

...
...
And wanting a kernel <= 2.4... Yicks!

Copyright 1998 says it all. Why don't you get a new version of this software?

Because, believe it or not, it is the newest!

I downloaded it the same day I posted, upgrading to 1.0.4 from 1.0.3:

nimrodel:~ # rpm -q -f `which vmware-config.pl` VMware-server-1.0.4-56528

I wouldn't be suprised if VMWare server wants a 2.4 kernel. Aren't many of the "enterprise" systems still on the 2.4 kernel even today?

No, the server machine is very happy with kernel 2.6. As it compiles two or three kernel modules, I don't think it would be very happy to see the wrong kernel version. No, it is that script that has not been mantained in ages.

...

I know VMWare workstation and player work fine on the 2.6 kernel. I just used Player today to launch my corporate XP image to get some work done.

So does the server version. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuhRGtTMYHG2NR9URAvx2AJ4mKRmCwO3LbGubJHjJVexnDcDTEQCcC9KR yKiHA+17N7P5/rfAPl80yx8= =z0nr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kai Ponte

19 Feb 19 Feb

00:14

On Monday 18 February 2008 03:26:59 pm Carlos E. R. wrote:

...

No, the server machine is very happy with kernel 2.6. As it compiles two or three kernel modules, I don't think it would be very happy to see the wrong kernel version.

No, it is that script that has not been mantained in ages.

vmware-config.pl? Oh. I find it rather bizarre that I have to run it every time I upgrade my kernel. i notice this isn't the issue with Virtual Box. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

01:13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-18 at 16:14 -0800, Kai Ponte wrote:

...

On Monday 18 February 2008 03:26:59 pm Carlos E. R. wrote:

...
No, the server machine is very happy with kernel 2.6. As it compiles two or three kernel modules, I don't think it would be very happy to see the wrong kernel version.

No, it is that script that has not been mantained in ages.

vmware-config.pl? Oh.

Oops! Sorry, no, my mistake. It is "vmware-mount.pl"; although both have the same copyright date, it is the second one that complains of the kernel version: if (Kernel_RunningVersion() >= Kernel_MakeVersion(2, 4, 0)) { my $ans; $ans = query("It has been reported that this program does not work correctly with 2.4+ Linux kernels in some cases, and you are currently running such a kernel. Do you really want to continue?", "N"); if ($ans !~ /^[yY]/) { print wrap("\nAborted.\n"); exit(0); } } - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHui1LtTMYHG2NR9URAjPJAJ9IUoNQHM/xAOx4JGMfcS+SV7uf5QCfQefz t2TTZJEh+wRNqtVdvI0+wDY= =juxf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jonathan Ervine

02:39

On Tuesday 19 February 2008 08:14:47 Kai Ponte wrote:

...

On Monday 18 February 2008 03:26:59 pm Carlos E. R. wrote:

...
No, the server machine is very happy with kernel 2.6. As it compiles two or three kernel modules, I don't think it would be very happy to see the wrong kernel version.

No, it is that script that has not been mantained in ages.

vmware-config.pl? Oh.

I find it rather bizarre that I have to run it every time I upgrade my kernel. i notice this isn't the issue with Virtual Box.

Ummm - why should it be bizarre to run a script that compiles kernel modules every time the kernel is upgraded. This ensures that the modules load cleanly in the new kernel. It would be impractical to ship these modules as binaries for _every_ shipping kernel, so VMware provide a script that allows the user to compile them for their running kernel. And very well it seems to work too. Also, isn't running /etc/init.d/vboxdrv setup (or whatever the command is) doing exactly the same process for VirtualBox? The copyright notice on a specific script/source code is no indication as to when it has last been modified/changed. Shock: the /etc/inittab file has copyright 1996-2002 written in it. The vmware-config.pl file has copyright 1998-2007 written. Anyone want to make a wild guess as to when the scripts were originally written and the last update made? Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

02:49

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-02-19 at 10:39 +0800, Jonathan Ervine wrote:

...

...
...
No, it is that script that has not been mantained in ages.

vmware-config.pl? Oh.

I find it rather bizarre that I have to run it every time I upgrade my kernel. i notice this isn't the issue with Virtual Box.

Ummm - why should it be bizarre to run a script that compiles kernel

Hold on, it seems you didn't see my email in which I said the problem script is not 'vmware-config.pl' but 'vmware-mount.pl'

...

The copyright notice on a specific script/source code is no indication as to when it has last been modified/changed. Shock: the /etc/inittab file has copyright 1996-2002 written in it. The vmware-config.pl file has copyright 1998-2007 written. Anyone want to make a wild guess as to when the scripts were originally written and the last update made?

No, the problem is not simply the copyright notice. The problem is that the script complains that the kernel is newer than 2.4 and that is known to be problematic. It's a kernel too new for the script. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHukOytTMYHG2NR9URAsuKAJ9IIFLUYU26pm2dLgVF+FMz6wt0jACeLCcA FEiJ4M+c6WvvIqB+FHjhUAo= =59tu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jonathan Ervine

04:31

On Tuesday 19 February 2008 10:49:12 Carlos E. R. wrote:

...

The Tuesday 2008-02-19 at 10:39 +0800, Jonathan Ervine wrote:

...
...
...
No, it is that script that has not been mantained in ages.

vmware-config.pl? Oh.

I find it rather bizarre that I have to run it every time I upgrade my kernel. i notice this isn't the issue with Virtual Box.

Ummm - why should it be bizarre to run a script that compiles kernel

Hold on, it seems you didn't see my email in which I said the problem script is not 'vmware-config.pl' but 'vmware-mount.pl'

Apologies - I first checked on my test system, running VMware server 2 beta. You'll no doubt be delighted to know that the perl script has been replaced with a vmware-mount binary file there.

...

...
The copyright notice on a specific script/source code is no indication as to when it has last been modified/changed. Shock: the /etc/inittab file has copyright 1996-2002 written in it. The vmware-config.pl file has copyright 1998-2007 written. Anyone want to make a wild guess as to when the scripts were originally written and the last update made?

No, the problem is not simply the copyright notice. The problem is that the script complains that the kernel is newer than 2.4 and that is known to be problematic. It's a kernel too new for the script.

The script warns that it has been reported that it can be problematic in some cases. Still seems to mount the disk images just fine though. I can't help but feeling you're making a crisis out of a minor drama here. Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

11:13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-02-19 at 12:31 +0800, Jonathan Ervine wrote: ...

...

...
Hold on, it seems you didn't see my email in which I said the problem script is not 'vmware-config.pl' but 'vmware-mount.pl'

Apologies - I first checked on my test system, running VMware server 2 beta. You'll no doubt be delighted to know that the perl script has been replaced with a vmware-mount binary file there.

I saw the beta, but I didn't feel up to testing it right now. Does it work well? Faster? More features? Mine uses a lot of cpu even when doing aparently nothing.

...

...
No, the problem is not simply the copyright notice. The problem is that the script complains that the kernel is newer than 2.4 and that is known to be problematic. It's a kernel too new for the script.

The script warns that it has been reported that it can be problematic in some cases. Still seems to mount the disk images just fine though. I can't help but feeling you're making a crisis out of a minor drama here.

Could be I'm oversensitive to things I don't understand, like installing a network device to mount a file. The warning about the kernel coupled with that, made me jump. I made do with a simple losetup call, anyway. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHurnCtTMYHG2NR9URApzsAJ400zCI51Vawj/ITThaGZ9JEeP2uACcDpOp HhZKiIRnXlbOYRp8wLkVxzw= =T0a6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jonathan Ervine

20 Feb 20 Feb

02:19

On Tuesday 19 February 2008 19:13:06 Carlos E. R. wrote:

...

The Tuesday 2008-02-19 at 12:31 +0800, Jonathan Ervine wrote:

...

...
...
Hold on, it seems you didn't see my email in which I said the problem script is not 'vmware-config.pl' but 'vmware-mount.pl'

Apologies - I first checked on my test system, running VMware server 2 beta. You'll no doubt be delighted to know that the perl script has been replaced with a vmware-mount binary file there.

I saw the beta, but I didn't feel up to testing it right now. Does it work well? Faster? More features?

Mine uses a lot of cpu even when doing aparently nothing.

I'd say the beta is slower and more of a resource hog, but I think it's a 'proper' beta with debug code included. As per my other mail in reply to Sunny, I think they're looking to put some distance between Workstation and Server with this release. In some respects this won't suit everyone, but then maybe they found Server was cannibalising sales of Workstation with the current situation. Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sunny

19 Feb 19 Feb

15:15

On Feb 18, 2008 10:31 PM, Jonathan Ervine wrote:

...

Apologies - I first checked on my test system, running VMware server 2 beta. You'll no doubt be delighted to know that the perl script has been replaced with a vmware-mount binary file there.

What are your observations/comments on beta 2? AFAIC they removed the server-console, and replace it with some web UI. How does it perform? -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jonathan Ervine

20 Feb 20 Feb

02:16

On Tuesday 19 February 2008 23:15:32 Sunny wrote:

...

On Feb 18, 2008 10:31 PM, Jonathan Ervine wrote:

...
Apologies - I first checked on my test system, running VMware server 2 beta. You'll no doubt be delighted to know that the perl script has been replaced with a vmware-mount binary file there.

What are your observations/comments on beta 2? AFAIC they removed the server-console, and replace it with some web UI. How does it perform?

The server-console has been replaced with a web UI which seems pretty nice. It does however run on top of tomcat, so there is an added load onto the VMware server itself which I'm sure some will see as something they don't want. The remote console is now handled by a plugin for both Firefox and Internet Explorer. I've not been able to get the plugin to install into Firefox on Linux yet. I've tried the various versions that shipe with openSUSE 10.3 as well as the betas of 3. The installation never seems to take hold though. I've been able to install the plugin into IE through Crossover on Linux, only to see the utilisation of vm-debug (or something named like that) shoot up to ~95% CPU and IE and VMware become unresponsive. I was only testing on a 1GB of RAM test system, so may not have had enough RAM for the host and guest together. They seem to be putting a bit of distance between VMware Server and VMware Workstation with this release, and at the moment it is still beta software. However, it does look pretty good, and I do like the move to the web UI (so long as the plugins for various browsers end up working of course) Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sunny

05:02

On Feb 19, 2008 8:16 PM, Jonathan Ervine wrote:

...

They seem to be putting a bit of distance between VMware Server and VMware Workstation with this release, and at the moment it is still beta software. However, it does look pretty good, and I do like the move to the web UI (so long as the plugins for various browsers end up working of course)

Thanks for the info Jonathan. I still wonder how they protect their Workstation sales by crippling the server, as one can always use the server to build the VM and then the player to use it. For what I hear from you, it just makes troubleshooting a problematic systems booting a lot harder and slow, than using the console, and that's all. Anyway, I I'm barking at the wrong place :) Cheers, and thanks again Sunny -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kai Ponte

19 Feb 19 Feb

03:27

On Monday 18 February 2008 06:39:43 pm Jonathan Ervine wrote:

...

Ummm - why should it be bizarre to run a script that compiles kernel modules every time the kernel is upgraded.

...simply because I fail to see why a third-party application would need to be linked so tightly to the kernel. IMO, they should be abstracted, unless they're a hardware driver or a memory module. Same goes for the cisco vpn client. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jonathan Ervine

04:16

On Tuesday 19 February 2008 11:27:27 Kai Ponte wrote:

...

On Monday 18 February 2008 06:39:43 pm Jonathan Ervine wrote:

...
Ummm - why should it be bizarre to run a script that compiles kernel modules every time the kernel is upgraded.

...simply because I fail to see why a third-party application would need to be linked so tightly to the kernel.

IMO, they should be abstracted, unless they're a hardware driver or a memory module.

Abstracted how? VMware and other virtualisation techniques have to make sure that each running VM doesn't try and access the same resources simultaneously. In order to do this they have to interact with the kernel. This involves creating network interfaces and monitoring the memory and processor requests etc. There's no way round this (yet) without requiring kernel modules. I don't think even the VMI code being put into the kernel will get away from this in the near future.

...

Same goes for the cisco vpn client.

Can't say I know the Cisco VPN client, but I imagine it uses IPsec and is also making use of network devices. For the same reason as above this requires an interface to the kernel and/or a new device being created. Not too sure how you propose doing that without requiring a kernel module. Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Aaron Kulkis

03:23

Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2008-02-17 at 19:11 -0500, Aaron Kulkis wrote:

...
...
And wanting a kernel <= 2.4... Yicks!

Copyright 1998 says it all. Why don't you get a new version of this software?

Because, believe it or not, it is the newest!

I downloaded it the same day I posted, upgrading to 1.0.4 from 1.0.3:

nimrodel:~ # rpm -q -f `which vmware-config.pl` VMware-server-1.0.4-56528

WOW! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

5917

Age (days ago)

5920

Last active (days ago)

List overview

Download

32 comments

8 participants

participants (8)

Aaron Kulkis
Anders Johansson
Carlos E. R.
Greg Freemyer
Jonathan Ervine
Kai Ponte
kanenas＠hawaii.rr.com
Sunny