hi Ryan,
You're right. Starting with 6.0 the file system is under tighter security. Your plugin can write its logs in /storage/log/vmware/vsphere-client
The SDK 6.0 Release Notes mention the fact that plugins can use the env variable VMWARE_DATA_DIR for this storage directory location (on linux and windows)
Are you able to follow the upgrade path for 4.1 to 5.0 on the 4.1 host? If so, try it. Getting the old host on a newer hypervisor version may at minimum allow you to upgrade the hardware version and then let you either run converter against it or even vMotion it off that host.
I guess this comes down to the VM name and the guest name not being the same, if you have trouble when VMs are renamed?
You should be able to use$Computer=Get-QADComputer-Identity$VM.Guest.Hostname
Upgarde your first ESXi4.1 to 5.x level. upgrade the hardware version of the VMs and then try to migrate them to the new ESX6.0. If you manage to upgrade the ESX to 5.5 level you can directly attach the same ESX to the vcenter server appliance and migrate the VMs.
I am using the same scenario but different is, we configured two 10G NIC in same switch-01 port group which is connected with ISCSI storage through ISCSI switch.( you don't required switch,if you have maximum only two hosts)
All devices which we have been using should have 10G NIC for route traffic else you will not get exact result.
below mention url will help to understand network routing best practice in VMware.
Hi,
Which version of convertor are you using ? Are you able to upload the log bundle please.
Rich
I have a clean install of a retail copy of windows 7 Pro 32-bit (SP!) (I don't mind activating 10 Win7 manually, so w/o VLK is no issue for me), immediately I installed the VMtools, reboot it and shutdown, enable Administrator account and set new password, removed all other accounts, turned off firewall, no Windows Update performed. Shutoff, then I clone it and keep the original one off at all time.
As for the Win7 copy, I added it to AD domain, reboot it, then install Horizon View Agent, reboot, then I login to it using local administrator account, remove it from Active Directory, provide ADDC account info, then reboot it. When it boots up, I shut it down and cloned it into a new templateX.
I setup New Customization: Here is my setup:
Properties: Target VM Operating System: Windows, Customization Spec Name: Win7-Custom
Registration: Name: Labs Orgization: Ztech Inc
Computer Name: "Use the virtual MAchine Name"
Windows License: empty
Adm Password: msy1967sys
Time Zone: CST
Run Once: None
Network: I choose two method: (1) "Use Standard...." or (2) "Manual Setup, NIC1, DHCP, DNS: 192.168.1.5" 192.168.1.5 is my DNS, and my gateway is 192.168.1.1 I tried both
WorkGroup or Domain: Windows Server Domain: ztech.lab
Username: data2008@ztech.lab (I use data2008 as the adm account for my Domain), Password: MS1369Dj (domain password)
Operating System Option: Generate SID
I tried to deploy new VM using the
If you watched Keith Barker's Horizon View video, he had great difficulty in this, I also tried his suggestion without success. No mater how I try this, I could NOT have new VM using templateX and the Customization method (as above). The new VMs reject all login using ZTECH\data2008, Administrator account also disabled!
Since I need to build manual and auto pools, I need to make sure Windows 7 can be deployed automatically by Connection Server and added to Active Direcotory automatically, but one week, no success, it is obvious to me VMware has a sloppy attitude to their software (so unreliable), such bad experiences happened to me many times,
Thank you Burke-.
Just for history:
Code for ip addresses of your gateway
gwConfig = gateway.configuration;
var gwInterfaces = gwConfig.gatewayInterfaces.gatewayInterface.enumerate();
var address = [];
for each (gwi in gwInterfaces){ if(gwi.subnetParticipation != null){ // VclObjectList -- related obj types: VclSubnetParticipation var gwiSubnets = gwi.subnetParticipation.enumerate(); for each (gwiSubnet in gwiSubnets){ address.push(gwiSubnet.ipAddress) } } }
System.log (address[0]);
System.log (address[1])Couple thoughts. You can run multiple vKernels for VSAN and vMotion (allowing one on each switch). For VSAN use separate VLAN/Subnets (One on each switch gives you a nice A/B gap) while vMotion needs to have all vkernel's on the same layer 2 subnet ideally. This allows for maximum resiliency, in theory faster failover, and access to throughput. This also has the benefit of if your cluster isn't large (bigger than say 48 ports) you can avoid having multi-cast leaving the switch (generally requires more wrangling with the network cats) as each TOR switch will be its own VSAN network. You then use NIOC to throttle and protect traffic from each other. Now NIOC isn't 100% as effective as SR-IOV (but its good enough) and will let you maximize your 10Gbps investment without flooding things out.
In this case VLAN 100, 101, and 102 would need to be on all switches.
*103 and 104 could be setup to only exist on each switch (A/B isolation, set failover not to fail over and don't configure on both) or exist on both (and use Standby) as described. This design will focus on keeping host to host communication on the same switch (Lowers complications with multicast, lowers latency as VSAN traffic will not have to hop to another switch unless you run out of switch ports, although now with dense 40Gbps switches using 10Gbps break outs in theory you could hit the 64 node limit on a single switch).
I'm curious anyone's thoughts on just disabling failover and forcing it to each kernel to stick to its switch (and accepting loss of communication) on that vKernel in the event of a switch failure. I'd like to do some lab tests with both and test switch/path failover between both of these configurations (vs. a single vkernel configuration).
Some people though prefer a "simpler" setup though (and I'm not opposed to that).
Duncan mapped out an active passive failover configuration with single vKernel's for each host.
In theory not being as dependent on NIOC for storage isolation should help latency for the short bursts it takes for NIOC to kick in vs the active active design.
Virtual SAN and Network IO Control
Merhaba
Vmware vCenter Converter Standalone 5.5.0 kullanarak. Vmware centos convert ederek diskleri thin olarak ayarlayıp işlem başarılı şekilde gerçekleştiriyor.
Vsphire den convert edilen makinayı açınca aşağıdaki ekran görüntüsü ile karşılaşıyorum ve çözüm bulamadım bilgisi olan varmıdır?
Hi,
You can set DNS Suffix using DNS custom option, find below details.
Configure the Management Network of the vCenter Server Appliance
The vCenter Server Appliance can obtain networking settings from a DHCP server, or use static IP addresses. You can change the networking settings of the vCenter Server Appliance from the Direct Console User Interface. You can change the IPv4, IPv6, and DNS configuration.
Prerequisites
To change the IP settings of the vCenter Server Appliance, make sure that the system name of the appliance is an FQDN. If, during the vCenter Server Appliance deployment, you set up the appliance to use an IP address as a system name, you cannot change the IP settings.
Procedure
We're running with a View 5.2 Connection server and are about to upgrade to Horizon 6.2.
My question is: what is the most recent client that is certified to run with View 5.2?
Ideally, this client would also work with Horizon 6.2, so we can use one client version while we upgrade.
I see from this page:
Documentation Center for Horizon 6 version 6.1 ... that Horizon Client 3.3 is compatible with 5.2 Connection server.
On this page:
Documentation for VMware Horizon 6 version 6.2, they state that Horizon client 3.5 is compatible with "Connection server: earlier version"
However, on this page:
VMware Horizon Clients Documentation (and click on "VMware Horizon Client for Windows Release Notes"), it says that Horizon Client is compatible with View 5.3 and above - no mention of 5.2.
I can't find any doco on 3.4 is compatible with, even though it's supposed to be the replacement for 3.3 to fix Security Advisory 2015-00004: VMSA-2015-0004 | United States
Anyone have a definitive answer?
OK - changed the MTU in the file /etc/sysconfig/network/ifcfg-eth0 and rebooted vcenter, before I only used /sbin/ifconfig etho mtu 1280 and it looked OK in the output.
Now it is working!
Thanks,
/Mattias
Hi ,
I have a Hp Server , i am planning to install Vmware on it .Please help me on below issues.
1> Which version of Vmware would be appropriate to install (ESXi 5.5 or 6.0)
2> Installation on BARE METAL Procedure.
Thank You
Anup Kumar
Hi,
This information can be fetched through powercli, check the below article for more details
thks, I've resolved my problem
Hello everyone,
I have a question which am searching from a week and I don't have any proper answer for the same. For any VMware VM either Linux or Windows OS, how do we differentiate a disk as OS disk & data disk ? Is there any way that we can recognize a disk as OS or data disk ??
Regards
Venkat.
"I'm curious anyone's thoughts on just disabling failover and forcing it to each kernel to stick to its switch (and accepting loss of communication) on that vKernel in the event of a switch failure. I'd like to do some lab tests with both and test switch/path failover between both of these configurations (vs. a single vkernel configuration)."
If i have this right you are suggesting relying on fail-over at the interface team level. Where a single vKernel is connected to this team. Instinct tells me there might be ARP cache issues, and a very unpredictable time to a solid link. The added complexity of the unique multiple vKernels networks is required in order to make a failure event predictable.
O yah, and great post! Perfect.
Thanks ksushil.
Well the problem was that EVC mode was enabled on the cluster and there were some 4.1 esxi hosts in the cluster. once i removed the 4.1 host out of the cluster the converter offered 8,9 and 10 virtual machine versions which support efi. This resolved the prob.