Hello Sascha,
welcome to the forums!
Is there a chance that the IP address that you assigned to the ESXi host is already in use by some other device?
Then you may randomly end up on the one or the other device.
Andreas
Hello Sascha,
welcome to the forums!
Is there a chance that the IP address that you assigned to the ESXi host is already in use by some other device?
Then you may randomly end up on the one or the other device.
Andreas
Thank you,
Hi,
Can I link both NSX T and NSX V to one vCenter and different clusters?
when I am chaning the MTU size, Do I need to change the MTU on the vDS only or on the VMs too in order to allow the VM to utilize the MTU size ?
dmesg | grep sas ->
PCI: driver mpt2sas is looking for devices
mpt2sas0: setting logging_level(0x00000000)
mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED.
mpt2sas0: MSI-X vectors supported: 1, no of cores: 32, max_msix_vectors: -1 mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 18 mpt2sas0: iomem(0x00000000d0ff0000), mapped(0x0x41001cf40000), size(65536) mpt2sas0: ioport(0x000000000000bc00), size(256)
mpt2sas0: _base_get_ioc_facts: IOC_STATE(0x22000000)
mpt2sas0: _base_get_ioc_facts: failed going to ready state (ioc_state=0x20000000)
mpt2sas0: sending diag reset !! mpt2sas0: diag reset: SUCCESS
mpt2sas0: Allocated physical memory: size(1416 kB) mpt2sas0: Current Controller Queue Depth(595), Max Controller Queue Depth(1720)
mpt2sas0: Scatter Gather Elements per IO(128)
mpt2sas0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)
mpt2sas0: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C)
mpt2sas0: Protocol=(Initiator), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ2018-12-08T22:01:07.497Z cpu17:66326))
mpt2sas0: sending port enable !!
mpt2sas0: host_add: handle(0x0001), sas_addr(0x5b8ca3a0e79ac000), phys(8)
mpt2sas0: expander_add: handle(0x0009), parent(0x0001), sas_addr(0x500056b37789abff), phys(22)
mpt2sas0: Get SATA identify successfully for handle=0xa with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0xb with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0xc with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0xd with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0xe with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0xf with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0x10 with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0x11 with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0x12 with try_count=1
mpt2sas0: Get SATA identify successfully for handle=0x13 with try_count=1
mpt2sas0: port enable: SUCCESS
mpt2sas0: Get SATA identify successfully for handle=0xe with try_count=1 Fusion MPT SAS Host:2:0:0:0 :: SATA: handle(0x000e), sas_addr(0x500056b37789abee), phy(14), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0xa with try_count=1 Fusion MPT SAS Host:2:0:1:0 :: SATA: handle(0x000a), sas_addr(0x500056b37789abe4), phy(4), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0xb with try_count=1 Fusion MPT SAS Host:2:0:2:0 :: SATA: handle(0x000b), sas_addr(0x500056b37789abe5), phy(5), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0xc with try_count=1 Fusion MPT SAS Host:2:0:3:0 :: SATA: handle(0x000c), sas_addr(0x500056b37789abe6), phy(6), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0xd with try_count=1 Fusion MPT SAS Host:2:0:4:0 :: SATA: handle(0x000d), sas_addr(0x500056b37789abe7), phy(7), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0xf with try_count=1 Fusion MPT SAS Host:2:0:5:0 :: SATA: handle(0x000f), sas_addr(0x500056b37789abef), phy(15), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0x10 with try_count=1 Fusion MPT SAS Host:2:0:6:0 :: SATA: handle(0x0010), sas_addr(0x500056b37789abf0), phy(16), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0x11 with try_count=1 Fusion MPT SAS Host:2:0:7:0 :: SATA: handle(0x0011), sas_addr(0x500056b37789abf1), phy(17), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0x12 with try_count=1 Fusion MPT SAS Host:2:0:8:0 :: SATA: handle(0x0012), sas_addr(0x500056b37789abf2), phy(18), device_name(0x0000000000000000)
mpt2sas0: Get SATA identify successfully for handle=0x13 with try_count=1 Fusion MPT SAS Host:2:0:9:0 :: SATA: handle(0x0013), sas_addr(0x500056b37789abf3), phy(19), device_name(0x0000000000000000)
PCI: driver mpt2sas claimed device 0000:41:00.0
PCI: driver mpt2sas claimed 1 device
Mod: 4972: Initialization of mpt2sas succeeded with module ID 4154. mpt2sas loaded successfully.
ESXi host found all 10 disk, but show only 1.
I found some error in log file:
2018-12-08T22:01:15.137Z cpu17:66326)<6>Fusion MPT SAS Host:2:0:6:0 :: SATA: handle(0x0010), sas_addr(0x500056b37789abf0), phy(16), device_name(0x0000000000000000)
2018-12-08T22:01:15.137Z cpu17:66326)<6>Fusion MPT SAS Host:2:0:6:0 :: SATA: enclosure_logical_id(0x500056b36789abff), slot(1)
2018-12-08T22:01:15.137Z cpu17:66326)<6>Fusion MPT SAS Host:2:0:6:0 :: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
2018-12-08T22:01:15.137Z cpu17:66326)<6>Fusion MPT SAS Host:2:0:6:0 :: serial_number(FF1807890C3F04286748)
2018-12-08T22:01:15.137Z cpu17:66326)<6>Fusion MPT SAS Host:2:0:6:0 :: qdepth(32), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1)
2018-12-08T22:01:15.137Z cpu17:66326)<6>mpt2sas0: Get SATA identify successfully for handle=0x11 with try_count=1
2018-12-08T22:01:15.138Z cpu17:66326)WARNING: ScsiUid: 411: vmhba1:C0:T7:L0: NAA identifier type has an unknown naa value of 0x0
2018-12-08T22:01:15.138Z cpu17:66326)ScsiUid: 180: Failed to create uid for path vmhba1:C0:T7:L0: Failure
2018-12-08T22:01:15.138Z cpu17:66326)ScsiScan: 1206: Path 'vmhba1:C0:T7:L0' : No standard UID: Failure. ANSI version 'SCSI-3 SPC4' (0x6).
2018-12-08T22:01:15.138Z cpu17:66326)VMWARE SCSI Id: Id for vmhba1:C0:T7:L0
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x50 0x61 0x74 0x72 0x69 0x6f
Hi LucD
Thanks for the reply.
Apologies, I am providing the alarm definition, I just didn't copy the whole of the PS script into the post.
These two alarms are the only ones out of the 260+ alarms available in vCenter 6.7u1 that are failing to set a 'Yellow to Red' trigger.
Pretty sure its not the script, but something more fundamental regarding these two alarms themselves.
Cheers
Martin
A la création d'une VM j'obtiens le message : Problème lors du démarrage de c:\Program Files(x86)\VMware\VMware Workstation\ClientWOW64\TPCinVM.dll Le module spécifié est introuvable.
Je pense que c'est lié à l'activation des Options Virtual Printer dans mes préférences, mais j'aimerais que cela fonctionne.
Pouvez-vous m'aider ?
Merci.
Stéphane
Same problem. Haven't had any luck to figure out a workaround.
Hello together,
everyone know the problem about High resolution screen and small user interfaces.
microsoft said its the aplication developer should solve this. Even there own user interface is to small.
VMWare is a system wich virtualise the hardware. so at least from them i would expect that they can handle diffrent screensizes well
but what ever i try, it does not matter wich version i try. They also cant handle this.
Does anyone know a good virtual system ?
thanks
Would you mind sharing at the least the lines of code involving the alarms?
Are you handling both alarms at the same time or separate?
I am switching from a mac laptop to a dell xps laptop. so I have to switch from fusion to workstation. (the guest was always ubuntu.)
most of the guest seems to work fine. I have installed all the items, vmware-tools, open-vm-desktop-tools, etc. workstation does not seem as smooth as fusion, but it is ok. plenty of memory, plenty of CPU power, plenty Video RAM.
...except for the web browsers. I have tried both firefox and opera. the browser windows get drawn very slowly. for example, even the firefox homescreen may take 5 seconds, during which I see the individual elements being drawn one by one. [interestingly, the search bar is drawn first.] when I load a web page that tries to view images (e.g., as in google image search), the individual images are updated only when my mouse cursor moves over them, but not otherwise. I cannot scroll, because I cannot see the changed page...except again when I then move my cursor around on the new page.
it seems like a much worse graphics driver on workstation than on fusion, somehow interacting with how browsers think they have redrawn the screen. (many other ubuntu GUIs work just fine).
is this a known problem? is there a better-GUI virtual host?
advice appreciated.
/iaw
You posted this in NSX, so I'm assuming you're changing the MTU because of vxlan. You don't need to change the MTU inside the VM guests for this.
What version of VMware Workstation are you attempting to run on Ubuntu 18.04?
Seems they have abandoned 14 only to push out 15. Bugs still exist in 14???? Just upgrade to 15. Ridiculous!
Last time I give vmware any of my money!
Word to wise...just use Virtualbox. Its faster and less bugs ( it doesnt lock up and cause kernel panics in both windows and linux.)
I have same issue GSOD after power on guest.
Here is my memory.dmp
On Sat 08.12.2018 13:16:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: vmx86.sys (vmx86+0x10BE)
Bugcheck code: 0x139 (0x3B, 0xFFFFDF0494379060, 0xFFFFDF0494378FB8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\vmx86.sys
product: VMware kernel driver
company: VMware, Inc.
description: VMware kernel driver
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vmx86.sys (VMware kernel driver, VMware, Inc.).
Google query: vmx86.sys VMware, Inc. KERNEL_SECURITY_CHECK_FAILURE
It clearly names VMware kernel driver as the culprit but updating to latest program version and running "check for updates" show no updates for vmx86.sys (VMware kernel driver, VMware, Inc.)
Key will work but you have to check license key legally.
there seems to be something wrong with what vrops mean by
Capacity Usage (%) and Capacity REminaining (%)
both are not adding up.
Hi,
Please send your vSphere version and it seems, you were using VMFS3 and did hardware version upgrade!