I guess the bug is still there in U3h, but I didn't see anyone try U3g?
Again, the most recent version that does not have this issue is VCS 6.0 U1b, which I am using fine in a production environment.
I guess the bug is still there in U3h, but I didn't see anyone try U3g?
Again, the most recent version that does not have this issue is VCS 6.0 U1b, which I am using fine in a production environment.
Hi,
Try to stop usbarbitrator by using the below command and then check issue:
/etc/init.d/usbarbitrator stop
Start the service after checking otherwise USB devices which attached on VMs will not work.
I have a virtual disk that lost the descriptor files and I've tried going through the process of recreating them but I just cant figure it out...
It is in a seperate datastore than the VM. I can use the
/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2 # vmkfstools -v 10 -e AGEC-SERVER2008R2_1-000001.vmdk
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000010-delta.vmdk" : open successful (14) size = 18959282176, hd = 5664418. Type 8
DISKLIB-DSCPTR: Opened [0]: "AGEC-SERVER2008R2_1-000010-delta.vmdk" (0xe)
DISKLIB-LINK : Opened '/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001.vmdk' (0xe): vmfsSparse, 1048576000 sectors / 500 GB.
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-flat.vmdk" : open successful (14) size = 536870912000, hd = 5664419. Type 3
DISKLIB-DSCPTR: Opened [0]: "AGEC-SERVER2008R2_1-flat.vmdk" (0xe)
DISKLIB-LINK : Opened '/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1.vmdk' (0xe): vmfs, 1048576000 sectors / 500 GB.
DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1
DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 5664419, extentType = 2
DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 5664418, extentType = 0
DISKLIB-LIB : Opened "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001.vmdk" (flags 0xe, type vmfs).
Disk chain is consistent.
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000010-delta.vmdk" : closed.
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-flat.vmdk" : closed.
AIOMGR-S : stat o=2 r=6 w=0 i=0 br=98304 bw=0
AIOMGR-U : stat o=3 r=1 w=0 i=5 br=2048 bw=0
OBJLIB-LIB: ObjLib cleanup done.
But if I go up the chain one more delta....
/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2 # vmkfstools -v 10 -e AGEC-SERVER2008R2_1-000002.vmdk
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002-delta.vmdk" : open successful (14) size = 185577472, hd = 6271401. Type 8
DISKLIB-DSCPTR: Opened [0]: "AGEC-SERVER2008R2_1-000002-delta.vmdk" (0xe)
DISKLIB-LINK : Opened '/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002.vmdk' (0xe): vmfsSparse, 1048576000 sectors / 500 GB.
DISKLIB-DSCPTR: descriptor above max size: 1158656000
DISKLIB-LINK : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001-delta.vmdk" : failed to open (The file specified is not a virtual disk).
DISKLIB-CHAIN :"/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002.vmdk": Failed to open parent "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001-delta.vmdk": The file specified is not a virtual disk.
DISKLIB-CHAIN : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001-delta.vmdk" : failed to open (The parent of this virtual disk could not be opened).
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002-delta.vmdk" : closed.
DISKLIB-LIB : Failed to open '/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002.vmdk' with flags 0xe The parent of this virtual disk could not be opened (23).
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002-delta.vmdk" : open successful (12) size = 185577472, hd = 6304169. Type 8
DISKLIB-DSCPTR: Opened [0]: "AGEC-SERVER2008R2_1-000002-delta.vmdk" (0xc)
DISKLIB-LINK : Opened '/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002.vmdk' (0xc): vmfsSparse, 1048576000 sectors / 500 GB.
DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1
DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 6304169, extentType = 0
DISKLIB-LIB : Opened "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002.vmdk" (flags 0xc, type vmfsSparse).
Disk link /vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002.vmdk successfully opened.
DISKLIB-DSCPTR: descriptor above max size: 1158656000
DISKLIB-LINK : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001-delta.vmdk" : failed to open (The file specified is not a virtual disk).
DISKLIB-CHAIN : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001-delta.vmdk" : failed to open (The file specified is not a virtual disk).
DISKLIB-LIB : Failed to open '/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001-delta.vmdk' with flags 0xc The file specified is not a virtual disk (15).
Failed to open disk link /vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000001-delta.vmdk :The file specified is not a virtual disk (15)Disk chain is not consistent : The parent of this virtual disk could not be opened (23)
DISKLIB-VMFS : "/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2/AGEC-SERVER2008R2_1-000002-delta.vmdk" : closed.
AIOMGR-S : stat o=4 r=22 w=0 i=0 br=174208 bw=0
AIOMGR-U : stat o=3 r=2 w=0 i=4 br=4096 bw=0
OBJLIB-LIB: ObjLib cleanup done.
Here are the vmdk descriptor files I had to recreate. There are 10 total. This the first 2:
/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2 # cat AGEC-SERVER2008R2_1-000001.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=010000d1
parentCID=ab35c349
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="AGEC-SERVER2008R2_1.vmdk"
# Extent description
RW 1048576000 VMFSSPARSE "AGEC-SERVER2008R2_1-000010-delta.vmdk"
# The Disk Data Base
#DDB
ddb.longContentID = "806f6d739509977d43cbe1196ef7c8f5"
/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2 # cat AGEC-SERVER2008R2_1-000002.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=10000d2
parentCID=01000d1
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="AGEC-SERVER2008R2_1-000001-delta.vmdk"
# Extent description
RW 1048576000 VMFSSPARSE "AGEC-SERVER2008R2_1-000002-delta.vmdk"
# The Disk Data Base
#DDB
ddb.longContentID = "806f6d739509977d43cbe1196ef7c8f5"
And here is my vfms descriptor:
/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2 # cat AGEC-SERVER2008R2_1.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=ab35c349
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"
# Extent description
RW 1048576000 VMFS "AGEC-SERVER2008R2_1-flat.vmdk"
# The Disk Data Base
#DDB
ddb.adapterType = "lsilogic"
ddb.geometry.cylinders = "65270"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "3a43f90f4a0828135c6c5ddbab35c349"
ddb.uuid = "60 00 C2 96 17 79 b7 12-1d 50 c0 aa e8 f3 e2 a8"
ddb.virtualHWVersion = "8"
/vmfs/volumes/53612937-dc2dee84-51cc-f8bc123d168c/AGEC-SERVER2008R2-Disk2 #
Any help would be appreciated!
Hi everyone,
I just want to check with anyone who had the experience, if i were to purchase VMWorksation 15 pro and installed it into a Windows Server OS. Do I need to purchase additional Windows Server licenses to run more than 2 VMs?
FYI, these VMs are existing VMs that are already using licensed Windows OS. Also the windows license that I have for Windows Server is only for the physical cores that the server has.
Not sure what is happening in this script but it works, awesome.
Just one question, how do i specify the columns for the -ExcelChartDefinition.
At the moment I'm just selecting the entire column to 9999 but that kinda messes up the charts, and is there a way to set the X Axis as text. from the $chart ?
$chart = New-ExcelChart -Title "$Vm+Mem" -ChartType Line -NoLegend ` -XRange 'B2:B9999' -YRange 'C2:C9999', 'D2:D9999'
Also, where in the loop do i need to put this in. If I put in in the same section as the hashtable creation it names the Charts with all the VMs names. The others dont seem to populate the $chart value for the export so it doesn't create the chart.
bonjour, je recherche comment pouvoir jouer à des jeux dans une vm pour pas que les enfants casse mon ordi et mes settings
mais je cherche comment partager en direct ma CG dans une vm workstation directement ou des alternative mais pas esxi
désoler je suis un noob
et sil existe un tutoriel français? ou google translate au pire
passez un bon week-end et merci d'éclairer ma lumière
ryzen 1800x
gtx1080ti
32go de ram.
Je ne parle pas de la config de base de display, mais plutôt ajouter un pci X16
Hi all,
Recently we upgraded our 5.5 vCenter to 6.5 vCenter and the installation got failed. The appliance was deployed successfully. vCenter server appliance looks healthy and all its content seems fine. But, we are unable to login to the vCenter from any browser. We have tried rebooting the VCSA and restart its core services by SSH. But the issue persists.
We had a three ESXi hosts cluster with a SAN attached to it. We powered off the vCenter 5.5 server VM and took a snapshot backup of it prior to the 6.5 upgrade.
Now, we only have three ESXi hosts and VMs running on them without a vCenter management.
Below are the doubts we have:
Can we power on the 5.5 vCenter server appliance and revert it back to the snapshot which we took prior to the 6.5 upgrade? if so, would it take the IP address back, which was exported to the new 6.5 appliance during the migration process?
If not, can we do a fresh installation of 6.5 vCenter server appliance and attach the ESXI hosts to it ? If so, are there any dependencies (vCenter settings, Network settings, ESXi hosts Licensing, vCenter Licensing) we need to be aware of ?
That skewed graph is due to large amount of empty cells in that range.
Try like this (don't mind the TableName warning)
Note that you have to be aware of the scaling of your data. If one of the metric is in a different range, you might see the 2nd one as a flat line
$stats="cpu.ready.summation","cpu.usage.average","mem.usage.average","disk.usage.average","disk.maxTotalLatency.latest","net.usage.average"
$vm=Get-VM-Name (Import-Csv-Path.\vmnames.csv-UseCulture|Select-ExpandPropertyName)
Get-Stat-Entity$vm-Stat$stats-Start (Get-Date).AddDays(-20) -IntervalMins30-Instance "" |
Group-Object-Property {$_.Entity.Name} |
ForEach-Object-Process {
$sChart= @{
Title ="$($_.Name) CPU"
ChartType ='Line'
NoLegend =$true
XRange ='VMStats[TimeStamp]'
YRange = @('VMStats[cpu.ready.summation]','VMStats[cpu.usage.average]')
}
$chartMem=New-ExcelChart@sChart
$sExcel= @{
Path ='C:\Data\tst-Tst-xpt.xlsx'
WorksheetName ="$($_.Name)Stats"
TableName ='VMStats'
AutoSize =$true
ExcelChartDefinition =$chartMem
}
$obj1=[hashtable]::new()
$obj1.Add('VM',$_.Name)
$_.Group |Sort-Object-PropertyTimestamp|Group-Object-PropertyTimestamp|
ForEach-Object-Process {
$obj2=$obj1.Clone()
$obj2.Add('Timestamp',$_.Name)
$_.Group |Group-Object-PropertyMetricId|
ForEach-Object-Process {
$obj2.Add($_.Name,$_.Group[0].Value)
}
$sSelect= @{
Property ='VM','Timestamp'+$stats
}
New-Object-TypeNamePSObject-Property$obj2|Select-Object@sSelect
} |
Export-Excel@sExcel
}
Tried
$chart = New-ExcelChart -Title "$_.Name+Mem" -ChartType Line -XRange 'Timestamp[$B:$B]' -YRange 'cpu.ready.summation[$C:$C]', 'cpu.usage.average[$D:$D]'
To name the legend and limit the selection, didn't name anything and with the [] it does not do the selection.
a.p. Looking forward for your kind assistance.
Found a slight issue with that, the second tabs chart. Its not able to create the table as the table 'VMStats' is already used on the previous VMs tab. So the charts for all the successive VMs get there data from the first Vms Table.
Need to set it based on the VMs Name or something unique "$($_.Name)VMStats". Does not work in there. It create the unique tables just no data on the Chart.
Also is there a way to set the Legend from the Y Range Name?
$sChart = @{ Title = "$($_.Name)" ChartType = 'Line' NoLegend = $True XRange = '"$($_.Name)VMStats"[TimeStamp]' YRange = @('"$($_.Name)VMStats"[cpu.ready.summation]','"$($_.Name)VMStats"[cpu.usage.average]') } $chartMem = New-ExcelChart @sChart $sExcel = @{ Path = 'C:\Data\tst-Tst-xpt.xlsx' WorksheetName = "$($_.Name)Stats" TableName = "$($_.Name)VMStats" AutoSize = $true ExcelChartDefinition = $chartMemHi Paul
and welcome to the forums!
From the ovftool documentation (page 36) it looks like this is as simple as running
ovftool input.ovf output.ova
Andreas
It's a zip file actually, But i once tried to manually zip the files and rename the archive file to .ova, and the resulting file was not accepted by the vSphere client.
So there is probably more to it, and ovftool is safer to use.
Hi,
I spent 3 days with same thing. HDMI output on IGD is just not working and everything in guest os seems to be fine. I have found this qemu/igd-assign.txt at master · qemu/qemu · GitHub
According to it, IGD has two different modes for assignment using vfio-pci: Universal Pass-Through (UPT) mode and Legacy mode.
Configuring passthrough in ESXi we are probably in UPT mode, where it just don't work "Those guest drivers only support this mode for Broadwell and newer IGD, according to Intel.Additionally, this mode by default, and as officially supported by Intel, does not support direct video output."
Question is, how to get Legacy mode work on ESXi, when it is possible on linux kvm. That requirements states about specific address 02.0 of IGD in virtual machine (it is same position like IGD have on host)
Event with VMware Knowledge Base I did not figure it out how to address it. Should value be 2? When I set advanced setting pciPassthru0.pciSlotNumber = "2" it is alway changed back during vm startup.
Next requirement IGD device must have a VGA ROM, either provided via the romfile option or loaded automatically through vfio (standard). In ESXi that should probably be setting
pciPassthru0.opromEnabled=TRUE and booting ESXi with pcipSaveOPROM (VMware Knowledge Base)
But I still don't know how to set that address.
This seem to be still be live problem. HDMI output on IGD is not working. Re: ESX 6.7 with HDMI pass through - partly working.
It looks as if your PowerCLI installation is not correct, you might have a mix of versions installed.
Can you run
$PSVersionTable
$env:PSModulePath.Split(';')
Get-Module-NameVMware*-ListAvailable|SelectName,Version,ModuleBase
Get-PSSnapin-NameVMware*-Registered
Get-WmiObject-ClassWin32_Product-Filter"name like '%PowerCLI%'"|SelectName,Version
You are close, and the screenshot is ok. The delta/flat files are hidden from the GUI.
The only error that I can see is that "-delta" in the "parentFileNameHint". That needs to be removed.
Either edit your files, or use the ones that I've attached to this post.
Once uploaded, please check whether the VM's configuration (.vmx) file points to the latest snapshot file, which I assume is "AGEC-SERVER2008R2_1_000010.vmdk".
If you need to edit the .vmx file, don't forget to reload it (see https://kb.vmware.com/s/article/1026043) prior to powering on the VM. As mentioned in my previous post, I'd recommend that - prior to powering on the VM - you create another snapshot!
André
Hi everyone, I have a problem regarding the Workstation Pro 15 library.
The virtual machines are stored in several folders. When I finish using the machines (turn off or suspend the machines) and close Workstation, and again open the application, the library where the folders with their machines were disappear.
There's a solution?
I have tried to reinstall Workstation 15 and I have tried to install other previous versions, and the same thing happens.
It does not store folders with their virtual machines in the library.
As they disappear every time I close and open the application, I must manually open the machines ..
Attached images.
Before closing the application:
After closing and starting the application (Where is the folder with your machines?):
I hope you can help me and thank you.
WAIT a second!
Your screenshot shows file .vmdk names that didn't exist previously!?
Did you change anything with the VM in the meantime?
André