Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.electronics.design > #451625

Re: VMware v VirtualBox

Show all headers | View raw

Am 13.03.2017 um 15:21 schrieb bitrex:
> On 03/12/2017 05:23 PM, Don Y wrote:
>
>> There's also the choice of whether to use a vdisk or a *physical* disk
>> for the OS (on one of my machines, I use hot-swappable drives as a
>> quick and dirty way to just "pick" the guest OS).  And, I think there is
>> an upper limit on the size of the disks that you can support (though
>> I tend to want small disks as each machine is really only created for
>> some
>> specific task instead of as a "general workstation" -- which might need
>> gobs
>> of space for applications)
>
> One thing I learned the hard way is that with one particular application
> I had to save any work I did to a shared folder on the host OS -
> sometimes when I saved work from it to the vdisk, restarted the virtual
> machine and attempted to open the file I'd find that it had been corrupted.
>
> This happened under both VMWare and VirtualBox, so I think it has
> something to do with a peculiarity in the way that particular Windows
> app writes files.

I think this is related to the shutting down mode of the newer Windows
versions. By default, they do not switch off completely but enter only
some Zombie state where some buffers are not flushed.
I have forgotten how it is done, but it can be changed.

I moved from VirtualBox to VMware because at that time (2 or 3
years ago) they had better USB support for virtual machines.
I needed it for a tiny but excellent vector network analyzer.
(that is not superfluous even sitting next to my VNB-8)

It was possible to transport VMs from Virtual box to VMware without
problems using this open virtual machine format.

regards, Gerhard

<  http://sdr-kits.net/VNWA3_Description.html  >

Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-11 22:34 -0700
  Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-12 11:39 -0400
    Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-12 12:38 -0700
      Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-12 15:51 -0400
        Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-12 14:23 -0700
          Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-13 10:21 -0400
            Re: VMware v VirtualBox Gerhard Hoffmann <ghf@hoffmann-hochfrequenz.de> - 2017-03-13 16:57 +0100
            Re: VMware v VirtualBox Jon Elson <jmelson@wustl.edu> - 2017-03-13 17:37 -0500
              Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-13 17:20 -0700
    Re: VMware v VirtualBox Martin Riddle <martin_ridd@verizon.net> - 2017-03-12 16:08 -0400
  Re: VMware v VirtualBox bitrex <bitrex@de.lete.earthlink.net> - 2017-03-12 15:37 -0400
  Re: VMware v VirtualBox Jasen Betts <jasen@xnet.co.nz> - 2017-03-13 11:18 +0000
  Re: VMware v VirtualBox Jon Elson <jmelson@wustl.edu> - 2017-03-13 17:33 -0500
    Re: VMware v VirtualBox Don Y <blockedofcourse@foo.invalid> - 2017-03-14 09:42 -0700

csiph-web