Огромное спасибо. Это я и хотел услышать.
Недавно открыл для себя 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 ей подобных?
Есть ли у вас в явном виде пункт в BIOS по включения\выключению vt-d?
Явно vt-d нет. Есть только enable/disable Vanderpool Technology
Боюсь, что тут больше вопросы к железу, чем к ESXi и лучше уточнять на форуме ASUS )
При общении с железячниками при упоминании "vmware" очень часто они входят в ступор Для многих это "все от лукавого" Им винду подавай. такие вот у нас супер специалисты.
За ссылку спасибо. Как-то я её проморганил. Вроде шерстил тот форум. Видать вопрос в поиске не верно задал.
> I have a not-too-easy taks, for data analysis and recovery attempts I want to make use of hard disk clones to save some time..
Actually this is much easier than you probably thought.
The image type :" thick-provisioned eager zeroed-flat.vmdk" was formerly known as "full dd disk-image"
Actually it is exactly the same !!!!
Lets construct an example so that you can see if you have the same thing in mind.
you have a 233 gb file named "this-is-why-Hugo-is-in-jail-now
"
Tomorrow you have to present the case to the judges.
Hugo was a big fisk so you and 3 of your colleagues all get the task: inspect the file "this-is-why-Hugo-is-in-jail-now" because it is assumed to be the bootdisk of Hugos computer.
With these conditions you will need 4 linked clones and every colleague must keep the image as it will look when they are finished.
So the plan looks like this if you watch step by step:
1. check: is this a dd-image (hexdump -C -n 2mb | less) ----> you should see the first sector is an MBR or a GPT
----> if you see that the first sector is an ntldr or bootmgr assume that you have a partition-image (also possible but requires extra steps.
2. does the size of the image fit to the values in the par4titiontable ? (run fdisk or gdisk or partedUtil against "this-is-why-Hugo-is-in-jail-now" - you should see the partitiontable displayed - check filesize
3. does the size of the file is a multiple of 512 ? -----> if not - it maybe corrupt
4. if everything looks good - create a descriptorfile for "this-is-why-Hugo-is-in-jail-now"
- see the long version here:
Use dd image as VMDK .
in short: size in bytes / 512 = size in sectors = X
size in sectors / 16065 round down = Y
This results in
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=Z
parentCID=ffffffff
createType="vmfs"
# Extent description
RW X VMFS "this-is-why-Hugo-is-in-jail-now"
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "8"
ddb.geometry.cylinders = "Y"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
Since the best possible CID-value (12345678) was recently discovered simpy use it for Z.
5.ESXi should now be able to detect the newly created descriptor as a valid vmdk. In the example you named the descriptor hugo.vmdk
Put the 2 files into a directory you reserve for the masterimage - named "master"
6. create a first snapshot - we will use it to protect the master
you should now have:
hugo.vmdk
this-is-why-Hugo-is-in-jail-now
hugo-000001.vmdk
hugo-000001-delta.vmdk
7. create another snapshot - we will use it with 4 copies - you should now have
hugo.vmdk
this-is-why-Hugo-is-in-jail-now
hugo-000001.vmdk
hugo-000001-delta.vmdk
hugo-000002.vmdk
hugo-000002-delta.vmdk
8. create new directories - one for each linked clone - you should now have
hugo.vmdk
this-is-why-Hugo-is-in-jail-now
hugo-000001.vmdk
hugo-000001-delta.vmdk
hugo-000002.vmdk
hugo-000002-delta.vmdk
cloneA
cloneB
cloneC
cloneD
9. edit hugo-000002.vmdk
change line
parentfileNameHint = "hugo-000001.vmdk"
to
parentfileNameHint = "/vmfs/volumes/datastore/master/hugo-000001.vmdk"
copy the modified
hugo-000002.vmdk
hugo-000002-delta.vmdk
into each clnedirectories - you should now have
hugo.vmdk
this-is-why-Hugo-is-in-jail-now
hugo-000001.vmdk
hugo-000001-delta.vmdk
hugo-000002.vmdk
hugo-000002-delta.vmdk
cloneA/hugo-000002.vmdk
cloneA/hugo-000002-delta.vmdk
cloneB/hugo-000002.vmdk
cloneB/hugo-000002-delta.vmdk
cloneC/hugo-000002.vmdk
cloneC/hugo-000002-delta.vmdk
cloneD/hugo-000002.vmdk
cloneD/hugo-000002-delta.vmdk
----------------------------------------------
Now you have 4 independant linked clones - and all of them can be stored independantly.That was the vmdk part - you should see the pattern by now and be able to create vmx-files for the 4 different snapshot-chains.See long description I wrote years ago:linked-clnes-with-esxi
I hope you get it - nothing special necessary: just standard technics:manually create a descriptor and a few vmdk-edits
.
Ulli
Dont even consider to use Converter - it is neither necessary nor will you get away with that at court.
+1
There are a lot of Powercli stuff on how to perform restoration, but no dedicated vR cmdlets.
Has someone some info on managing vR through Powercli ?
vinny
в случае с directpath вам бы пришлось прокидывать локальный контроллер сначала, если он распаян на материнке, то не факт, что это все взлетело
ESXi умеет показывать ошибки SMART если они отдаются
а также при наличии проблем можно читать в vmkernel логе SCSI ошибки, которые стандартизированы и легко расшифровываются
да и как бы обычно собирают RAID на нескольких дисках, и тут уже выяснение информации про bad блоки становится не особо актуальной, потому что RAID контроллер вам и так должен предоставлять информацию, все ли хорошо с дисками или нет
Вывода esxcli и вот этих строк вполне хватило
2016-03-25T09:37:33.154Z cpu0:34102 opID=e32c1fc1)LVM: 10080: Device t10.ATA_____WDC_WD1001FALS2D00J7B1________________________WD2DWMATV1883224:1 detected to be a snapshot:
2016-03-25T09:37:33.154Z cpu0:34102 opID=e32c1fc1)LVM: 10087: queried disk ID: <type 1, len 26, lun 0, devType 0, scsi 0, h(id) 17948703437476516516>
2016-03-25T09:37:33.154Z cpu0:34102 opID=e32c1fc1)LVM: 10094: on-disk disk ID: <type 1, len 14, lun 0, devType 0, scsi 0, h(id) 7322232454884392162>
Would storage work if you set storage to native ide mode?
Hello,
Could you provide some more information on this - screenshot with the workflow failure, some vro logs located here /var/log/vco/app-server/server.log?
Regards,
Galina