Hello All,
Slowly coming up to speed with the VMware certification tracks.
I am starting to prep for the VCA6-DCV exam and had a few questions on the below:
[1] Is there a VMware Hands On Lab course I can look at for the DCV track ?
[2] There seems to be a VMware Press DCV Cert Guide. Is it helpful or should the Data Center Virtualization Fundamentals track be sufficient ?
Appreciate your input. Thank you !
I have seen mentions where the VM you are trying to export was configured with a static IP.
Once the VM was reconfigured to use DHCP, the export worked.
A wild guess, but perhaps worth a try.
Also check the vpxd log.
Or did you already do that, and saw the same message that was mentioned ?
Thanks LucD.You are always the best:)
I will try this out.
How about Step#2 wherein I need to map the disks to VM using Powercli with exact same configurations as that info pulled from Step#1?
Hi,
That is related to new feature on VMware Tools 10 and don't remove that.
Common Agent Framework: Common Agent Framework (CAF) provides the basic services necessary to simplify secure and efficient management of agents inside the guest virtual machines.
BR
Can you please try full path to the vib rather than relative path
esxcli software vib install -v < full path to the vib>
Друзья подскажите.
Имеется:
MB - P5E3 Deluxe > линк на Никс
Биос последний > 1502
Vanderpool Technology в биосе включено.
Проц - Intel Core2 Quad Processor Q9300 - Intel® Core™2 Quad Processor Q9300 (6M Cache, 2.50 GHz, 1333 MHz FSB) Спецификации
ESXi - 6.0.0 (Build 3620759)
Вроде (по спецификациям) все поддерживает vt-d.
Но зайдя в Advanced Settings (VMware vSphere Client) - имею "Host does not support passthrough configuration"
Совсем не как не не получиться задействовать проброс устройств?
Hi,
You need to read this document from Ubuntu:
https://help.ubuntu.com/lts/installation-guide/i386/ch04s06.html
Also about VMware customization:
Судя по тем выводам вероятно host client не научили работать с лунами, которые определяются как снапшот.
И тогда надо либо пользоваться старым добрым c# клиентом, либо смонтировать VMFS из командной строки.
В принципе подобных проблем =можно ожидать, потому что релиз клиента имеет версию 1.0.0
Что в практике VMware означает совсем нулевой продукт. В следующей мажорной версии ESXi (например 6.5), его могут сильно допилить и привести к версионности ESXi.
Если есть возможно - рекомендую открыть кейс в техподдержке и сообщить о своей находке.
Вряд ли что-то получится сделать с помощью форума в вашем случае
Огромное спасибо. Это я и хотел услышать.
Недавно открыл для себя Embedded Host Client. Совершенно случайно
И вот пытаюсь для себя понять - хоронить (удалить) ли VMware vSphere Client и полностью перейти на Embedded Host Client (уж очень он хорош) или все-таки рано ещё.
Да и ещё, дабы не вводить в заблуждение.
Вывод первой команды - это вывод в PuTTY (SSH)
Вывод второй команды - это после нажатия Rescan в VMware vSphere Client а не в Embedded Host Client.
В Embedded Host Client пимпы "Rescan" я чет не увидел.
Hi opedro,
Please enable TLS1.0 for PCOIP in the Remote desktop and connection server, you can get the methods from the kb VMware KB: Configure security protocols for PCoIP for Horizon 6 version 6.2 and later, and Horizon Client 3.5 and la…
Thanks.
Could you upload log bundle?
Try to convert with recommended SCSI controller, curiously I've seens the conversions that succeed with IDE controller depends on Windows configuration.
Also check the WS logs.
HTH
Вот тут на форуме ASUS пишут, что скорее всего в этих материнках нет поддержки VT-d
Есть ли у вас в явном виде пункт в BIOS по включения\выключению vt-d?
Боюсь, что тут больше вопросы к железу, чем к ESXi и лучше уточнять на форуме ASUS )
Таки рискнул нажать "Finish"
Молодцы - предупреждают - "The entire contents of this disk are about to be erased and replaced with the specified configuration, are you sure?"
Значиться это не наш путь.
You will have to use the ReconfigVM method for that.
There's an example in 3. Re: Automate add Windows Hard Disk
Если не секрет, что вы хотите прокидывать в виртуалку? может быть есть обходные варианты достижения конечной цели
Вот слепошара. Нашел я Rescan в сабже.
Так - на всякий случай вывод при нажатии Rescan в EHC
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0x1, handler ACPI Interrupt
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0x2, handler hpet
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xb, handler uhci_hcd:usb3
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xb, handler vmnic0
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xc, handler uhci_hcd:usb4
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xd, handler uhci_hcd:usb8
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xd, handler uhci_hcd:usb5
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xd, handler ehci_hcd:usb1
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xe, handler uhci_hcd:usb6
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xe, handler ehci_hcd:usb2
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xf, handler uhci_hcd:usb7
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0x10, handler ata_piix
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0x10, handler ata_piix
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xef, handler timer
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xf3, handler hv_ipi
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xf4, handler timer-ipi
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xf5, handler monitor
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xf6, handler resched
2016-03-25T11:01:49.615Z cpu2:70846)IntrCookie: 4395: cookie 0xf8, handler tlb
2016-03-25T11:01:49.616Z cpu2:70846)IntrCookie: 4395: cookie 0xfa, handler perfctr
2016-03-25T11:01:49.616Z cpu2:70846)IntrCookie: 4395: cookie 0xfc, handler thermal
2016-03-25T11:01:49.616Z cpu2:70846)IntrCookie: 4395: cookie 0xfd, handler lint1
2016-03-25T11:01:49.616Z cpu2:70846)IntrCookie: 4395: cookie 0xfe, handler error
2016-03-25T11:01:49.616Z cpu2:70846)IntrCookie: 4395: cookie 0xff, handler spurious
2016-03-25T11:01:49.654Z cpu2:70846)WARNING: PCI: 157: 0000:00:1c.0: Bypassing non-ACS capable device in hierarchy
2016-03-25T11:01:49.660Z cpu2:70846)WARNING: PCI: 157: 0000:00:1c.5: Bypassing non-ACS capable device in hierarchy
2016-03-25T11:01:49.731Z cpu2:70846)WARNING: PCI: 157: 0000:01:00.0: Bypassing non-ACS capable device in hierarchy
2016-03-25T11:02:01.499Z cpu0:32786)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d80263e80, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-03-25T11:02:04.137Z cpu0:70918)VMKStats: 586: Failed to acquire page pool stats for WorldYieldTarget (Operation not permitted), used memory count won't be useful
2016-03-25T11:02:04.137Z cpu0:70918)VMKStats: 586: Failed to acquire page pool stats for worldlets (Operation not permitted), used memory count won't be useful
2016-03-25T11:02:04.137Z cpu0:70918)VMKStats: 586: Failed to acquire page pool stats for Interrupts (Operation not permitted), used memory count won't be useful
2016-03-25T11:02:04.137Z cpu0:70918)VMKStats: 586: Failed to acquire page pool stats for Default (Operation not permitted), used memory count won't be useful
2016-03-25T11:02:04.137Z cpu0:70918)VMKStats: 586: Failed to acquire page pool stats for Default (Operation not permitted), used memory count won't be useful
2016-03-25T11:02:04.217Z cpu0:32786)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d802b3500, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE
2016-03-25T11:02:04.220Z cpu0:32786)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x439d802b3500, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-03-25T11:02:04.228Z cpu0:32786)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d802b3500, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE
2016-03-25T11:02:04.228Z cpu1:70918)NMP: nmpStateLogger:3204: NMP module ID: 21.
2016-03-25T11:02:04.228Z cpu1:70918)NMP: nmpStateLogger:3205: NMP heap ID: 0x4302e1eb8000.
2016-03-25T11:02:04.228Z cpu1:70918)NMP: nmpStateLogger:3206: NMP slab ID: 0x430073683240.
2016-03-25T11:02:04.228Z cpu1:70918)NMP: nmpStateLogger:3218: NMP is managing 3 devices:
2016-03-25T11:02:06.106Z cpu0:70918)WARNING: NFS41: NFS41_VSIGetMaxQueueDepth:3509: Invalid arg count! (0): Usage <FS>
2016-03-25T11:02:06.106Z cpu0:70918)WARNING: NFS41: NFS41_VSIGetShares:3385: Invalid arg count! (0): Usage <FS> <worldID>
2016-03-25T11:02:06.106Z cpu0:70918)VFLASHVSI: 874: Module vfc does not support VFLASH_IOCTL_GET_PRIVATE_INFO.
2016-03-25T11:02:15.322Z cpu1:70918)IntrCookie: 4395: cookie 0x1, handler ACPI Interrupt
2016-03-25T11:02:15.322Z cpu1:70918)IntrCookie: 4395: cookie 0x2, handler hpet
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xb, handler uhci_hcd:usb3
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xb, handler vmnic0
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xc, handler uhci_hcd:usb4
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xd, handler uhci_hcd:usb8
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xd, handler uhci_hcd:usb5
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xd, handler ehci_hcd:usb1
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xe, handler uhci_hcd:usb6
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xe, handler ehci_hcd:usb2
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xf, handler uhci_hcd:usb7
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0x10, handler ata_piix
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0x10, handler ata_piix
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xef, handler timer
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xf3, handler hv_ipi
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xf4, handler timer-ipi
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xf5, handler monitor
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xf6, handler resched
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xf8, handler tlb
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xfa, handler perfctr
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xfc, handler thermal
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xfd, handler lint1
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xfe, handler error
2016-03-25T11:02:15.323Z cpu1:70918)IntrCookie: 4395: cookie 0xff, handler spurious
2016-03-25T11:02:15.361Z cpu1:70918)WARNING: PCI: 157: 0000:00:1c.0: Bypassing non-ACS capable device in hierarchy
2016-03-25T11:02:15.368Z cpu1:70918)WARNING: PCI: 157: 0000:00:1c.5: Bypassing non-ACS capable device in hierarchy
2016-03-25T11:02:15.440Z cpu1:70918)WARNING: PCI: 157: 0000:01:00.0: Bypassing non-ACS capable device in hierarchy
2016-03-25T11:02:21.993Z cpu0:32786)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802b3500, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-03-25T11:02:51.548Z cpu0:32786)NMP: nmp_ThrottleLogForDevice:3231: last error status from device mpx.vmhba32:C0:T0:L0 repeated 10 times
2016-03-25T11:03:06.301Z cpu0:32923)ScsiUid: 273: Path 'vmhba0:C0:T0:L0' does not support VPD Device Id page.
2016-03-25T11:03:06.303Z cpu0:32923)VMWARE SCSI Id: Could not get disk id for vmhba0:C0:T0:L0
2016-03-25T11:03:06.317Z cpu1:33132)usb-storage: detected SCSI revision number 0 on vmhba32
2016-03-25T11:03:06.317Z cpu1:33132)usb-storage: patching inquiry data to change SCSI revision number from 0 to 2 on vmhba32
2016-03-25T11:03:06.317Z cpu0:32926)ScsiUid: 273: Path 'vmhba32:C0:T0:L0' does not support VPD Device Id page.
2016-03-25T11:03:06.317Z cpu0:32926)VMWARE SCSI Id: Could not get disk id for vmhba32:C0:T0:L0
2016-03-25T11:03:06.330Z cpu2:36278 opID=98f64acd)World: 15516: VC opID 7c9fbbc2 maps to vmkernel opID 98f64acd
2016-03-25T11:03:06.330Z cpu2:36278 opID=98f64acd)ScsiScan: 836: Path vmhba35:C0:T0:L0 supports REPORT LUNS 0x11
2016-03-25T11:03:06.344Z cpu3:32789)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d8027c580, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE
2016-03-25T11:03:06.347Z cpu3:32789)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d8027c580, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE
2016-03-25T11:03:18.554Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x439d802ab980, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
Thanks a lot, I'll try again use correct version.
Обходные пути я знаю - RDM
Но вот сколько не юзаю ESXi все не могу для себя понять.
Могу ли я при пробросе диска посредством RDM чекать диск на BadBlock, посредством всяких Viktory ей подобных?