Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Most recent forum messages

older | 1 | .... | 5791 | 5792 | (Page 5793) | 5794 | newer

    0 0

    Sorry to hear that then. It sounds like an ESXi host reboot is the only option. Best to plan for the best time to do the reboot and plan a shutdown/startup order. Situations like these are good opportunities to discuss possible expansion of redundancy with an additional host with vCenter to avoid the issue in the future. Additional costs but saves pain down the road. 


    0 0

    Only a solution user can get the password. That's a restriction. So you will need to get vIDM based solution user token.


    0 0

    If DHCP, the state data collection collects the primary IP address. By default it is 15 minutes cycle unless you change it.


    0 0

    Go into SCCM directly and right click on the target collection where you intend to register machine. If you see "Add Resources" option disabled then you won't be able to do the same thing from vRA. If it is enabled then it may be some other problem. But I suggest to check upon that first.


    0 0

    Hello,

     

    The problem is not Windows 7, but the host macOS version, apple has made non compatible changes in Sierra making the old Fusion to no longer work.

     

    You need at least Fusion 8 in order to be able to run it on macOS Sierra (well technically you can have some form of success with VMware Fusion 7, but there will be some issues)

     

    So the only thing you can do at this moment is to uninstall Fusion 5 and then get the trial version.

     

    If you want to test the newer version to see if it is worth your spending you can install and run a 30 day fully functional version before actually committing to spending anything.

     

    After the 30 days, you buy a license to change the installed Fusion into an unlimited version.

     

    Direct Download link to Fusion evaluation

     

    Hope this helps,

    --

    Wil


    0 0
    0 0

    Can i get PowerCLI Script for More than 10 Days Power off VM list in the VCenter... pls Assist


    0 0

    do you still have the issue? Maybe some malformed json in response? what's your "Accept" header?


    0 0

    I've been struggling to recover a missing local vfms 5 datastore, the LUN is visible but refreshing and or rescanning the Datastore just does not appear.

    I am unable to mount in CLI either.

     

    The HP SmartArray P400i controller shows the disks as ok although the boot information shows

    1720 - S.M.A.R.T. Hard Drive(s) Detect Imminent Failure Port 2I: Box 1: Bay 4 - suggesting a SAS disk issue is imminent.

     

    Is there anything I can do to recover a vm from this missing Datastore?

     

    PartedUtil shows

    # partedUtil getptbl /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

    gpt

    71380 255 63 1146734896

    1 2048 1146734591 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

     

     

    /vmfs/volumes # esxcli storage core device list |grep -A27 ^mpx.vmhba1:C0:T0:L0

    mpx.vmhba1:C0:T0:L0

       Display Name: Local VMware Disk (mpx.vmhba1:C0:T0:L0)

       Has Settable Display Name: false

       Size: 559929

       Device Type: Direct-Access

       Multipath Plugin: NMP

       Devfs Path: /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

       Vendor: VMware

       Model: Block device

       Revision: 1.0

       SCSI Level: 2

       Is Pseudo: false

       Status: on

       Is RDM Capable: false

       Is Local: true

       Is Removable: false

       Is SSD: false

       Is Offline: false

       Is Perennially Reserved: false

       Queue Full Sample Size: 0

       Queue Full Threshold: 0

       Thin Provisioning Status: unknown

       Attached Filters:

       VAAI Status: unsupported

       Other UIDs: vml.0000000000766d686261313a303a30

       Is Local SAS Device: false

       Is Boot USB Device: false

       No of outstanding IOs with competing worlds: 32

     

     

    offset="128 2048"; for dev in `esxcfg-scsidevs -l | grep "Console Device:" | awk {'print $3'}`; do disk=$dev; echo $disk; partedUtil getptbl $disk; { for i in `echo $offset`; do echo "Checking offset found at $i:"; hexdump -n4 -s $((0x100000+(512*$i))) $disk; hexdump -n4 -s $((0x1300000+(512*$i))) $disk; hexdump -C -n 128 -s $((0x130001d + (512*$i))) $disk; done; } | grep -B 1 -A 5 d00d; echo "---------------------"; done

     

    Result -

    ---------------------

    /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

    gpt

    71380 255 63 1146734896

    1 2048 1146734591 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

    Checking offset found at 2048:

    0200000 d00d c001

    0200004

    1400000 f15e 2fab

    1400004

    0140001d  4c 43 4c 5f 52 41 49 44  30 00 00 00 00 00 00 00  |LCL_RAID0.......|

    0140002d  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

     

    vmkernel.log output -

    2017-06-07T17:40:21.582Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:21.582Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e8087c140) 0x28, CmdSN 0x2c5 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:24.695Z cpu2:32825)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:24.695Z cpu2:32787)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x28 (0x412e80859ac0, 33801) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL

    2017-06-07T17:40:24.695Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:24.695Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80859ac0) 0x28, CmdSN 0x2c7 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:27.807Z cpu2:32783)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:27.807Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:27.807Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80859200) 0x28, CmdSN 0x2c9 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:30.920Z cpu2:32825)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:30.920Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:30.920Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80858a80) 0x28, CmdSN 0x2cb from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:34.032Z cpu2:32779)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:34.032Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:34.032Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80858300) 0x28, CmdSN 0x2cd from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:37.144Z cpu2:32793)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:37.145Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:37.145Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e808569c0) 0x28, CmdSN 0x2db from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:40.255Z cpu2:32843)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:40.255Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:40.255Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80856240) 0x28, CmdSN 0x2dd from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:43.367Z cpu2:32779)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:43.367Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:43.367Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80855ac0) 0x28, CmdSN 0x2df from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:46.479Z cpu2:32779)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:40:46.480Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:40:46.480Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80855340) 0x28, CmdSN 0x2e1 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

    2017-06-07T17:40:46.480Z cpu3:33801)Fil3: 15338: Max timeout retries exceeded for caller Fil3_FileIO (status 'Timeout')

    2017-06-07T17:40:48.804Z cpu1:33801)Config: 346: "SIOControlFlag2" = 0, Old Value: 0, (Status: 0x0)

    2017-06-07T17:40:52.761Z cpu1:34271)WARNING: UserEpoll: 542: UNSUPPORTED events 0x40

    2017-06-07T17:40:53.563Z cpu2:34271)WARNING: LinuxSocket: 1854: UNKNOWN/UNSUPPORTED socketcall op (whichCall=0x12, args@0xffd12d8c)

    2017-06-07T17:40:54.445Z cpu3:33801)Config: 346: "VMOverheadGrowthLimit" = -1, Old Value: -1, (Status: 0x0)

    2017-06-07T17:40:57.728Z cpu2:33989)Hardware: 3124: Assuming TPM is not present because trusted boot is not supported.

    2017-06-07T17:41:00.176Z cpu2:34050)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

    2017-06-07T17:41:00.177Z cpu2:32787)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x28 (0x412e8086a4c0, 33986) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x3 D:0x0 P:0x0 Possible sense data: 0x5 0x20 0x0. Act:EVAL

    2017-06-07T17:41:00.177Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

    2017-06-07T17:41:00.177Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e8086a4c0) 0x28, CmdSN 0x38e from world 33986 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x5 0x20 0x0.

    2017-06-07T17:41:00.247Z cpu2:34933)Boot Successful

    2017-06-07T17:41:01.007Z cpu3:33804)Config: 346: "SIOControlFlag2" = 1, Old Value: 0, (Status: 0x0)

    2017-06-07T17:41:01.736Z cpu1:34988)MemSched: vm 34988: 8263: extended swap to 8192 pgs


    0 0

    Hi,

     

    I don't know how to test whether does it work or not because my ESX always presents with vkernel port MAC address (i have 2 physical cards). How to check which card is used ?


    0 0

    I can set backup only as crash consistent task?


    0 0

    Unless you're actually using Red Hat Linux and its crash utility, I'd drop the "-l" and "-N" options from the vmss2core command line – just give vmss2core the filenames for debug.{guest,vmem}, nothing else.  Does it still fail?

     

    Can you post a vmware.log showing the failure here in the forums?  Just use the attach button in the lower-right when composing a reply... please don't copy-and-paste the entire log.  I'll take a peek at the log and see if I can provide some guidance.

     

    Cheers,

    --

    Darius


    0 0

    Please try run VMware-workstation-full-12.5.7-5813279.exe as administrator.


    0 0
  • 06/24/17--12:50: 3D Issue with games
  • Hello,

     

    Not sure whether I should come here or to the linux amdgpu developers for this one?

     

    With both the current simcity and simcity 4 games there is an issue where the lighting is not correct after having switched from the AMD drivers to the AMDGPU open source drivers on my linux host where the Win7 Pro VM resides. The screenshots attached probably provide a better explanation than I can write for this one. I had not issues with the previous versions of the ati-drivers versions 15.12, 15.9, etc.

     

    My host is running kernel 4.9.33 and Workstation 12.5.7.


    0 0

    Hi

     

    Thanks for the suggestion, that indeed does partially resolve the problem

     

    The integrated USB fingerprint reader handles this nicely as does the integrated Bluetooth adapter .  But the integrated webcam does not have a power management tab?

     

    thanks

    Andy


    0 0

    To make sure I get the question, you want a script that lists the VMs that have been powered off for more than 10 days?


    0 0

    If my assumption was correct, try like this

     

    $poweredOff=Get-VIEvent-Start (Get-Date).AddDays(-10) -MaxSamples ([int]::MaxValue) |

        where{$_-is[VMware.Vim.VmPoweredOffEvent]} |%{$_.Vm.Name}

    Get-VM  |where{$_.PowerState -eq'poweredoff'-and$poweredOff-notcontains$_.Name} |select-ExpandPropertyName

     


    0 0

    Check /var/log/vnetlib for hints, e.g.:

     

     

    Jun 24 17:08:47 VNLAdapterStatus - ioctl: SIOCGIFFLAGS failed, error: Device not configured

    Jun 24 17:08:47 VNLAdapterStatuInternet Software Consortium DHCP Server 2.0

    Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.

    All rights reserved.

     

    Please contribute if you find this software useful.

    For info, please visit http://www.isc.org/dhcp-contrib.html

     

    /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf line 45: semicolon expected.

     

    See also https://linux.die.net/man/5/dhcp-options


    0 0

    There is a "USB selective suspend setting" under "USB settings" in "Change advanced power settings" in Powercfg.cpl for each individual plan if you click on "Change plan settings". By default it is "Enabled" even for "Plugged In" in "High performance plan"

     

    In theory, setting this to "Disabled" in the Power Management plan setting should affect all USB devices to not suspend itself to save power.


    0 0

    Bonjour,

     

    J'ai une VM msdos 6 avec des outils de développement du siècle dernier pour une besoin spécial.

    Ces outils compilent du code qui est ensuite transféré dans des équipements par liaison sérielle RS232.

    Depuis au moins 2005 cette VM fonctionnait avec les versions gratuites du player et les ports séries n'ont

    jamais fait de problèmes, qu'ils soient intégrés à la carte mère ou via USB (convertisseur type FTDI).

     

    J'ai ensuite acheté WS pro 12 que j'ai utilisé sur un PC portable sous Windows 7 pro 64 et cette VM a

    toujours aussi bien fonctionné sous cet OS.

     

    J'ai rajouté un disque dur dans ce portable et j'ai fait un dual boot avec Linux FC25 pour migrer progressivement;

    puis j'ai installé la version Linux de WS 12. Mes autres VMs fonctionnent normalement sous FC25 à l'exception de

    celle avec msdos 6 et ce fichu port sériel.

     

    Dès qu'un accès au port série est lancé par l'outil de développement, VMware crash complètement et se ferme

    avec un message peu rassurant:

     

    >VMware Player unrecoverable error: (vcpu-0)
    >NOT_IMPLEMENTED bora/devices/serial/serialDevicePosix.c:1287
    >A log file is available in "/home/me/VmwarePcs/MSDOS6/vmware.log". 
    >You can request support.

     

    Bien entendu la période de support incluse est passée sans que j'ai pu en profiter.

     

    C'est pourtant bien un bug ou vice de programmation du logiciel dans sa version Linux, vu qu'avec exactement

    le même matériel et une version de même niveau/plus ancienne sous windows, ça fonctionne.

     

    Quelq'un a t-il déjà rencontré ce défaut du logiciel et réussi à la résoudre ?

     

    J'ai installé la dernière màj 12.5.7 mais ça ne change rien au problème.

     

    Le port série semble quand même fonctionner partiellement: Sur l'équipement connecté au port sériel il y a des

    leds témoins d'activité, si j'envoie quelques caractères avec la ligne de commandes sous dos, on voit bien qu'il

    y a du traffic..

     

    L'outil de développement ne sait pas se connecter aux équipements par autre chose qu'un port série, il n'y a que

    ce support de disponible.

     

    L'idée de devoir me résigner à garder un dual boot et acheter du W10, juste pour pouvoir y lancer une (1) VM

    avec dos dedans, me file déjà la nausée.


older | 1 | .... | 5791 | 5792 | (Page 5793) | 5794 | newer