Say a host has 64GB of memory and vms are using up to 60GB for example.
Does it mean I can still use the rest of the 4GB?
What I mean is, does the host take what ever it needs and what ever is left is what is given to the vms to share?
If I max out the memory beyond sharing it between vms, can the host end up crashing?
Thanks for your response. No specific error message. I think it would be much easier to script an install of the client if I had an MSI that I could use MSI switches with. The software deployment console I'm using has been tailored to make MSI installs a breeze, and in turn has made EXE installs a little clunkier. That's no fault of VMware of course, and I'm not saying that it is. I'm just wondering what the reason is for not providing an MSI (additionally restricting the ability to extract the contents of the EXE and pull out an MSI), when most other software makers provide an MSI, if not both an MSI and an EXE.
FWIW, it appears I'd filed SR #1575281151 on this.
-Andrew
Hello
Thank you for the come back.
>Open Suse leap 42 is not supported with vmware Workstation 12.5.7.
You are indeed correct that openSUSE LEAP 42.3 (which will be released in 6 days*) and which is currently on kernel 4.4.76-1-default** is not supported on the lastest build of VMware Workstation (which was 12.5.7 build-5813279.x86_64 as of 10 days ago).
[*] URL: openSUSE News
cat /etc/os-release
NAME="openSUSE Leap"
VERSION="42.3"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.3"
PRETTY_NAME="openSUSE Leap 42.3"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.3"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
[**]
uname -a
Linux hero 4.4.76-1-default #1 SMP Fri Jul 14 08:48:13 UTC 2017 (9a2885c) x86_64 x86_64 x86_64 GNU/Linux
This is exactly the reason ***why*** I created this thread - I am an early adopter and I use vmware Workstation on linux.
Please note that vmware Workstation has been supported on openSUSE LEAP 42.2 for ages. I would have raised an issue here for all and any problems if it wasn't.
According to my records, the last vmware Workstation update for linux was in ~Dec 2015. At that least that was the last time I paid to update my vmware Workstation licence.
virtualbox-5.1.22-20.2.x86_64 works on openSUSE LEAP 42.3, the problem is that my linux setup is adapted to vmware Workstation and I am lazy. At least for now.
The bottom line is that :
1) I would like to run vmware Workstation on openSUSE Leap 42.3 but both vmnet-only and vmmon-only modules error out when compiling
2) no one in my house uses Windows except under vmware because I have the choice.
The second point isn't going to change - I am keeping my fingers crossed however, and hoping that the first point will change soon : choice is good.
TIA
Regards
James
I need disconnect from View session without locking Windows. Is it possible?
Have a look at this Re: Kernel 4.6 - VmPlayer 12 - vmnet & vmmon compilation failure which appeared on "More Like This" panel on the right hand side.
Actually, Fusion doesn't "change" it to a bootable media..
it copy's the app to a "temp" folder within the Virtual machine *.vm package on host..
it then creates a second VM hard drive and copy's the installation to "it" You can see this if you edit virtual machine settings, gi to "Hard drive" there will be two listed.. One, being the installation as it will be small capacity and bootable. This second disk will be removed after install has completed.
I get the same "cannot create media" error, if for example, its VM is created from an external drive/ NAS, that get disconnected.
actually looks like i got this one sorted.. Over on another post i saw abut keeping Network disabled and booting up... that worked.
Welcome to the Community,
The descriptor file seems to be ok, although I'd suggest you remove the "ddb.longContentID" entry (even though you added the "#") from it to avoid confusion.
Anyway, since the descriptor seems to be ok, you may need to check the sparse files for errors. A first quick check would be to see whether these files start with "KDMV" (reverse of "VMDK"). Often issues like yours is related to file corruption in recovered .vmdk files.
Some time ago I posted an XLS file with a macro, which checks .vmdk files (see Re: Corrupt redo log freezing VM). Maybe this helps.
André
Hello,
Have a Win-10 x64 VM in Workstation 12.5.2 and installed Win-10 updates today. After updates got installed, machine needed a reboot and from that point onwards it is stuck at VMWare boot screen, does not even get to loading Windows, keeps LOOPING at this screen
Attached is screenshot
Any suggestions?
Thanks,
Saludos.
Mira el siguiente documento, puede ser lo qeu necesitas, el tema de licenciamiento de Windows en una
server físico es igual en una VM.
Windows Server 2012: Cambiar Standard a Datacenter (Legal) | WindowServer
Hi janasrs,
Thank you for the log file. I'm pretty sure that the following bit of the log explains the behavior you're seeing:
ExportFiles: Processing folder '<Desktop>' (part of Windows Settings\Windows Explorer.INI)
The screenshot of Copy of WinSCP-quicklaunch.xml that you included at the start of this thread shows that that shortcut was created on the desktop, so at some point the shortcut ended up in the Windows Explorer profile archive (which means that it will "come back" at the next logon, when that user profile archive is imported).
Undo actions are performed after exporting, so even if the shortcut was configured for undo at logoff at that time, it would have ended up in the profile archive. There is no one-size-fits-all solution to deal with the scenario where you both want to dynamically create shortcuts on the desktop and save all the files from the desktop, but there are a few options for this that we can discuss separately.
In the meantime, a few other observations:
And a few suggestions:
When using the REST API to log into vCloud, I get 401 Unauthorized. I have tried passing my username and password via Basic authentication, and have tried my username in both all-uppercase and all-lowercase. The documentation says I need to use USERNAME@ORGANIZATION so I wonder if I need to find my ORGANIZATION name in vCloud. Where do I find that? I do see a name at the very top of the browser window after logging in, but it is very long and has spaces, so I'm not sure that is the correct name to use.
Thank you for the reply. I removed the "ddb.longContentID" long ago, just decided to keep it in the uploaded file.
What file size should I specify in the macros? The one it calculates automatically or the real size of the virtual machine's disk? With the automatically calculated size it says "Invalid MagicNumber" for all files. Does it mean they are corrupted?
So to give an update on this. I have a ticket opened with the same issue 17505719607. I have gotten with one of the Appvolumes Developers and he found the issue and is working on including the fix on the next Appvolumes release. It seems like the workaround in the mean time is to remove the Ldap load balancer VIP and enter the DC manually. This is on 2.12.1 of appvolumes.
My vCenter server is 6.0 and I am trying to bring in a host with version 6.5 and I get the above error.
Do I need to down grade my host to v6.0?
Hello
Thank you for the comeback.
I will check out what you suggested and report back.
In the meantime I just installed VMware-Workstation-Full-e.x.p-6056110.x86_64.bundle in order to see what would happen...
When I try to compile the vmnet module on the e.x.p version - it fails
The vmmon module complies OK
The error when I compile the vmnet module follows...
^
/tmp/vmware/source/vmnet-only/netif.c:468:4: note: in expansion of macro ‘compat_netif_trans_update’
compat_netif_trans_update(dev);
^
/usr/src/linux-4.4.76-1/scripts/Makefile.build:259: recipe for target '/tmp/vmware/source/vmnet-only/netif.o' failed
make[4]: *** [/tmp/vmware/source/vmnet-only/netif.o] Error 1
/usr/src/linux-4.4.76-1/Makefile:1428: recipe for target '_module_/tmp/vmware/source/vmnet-only' failed
make[3]: *** [_module_/tmp/vmware/source/vmnet-only] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make[1]: *** [__sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-4.4.76-1-obj/x86_64/default'
Makefile:120: recipe for target 'vmnet.ko' failed
make: *** [vmnet.ko] Error 2
Finished compiling the vmnet module...
ls: cannot access 'vmnet.o': No such file or directory
Copying the vmnet module to /lib/modules/4.4.76-1-default/kernel/drivers/misc/...
cp: cannot stat './vmnet.o': No such file or directory
Below is what I get when I stop / start the VMware services...
Restarting vmware...
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family done
Blocking file system done
Virtual ethernet failed
VMware Authentication Daemon done
All comments welcome !
TIA
Regards
James
Just verified that the host is on the subnet mask as another ESXi host that is connected to VCenter.
Interesting... Our devs are watching this forum so we'll get a bug filed.
Standard display monitor or 4K?
1920 x 1080