Unable to import Virtual PC VM in workstation 10 (Error message "failed to import") ?
Unable to import Virtual PC VM in workstation 10 (Error message "failed to import") ?
Unable to boot and install the OS on VMWare Workstation 9
Hi,
I have installed Workstation 9.
When I tired to run CentOS 6.5 64bit.iso, I got the following error message:
Network boot from Intel E1000
Client MAC ADDR: 00 0C....
PXE-E53:No boot filename received
PXE-MOF:Exiting Intel PXE ROM
Operating system not found
I have reinstalled Workstation 9 and they run as an administrator but the issue is the same.
Attached screenshot of Virtual Machine settings.
TIA !
Can someone help me select a cpu and other hardware for a Virtual machine rig/server?
Hey everyone, I'm looking to run about 20 virtual machines off one rig. I plan or hope to run windows 7 on each virtual machine, so I'm looking for 2 gigs of ram and 1 core with 2 threads per each machine?
Currently my i7 930 @ 3.7 ghz can only run 5 machines with 15% cpu usage per virtual machine. I was really wondering what kind of cpu it would take to run about 15-20 on one machine? Would I need to build around a server cpu for more logical processors?
I don't know much about server cpus and their abilities or limitations, if I did need one could someone help recommend one that would suit the needs for this task?
I also read that to run each virtual machine optimally I would need to allocate at least 40 gigs of hard drive per virtual machine running under windows 7 os? If I only use about 20 gigs max on the virtual machine, would I really still need 40 gigs per machine?
Any help is much appreciated
VMware WS install on a btrfs partition?
I've beeen looking around (albeit not exhaustively) for any information on installing WS on a btrfs partition. Has anybody tried this? Is it posssible?
Changing the VMnet8 network adapter configurations
HI,
I have VMWare Workstation 9 running on my Windows 7 host. I have 2 virtual machines: Windows Server 2012 and Windows 8.
The 2012 Server is a configured Domain Controller which has DHCP and DNS services.
Now I am using the VMnet8 adapter for the 2 VMs. I have disabled DHCP from the adapter due to having a DHCP service on the 2012 Server.
The 2012 Server has a static IP address of 192.168.197.3 (where 197 is the "net" value in VMnet8). The Server is configured correctly with DNS and DHCP (Router and DNS IP address are 192.168.197.2).
When I try to connect the Windows 8 VM to the domain, I get a "active directory domian controller could not be contacted, etc" error?
Can I use the VMnet8 configuration by disabling the DHCP, and allowing the DC to do it itself?
Hope this is clear.
Thanks.
This host does not support Intel VT-x.
Re: This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible. This host does not support Intel VT-x.
Please is there any solution to this problem? I am using HP G61-100sa. it can work with 32-bit guest but not 64.
i am trying to install Windows Server 2012 and Vmware version 10 and I got this error message. Is there any software solution?
Deleted VM still takes up HDD space
Hi everyone,
I recently deleted a VM but it looks like it could still be taking up space on my external drive. How can I go about fixing this?
Thanks
OEM Windows 7 Installation Problems.
I'm having issues with the OEM licence code on a Windows 7 Machine in that when installing using the OEM Dell Windows 7 disk, VMWare does not seem to allow the installer to see that there is an OEM key embeded in the bios.
For history, the machine in question is a Dell Precession T1700, that has a Windows 8 Pro OEM licence, which came with Windows 7 Pro Downgrade preinstalled by Dell.
Within our research department, we always have a Linux host, and install WIndows in a virtual using VMWare Player.
Previously on machines that came with a Windows 7 sticker on them, I;ve been able to install and enter the key as specifed then activate windows afterwards, even if done over the phone.
Now I cannot do that as the OEM install disk, that works fine installing on the machine directlly correctlly knows it is a Dell PC and doesn't ask for a key or activation.
I have fond information that says to add the option SMBIOS.reflectHost = TRUEto the VMX file of the virtual prior to install but this does not seem to work.
I've also tried grabbing the key for windows 7 after installing directlly and then trying this in the vitual and this will not work as windows complains that this key is not valid for activation.
I've also tried running this in the trial of Workstation to no avail.
I've resigned myself to the fact that I will have to buy a VL key for windows 7 to do this now.
Does anyone have any experience of this or have any way round this?
Marc
VM Isolation, but with Internet Access
Greetings all,
I am needing to grant one of my VMs internet access while completely isolating it from the host. I don't want the VM to interact with the host in anyway.
How would I go about getting this accomplished.
Thank you all in advance for your assistance.
Virtual Ethernet is missing
Networking In VMWare Workstation 10.0.2
Hey Everyone,
I need to establish a network between a ubuntu host and three virtual machine such that every device connects to every other device in the network.How can this be done.
Also I want to know if it is possible to connec amore than two Virtual machines via a virtual switch (say vmnet2) in custom networking.
Please help
Thanks.
Ethernet controller shows yellow under device manager in Windows server 2012 Standard installed in VMware Workstation 10.0.2.
Hello,
I have installed Windows server 2012 Standard smoothly in VMware Workstation 10.0.2. and after that i installed succesfully the vmware tools.
Before the installation of server 2012 i have added second Network adapter. I need this because of my course.
After these all, i saw under device manager that Ethernet controller shows yellow. After that another yellow sign shows under usb: Standard Universal PCI to USB Host Controller. I tried to update the drivers but the windows can't find any driver.
Does anyone know what the problem might be?
VMWare Workstation 10 - jerky and unresponsive under load. [UPDATED: DisplayFusion possible cause] [SOLVED: DisplayFusion settings]
I've got a problem with certain VMWare Workstation guests, whereby the mouse and keyboard in the VM becomes unresponsive for a second or two when under load. The mouse cursor will halt, or jerk around the screen, and once the load has passed will generally shoot to some other part of the screen. Similarly the keyboard will become unresponsive, but when the load passes it will have a tendency to double/triple type whatever characters were being typed during the slow down.
I use these VMs mainly for programming and a good example of the guest being "under load" is when I am compiling; this is both a heavy CPU load and an IO load.
Both my 64bit Windows 8 and Windows 8.1 guest behave in this way, although an older Windows 2003 R2 guest does not.
The VMs are configured with either 2GB or 4GB, all of which is set to fit into host (which has plenty free). The VMs and disks are on one of two SSD drives. They are both configured for multiple monitor use. In both cases there is a primary 60GB virtual disk, preeallocated and not split, and a 10GB virtual disk, preallocated, not split and set as independent.
I've tried a number of tweaks, including having the 3D acceleration on and off, manually overriding the CPU virtualisation settings in VMWare and I've tried all of the following settings (together and separately), none of which have fixed the problem:
svga.vramSize = 134217728
mainMem.useNamedFile = "FALSE"
sched.mem.pshare.enable = "FALSE"
prefvmx.useRecommendedLockedMemSize = "TRUE"
mainmem.backing = "swap"
isolation.tools.unity.disable = "TRUE"
If I connect using RDP to these machines, rather than use the Workstation console, I don't get the problem and there isn't any particularly noticeable slowdown in performance
I had this behaviour previously in Workstation 9, but the upgrade to 10 has not made any difference.
Does anyone have any recommendations for investigating or fixing this issue - it is rendering the VMs useless for software development which is their primary use?
Thanks in advance for any advice or help.
My host system is as follows:
Mobo: ASUS P8Z68-V PRO
CPU: Intel i7 2600K
RAM: 16GB
Video: Nvidia 580 for 2 monitors, inbuilt Intel SandyBridge for third.
HDD: guests on Samsung 840 Pro SSD, Crucial CT128 M225 SSD, Western Digital 2TB HDD
Host OS: Windows 7 x64
[SOLVED]
Thanks to Keith Lammers in this thread on the DisplayFusion website.
It seems that enabling the Processor Affinity option in DIsplay Fusion's Advanced Setttings makes the problem disappear.
VMware Workstation 10:Operating System Not found
Hi,
Iam new to VMware and when i try to power on the machine,i got the operating system not found error.I tried some solutions in this community but
the problem still occurs.It detect windows 98 at first but after being powered on it just says operating system not found.Please help me.
Thanks
Workstation 10: Bridged modus extremely slow / unusable on Intel i217 NIC
Hello all,
I have a Dell Latitude E6540 notebook with Vmware Workstation 10 running under Windows 8.1 64 bit. The notebook has an Intel i217 NIC.
In my 64-bit Windows-7 virtual machine, "bridged" networking is totally unusable. It's extremely slow (0.1 megabytes/sec) and I get tcp-related timeouts all the time. I'm talking about tcp connections into our local network (SQL server) here, so it's not a gateway issue. As soon as I switch to NAT networking the problem disappears completely and I get full bandwidth !!! My previous notebook (also a Dell, with a different NIC) didn't have any of these issues. I think it is related to the Intel network card. I have already downloaded and installed the latest i217 drivers directly from Intel's website but it doesn't change anything.
Does anybody have an idea how I can get decent performance using bridged networking on my computer?
Kind regards,
Arthur Hoornweg
Workstation 10.0.2 exceptionCode 0xc0000005 changing CDROM ISO
I'm evaluating workstation 10.0.2. Created a Windows 2003 R2 VM and got everything installed. When windows was booted and at the desktop prompting for CD#2, I swapped ISO images for the CRDOM in vmware settings. Then vmware crashed.
Crash text and log attached.
In case others run into this problem, the relevant sections from the log:
2014-05-29T14:55:18.510-07:00| vmx| W110: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
2014-05-29T14:55:18.510-07:00| vmx| W110: ExceptionAddress 0x13fc12a63 eflags 0x00010297
2014-05-29T14:55:18.510-07:00| vmx| W110: rwFlags 0 badAddr 0
2014-05-29T14:55:18.510-07:00| vmx| W110: rax 0x335da0 rbx 0x20f040 rcx 0x3c9ac78
2014-05-29T14:55:18.510-07:00| vmx| W110: rdx 0x335da0 rsi 0xca rdi 0x3c9abd0
2014-05-29T14:55:18.510-07:00| vmx| W110: r8 0 r9 0xfffffffffc365388 r10 0x2
2014-05-29T14:55:18.510-07:00| vmx| W110: r11 0x8101010101010100 r12 0x1 r13 0
2014-05-29T14:55:18.510-07:00| vmx| W110: r14 0x20f3a0 r15 0
2014-05-29T14:55:18.510-07:00| vmx| W110: rip 0x13fc12a63 rsp 0x20efb0 rbp 0x3c9abd0
2014-05-29T14:55:18.510-07:00| vmx| W110: LastBranchToRip 0 LastBranchFromRip 0
2014-05-29T14:55:18.510-07:00| vmx| W110: LastExceptionToRip 0 LastExceptionFromRip 0
2014-05-29T14:55:18.510-07:00| vmx| W110: The following data was delivered with the exception:
2014-05-29T14:55:18.510-07:00| vmx| W110: -- 0
2014-05-29T14:55:18.510-07:00| vmx| W110: -- 0
2014-05-29T14:55:18.510-07:00| vmx| W110: CoreDump: Writing minidump to D:\Virtual Machines\2003R2\vmware-vmx-1328.dmp
<snip>
2014-05-29T14:55:18.613-07:00| vmx| I120: backtrace[00] frame 0x0020efa8 IP 0x13fc12a63 params 0x13fb5ec99 0x20f079 0x65446d65ffffffff 0x3c9abd0 opus_decoder_destroy + 0xbcc53 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x00141a63]
2014-05-29T14:55:18.614-07:00| vmx| I120: backtrace[01] frame 0x0020f030 IP 0x13fd71dd7 params 0x3c9abd0 0x3c9abd0 0x3426d50 0x4bb00090015 opus_decoder_destroy + 0x21bfc7 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x002a0dd7]
2014-05-29T14:55:18.614-07:00| vmx| I120: backtrace[02] frame 0x0020f070 IP 0x13fc406d2 params 0x20f200 0x1401be9d0 0x3426d50 0 opus_decoder_destroy + 0xea8c2 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x0016f6d2]
2014-05-29T14:55:18.614-07:00| vmx| I120: backtrace[03] frame 0x0020f0b0 IP 0x13fb72c1f params 0 0x1 0xa 0 opus_decoder_destroy + 0x1ce0f [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x000a1c1f]
2014-05-29T14:55:18.614-07:00| vmx| I120: backtrace[04] frame 0x0020f340 IP 0x13fbb2530 params 0x3c64ac0 0x4fd360f0 0x3c64ac0 0x3c64ac0 opus_decoder_destroy + 0x5c720 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x000e1530]
2014-05-29T14:55:18.614-07:00| vmx| I120: backtrace[05] frame 0x0020f590 IP 0x13fbb79b4 params 0 0x4f59b470 0x3cb2e70 0x1 opus_decoder_destroy + 0x61ba4 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x000e69b4]
2014-05-29T14:55:18.615-07:00| vmx| I120: backtrace[06] frame 0x0020fae0 IP 0x13fbb7d91 params 0x3cb2e70 0x4 0x20fb60 0 opus_decoder_destroy + 0x61f81 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x000e6d91]
2014-05-29T14:55:18.615-07:00| vmx| I120: backtrace[07] frame 0x0020fb10 IP 0x13fcc137e params 0x4 0x13fb41133 0x3a8df20 0x3b14de0 opus_decoder_destroy + 0x16b56e [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x001f037e]
2014-05-29T14:55:18.615-07:00| vmx| I120: backtrace[08] frame 0x0020fb50 IP 0x14003b566 params 0x3b14de0 0x3a8df20 0x2fe230 0x13fb5ec09 opus_repacketizer_get_nb_frames + 0x852f6 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x0056a566]
2014-05-29T14:55:18.616-07:00| vmx| I120: backtrace[09] frame 0x0020fb80 IP 0x13fb37884 params 0x3a8df20 0x2658b0 0x3c9fbc0 0x24a01500 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x00066884]
2014-05-29T14:55:18.616-07:00| vmx| I120: backtrace[10] frame 0x0020fbd0 IP 0x13fb38f0c params 0x2658b0 0x24a01500 0x140534b00 0 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x00067f0c]
2014-05-29T14:55:18.616-07:00| vmx| I120: backtrace[11] frame 0x0020fc30 IP 0x13fb391b9 params 0x2658b0 0x2658b0 0 0x32377d0 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x000681b9]
2014-05-29T14:55:18.616-07:00| vmx| I120: backtrace[12] frame 0x0020fc80 IP 0x13fb3acd0 params 0 0 0x140534b30 0x140073ace ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x00069cd0]
2014-05-29T14:55:18.616-07:00| vmx| I120: backtrace[13] frame 0x0020fcd0 IP 0x13fafa2ad params 0x3a92160 0 0x67aa00 0x3a94180 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x000292ad]
2014-05-29T14:55:18.617-07:00| vmx| I120: backtrace[14] frame 0x0020fdb0 IP 0x13fafa891 params 0x67a570 0x3a94180 0x2 0x1056035800c8 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x00029891]
2014-05-29T14:55:18.617-07:00| vmx| I120: backtrace[15] frame 0x0020fde0 IP 0x13fad318f params 0 0x1 0 0 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x0000218f]
2014-05-29T14:55:18.617-07:00| vmx| I120: backtrace[16] frame 0x0020fe30 IP 0x13fad3257 params 0 0 0 0 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x00002257]
2014-05-29T14:55:18.617-07:00| vmx| I120: backtrace[17] frame 0x0020fee0 IP 0x13fad11de params 0 0 0 0 ??? [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x13fad0000 0x0001:0x000001de]
2014-05-29T14:55:18.618-07:00| vmx| I120: backtrace[18] frame 0x0020fee8 IP 0x77af5a4d params 0 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\kernel32.dll base 0x77ae0000 0x0001:0x00014a4d]
2014-05-29T14:55:18.620-07:00| vmx| I120: backtrace[19] frame 0x0020ff18 IP 0x77c2ba01 params 0 0 0 0x77b7ba40 RtlUserThreadStart + 0x0021 [C:\Windows\SYSTEM32\ntdll.dll base 0x77c00000 0x0001:0x0002aa01]
2014-05-29T14:55:18.620-07:00| vmx| I120: Msg_Post: Error
Defect report: cloning ready-for-easy-install machines
I'm not sure if this is the place for this if you want to report a bug and you are not the owner of the licenses but you are working for someone who owns the license and provides you access to the workstations.
These are the steps to reproduce the defect:
Create a VM (in my case XP) and configure it to use Easy Install. Don't power it.
* At this point a floppy autoinstall image is created in a temp directory and attached to the VM
Clone the VM
Start the original one, let it install
* At some point through the installation, the floppy is removed
Start the cloned one. It doesn't lunch Easy Install because the workstation didn't generate a specific easy install floppy for this vm.
Another defect:
Create a VM (in my case XP) and configure it to use Easy Install. Don't power it.
* At this point a floppy autoinstall image is created in a temp directory and attached to the VM
Clone the VM
Start both at once
Again, since the workstation didn't generate a specific easy install floppy for the cloned vm, the cloned vm shows an error on trying to access one of its virtual devices as it's in use
Hope the VMWare guys take a look at this
Kind regards.
how to install customized red hat enterprise
cant install customized red hat enterprise 6.1 on VMware workstation 10.0.1...?
Workstation 10.0.2 on Win 7 - kubuntu 64 bit stalls at Preparing to Install
I created a new virtual machine with VMWare on Windows 7 host to install 14.04 Kubuntu 64-bit guest. I selected install OS later to avoid irritating problems with Easy Install. When I proceed with the install and reach Preparing to install Kubuntu, nothing happens, no progress. Here is the vmx contents:
.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "10"
numvcpus = "2"
cpuid.coresPerSocket = "2"
vcpu.hotadd = "TRUE"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
sata0.present = "TRUE"
memsize = "4096"
mem.hotadd = "TRUE"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "kubuntu.vmdk"
sata0:1.present = "TRUE"
sata0:1.autodetect = "TRUE"
sata0:1.deviceType = "cdrom-image"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
usb.present = "TRUE"
ehci.present = "TRUE"
ehci.pciSlotNumber = "35"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
mks.enable3d = "TRUE"
serial0.present = "TRUE"
serial0.fileType = "thinprint"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
usb.vbluetooth.startConnected = "TRUE"
displayName = "kubuntu"
guestOS = "ubuntu-64"
nvram = "kubuntu.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
extendedConfigFile = "kubuntu.vmxf"
uuid.bios = "56 4d ab a3 51 4f 1a b2-0d ef 1c 55 6f 52 68 1d"
uuid.location = "56 4d ab a3 51 4f 1a b2-0d ef 1c 55 6f 52 68 1d"
replay.supported = "FALSE"
replay.filename = ""
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
sound.pciSlotNumber = "34"
vmci0.pciSlotNumber = "36"
sata0.pciSlotNumber = "37"
ethernet0.generatedAddress = "00:0c:29:52:68:1d"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "1867671581"
monitor.phys_bits_used = "40"
vmotion.checkpointFBSize = "134217728"
cleanShutdown = "FALSE"
softPowerOff = "FALSE"
usb:1.speed = "2"
usb:1.present = "TRUE"
usb:1.deviceType = "hub"
usb:1.port = "1"
usb:1.parent = "-1"
sata0:1.fileName = "C:\zips\_linux\kubuntu-14.04-desktop-amd64.iso"
floppy0.present = "FALSE"
usb:0.present = "TRUE"
usb:0.deviceType = "hid"
usb:0.port = "0"
usb:0.parent = "-1"
Why am I getting Event ID 1 each time I start VMware Workstation 10.0.2 build-1744117 on WIndows 8.1.1 Pro x64?
Here's the XML version of the Event. What is it telling me? Is there a fix or should I just ignore it?
</System>
</EventData>
</Event>