2003 to SCSI IDE
I need to convert a guest 2003 IDE disks SCSI disks. I tried to change the ddb.adapterType of the ide to free in the file vmdk and reissue of links it as a SCSI drive, however when it does start it bluescreens. I guess I have to install a driver in the guest PC before changing the type. I don't know which driver or where to find this driver however. Are there other settings I need to change other than the ddb.adapterType?
Thank you
"Inject" the correct driver, the simplest method is to add an additional to the VM of Windows 2003 free SCSI drive temporarily while it is still running on the IDE drive. This will load the driver that will be used for the system disk after changing the settings you mentioned.
André
Tags: VMware
Similar Questions
-
Get a scsi and ide port to csv
Hello
I am looking for a way to get the next field in a csv file
Controller, channel, diskName, vmdk, vm
At the moment I have:
SE connect-VIServer localhost | Out-Null
$VMs = get - VM SEQDEV7 | Get-View
{ForEach ($VM to $VMs)
{If ($VM)}
Foreach ($SCSI_Controller in ($VM. Config.Hardware.Device | where {$_.} (({DeviceInfo.Label - like "SCSI *"})) {}
Write-Host $SCSI_Controller.DeviceInfo.Label
{Foreach ($Disk_Key to $SCSI_Controller.Device)}
Foreach ($Disk_Device in ($VM. Config.Hardware.Device | where {$_.key - eq $Disk_Key})) {}
Write-Host "" $Disk_Device.UnitNumber: $Disk_Device.DeviceInfo.Label: $Disk_Device.Backing.Filename
}
}
}
}
}
$DiskPort | Export-Csv - NoTypeInformation-path C:\Users\malabelle\Desktop\tests\test-scsi-ide.csv
{ForEach ($VM to $VMs)
{If ($VM)}
Foreach ($SCSI_Controller in ($VM. Config.Hardware.Device | where {$_.} (({DeviceInfo.Label - like "IDE *"})) {}
Write-Host $SCSI_Controller.DeviceInfo.Label
{Foreach ($Disk_Key to $SCSI_Controller.Device)}
Foreach ($Disk_Device in ($VM. Config.Hardware.Device | where {$_.key - eq $Disk_Key})) {}
Write-Host "" $Disk_Device.UnitNumber: $Disk_Device.DeviceInfo.Label: $Disk_Device.Backing.Filename
}
}
}
}
}Gives me
SCSI controller 0
0: disc 1: SEQDEV7/SEQDEV7.vmdk [TEST_Sequence_Dev]
1: HDD 2: SEQDEV7/SEQDEV7_2.vmdk [TEST_Sequence_Dev]
SCSI controller 1
14: hard disk 3: SEQDEV7/SEQDEV7_3.vmdk [TEST_Sequence_Dev]
IDE 0
IDE 1
0: 1 CD/DVD drive: [TEST150A] ISO/pe-defrag - directboot.iso
Any idea?
I did a major rewrite of your script to do it in a way PowerShell over doing things. I think that the following script will give you the desired result:
Connect-VIServer localhost | Out-Null Get-VM | ForEach-Object { $VM = $_ $VM.ExtensionData.Config.Hardware.Device | ` Where-Object {$_.DeviceInfo.Label -like "SCSI*" -or $_.DeviceInfo.Label -like "IDE*"} | ` ForEach-Object { $SCSI_Controller = $_ $SCSI_Controller.Device | ForEach-Object { $Disk_Key = $_ $VM.ExtensionData.Config.Hardware.Device | ` Where-Object {$_.key -eq $Disk_Key} | ` ForEach-Object { $Disk_Device = $_ $Report = "" | Select-Object -Property Controller,Channel,Disk,Vmdk,VM $Report.Controller = $SCSI_Controller.DeviceInfo.Label $Report.Channel = $Disk_Device.UnitNumber $Report.Disk = $Disk_Device.DeviceInfo.Label $Report.Vmdk = $Disk_Device.Backing.Filename $Report.VM = $VM.Name $Report } } } } | Export-Csv -NoTypeInformation -Path C:\Users\malabelle\Desktop\tests\test-scsi-ide.csvBest regards, Robert
-
SCSI vs SATA in HDD VM settings.
Hello
I just upgraded to Fusion 8. I have a MacBook Pro 15 "mid 2015 (the one with the flash SSD) and I installed Windows Home 10 in a virtual machine."
In the settings/hard disc VM, I see three options for 'Type of Bus': SCSI, IDE and SATA. The default merge chose is SCSI. Is it better to leave it as it is, or should I put it to SATA? As I use Visual Studio on Windows, each gain perf rejoice more and I was wondering if in mode will make a difference.
Many thanks for any help.
Hello
If it makes a difference then the difference is quite tiny as the limits are applied by the host system.
The default values are normally your best bet on what they are listening to VMware.
In this case the SCSI virtual device as far as I KNOW has a greater depth of queue as the SATA, so - at least theoretically - it, you should get better performance by sticking with the disk virtual scsi.
PS: I forget - in theory - I have not personally ran the performance tests on Windows 10 guests.
--
Wil
-
File < unspecified filesname > was not found.
Hello
There is a lot of discussion on this topic.
Story, I stopped the host to add more memory back up nicely with all the machines works very well except one.
11:39:21.793 17 August: vmx | Journal for VMware ESX pid = version 104526 = 4.0.0 Build = build-208167 option = output
11:39:21.794 17 August: vmx | Host codepage = UTF-8 encoding = UTF-8
11:39:21.796 17 August: vmx | Hostname = VM2. Trident.com
11:39:21.797 17 August: vmx | IP = 127.0.0.1 (lo)
11:39:21.798 17 August: vmx | IP = 172.16.254.20 (vswif0)
11:39:21.798 17 August: vmx | IP = 172.18.20.251 (vswif1)
11:39:21.799 17 August: vmx | IP = 192.168.41.13 (vswif2)
11:39:21.799 17 August: vmx | Command line: "/ usr/lib/vmware/bin/vmware-vmx" "-ssched.group = host/user" "-#" "name = VMware ESX; version = 4.0.0. BuildNumber = 208167; licensename = VMware ESX Server; licenseversion = 4.0 build-208167; «"-@" "tube = / tmp/vmhsdaemon-0/vmx3b9d5a6ca604e47a;» "/ vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/New Virtual Machine / new Virtual Machine.vmx.
11:39:21.804 17 August: vmx | Msg_SetLocale: HostLocale = UTF-8 UserLocale = NULL
11:39:21.866 17 August: vmx | "UI connection to the pipe" / tmp/vmhsdaemon-0/vmx3b9d5a6ca604e47a ' with the user (null) ".
11:39:21.867 17 August: vmx | VMXVmdb: Expiration of the local connection: 60000 ms.
11:39:21.890 17 August: vmx | / vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/New Machine Virtual virtual/New Machine.vmx: configuration link symbolic/var/run/vmware/1f5d3c4d95660ac7b4bf26aec5a717c8->/var/run/vmware/root_0/1282041561806039_104526
11:39:21.892 17 August: vmx | VIX: : VMAutomation: initialization of VMAutomation.
11:39:21.894 17 August: vmx | VIX: : VMAutomation: detected the VM is not managed
11:39:21.895 17 August: vmx | VIX: : VMAutomationOpenListenerSocket() to listen
11:39:21.896 17 August: vmx | Sig_Init already initialized
11:39:21.899 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1
11:39:21.900 17 August: vmx | VMX/execState/val goes to poweredOff
11:39:21.900 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1
11:39:21.901 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 2, newAppState = 1877, success = 1
11:39:21.901 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 3, newAppState = 1881, success = 1
11:39:21.905 17 August: vmx | Provider CPUID [0]: GenuntelineI
11:39:21.905 17 August: vmx | CPUID level [0] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.906 17 August: vmx | CPUID level [0] 00000001, 0: 0 x 00010676 0 x 00040800 0x000ce3bd 0xbfebfbff
11:39:21.907 17 August: vmx | CPUID level [0] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.907 17 August: vmx | CPUID level [0] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.908 17 August: vmx | CPUID level [0] 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.908 17 August: vmx | CPUID level [0] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.909 17 August: vmx | Provider CPUID [1]: GenuntelineI
11:39:21.909 17 August: vmx | CPUID level [1] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.910 17 August: vmx | CPUID level [1] 00000001, 0: 0 x 00010676 0 x 01040800 0x000ce3bd 0xbfebfbff
11:39:21.911 17 August: vmx | CPUID level [1] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.911 17 August: vmx | CPUID level [1] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.912 17 August: vmx | Level [1] CPUID 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.912 17 August: vmx | CPUID level [1] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.913 17 August: vmx | Provider CPUID [2]: GenuntelineI
11:39:21.913 17 August: vmx | CPUID level [2] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.914 17 August: vmx | CPUID level [2] 00000001, 0: 0 x 00010676 0 x 02040800 0x000ce3bd 0xbfebfbff
11:39:21.914 17 August: vmx | CPUID level [2] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.915 17 August: vmx | CPUID level [2] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.916 17 August: vmx | CPUID level [2] 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.916 17 August: vmx | CPUID level [2] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.917 17 August: vmx | Provider CPUID [3]: GenuntelineI
11:39:21.917 17 August: vmx | CPUID level [3] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.918 17 August: vmx | CPUID level [3] 00000001, 0: 0 x 00010676 0 x 03040800 0x000ce3bd 0xbfebfbff
11:39:21.918 17 August: vmx | CPUID level [3] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.919 17 August: vmx | CPUID level [3] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.920 17 August: vmx | Level [3] CPUID 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.920 17 August: vmx | CPUID level [3] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.921 17 August: vmx | Provider CPUID [4]: GenuntelineI
11:39:21.921 17 August: vmx | CPUID level [4] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.922 17 August: vmx | CPUID level [4] 00000001, 0: 0x0001067a 0 x 04040800 0x000ce3bd 0xbfebfbff
11:39:21.922 17 August: vmx | CPUID level [4] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.923 17 August: vmx | CPUID level [4] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.924 17 August: vmx | CPUID level [4] 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.924 17 August: vmx | CPUID level [4] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.925 17 August: vmx | Provider CPUID [5]: GenuntelineI
11:39:21.925 17 August: vmx | CPUID level [5] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.926 17 August: vmx | CPUID level [5] 00000001, 0: 0x0001067a 0 x 05040800 0x000ce3bd 0xbfebfbff
11:39:21.926 17 August: vmx | CPUID level [5] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.927 17 August: vmx | CPUID level [5] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.928 17 August: vmx | CPUID level [5] 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.928 17 August: vmx | CPUID level [5] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.929 17 August: vmx | Provider CPUID [6]: GenuntelineI
11:39:21.929 17 August: vmx | CPUID level [6] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.930 17 August: vmx | CPUID level [6] 00000001, 0: 0x0001067a 0 x 06040800 0x000ce3bd 0xbfebfbff
11:39:21.931 17 August: vmx | CPUID level [6] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.931 17 August: vmx | CPUID level [6] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.932 17 August: vmx | CPUID level [6] 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.932 17 August: vmx | CPUID level [6] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.933 17 August: vmx | Provider CPUID [7]: GenuntelineI
11:39:21.934 17 August: vmx | CPUID level [7] 00000000, 0: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.934 17 August: vmx | CPUID level [7] 00000001, 0: 0x0001067a 0 x 07040800 0x000ce3bd 0xbfebfbff
11:39:21.935 17 August: vmx | CPUID level [7] 0000000 a, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.935 17 August: vmx | CPUID level [7] 80000000, 0: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.936 17 August: vmx | CPUID level [7] 80000001, 0: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.936 17 August: vmx | CPUID level [7] 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.937 17 August: vmx | hostCPUID provider: GenuntelineI
11:39:21.937 17 August: vmx | hostCPUID 00000000, 0 level: 0x0000000a 0x756e6547 0x6c65746e 0x49656e69
11:39:21.938 17 August: vmx | hostCPUID level 00000001, 0: 0 x 00010676 0 x 00040800 0x000ce3bd 0xbfebfbff
11:39:21.939 17 August: vmx | hostCPUID 0000000 a level, 0: 0 x 07280202 0x00000000 0x00000000 0 x 00000503
11:39:21.939 17 August: vmx | hostCPUID level 0, 80000000: 0 x 80000008 0x00000000 0x00000000 0x00000000
11:39:21.940 17 August: vmx | hostCPUID level 0, 80000001: 0x00000000 0x00000000 0x00000001 0 x 20100800
11:39:21.940 17 August: vmx | hostCPUID level 80000008, 0: 0 x 00003026 0x00000000 0x00000000 0x00000000
11:39:21.941 17 August: vmx | CPUID Maximum physical address Bits supported on all processors: 38
11:39:21.942 17 August: vmx | CPU [0]: MSR 0 X 480 = 0X5A08000000000D
11:39:21.942 17 August: vmx | CPU [1]: MSR 0 X 480 = 0X5A08000000000D
11:39:21.943 17 August: vmx | [2] CPU: MSR 0 X 480 = 0X5A08000000000D
11:39:21.943 17 August: vmx | CPU [3]: MSR 0 X 480 = 0X5A08000000000D
11:39:21.944 17 August: vmx | CPU [4]: MSR 0 X 480 = 0X5A08000000000D
11:39:21.944 17 August: vmx | CPU [5]: MSR 0 X 480 = 0X5A08000000000D
11:39:21.945 17 August: vmx | CPU [6]: MSR 0 X 480 = 0X5A08000000000D
11:39:21.946 17 August: vmx | CPU [7]: MSR 0 X 480 = 0X5A08000000000D
11:39:21.946 17 August: vmx | Frequent: MSR 0 x 480 = 0x5a08000000000d
11:39:21.947 17 August: vmx | CPU [0]: 0 X 481 MSR = 0X3F00000016
11:39:21.947 17 August: vmx | CPU [1]: MSR 0 X 481 = 0X3F00000016
11:39:21.948 17 August: vmx | [2] CPU: 0 X 481 MSR = 0X3F00000016
11:39:21.948 17 August: vmx | CPU [3]: MSR 0 X 481 = 0X3F00000016
11:39:21.949 17 August: vmx | CPU [4]: MSR 0 X 481 = 0X3F00000016
11:39:21.950 17 August: vmx | CPU [5]: MSR 0 X 481 = 0X3F00000016
11:39:21.950 17 August: vmx | CPU [6]: 0 X 481 MSR = 0X3F00000016
11:39:21.951 17 August: vmx | CPU [7]: MSR 0 X 481 = 0X3F00000016
11:39:21.951 17 August: vmx | Frequent: MSR 0 x 481 = 0x3f00000016
11:39:21.952 17 August: vmx | CPU [0]: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.952 17 August: vmx | CPU [1]: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.953 17 August: vmx | [2] CPU: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.953 17 August: vmx | CPU [3]: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.954 17 August: vmx | CPU [4]: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.955 17 August: vmx | CPU [5]: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.955 17 August: vmx | CPU [6]: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.956 17 August: vmx | CPU [7]: MSR 0 X 482 = 0XF7F9FFFE0401E172
11:39:21.956 17 August: vmx | Frequent: MSR 0 x 482 = 0xf7f9fffe0401e172
11:39:21.957 17 August: vmx | CPU [0]: 0 X 483 MSR = 0X3FFFF00036DFF
11:39:21.957 17 August: vmx | CPU [1]: MSR 0 X 483 = 0X3FFFF00036DFF
11:39:21.958 17 August: vmx | [2] CPU: 0 X 483 MSR = 0X3FFFF00036DFF
11:39:21.959 17 August: vmx | CPU [3]: MSR 0 X 483 = 0X3FFFF00036DFF
11:39:21.959 17 August: vmx | CPU [4]: MSR 0 X 483 = 0X3FFFF00036DFF
11:39:21.960 17 August: vmx | CPU [5]: MSR 0 X 483 = 0X3FFFF00036DFF
11:39:21.961 17 August: vmx | CPU [6]: 0 X 483 MSR = 0X3FFFF00036DFF
11:39:21.961 17 August: vmx | CPU [7]: MSR 0 X 483 = 0X3FFFF00036DFF
11:39:21.962 17 August: vmx | Frequent: MSR 0 x 483 = 0x3ffff00036dff
11:39:21.962 17 August: vmx | CPU [0]: 0 X 484 MSR = 0X3FFF000011FF
11:39:21.963 17 August: vmx | CPU [1]: MSR 0 X 484 = 0X3FFF000011FF
11:39:21.963 17 August: vmx | [2] CPU: MSR 0 X 484 = 0X3FFF000011FF
11:39:21.964 17 August: vmx | CPU [3]: MSR 0 X 484 = 0X3FFF000011FF
11:39:21.965 17 August: vmx | CPU [4]: MSR 0 X 484 = 0X3FFF000011FF
11:39:21.965 17 August: vmx | CPU [5]: MSR 0 X 484 = 0X3FFF000011FF
11:39:21.966 17 August: vmx | CPU [6]: MSR 0 X 484 = 0X3FFF000011FF
11:39:21.966 17 August: vmx | CPU [7]: MSR 0 X 484 = 0X3FFF000011FF
11:39:21.967 17 August: vmx | Frequent: MSR 0 x 484 = 0x3fff000011ff
11:39:21.967 17 August: vmx | CPU [0]: 0 X 485 MSR = 0X403C0
11:39:21.968 17 August: vmx | CPU [1]: MSR 0 X 485 = 0X403C0
11:39:21.968 17 August: vmx | [2] CPU: MSR 0 X 485 = 0X403C0
11:39:21.969 17 August: vmx | CPU [3]: MSR 0 X 485 = 0X403C0
11:39:21.970 17 August: vmx | CPU [4]: MSR 0 X 485 = 0X403C0
11:39:21.970 17 August: vmx | CPU [5]: MSR 0 X 485 = 0X403C0
11:39:21.971 17 August: vmx | CPU [6]: MSR 0 X 485 = 0X403C0
11:39:21.971 17 August: vmx | CPU [7]: MSR 0 X 485 = 0X403C0
11:39:21.972 17 August: vmx | Frequent: MSR 0 x 485 = 0x403c0
11:39:21.972 17 August: vmx | CPU [0]: 0 X 486 MSR = 0 X 80000021
11:39:21.973 17 August: vmx | CPU [1]: MSR 486 X 0 = 0 X 80000021
11:39:21.974 17 August: vmx | [2] CPU: MSR 486 X 0 = 0 X 80000021
11:39:21.974 17 August: vmx | CPU [3]: MSR 486 X 0 = 0 X 80000021
11:39:21.975 17 August: vmx | CPU [4]: MSR 486 X 0 = 0 X 80000021
11:39:21.975 17 August: vmx | CPU [5]: MSR 486 X 0 = 0 X 80000021
11:39:21.976 17 August: vmx | CPU [6]: MSR 486 X 0 = 0 X 80000021
11:39:21.976 17 August: vmx | CPU [7]: MSR 486 X 0 = 0 X 80000021
11:39:21.977 17 August: vmx | Frequent: MSR 486 x 0 = 0 x 80000021
11:39:21.978 17 August: vmx | CPU [0]: 0 X 487 MSR = 0XFFFFFFFF
11:39:21.978 17 August: vmx | CPU [1]: MSR 0 X 487 = 0XFFFFFFFF
11:39:21.979 17 August: vmx | [2] CPU: 0 X 487 MSR = 0XFFFFFFFF
11:39:21.979 17 August: vmx | CPU [3]: MSR 0 X 487 = 0XFFFFFFFF
11:39:21.980 17 August: vmx | CPU [4]: MSR 0 X 487 = 0XFFFFFFFF
11:39:21.980 17 August: vmx | CPU [5]: MSR 0 X 487 = 0XFFFFFFFF
11:39:21.981 17 August: vmx | CPU [6]: 0 X 487 MSR = 0XFFFFFFFF
11:39:21.981 17 August: vmx | CPU [7]: MSR 0 X 487 = 0XFFFFFFFF
11:39:21.982 17 August: vmx | Frequent: MSR 0 x 487 = 0xffffffff
11:39:21.983 17 August: vmx | CPU [0]: 0 X 488 MSR = 0X2000
11:39:21.983 17 August: vmx | CPU [1]: MSR 0 X 488 = 0X2000
11:39:21.984 17 August: vmx | [2] CPU: 0 X 488 MSR = 0X2000
11:39:21.984 17 August: vmx | CPU [3]: MSR 0 X 488 = 0X2000
11:39:21.985 17 August: vmx | CPU [4]: MSR 0 X 488 = 0X2000
11:39:21.985 17 August: vmx | CPU [5]: MSR 0 X 488 = 0X2000
11:39:21.986 17 August: vmx | CPU [6]: 0 X 488 MSR = 0X2000
11:39:21.987 17 August: vmx | CPU [7]: MSR 0 X 488 = 0X2000
11:39:21.987 17 August: vmx | Frequent: MSR 0 x 488 = 0x2000
11:39:21.988 17 August: vmx | CPU [0]: 0 X 489 MSR = 0X27FF
11:39:21.989 17 August: vmx | CPU [1]: MSR 0 X 489 = 0X27FF
11:39:21.989 17 August: vmx | [2] CPU: MSR 0 X 489 = 0X27FF
11:39:21.990 17 August: vmx | CPU [3]: MSR 0 X 489 = 0X27FF
11:39:21.990 17 August: vmx | CPU [4]: MSR 0 X 489 = 0X27FF
11:39:21.991 17 August: vmx | CPU [5]: MSR 0 X 489 = 0X27FF
11:39:21.991 17 August: vmx | CPU [6]: 0 X 489 MSR = 0X27FF
11:39:21.992 17 August: vmx | CPU [7]: MSR 0 X 489 = 0X27FF
11:39:21.993 17 August: vmx | Frequent: MSR 0 x 489 = 0x27ff
11:39:21.993 17 August: vmx | CPU [0]: MSR 0X48A = 0X2C
11:39:21.994 17 August: vmx | CPU [1]: MSR 0X48A = 0X2C
11:39:21.994 17 August: vmx | [2] CPU: MSR 0X48A = 0X2C
11:39:21.995 17 August: vmx | CPU [3]: MSR 0X48A = 0X2C
11:39:21.995 17 August: vmx | CPU [4]: MSR 0X48A = 0X2C
11:39:21.996 17 August: vmx | CPU [5]: MSR 0X48A = 0X2C
11:39:21.996 17 August: vmx | CPU [6]: MSR 0X48A = 0X2C
11:39:21.997 17 August: vmx | CPU [7]: MSR 0X48A = 0X2C
11:39:21.998 17 August: vmx | Frequent: MSR 0x48a = 0x2c
11:39:21.998 17 August: vmx | CPU [0]: MSR 0X48B = 0 X 4100000000
11:39:21.999 17 August: vmx | CPU [1]: MSR 0X48B = 0 X 4100000000
11:39:21.999 17 August: vmx | [2] CPU: MSR 0X48B = 0 X 4100000000
11:39:22.000 17 August: vmx | CPU [3]: MSR 0X48B = 0 X 4100000000
11:39:22.000 17 August: vmx | CPU [4]: MSR 0X48B = 0 X 4100000000
11:39:22.001 17 August: vmx | CPU [5]: MSR 0X48B = 0 X 4100000000
11:39:22.002 17 August: vmx | CPU [6]: MSR 0X48B = 0 X 4100000000
11:39:22.002 17 August: vmx | CPU [7]: MSR 0X48B = 0 X 4100000000
11:39:22.003 17 August: vmx | Frequent: MSR 0x48b = 0 x 4100000000
11:39:22.003 17 August: vmx | CPU [0]: MSR 0X48C = 0
11:39:22.004 17 August: vmx | CPU [1]: MSR 0X48C = 0
11:39:22.004 17 August: vmx | [2] CPU: MSR 0X48C = 0
11:39:22.005 17 August: vmx | CPU [3]: MSR 0X48C = 0
11:39:22.006 17 August: vmx | CPU [4]: MSR 0X48C = 0
11:39:22.006 17 August: vmx | CPU [5]: MSR 0X48C = 0
11:39:22.007 17 August: vmx | CPU [6]: MSR 0X48C = 0
11:39:22.007 17 August: vmx | CPU [7]: MSR 0X48C = 0
11:39:22.008 17 August: vmx | Frequent: MSR 0x48c = 0
11:39:22.008 17 August: vmx | CPU [0]: MSR 0X48D = 0
11:39:22.009 17 August: vmx | CPU [1]: MSR 0X48D = 0
11:39:22.009 17 August: vmx | [2] CPU: MSR 0X48D = 0
11:39:22.010 17 August: vmx | CPU [3]: MSR 0X48D = 0
11:39:22.011 17 August: vmx | CPU [4]: MSR 0X48D = 0
11:39:22.011 17 August: vmx | CPU [5]: MSR 0X48D = 0
11:39:22.012 17 August: vmx | CPU [6]: MSR 0X48D = 0
11:39:22.012 17 August: vmx | CPU [7]: MSR 0X48D = 0
11:39:22.013 17 August: vmx | Frequent: MSR 0x48d = 0
11:39:22.013 17 August: vmx | CPU [0]: MSR 0X48E = 0
11:39:22.014 17 August: vmx | CPU [1]: MSR 0X48E = 0
11:39:22.015 17 August: vmx | [2] CPU: MSR 0X48E = 0
11:39:22.015 17 August: vmx | CPU [3]: MSR 0X48E = 0
11:39:22.016 17 August: vmx | CPU [4]: MSR 0X48E = 0
11:39:22.017 17 August: vmx | CPU [5]: MSR 0X48E = 0
11:39:22.017 17 August: vmx | CPU [6]: MSR 0X48E = 0
11:39:22.018 17 August: vmx | CPU [7]: MSR 0X48E = 0
11:39:22.018 17 August: vmx | Frequent: MSR 0x48e = 0
11:39:22.019 17 August: vmx | CPU [0]: MSR 0X48F = 0
11:39:22.019 17 August: vmx | CPU [1]: MSR 0X48F = 0
11:39:22.020 17 August: vmx | [2] CPU: MSR 0X48F = 0
11:39:22.021 17 August: vmx | CPU [3]: MSR 0X48F = 0
11:39:22.021 17 August: vmx | CPU [4]: MSR 0X48F = 0
11:39:22.022 17 August: vmx | CPU [5]: MSR 0X48F = 0
11:39:22.022 17 August: vmx | CPU [6]: MSR 0X48F = 0
11:39:22.023 17 August: vmx | CPU [7]: MSR 0X48F = 0
11:39:22.023 17 August: vmx | Frequent: MSR 0x48f = 0
11:39:22.024 17 August: vmx | CPU [0]: MSR 490 = 0X0
11:39:22.024 17 August: vmx | CPU [1]: MSR 490 = 0X0
11:39:22.025 17 August: vmx | [2] CPU: MSR 490 = 0X0
11:39:22.026 17 August: vmx | CPU [3]: MSR 490 = 0X0
11:39:22.026 17 August: vmx | CPU [4]: MSR 490 = 0X0
11:39:22.027 17 August: vmx | CPU [5]: MSR 490 = 0X0
11:39:22.027 17 August: vmx | CPU [6]: MSR 490 = 0X0
11:39:22.028 17 August: vmx | CPU [7]: MSR 490 = 0X0
11:39:22.028 17 August: vmx | Frequent: MSR 0 x 490 = 0
11:39:22.038 17 August: vmx | ACL_InitCapabilities: the current CPI thread
11:39:22.039 17 August: vmx | ACL_InitCapabilities: done
11:39:22.045 17 August: vmx | change directory to/vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/New Virtual Machine.
11:39:22.046 17 August: vmx | The configuration file: / vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/New Machine Virtual virtual/New Machine.vmx
11:39:22.055 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1
11:39:22.056 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 2, newAppState = 1878, success = 1
11:39:22.183 17 August: vmx | VMXVmdb_LoadRawConfig: Loading of raw configuration
11:39:22.260 17 August: vmx | VMXVmdbCbVmVmxExecState: Change of State Exec requested from receiving State without a reset, soft.
11:39:22.261 17 August: vmx | TOOLS, delaying state change of State 3 request
11:39:22.261 17 August: vmx | PowerOn
11:39:22.268 17 August: vmx | VMXVmdb_LoadRawConfig: Loading of raw configuration
11:39:22.273 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1871, success = 1
11:39:22.274 17 August: vmx | UNAME Linux Vm2.Trident.com 2.6.18 - 128.ESX #1 Fri Oct 15 16:11:16 PDT 2009 x86_64 (uwglibc release: vmware, version: 2.5)
11:39:22.275 17 August: vmx | DICT - USER PREFERENCES
11:39:22.275 17 August: vmx | DICT - DEFAULT USER
11:39:22.276 17 August: vmx | DICT - DEFAULT HOST
11:39:22.276 17 August: vmx | DICT libdir = / usr/lib/vmware
11:39:22.277 17 August: vmx | DICT authd.fullpath = / usr/sbin/vmware-authd
11:39:22.277 17 August: vmx | DICT = 902 authd.client.port
11:39:22.278 17 August: vmx | DICT vmware.fullpath = / usr/bin/vmware
11:39:22.278 17 August: vmx | DICT control.fullpath = / usr/bin/vmware-cmd
11:39:22.279 17 August: vmx | DICT serverd.fullpath = / usr/sbin/vmware-serverd
11:39:22.279 17 August: vmx | DICT = /usr/lib/vmware/serverd/init.pl serverd.init.fullpath
11:39:22.280 17 August: vmx | Authd.proxy.vim DICT = vmware - hostd:hostd - vmdb
11:39:22.280 17 August: vmx | DICT = vmware authd.proxy.nfc - pass: ha - nfc
11:39:22.281 17 August: vmx | DICT = vmware authd.proxy.nfcssl - pass: ha-nfcssl
11:39:22.281 17 August: vmx | DICT authd.soapServer = TRUE
11:39:22.282 17 August: vmx | DICT authd.proxy.vpxa - nfc = vmware - vpxa:vpxa - nfc
11:39:22.282 17 August: vmx | Authd.proxy.vpxa - nfcssl = vmware DICT - vpxa:vpxa - nfcssl
11:39:22.283 17 August: vmx | Authd.proxy.vua DICT = vmware - vua:vua
11:39:22.283 17 August: vmx | DICT - DEFAULT OF SITE
11:39:22.284 17 August: vmx | Tag.help = introduction.htm DICT
11:39:22.284 17 August: vmx | DICT = config_editor_newvm.htm tag.configurationEditor
11:39:22.285 17 August: vmx | DICT = devices_virtualdrive.htm tag.ideConfig
11:39:22.285 17 August: vmx | DICT = devices_floppy.htm tag.floppyConfig
11:39:22.286 17 August: vmx | DICT = devices_mouse.htm tag.mouseConfig
11:39:22.286 17 August: vmx | DICT = devices_netadapter.htm tag.netConfig
11:39:22.287 17 August: vmx | DICT = devices_parallel.htm tag.parallelConfig
11:39:22.287 17 August: vmx | DICT = devices_serial.htm tag.serialConfig
11:39:22.288 17 August: vmx | DICT = devices_sound.htm tag.soundConfig
11:39:22.288 17 August: vmx | DICT = configvm_memory.htm tag.memConfig
11:39:22.289 17 August: vmx | DICT = configvm.htm tag.miscConfig
11:39:22.289 17 August: vmx | DICT = devices_usb.htm tag.usbConfig
11:39:22.290 17 August: vmx | DICT tag.displayConfig = configvm_display - problems.htm
11:39:22.290 17 August: vmx | DICT = vmtools.htm tag.tools
11:39:22.291 17 August: vmx | DICT - COMMAND LINE
11:39:22.291 17 August: vmx | Sched.group = host/user DICT
11:39:22.292 17 August: vmx | DICT - CONFIGURATION
11:39:22.293 17 August: vmx | DICT config.version = 8
11:39:22.293 17 August: vmx | DICT = 4 virtualHW.version
11:39:22.293 17 August: vmx | DICT floppy0.present = TRUE
11:39:22.294 17 August: vmx | Nvram DICT = New Virtual Machine.nvram
11:39:22.294 17 August: vmx | DICT deploymentPlatform = windows
11:39:22.295 17 August: vmx | DICT virtualHW.productCompatibility hosted =
11:39:22.296 17 August: vmx | Tools.upgrade.policy DICT = useGlobal
11:39:22.296 17 August: vmx | DICT powerType.powerOff = default
11:39:22.296 17 August: vmx | DICT powerType.powerOn = default
11:39:22.297 17 August: vmx | DICT powerType.suspend = default
11:39:22.297 17 August: vmx | DICT powerType.reset = default
11:39:22.298 17 August: vmx | DICT displayName = DR - App - 2K 3
11:39:22.299 17 August: vmx | ExtendedConfigFile DICT = New Machine.vmxf virtual
11:39:22.299 17 August: vmx | DICT = 2 numvcpus
11:39:22.300 17 August: vmx | DICT scsi0.present = TRUE
11:39:22.300 17 August: vmx | DICT = none scsi0.sharedBus
11:39:22.301 17 August: vmx | Scsi0.virtualDev DICT = free
11:39:22.301 17 August: vmx | DICT memsize = 4000
11:39:22.302 17 August: vmx | DICT scsi0:0.present = TRUE
11:39:22.302 17 August: vmx | Scsi0:0.fileName DICT = / vmfs/volumes/49d49d5a-7a2c59b4 - 84 b 2-00215ad0ad60/New Machine Virtual virtual/New Machine.vmdk
11:39:22.303 17 August: vmx | DICT scsi0:0.deviceType = scsi-disk hard
11:39:22.303 17 August: vmx | DICT ide0:0.present = TRUE
11:39:22.304 17 August: vmx | DICT = /vmfs/volumes/4a647488-7b17ef50-cfac-001f295fac34/ISO/en_sql_2005_ent_x86_cd2.iso ide0:0.fileName
11:39:22.305 17 August: vmx | DICT ide0:0.deviceType = cdrom-image
11:39:22.305 17 August: vmx | DICT floppy0.startConnected = FALSE
11:39:22.306 17 August: vmx | DICT floppy0.clientDevice = TRUE
11:39:22.306 17 August: vmx | DICT ethernet0.present = TRUE
11:39:22.307 17 August: vmx | Ethernet0.networkName DICT = Trident VM DR network
11:39:22.307 17 August: vmx | Ethernet0.addressType DICT = vpx
11:39:22.308 17 August: vmx | DICT ethernet0.generatedAddress = 00:50:56:af:21:ac
11:39:22.308 17 August: vmx | DICT chipset.onlineStandby = FALSE
11:39:22.309 17 August: vmx | DICT guestOSAltName = Microsoft Windows Server 2003, Standard Edition (32-bit)
11:39:22.309 17 August: vmx | DICT guestOS = winnetstandard
11:39:22.310 17 August: vmx | DICT uuid.bios = 50 2f b 32 9 79 b9 92 29 - 5 d 0a 3 c cd e0 b8 8f b2
11:39:22.310 17 August: vmx | Snapshot.action = DICT continue
11:39:22.311 17 August: vmx | DICT = 0 sched.cpu.min
11:39:22.311 17 August: vmx | Sched.cpu.units DICT = mhz
11:39:22.312 17 August: vmx | Sched.cpu.shares = normal DICT
11:39:22.312 17 August: vmx | DICT = 0 sched.mem.minsize
11:39:22.313 17 August: vmx | Sched.mem.shares = normal DICT
11:39:22.314 17 August: vmx | DICT toolScripts.afterPowerOn = TRUE
11:39:22.314 17 August: vmx | DICT toolScripts.afterResume = TRUE
11:39:22.315 17 August: vmx | DICT toolScripts.beforeSuspend = TRUE
11:39:22.315 17 August: vmx | DICT toolScripts.beforePowerOff = TRUE
11:39:22.316 17 August: vmx | DICT floppy0.fileName = / dev/fd0
11:39:22.316 17 August: vmx | Scsi0:0.redo = DICT
11:39:22.317 17 August: vmx | DICT ide0:0.startConnected = FALSE
11:39:22.317 17 August: vmx | DICT tools.syncTime = FALSE
11:39:22.318 17 August: vmx | DICT uuid.location = 56 4 d 38 36 6 e6 9 c a3 40-17 45 d 71 a0 4 b aa f5
11:39:22.318 17 August: vmx | DICT migrate.hostlog is. / New Virtual Machine - ad94a097.hlog
11:39:22.319 17 August: vmx | DICT sched.swap.derivedName = / vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/New Machine virtual/new Virtual Machine - ad94a097.vswp
11:39:22.319 17 August: vmx | HostCPUID.0 DICT = 0000000a756e65476c65746e49656e69
11:39:22.320 17 August: vmx | GuestCPUID.0 DICT = 0000000a756e65476c65746e49656e69
11:39:22.320 17 August: vmx | UserCPUID.0 DICT = 0000000a756e65476c65746e49656e69
11:39:22.321 17 August: vmx | HostCPUID.1 DICT = 0001067600040800000ce3bdbfebfbff
11:39:22.321 17 August: vmx | GuestCPUID.1 DICT = 0001067600010800000822010febbbff
11:39:22.322 17 August: vmx | UserCPUID.1 DICT = 0001067600040800000822010febbbff
11:39:22.322 17 August: vmx | DICT = 00000000000000000000000120100800 hostCPUID.80000001
11:39:22.323 17 August: vmx | DICT = 00000000000000000000000120100800 guestCPUID.80000001
11:39:22.323 17 August: vmx | DICT = 00000000000000000000000120100800 userCPUID.80000001
11:39:22.324 17 August: vmx | DICT evcCompatibilityMode = FALSE
11:39:22.324 17 August: vmx | DICT ide0:0.clientDevice = FALSE
11:39:22.325 17 August: vmx | DICT tools.remindInstall = TRUE
11:39:22.325 17 August: vmx | Vc.uuid DICT = 502fe142-b302-7f61-5d96-238a7a35bfc4
11:39:22.326 17 August: vmx | DICT cleanShutdown = TRUE
11:39:22.326 17 August: vmx | DICT replay.supported = FALSE
11:39:22.327 17 August: vmx | DICT vmotion.checkpointFBSize = 4194304
11:39:22.327 17 August: vmx | DICT - DEFAULT USER
11:39:22.328 17 August: vmx | DICT - DEFAULT HOST
11:39:22.328 17 August: vmx | DICT libdir = / usr/lib/vmware
11:39:22.329 17 August: vmx | DICT authd.fullpath = / usr/sbin/vmware-authd
11:39:22.329 17 August: vmx | DICT = 902 authd.client.port
11:39:22.330 17 August: vmx | DICT vmware.fullpath = / usr/bin/vmware
11:39:22.330 17 August: vmx | DICT control.fullpath = / usr/bin/vmware-cmd
11:39:22.331 17 August: vmx | DICT serverd.fullpath = / usr/sbin/vmware-serverd
11:39:22.331 17 August: vmx | DICT = /usr/lib/vmware/serverd/init.pl serverd.init.fullpath
11:39:22.332 17 August: vmx | Authd.proxy.vim DICT = vmware - hostd:hostd - vmdb
11:39:22.332 17 August: vmx | DICT = vmware authd.proxy.nfc - pass: ha - nfc
11:39:22.333 17 August: vmx | DICT = vmware authd.proxy.nfcssl - pass: ha-nfcssl
11:39:22.333 17 August: vmx | DICT authd.soapServer = TRUE
11:39:22.334 17 August: vmx | DICT authd.proxy.vpxa - nfc = vmware - vpxa:vpxa - nfc
11:39:22.334 17 August: vmx | Authd.proxy.vpxa - nfcssl = vmware DICT - vpxa:vpxa - nfcssl
11:39:22.335 17 August: vmx | Authd.proxy.vua DICT = vmware - vua:vua
11:39:22.335 17 August: vmx | DICT - DEFAULT OF SITE
11:39:22.336 17 August: vmx | Tag.help = introduction.htm DICT
11:39:22.336 17 August: vmx | DICT = config_editor_newvm.htm tag.configurationEditor
11:39:22.337 17 August: vmx | DICT = devices_virtualdrive.htm tag.ideConfig
11:39:22.337 17 August: vmx | DICT = devices_floppy.htm tag.floppyConfig
11:39:22.338 17 August: vmx | DICT = devices_mouse.htm tag.mouseConfig
11:39:22.338 17 August: vmx | DICT = devices_netadapter.htm tag.netConfig
11:39:22.339 17 August: vmx | DICT = devices_parallel.htm tag.parallelConfig
11:39:22.339 17 August: vmx | DICT = devices_serial.htm tag.serialConfig
11:39:22.340 17 August: vmx | DICT = devices_sound.htm tag.soundConfig
11:39:22.340 17 August: vmx | DICT = configvm_memory.htm tag.memConfig
11:39:22.341 17 August: vmx | DICT = configvm.htm tag.miscConfig
11:39:22.341 17 August: vmx | DICT = devices_usb.htm tag.usbConfig
11:39:22.342 17 August: vmx | DICT tag.displayConfig = configvm_display - problems.htm
11:39:22.342 17 August: vmx | DICT = vmtools.htm tag.tools
11:39:22.343 17 August: vmx | DICT - GLOBAL SETTINGS
11:39:22.350 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1
11:39:22.351 17 August: vmx | hostCpuFeatures = 0x446001fc
11:39:22.352 17 August: vmx | hostNumPerfCounters = 2
11:39:22.352 17 August: vmx | MONITOR MODE: enabled modes: HV BT
11:39:22.353 17 August: vmx | MONITORING MODE: user requested modes: BT HV HWMMU
11:39:22.353 17 August: vmx | MONITORING MODE: guestOS favorite modes: HWMMU HT BT
11:39:22.354 17 August: vmx | MONITORING MODE: filtered the list: HV BT
11:39:22.354 17 August: vmx | HV settings: exec virtual = "hardware"; MMU virtual = "software".
11:39:22.412 17 August: vmx | VMMon_ConfigMemSched: vmmon.numVCPUs = 2
11:39:22.413 17 August: vmx | CreateVM: Swap: normal file name generation.
11:39:22.415 17 August: vmx | The swap file path: ' / vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/New Virtual Machine / new VM - ad94a097.vswp'
11:39:22.510 17 August: vmx | The swap file using "/ vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/New Virtual Machine/new Virtual Machine - ad94a097.vswp'"
11:39:22.510 17 August: vmx | VMXVmdb_LoadRawConfig: Loading of raw configuration
11:39:22.531 17 August: vmx | LogBackupByRenumber: cannot read directory ' / vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/a new Machine virtual/stats.
11:39:22.535 17 August: vmx | LogBackupByRenumber: cannot read directory ' / vmfs/volumes/47acbc44-4fba0e6d-f782-001f295fa140/a new Machine virtual/stats.
11:39:22.547 17 August: vmx | Vmm32-modules: [vmm.vmm32 .data:0x2b000 - 0xe44 .sdata:0x2c000 - 0x4e4 .statvars:0x2d000 - 0x3a8 .peer:0x2e000 - 0x261c0 .shared:0 x 56000-0x190c0 .bss:0 x 70000-0x5dc8 .rodata:0 x 77000-0xbec0 .text:0 x 84000-0x614bd .kstatvars:0 x 3000-0 x 0, mmu - pae.vmm32 .rodata:0x82ec0 - .data:0x2be44 0 x 44 - 0xc .peer:0x541c0 - 0x16c0 .shared:0x6f0c0 - 0 x 380 .bss:0x75de0 - 0x51c .text:0xe54c0 - 0xa927 .comment:0x40000e10 - 0x10e .statvars:0 x 2000 - .kstatvars:0 2000 x 0 x 0 0 x 0 .scb:0x40004fe0 - 0 x 180 .shared_meta:0x40004f50 - 0 x 390 .peer_meta:0x40000e70 - 0 x 210, sharedmmu - none.vmm32 .text:0xefde8 - .comment:0x40000f1e 0 x 37-0 x 12] , pv - none.vmm32 .shared:0x6f440 - 0 x 180 .bss:0 x 76300 - .text:0xefe20 0 x 84 - .comment:0x40000f30 0xe2-0 x 48 .shared_meta:0x400052e0 - 0 x 90, vprobe - none.vmm32 .text:0xeff04 - .comment:0x40000f78 0 x 19-0 12, hv - vt.vmm32 .rodata:0x82f04 - .data:0 x 1000 0 4 - .peer:0 x 1000 x 0 x 0 0 0 x 1000 .shared:0 - .bss:0 x 1000 0 x 0 0 0 .text:0xeff20 - 0x1a1 .comment:0x40000f8a - 0 x 12 .statvars:0 x 1000 - .kstatvars:0 x 1000 0 x 0 0 x 0 , gphys - sw.vmm32 .peer:0 x 55880 - .shared:0x6f5c0 0x40 - .bss:0 x 2000 0x80 - .text:0xf00d0 0 x 0-0 763 .comment:0x40000f9c - 0 x 12 .scb:0 x 40005160-0 x 60 .shared_meta:0 x 40005370 - 0 x 240 .peer_meta:0 x 40001080-0 x 30, vassert - none.vmm32 .text:0xf0834 - 0xf .comment:0x40000fae - 0 x 12, vmsafe - none.vmm32 .text:0xf0844 - 0x1b .comment:0x40000fc0 - 0 x 12, videio - none.vmm32 .rodata:0x82f08 - 0xdf .data:0 x 1000 - .peer:0 x 1000 0 x 0 0 0 x 1000 .shared:0 - .bss:0 x 1000 0 x 0 0 x 0 .text:0xf0860 - 0xaa .comment:0x40000fd2 - 0 x 12 x 1000 .statvars:0 - .kstatvars:0 1000 x 0 x 0-0 [x 0 .rodata:0x82fe7 - 0x3e9]
11:39:22.551 17 August: vmx | KHZEstimate 2833334
11:39:22.551 17 August: vmx | 2833 MHZEstimate
11:39:22.552 17 August: vmx | NumVCPUs 2
11:39:22.553 17 August: vmx | UUID: location-UUID is 4 d 56 19 85 9th 7th 5 c cb - c9 c1 16 c4 60 6 d3 b 9 c
11:39:22.554 17 August: vmx | UUID: location-UUID is 4 d 56 19 85 9th 7th 5 c cb - c9 c1 16 c4 60 6 d3 b 9 c
11:39:22.554 17 August: vmx | UUID: location-UUID is 4 d 56 19 85 9th 7th 5 c cb - c9 c1 16 c4 60 6 d3 b 9 c
11:39:22.555 17 August: vmx | UUID: location-UUID is 4 d 56 19 85 9th 7th 5 c cb - c9 c1 16 c4 60 6 d3 b 9 c
11:39:22.555 17 August: vmx | Msg_Question:
11:39:22.556 17 August: vmx | http://Msg.UUID.altered this virtual machine may have been moved or copied.
11:39:22.556 17 August: vmx |
11:39:22.556 17 August: vmx | In order to configure certain management and network features VMware ESX must know that.
11:39:22.556 17 August: vmx |
11:39:22.556 17 August: vmx | Did you move this virtual machine, or you copied it?
11:39:22.556 17 August: vmx | If you are unsure, answer "I copied it".
11:39:22.556 17 August: vmx |
11:39:22.556 17 August: vmx | -
11:40:01.066 17 August: vmx | Msg_Question: answer = 1 msg.uuid.altered
11:40:01.068 17 August: vmx | "UUID: writing uuid.location value: ' 4 d 56 19 85 9th 7th 5 c cb - c9 9 c c1 16 c4 60 6B d3.
11:40:01.079 17 August: vmx | AIOGNRC: numThreads = 2 = 0, = 0 scsi ide, passthru = 1
11:40:01.080 17 August: vmx | WORKER: Create a new group with numThreads = 2 (2)
11:40:01.081 17 August: vmx | CPU0: PMC: Patch 0x60c, smmFrz (hw) level: (1).
11:40:01.082 17 August: vmx | PMC: IA32, Penryn
11:40:01.083 17 August: vmx | CPU1: PMC: Patch 0x60c, smmFrz (hw) level: (1).
11:40:01.084 17 August: vmx | PMC: IA32, Penryn
11:40:01.085 17 August: vmx | CPU2: PMC: Patch 0x60c, smmFrz (hw) level: (1).
11:40:01.086 17 August: vmx | PMC: IA32, Penryn
11:40:01.087 17 August: vmx | CPU3: PMC: Patch 0x60c, smmFrz (hw) level: (1).
11:40:01.088 17 August: vmx | PMC: IA32, Penryn
11:40:01.089 17 August: vmx | CPU4: PMC: Patch 0xa07, smmFrz (hw) level: (1).
11:40:01.090 17 August: vmx | PMC: IA32, Penryn
11:40:01.091 17 August: vmx | CPU5: PMC: Patch 0xa07, smmFrz (hw) level: (1).
11:40:01.092 17 August: vmx | PMC: IA32, Penryn
11:40:01.093 17 August: vmx | CPU6: PMC: Patch 0xa07, smmFrz (hw) level: (1).
11:40:01.094 17 August: vmx | PMC: IA32, Penryn
11:40:01.095 17 August: vmx | CPU7: PMC: Patch 0xa07, smmFrz (hw) level: (1).
11:40:01.096 17 August: vmx | PMC: IA32, Penryn
11:40:01.097 17 August: vmx | minDEThreshold: 76
11:40:01.162 17 August: vmx | Mainmem mapped as pageable
11:40:01.163 17 August: vmx | MStat: Creation vm.uptime Stat
11:40:01.163 17 August: vmx | MStat: Creation vm.suspendTime Stat
11:40:01.164 17 August: vmx | MStat: Creation vm.powerOnTimeStamp Stat
11:40:01.164 17 August: vmx | VMXAIOMGR: Use: simple = unbuf generic generic =
11:40:01.177 17 August: vmx | VMXVmdb_LoadRawConfig: Loading of raw configuration
11:40:01.184 17 August: vmx | Cannot find the file/vmfs/volumes/49d49d5a-7a2c59b4 - 84 b 2-00215ad0ad60/New Machine Virtual virtual/New Machine.vmdk
11:40:01.185 17 August: vmx | Cannot find the file/vmfs/volumes/49d49d5a-7a2c59b4 - 84 b 2-00215ad0ad60/New Machine Virtual virtual/New Machine.vmdk
11:40:01.186 17 August: vmx | DISC: Scsi0:0 [OPEN ' / vmfs/volumes/49d49d5a-7a2c59b4 - b 84-2 - 00215ad0ad60 / New Virtual Machine/new Virtual Machine.vmdk' persistent R]
11:40:01.187 17 August: vmx | Cannot find the file/vmfs/volumes/49d49d5a-7a2c59b4 - 84 b 2-00215ad0ad60/New Machine Virtual virtual/New Machine.vmdk
11:40:01.191 17 August: vmx | DISKLIB-DSCPTR: DescriptorDetermineType: cannot open ' / vmfs/volumes/49d49d5a-7a2c59b4 - b 84-2 - 00215ad0ad60 / New Virtual Machine/new Virtual Machine.vmdk': could not find the file (63)
11:40:01.194 17 August: vmx | DISKLIB-LINK: ' / vmfs/volumes/49d49d5a-7a2c59b4 - 84 b 2-00215ad0ad60/new Machine Virtual virtual/New Machine.vmdk ': cannot open (the system cannot find the specified file).
11:40:01.194 17 August: vmx | DISKLIB-STRING: "/ vmfs/volumes/49d49d5a-7a2c59b4 - 84 b 2-00215ad0ad60/new Machine Virtual virtual/New Machine.vmdk ': cannot open (the system cannot find the specified file).
11:40:01.195 17 August: vmx | "DISKLIB-LIB: can't open ' / vmfs/volumes/49d49d5a-7a2c59b4 - b 84-2 - 00215ad0ad60 / New Virtual Machine/new Virtual Machine.vmdk ' with flags 0xa (the system cannot find the specified file).
11:40:01.196 17 August: vmx | Msg_Post: error
11:40:01.196 17 August: vmx | http://Msg.disk.FileNotFound VMware ESX can not find the virtual disk "/ vmfs/volumes/49d49d5a-7a2c59b4 - 84 b 2-00215ad0ad60/new Machine Virtual virtual/New Machine.vmdk. Please check that the path is valid and try again.
11:40:01.197 17 August: vmx | http://Msg.disk.noBackEnd cannot open disk ' / vmfs/volumes/49d49d5a-7a2c59b4 - b 84-2 - 00215ad0ad60 / New Virtual Machine/new Virtual Machine.vmdk' or one of the snapshot disks it depends on.
11:40:01.197 17 August: vmx | http://Msg.disk.configureDiskError reason: the system cannot find the specified file. -.
11:40:01.210 17 August: vmx | Power DiskEarly module has failed.
11:40:01.213 17 August: vmx | VMX_PowerOn: ModuleTable_PowerOn = 0
11:40:01.215 17 August: vmx | WORKER: asyncOps = 0 maxActiveOps = 0 maxPending = 0 maxCompleted = 0
11:40:02.312 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1
11:40:02.321 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1
11:40:02.322 17 August: vmx | VMX/execState/val goes to poweredOff
11:40:02.323 17 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 0
11:40:02.323 17 August: vmx | Output of idle VMX
11:40:02.327 17 August: vmx | VIX: : VMAutomation_LateShutdown()
11:40:02.328 17 August: vmx | VIX: : VMAutomationCloseListenerSocket. Close the socket of the receiver.
11:40:02.336 17 August: vmx | VMX VMDB Flushing connections
11:40:02.351 17 August: vmx | IPC_exit: disconnect all discussions
11:40:02.352 17 August: vmx | Exit VMX (0).
11:40:02.352 17 August: vmx | AIOMGR-S: o stat = 1 r = 0 w = 0 I = 0 br = 0 = 0 p.c.
11:40:02.353 17 August: vmx | VMX has left the building: 0.
The virtual machine is showing the new Virtual Machine - flat hard. It fails on 60%
I don't think that there are pictures on this machine.
Any help would be welcome.
Thank you very much
Lee
The virtual machine is showing the new Virtual Machine - flat hard.
If it appears in the browser to store data, then it seems that the header/descriptor file is lost for some reason any.
Generally, it should show "Virtual Machine.vmdk"
To re-create the header file, see http://kb.vmware.com/kb/1002511
André
-
What is the difference between SATA and regular cables?
I am a student in the article so I have a small doubt
What is the difference between sata cables and normal"What is the difference between sata cables and normal."
If by "normal" you make cables referring to the old SCSI or IDE/PATA cables in water it
is a very big difference.
SCSI (IDE/PATA are similar, but with the pins are connecting less) is the former cable style and support of the motherboard for the latter is way of disappearance on newer systems.
SATA cables are used on the latest HARD drives and SSD and are supported by all the "modern".
motherboards. The one in the photo was an end at right angles, but most are right.
Two types of cable are used for HARD disk SSD and optical drives.
BTW - As an IT student would serve you yourself well learn how to search the Internet for
answers to these questions.
.
-
I am trying to configure my Aironet 1121 G acess points with several VLANs, got the VLAN everything works great with wired devices, but wireless devices don't you DHCP.
Basically I have the BVI on my virtual LAN management and two other vlans that cross, try to have the public WiFi on 1 vlan and the two VLAN corporate with separate wifi. Impossible to get IPs on any of them though.
Vlnas are moved by a catlayst 3550 with addresses of assistance set up on all the VLAN interfaces.
DHCP comes from 2 boxes of windows on another virtual local network Server 2003
any ideas?
Hello
If I understand, you have plugged your access point to one of the L2 switch. I suggest you to set up your L3 (tandem switch) with pool dhcp to obtain the ip address for vlan respective first.
To set the dhcp pool in your L3 192.168.2.1.
create interface IVR and IP address assignment for the VLAN respective (which will act as a gateway of the vlan respective)
Repeat the same for all the VLANS.
Create the DHCP pool for the vlan respective and router by default with the ip address of L3.
AccessPoint#configure terminal
AccessPoint(config)#interface dot11radio 0
AccessPoint(config-if)#ssid .......give the name of your ssid
AccessPoint(config-if-ssid)#vlan ?
AccessPoint(config-if-ssid)#authentication open
AccessPoint(config-if-ssid)#end
AccessPoint(config) interface fastethernet 0.30
AccessPoint(config-subif) encapsulation dot1Q 30
AccessPoint(config-subif) exit
AccessPoint(config) interface dot11radio 0.30
AccessPoint(config-subif) encapsulation dot1Q 30
AccessPoint(config-subif) exitCheck if you have the ip address for the customers.
In case await you get the IP address of your external dhcp server...
try to give below command on each respective dot11Radio 0 subinterface "helper-... to give the dhcp server ip address here"
Please let me know if it works...
Thank you
Vinod
-
11.1 workstation, Windows 7 SP1 x 64, EFI, the CD-ROM does not start
Is Windows 7 x 64 supported as an EFI guest OS in my computer with hardware 11.1 virtual v11?
I recently upgraded from Workstation v9 to v11.1.0 build-2496824 under my Windows 7 SP1 x 64 machine and tried to create a new guest Windows 7 support EFI and the installation media does not start to get the Setup will.
The same boot on any BIOS type invited media and I tried Windows 7 and Windows 7 with SP1 integrated all directly from Microsoft, not custom ISOs and none of them will work under EFI, but will work under BIOS. In the same way 2008 and 2008 R2 media starts if EFI is used.
EFI VMs can boot media of Windows 8 and successfully towards the top (2012 etc.) but not the previous generation of operating system.
I tried a few different things, such as starting the ISO from a disk share and local network.
I tried all 3 variants of the dvd/cdrom: SATA, SCSI, IDE, including the legacy mode which I don't think that is really work because it is not verified when I go back to change the setting.
I tried to install from the EFI shell initialization, but the media are not yet mounted under blk0 so I can't go any further.
My boot device options are all configured properly and tried to force the virtual cdrom boot at startup without success.
I also tried going through the physical CD-ROM mapping rather than the ISO file and not luck.
My Setup seems to be supported, however the matrix of interoperability and compatibility points vs EFI BIOS support. I know that Windows 7 supports UEFI then it should work and I've seen posts where people have deployed it successfully under different versions of workstation using the EFI emulation.
I also tried with hardware virtual v10
Both typical and custom installation modes recognize media but can't can at start up.
Should I do the start method USB with a sort of generation of personalized media?
Here is an excerpt from the log file where it seems just that it's not picking up on startup even though we clearly see the ISO it:
2015 03-27 T 13: 33:51.427 - 04:00 | vCPU-0 | I120: CDROM: connecting sata0:1 to 'D:\WIN7SP1X64ENT.iso '. Type = 2 distance = 0
2015 03-27 T 13: 33:51.427 - 04:00 | vCPU-0 | I120: DMG_Open: not a .dmg unencrypted file (footer signature 0 x 00000000).
2015 03-27 T 13: 33:51.427 - 04:00 | vCPU-0 | I120: DMG_Close: max cached entries 8
2015 03-27 T 13: 33:51.427 - 04:00 | vCPU-0 | I120: CDROM: check the status of the original physical media...
2015 03-27 T 13: 33:51.427 - 04:00 | vCPU-0 | I120: CDROM: CDROM initial physical state is 1 (meaning)
2015 03-27 T 13: 33:51.427 - 04:00 | vCPU-0 | I120: PolicyVMXFindPolicyKey: policy file does not exist.
I just want to know if it is actually supported and if someone else has this problem there.
It was about 3.5 GB but I just downloaded a new copy on the site MS VL and apparently boot into EFI now. Don't know how the ISO precedent (and other ISOs 2008) would work under BIOS but not EFI but it's good enough for me.
Thanks to confirm support of the scenario mentioned however, I had thoughts seconds on this subject.
-
Windows Embedded POS ready 2009
Last year I had successfully installed a loan in 2009, but since it was a trial that is no longer working and I tried to install a new POS Embedded Windows system but to the reboot I always end up with a blue screen.
I had tried with a partial disk configuration and configuration of disk full, but none works.
Someone at - he had similar experiences and what can be done for this install correctly on a virtual machine?
Thank you
\Manfred
A STOP 0x0000007B error means that Windows is not able to find the startup disk. This can occur if Windows does not have the correct driver installed for the (virtual) storage card.
This can happen if you create your guests with a SCSI LSILogic (virtual) adapter and then forget to install the SCSI driver that is appropriate during the initial installation of Windows.
If I had to guess, I would say that the Assistant new VM in VMware correctly detects the operating system on your installation CD, and the autoinstall process is therefore not get the appropriate SCSI driver installed.
Try to re-create your guest, but in the course of the new Virtual Machine Wizard, select "I will install the operating system later". Which will allow you to manually choose the type of hard drive that you want to install (Buslogic SCSI, IDE or SCSI free). Windows XP comes with the IDE and Buslogic drivers out of the box (if I remember correctly).
-
Thanks in advance for any input-
NOOB here after having downloaded and saved a VMware vSphere on a single server hypervisor (quad core Xeon 22 Gb ram 4 NIC and disk of 1 TB Raid 5). First attempt, use the converter stand alone on my PC. Worked perfectly. Then Server #1 Windows 2003 SP2 on IDE drive. A ran "Convert the Machine" even under XP. BSOD on startup. No safe mode. Attempted to change Boot.ini od but file was accurate. Reran conversion more than 2 times the same result. Then, the server #2. Once again Win 2003 SP2. Ran "convert to Machine. Web information found and ran "Configure machine" after sysprep installation correct files including install VMware tools. Exact same results except that now I get a VM splash screen before auto BSOD then reboot. Able to access safe mode. BSOD before anything else. What the hell I'm missing?
In the converter (step 3) wizard select 'trick' and the "disk controller" the value of "Preserve the Source" "LSI Logic.
André
-
Physical disk how can I add in the Virtual Machine?
I am trying to set up a network of storage, but I discovered it is there is a limitation for the addition of physical hard disks in the virtual machine.
I have 1 virtual hard disk for the operating system (SCSI), an invited so I try to add more than 4 disks, but it should not add more than 3. They showed that (IIRC).
I try to add 4 x 1 TB as physical hard disk in virtual machine hard disks, but it says that I must remove one to add.
1. in the settings of the Virtual Machine, is there a difference between (SCSI) (IDE) and why are the physical disks (IDE)?
2. What is the limitation of total hard drives under the VM settings, four?
Johwwy
physical disks can be detected such as IDE or SCSI - depends on the drivers used by the host
SATA in ide-compat mode is used as IDE
SATA AHCI mode is detected as SCSI
It is possible to rewrite the descriptions after their creation.
It is a little advanced - see my notes
http://sanbarrow.com/VMDK-basics.html#changeadapter
for a start, it may be necessary to also change the geometry... ask first so uncertain.
I think the limit of physical disks that can be attached to a virtual machine is 64 = 4 x 15 - scsi and IDE 4-disc drives
_________________________
VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual
-
Best method to migrate customers of hosted XP Workstation to ESXi?
Currently confused. I have an XP host workstation running 6. I want to migrate 4 XP clients to a server ESXi 3.5. I do not know if this post should be under ESXi, Workstation or converter... This seemed the best place.
I created an ESXi server with a data store and a guest. The guest is XP, I used LSILogic.flp to get the installed operating system. I understand that the import in ESXi option only works with the virtual appliance (ovf) files.
To migrate a guest, I used VM Workstation & gt; Import & gt; the workstation to ESXi server. Everything was going fine until, after that I specified the data store when I got the error "Unknown error returned from Agent VMware Converter". I know that the block of data store size is 1 MB, not sure if that is the question, how to change it, or if I should change the configuration of source comments beforehand.
Other issues as I see them are that (1) the comments of the workstation disks are IDE and in ESXi creates its SCSI drives and (2) I think I'll need to reinstall VMware Tools.
Above, Export/Import failed. Other methods available, I can see to migrate guests include the creation of an OVF file from the workstation customers (it is possible?), or be brutal and imaging my existing customers and then the installation of the image in a prompt on the ESXi machine.
What is the best way to proceed? Can I get the workstation import to succeed? Are there simple ways to deal with the SCSI/IDE and emits the VMware Tools?
I tried VMware converter?
-Matt
VCP, vExpert, Unix Geek
-
Windows Server 2003 on the HARD IDE in Mode ATAPI drive?
Hello!
My problem is that I want to know if a HDD IDE will run in Mode ATAPI.More details >
There is a motherboard of INTEL S5000 VSA server in the office. He already had Win 2003 and everything was fine until the HARD drive crashed and the people replaced by an a SCSI maintenance (I don't know if he had a SATA, SCSI or an IDE HDD previously). After installing new HARD drive, they were not able to install Win server 2003 and went for 2008. Windows Server 2008 creates problems for us and the maintenance people are also confused and unresponsive to the situation.
We have Windows Server 2003 R2. The motherboard has only one IDE port but scored the "working mode" as ATAPI. I was wondering if I could just attach an IDE HDD and install Win Server 2003 R2 (since win 2003 supports SATA out-of-the-box)
(Displayed in the section of WIN XP as Win 2003 sharing the same base with XP, XP users can comment too)
http://www.Intel.com/CD/channel/reseller/APAC/Eng/products/server/boards/DP/S5000VSA/feature/index.htm#specifications
If a geek myself, I'm not very educated when it comes to servers. a Google search also did not help. I would be grateful if someone can help out me.
Thank you
Chirag.Yes it will install and work fine on an IDE hard drive, ATAPI devices are all IDE drives. The downside is that the reader will be much slower than the SCSI on a busy server, which can be a big disadvantage.
For all its value that they probably could not install Server 2003 on the SCSI disk because they weren't using the method of F6 to provide drivers SCSI on a diskette or that they could not understand or how their wake worth installation CD. There is no need of such a monumental lapse, notwithstanding the limitation INT-13 NT4 Server installed on SCSI and Server 2003 installs on SCSI providing that you give appropriate when installing drivers.
John
-
WinXP Pro think my IDE/ATAPI Zip 100 Drive is a SCSI device and does not read disks.
Zip Drive 100 a () works fine in my old computer with Windows XP and my new computer P4 (Core 2 Duo) the analysis of the Bios boot correctly sees as an IDE/ATAPI drive, but the Device Manager Windows XP Pro says it's a SCSI device. Tried several zip disks that work very well old computer. Also noticed that the computer WinXP Pro says the disc have a RAW format file system when I click Properties of the drive in 'My computer', but the disks are formatted with the FAT of another computer file system. When I try to read the disc, WinXP Pro says that they aren't formatted - I want to get in shape, so I tried to format a and she failed.(1) problem RAW file system: CPU OS WIN XP D: drive is IDE/ATAPI ZIP - 100. C:HDD E:DVD F: CD-ROM. A ZIP disk would not format of older CPU. Also at the DOS prompt displayed ZIP disk saves but XP files don't display anything without files or diskThe drive was not recognized by XP because of the type of file in RAW format. COULD NOT read or format. Similar to your problem
To solve: KICKED CPU with the WIN ME & WIN ME CD startup disk. Backpack prompt type A: B: the ZIPPER was displayed. Then Typ B: format b: enter & reformatted in the ZIP in the BACK. Typed in the label to check the format. Rebooted FDD & CD removed & CPU disc. In XP my computer now recognizes the D: drive with a ZIP disk. The file system has changed from RAW to FAT. Correction of a problem
(2) your problem: IDE/ATAPI ZIP - 100 HDD not found in XP operating system but as seen in the BIOS.
To fix: check hardware configuration. ZIP drive must be jumped as a slave in the Middle connection on the water with your hard disk (HDD) cable. ZIP - 100 should show that D: & Hard drive show as C: make sure that the ribbon cable is attached properly - PIN 1 for the two discs in PIN 1 of the cable. Also, ZIP supply sheets must be connected correctly.
Hope the above will solve the two problems of ZIP - 100 drive your.
-
Windows 7 cannot see is not my SCSI disks when I try to install. As the IDE drive is showen but is not usable. Is there a FDISK program that can be run to solve this problem from a command promt?
Hello
You try to access BIOS and change the SCSI to IDE in the BIOS or Raid in IDE and try to install Windows 7.
If it fails, contact your SCSI manufacturer for the latest drivers for your SCSI and install it by clicking on load drivers and try to install Windows 7.
Hope this helps and works.
Chris
-
12, WinPE 10 workstation: storage cmdlets work for non-virtual IDE, SCSI virtual
I use Workstation 12 Pro to develop a code 10 WinPE for OS deployment/upgrades in service. 2 years without any problems, I have built several iterations.
Some new hardware platforms must be built as VMware images using SCSI, instead of IDE virtual disks, as it has always been used previously.
The VM with SCSI disks images works very well on XP Pro and POSReady 2009; However, when I boot to WinPE storage PowerShell cmdlets do not see the virtual SCSI disk, partitions, volumes, etc. I was initially using WinPE 5.x with PowerShell 4. I've recently updated to 10 WinPE and PowerShell 5, but still no joy. On the two WinPE 5.x and WinPE 10, the only storage Cmdlet that works is Get-physical disk.
In WinPE, diskpart and dos commands work fine with SCSI disks. In PowerShell, the "Get-WmiObject Win32_DiskDrive" and "Get-WmiObject Win32_LogicalDisk" commands also work, but not the Cmdlets Get-disk storage, Get-Partition, Get-Volume, which all return a null output report.
Any ideas or suggestions for debugging?
Thanks in advance,
vHomer
Hello
Thank you very much for the detailed information!
I just tried your procedure using a VHD disk image. (P.s. "My physical machine can start on this VHD file, is not a broken image.)
V2V converter can convert a VMDK image. Then, I created a computer virtual personalized by selecting this image VMDK file. But when I tried to convert it into a new virtual de VMware vCenter Converter Standalone machine, I got this error: "FAILED: could not find the system volume, reconfiguration is not possible.
Conversion to a system of physical hard disk to a virtual machine of closing is not officially supported by VMware vCenter Converter Standalone. P2V guide (physical disks or Partitions in Vmware vmdk (P2V) conversion ".ultrageek.") you provide has a few involved third-party tools. It is difficult to say what has caused the problem.
So, to isolate the problem, could you please try to reproduce the problem with only VMware Workstation? For example:
1. create a virtual machine with a VMDK of VMware Workstation file
2. make custom configurations: you can do it by the workstation user interface, or you can also change the configuration files of virtual machine manually
3. reproduce the problem
I tried the following scenario:
1 create a Windows VM 10 x 64 custom with IDE virtual drive, attach WinPE ISO
2. power on the virtual machine, it will boot to WinPE
3. check the storage Powershell cmdlets work well
4. Run diskpart, create a partition, format the partition to NTFS
5. power off the virtual machine
6 remove the virtual drive IDE virtual machine settings
7. Add a new virtual disk in the virtual machine settings, select SCSI type and using are virtual disk file
8. Select the virtual disk file removed in step 6, save and close the virtual machine settings
9. power on the virtual machine, it will boot to WinPE
Result: Storage PowerShell cmdlets work well with virtual drive SCSI in WinPE
This test reminds me of one thing, Win10 x 64 support only this controller of storage in VMware Workstation:
scsi0.present = "TRUE" scsi0.virtualDev = "lsisas1068"
So please make sure that these two lines are in vmx file your virtual machine and they must be configured as indicated above. If this isn't the case, you can try to change.
Kind regards
Shawn
Maybe you are looking for
-
Hi Gerry, You are able to access and view files, I added in Onedrive? Thank you Steve
-
Client VPN CISCO ASA for Android
Hi guys I just received a request from a client who said he expects the procedure to establish a VPN from an Android device, as far as I know there is a soft ANYCONNECT but in my case, the client uses a CISCO VPN CLIENT, in this case it is possible t
-
How to clone only given Advance Pricing
HelloMy company wishes to base our eComm on EBS12.1 advance pricing solution site.The problem is that our EBS has maintenance windows and it is not designed to be the site 24/7.Our idea was to clone the EBS to a site '' close '' the 'eComm' and thus
-
rename several virtual machines based on the State of food & VM name
I'm looking for a powershell script to rename the virtual machine based on the state name and vm power. For example, I have several virtual machines with a - temp at the end of the name of the server. Some are turned on and some are turned off. I
-
Steps: we received the file in PDF format and has been invited to modify the form.
Steps: we received the file in PDF format and has been invited to modify the form.My colleague edited in Livecycle es4.When we sent the document to them, they asked to have the title marked as H1, as it is currently labeled as content.In live cycle,