ROM of the Virtual Machine is not supported

Similar Questions

• Windows on VM - says my copy of Windows 7 on the virtual machine is not authentic

  I have the Virtual Machine on a Mac and am running Windows 7 on the virtual machine.  I get a message that my copy of windows is not genuine, so, how do I get a product key.
  I get a message from Microsoft that this copy of Windows is not supported.  If I need to buy Windows overall, how can I download it to VM?

  You can purchase a license for the edition you installed and change the key and activate it on the Internet.

  http://www.Microsoft.com/Windows/buy/default.aspx

  http://Windows.Microsoft.com/en-us/Windows7/get-a-new-Windows-product-key

  Click Start, right click on computer

  Click on properties

  Scroll down to the Windows Activation

  Click on the link "change product key".

  Enter the product key and click next to activate via the Internet.

• ESXi host goes to the State and the virtual machine does not restart on other host does not

  Hi all

  I'm looking for a solution, in which case the host goes to the State and the virtual machine on it does not restart on a different host (they'll just gray) does not not what could be the problem here and how to fix it

  later when the failed host returns upward machines either go to motor off the coast of the State, or they show that under tension

  While the host is down or not responding do not I am able to ping the host ESXi (5.5) and able to ping the default gateway and the DNS servers of the host itself

  Yes AF, the answer to all these questions is Yes, it is a HA and DRS cluster active, I tried restarting mgmt service, we use a shared storage (storage iSCSI HP 3PAR and left hand)

• In opening the virtual machine: "could not find a peer valid to connect to" or "error of Transport (VMDB) - 32" / "-14" ""»

  Hello

  Since yesterday after a reboot of my host (DELL E6410, W7 SP1 64-bit, 8 GB RAM, 2x750GB SATA3 running WorkStation 9.0.2 Update Windows Update), I can't open my existing VM.

  I often get "can not find a valid peer to connect to" and sometime before: "Transport (VMDB) - 32 error: Pipe: reading is not'or'error of Transport (VMDB)"-14: fitting broke"»

  I worked for 2 years on this machine without a hitch, WS7 reclassification in WS9 without any problem.

  FYI: we have changed the domain 3 months ago, but it has never be a problem.

  I have google and search several Forum. So far, I tried to:

  -restart the service vmware-auth as an administrator

  -launch vmware.exe administrator

  stop/start the vmx86 service

  -uninstall / reboot / install Workstation.  3 times. First using uninstall from the Control Panel, then doing a / clean before installation and finally track down any file/reg entry.

  -HE asked if any group policy changes were made recently (like not allowing to run vmware.exe?)

  -Rename vmware.exe (logs I look similar to what is in this post: http://communities.vmware.com/thread/331099?start=0 & tstart = 0 ... but no luck)
  

  -excluded vmware.exe in my AV (Microsoft ForeFront). Unfortunately, in that I'm not allowed disabled...

  -Open the virtual machine using the drive == > does not work either.

  This isn't a file corrupted in a virtual machine (even backup - 7zipped - don't work on my laptop... but the launch on the other).

  Even a newly created WM (boneless), unbootable! :-(

  *, BUT to BE NOTE *: if a virtual machine is created as a shared virtual machine, I can start the application locally remotely! And this same VM, if started (via the.vmx) does not work using Workstation GUI!

  I have attached 2 newspapers. Work a (vmware.log remotely) and the inactive (vmware-vmx - 4072.log thru WS GUI).

  Of after what I saw (and what little I understand), it's as if the CPU is not detected?

  The two newspapers have this line:

  FeatureCompat: EVC masks:

  but the non-working goes - we with

  Module CPUID initialization failed.

  While working it display information on CPU (hostCPUID name / family / type... etc...)

  Any idea is welcome.

  I'll answer me to my problem!

  A lot of research to this knowledge.

  In summary: don't mess with the processor affinity... or keep it in mind!

  Response to distinguish:

  I installed 6 months ago a small utility named prio (search for "PRI prnwatch"), because it can save the priority of a given process. What I did notice, is that it also save the processor affinity ! What happened: I probably changed the affinity once for a VM running to give greater priority to a 7zip archive process to complete more quickly (setting HT no core to 7zip and one - or 2? - HT core to VM). Everything works until the next reboot, where the CPU detection during * start EVERY * VM has been somewhat "damaged" leading to the wrong log message: failed initialization Module CPUID.

  This is the reason of *my* question. Perhaps it might help someone else?

  TIPS:

  For advanced people who do not want to check the processor affinity of each process in the Task Manager, you can try this Windows Powershell command (remember to launch PowerShell as an administrator):

  Get-Process | Format-Table-PriorityClass name, ProcessorAffinity property

  ProcessorAffinity column gives the number of representation of the authorized core, 1-bit by heart.

  15 = 1111 is all possible core (for a logical processor 4). Mine is 1 CPU with 2 core HT <=>4.

  LSB is the core lowest. So if you allow only core0 and core3 (1001) on a process, the number of ProcessorAffinity will be 9...

  Post edited by: cbiero (LSB and MSB...)

• NPIV enabled on the virtual machine, but not seen in the comments

  Hello

  I have a 5.0 with an HBA qlogic esxi. I created a VM and rhel is installed.

  Then I activated the npiv on this virtual machine and saw that it generated node WWN and port WWN.

  However, when I logged in the comments, I am not able to see the names of ports in

  / sys/Class/scsi_host/Host {n} / device / fc_host:host {n} / port_name

  Are there additional configuration on the side of the virtual machine to allow the WWNS within the guest?

  Thanks in advance.
  

  Hello

  This is a very detailed description of all the required tasks for use with VMware NPIV.

  NPIV: N-Port ID Virtualization

  Kind regards

  Ralf

• AutoSave is slow when the virtual machine is not active

  When I actively use a Windows 2000 Server VM and AutoSave is triggered, it's very fast.  But if I did not use the virtual machine for a while, it takes some minutes and minutes.  If I'm trying to go back to the virtual machine, I have to wait indefinitely for the automatic backup complete.

  Is it possible to set the priority for the automatic backup feature?

  Are you talking about VMware Fusion AutoProtect feature, or something else (perhaps in the comments)? Offhand, it seems that when you have not used within a certain time, Fusion got paged out. Taking the automatic snapshot requires paging backward, which can take some time. You can test this theory by looking at activity monitor and looking at the pageout/publication numbers when you see an automatic preview slow.

  Pageouts and pageins are controlled by OS X and not something we have control over. Adding RAM to the Mac, it is more likely merger will stay in memory and avoid this situation.

• With instant full VM LUN and now the virtual machine will not start or register

  Hello

  I have a case here, where we have a virtual machine that quickly filled the logic unit number and the snapshot is currently 110 GB. It is now available on the new LUN space, but the VM does not start and he was also addressed as 'unknown' in the viclient. I tried to cancel the registration and check-in again, but he refuses to register. It seems that the snapshot is damaged.

  When you try to save it, I get the following in hostd.log:

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': (17) successfully opened size = 48348147712, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': open with success (21) size = 48348147712, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 3

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-flat.vmdk ': closed.

  DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': (17) successfully opened size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': open with success (21) size = 214764819456, hd = 0. Type 8

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

  DISKLIB-VMFS: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000001-delta.vmdk ': closed.

  DISKLIB-LINK: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-STRING: ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ': cannot open (the specified file is not a virtual disk).

  DISKLIB-LIB: unable to open ' / vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA_1-000002-delta.vmdk ' with flags 0 x 11 (the specified file is not a virtual disk).

  Referred to as registry: AXAPTA/AXAPTA.vmx

  Vmsvc indicates file is loaded, by: /vmfs/volumes/48be6db3-f04f46d1-d765-001f2959edbb/AXAPTA/AXAPTA.vmx

  I also tried to copy virtual machines directory down to a local PC and run via VMware Converter, but I get the message "the source VMware Consolidated Backup"filename.vmx"has a missing catalog file.

  1. VMware - v

  VMware ESX Server 3.5.0 build-130756

  Any help is appreciated.

  Lars

  The problem (according to the newspaper) is AXAPTA_1-000001 - delta.vmdk no AXAPTA_1-000002 - delta.vmdk (the error on the second snapshot is probably because of the broken parent snapshot).

  The descriptors are ok, which means that the VMDK itself is broken.

  If you do not have a backup, you can try the following:

  -Copy the files in another data store

  -change the second snapshot descriptor to point to the basedisk as the parent

  -Try and mount the drive

  -If you're lucky, you should be able to recover at least some data of

  -If the disklib is complaining again then the two snapshots are broken - which is unlikely

  Depending on how old the second snapshot (the older one is better it is) the method above will not help.

• Problem using cdromdisconnect.pl to check for the use of CD-ROM on the virtual machines

  I have a problem with this script, cdromdisconnect.pl and I was hoping someone could help me with it...

  When I run ' cdromdisconnect.pl - my.esx.host - host list op - my.vc.host - server passthroughauth ", I get a"Host not found my.esx.host." But when I run "datacenterlisting.pl - datacenter MyDC" there 'my.esx.host' very well. Am I missing something here? Why is the cdrom script not able to find hosts when other scripts have no problem?

  Any help would be appreciated.

  -monkeedu

  As far as I KNOW, there isn't a way to do a review on a MoRef, right on the property values.  You cannot, for example, match against a property value of the table.  You have to adapt your script logic.  Once you have your view of system host ($host), then you must use the vm ($host-> vm) property to get a list of Virtual Machines.

  You will probably need to change:

  my $host_moRef = $host->{mo_ref}{value};
  #######################################################################################
  #     Get all VMs that are currently running on that ESX Server
  #######################################################################################
  
  my $vm_views = Vim::find_entity_views(view_type => 'VirtualMachine', filter => {'runtime.host' => $host_moRef});
  my $numDevices = 0;
  foreach my $vm_view (@$vm_views) {
  

  TO:

  #######################################################################################
  #     Get all VMs that are currently running on that ESX Server
  #######################################################################################
  
  my $numDevices = 0;
  my $vm_view;
  foreach (@{$host->vm}) {
       $vm_view = Vim::get_view( mo_ref => $_ );
  

  There are some optimizations I can suggest to speed it up, but its probably better to work first.

• Discover the virtual machine with VMware View 4.5.  "That underlies the virtual machine is not available.

  I have installed the following to an ESX 4.1 server:

  -VMware View connection server (Server 2008 R2 Ent)

  -V - Center (Server 2003 Std)

  Install the VMware Client with Local Mode 4.5 to a laptop

  Installed VMware Agent to a Windows XP and Win7 is a guest vm on the ESX Server.

  I can connet with success both of these machines.

  When I try to extract either of these machines, I get the error message after 2% saying, "underlying this desktop virtual machine is unavailable.

  

  Can someone tell what to do to solve this problem?  I can't find anything so far for this error.

  Thank you

  Did you install and configure a forwarding server?

  -Mike

• Windows Server 2003 physical to the virtual machine does not start

  I have converted a windows server machine 2003 virtual machine image.  Conversion completed successfully but the machine image custom virtual boot I get the blue screen of death which is probably do the scsi driver being changed during the conversion of my question is: how to install these drivers once the pc has been converted? I try to avoid to do from scratch with constraints of time it takes to get this virtual image starts, please help

  Semper Fi

  You must use SCSI.  Replace your SCSI controller during the conversion.

  ... also, I'm under the assumption that the destination ESX (i)?

• Register the virtual machine does not properly

  I run the following script, but it does not work as expected.

  $ESXHost = 'test - 01.Test.com '.

  $ResourcePool = get-VMHost $ESXHost | Get-ResourcePool | Get-View
  $vmFolder = get-View (Get-data center-name $Datacenter |) Get - Folder - name "vm") user.user
  $vmFolder.RegisterVM_Task ("[TIER2_VMSHARED_LASCX02_LUN2017]" + $VMName + "/" + $VMName + ".vmx", $VMName, $false, $ResourcePool.MoRef, $null ")

  When the script is run, it saves the VM on Test-04?  Any suggestions?

  E4F

  The last parameter to RegisterVM_Task is the host where you want the guest to save.

  You pass $null, so DRS will decide for you.

  If you want a specific host, you can do

  $ESXHost = "Test-01.Test.com"
  $esx = Get-VMHost -Name $ESXHost $ResourcePool = $esx | Get-ResourcePool | Get-View $vmFolder = Get-View (Get-Datacenter -Name $Datacenter | Get-Folder -Name "vm").id
  $vmFolder.RegisterVM_Task("[TIER2_VMSHARED_LASCX02_LUN2017] " +  $VMName + "/" + $VMName + ".vmx", $VMName, $false, $ResourcePool.MoRef, $esx.Extensiondata.MoRef)
  

• Virtual machines do not get IP address from the DHCP server

  Hello! I just spend Xenserver to ESXi. Created a couple of virtual machines and none of them gets an IP address from our DHCP server (DHCP server is a physical PC), and instead, they get a number of internal 192.168.x.y allowing connection to the internet.

  Looks like a way to do this is to install a virtual machine that is a router, as M0n0wall, and route traffic to connect to the external network and finally to access internet. But this is not what I have to do.

  I need to have virtual machines that are server to get an IP reserved for our DHCP server, and then our local windows client should be able to access it directly.

  I searched on google and forums for this but I can't seem to find how to configure virtual machines to directly belong to our local network.

  I thought that VMware would have a simpler way to do so than XenServer, but I was stuck on this one day now and really frustrated as I get not before with this project, stuck on this little problem... sigh...

  Thanks for your help.

  GER.

  ESXi does not IP addresses to the virtual machines it host - if the virtual machines are not able to access your physical network than that of the thw two virtual machines acts as a DHCP server - now to the question of network - if you are not able to reach the virtual machines on the physical network or achieve fitness network virtual machines , then there is a problem with the physical connection to the ESXi host, possibly the configuration of the physical port that connects to the - is a way to test this theory to assign an IP address on the same network that the management port - if you are able to access the virtual machine, then you know that the problem is with the switch port.

• List not updated virtual machines after the migration of the virtual machine to a different data store

  My vSphere infrastructure 5 uses several data stores.

  Two data warehouses are associated with NFS on different NAS shares.

  I migrate VM to a data to another store.

  The navigation data store, I see that the files are moved from the old data store to the new and that no file belonging to the migrated VM still does exist on the old data store.

  If I look at the list of VMs on the old data store, I still see the old VM.

  I see it in the list of the virtual machine on the new data store as well.

  I checked that no .iso no pagefile is in the old data store.

  How can I update the list of the virtual machine on the old data store?

  Above all, how can I safely delete the old data store by ensuring that the virtual machine works very well on the new data store and I don't lose anything?

  Concerning

  Marius

  This use of data store 'Phantom' is usually observed, if the current configuration of the virtual computer points to the 'old' data store (diskette, CD-ROM) or the virtual machine contains snapshots where - at the time where tone have been created - the VM has had these references. Once the snapshots are deleted from data store 'ghost' will go away from summary of the virtual machine.

  André

• Could not start the virtual machine after you use vmkfstools to resize - HELP!

  I thought I knew what I was doing, but apparently not...

  I tried to increase the size of a VM over 36 GB drive and now I can not start the server. Here's the change front of directory list:

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 9 February 14:55 PJAEast-DL01-000002 - delta.vmdk

  -rw - 1 root root 277 9 February 14:55 PJAEast-DL01 - 000002.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 25 August at 21:03 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1042 28 August to 01:52 PJAEast - DL01.vmsd

  -rwxr-xr-x 1 root root 2779 Feb 9 15:10 PJAEast - DL01.vmx

  -rw - r - r - 1 root root 267 Feb 9 15:10 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 9 February 14:55 PJAEast-DL01_1-000002 - delta.vmdk

  -rw - 1 root root 283 9 February 14:55 PJAEast-DL01_1 - 000002.vmdk

  -rw - 1 root root 36322836480 28 August at 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 597 25 August at 15:18 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 78710 25 August at 16:06 vmware - 1.log

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 vmware.log

  Then, I run the command:

  vmkfstools x 256g PJAEast - DL01_1.vmdk

  And now the virtual machine does not start, return an error: "the virtual disk parent has been changed since the child was created."

  The directory listing is now ("BOLD" indicates the change of information post-vmkfstools):

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 Feb 9 16:12 PJAEast-DL01-000003 - delta.vmdk

  -rw - 1 root root 277 Feb 9 16:12 PJAEast-DL01 - 000003.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 Feb 9 16:12 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1015 28 August 01:52 PJAEast - DL01.vmsd

  -rwx - 1 root root 2779 Feb 9 16:12 PJAEast - DL01.vmx

  -rw - 1 root root 267 Feb 9 16:12 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 Feb 9 16:12 PJAEast-DL01_1-000003 - delta.vmdk

  -rw - 1 root root 283 Feb 9 16:12 PJAEast-DL01_1 - 000003.vmdk

  -rw - 1 root root 274877906944 28 August 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 599 9 Feb 16:11 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 5.log - vmware

  -rw - r - r - 1 root root 39510 Feb 9 16:12 6.log - vmware

  -rw - r - r - 1 root root 39411 Feb 9 16:12 vmware - 7.log

  -rw - r - r - 1 root root 39410 Feb 9 16:14 vmware.log

  I can't do anything else until I get comments. Can anyone recommend a way to solve this problem?

  I thought I knew what I was doing, but apparently not...

  I agree

  Two a problem with the new drive.

  1. You get the error message comes from the basic disk with a different size than the disks of the snapshot.
  2. With a size of 256 GB, you will not be able to create snapshots of the disk (on ESXi prior to 5.0 with a block size of 1 MB)

  What you can try to do is to edit the file PJAEast - DL01_1.vmdk :

  • 536870912 VMFS 'PJAEast-DL01_1 - flat hard' RW--> RW 70943040 VMFS 'PJAEast-DL01_1 - flat hard. "
  • DDB. Geometry.Cylinders = "33418'-> ddb.geometry.cylinders = '4416.

  After that, I would recommend to clone the virtual disk to a new one, replace the virtual disk in the virtual machine settings and resize it to a maximum of 254GB (see "calculates the time system required by the snapshot files" at http://kb.vmware.com/kb/1012384)

  • vmkfstools-i PJAEast-DL01_1 - 000003.vmdk PJAEast - DL01_1a.vmdk

  André

• Virtual machine does not start the Server Windows 2003 Std ISO file?

  Hello

  I am trying to create a virtual Windows 2003 machine, I created the ISO file, downloaded on my ISO library and connected the CDROM drive for the ISO file.

  When I boot the maching, I select the start menu and select the CDROM drive the virtual machine starts the ISO?

  The continuous boot just on the network card boot.

  It's as if the virtual machine does not see the CDROM drive?

  I use folder2iso

  To me, it sounds as if the ISO created may not be bootable! How did you create the ISO file?

  André