VMS within vApps

Similar Questions

• How to create VMS of vapp model

  looking at the sample code in HellovCloud.cs, it shows how to create a VAPP model and which allows to create a paralytic, but can anyone provide an example of how select a model of VAPP existing and which allows to create a paralytic? If there are already examples of code, please point me to it. Thank you.

  Think I might have answered this in another thread for you - but in case others are looking...

  Hope this helps, by using the .NET SDK:

  Load the VCC you want to put TIME in

  VCC Vcc = Vdc.GetVdcByReference (customer, vdcReferenceUrl);

  Load the model you want to use

  Model VappTemplate = VappTemplate.GetVappTemplateByReference (customer, templateReferenceUrl);

  InstantiationParamsType instantiationParamsType = new InstantiationParamsType();

  InstantiateVAppTemplateParamsType = new InstantiateVAppTemplateParamsType stuff

  {
  AllEULAsAccepted = true,
  name = "the name of vapp",
  Source = model. Reference,
  deploy = true,
  Description = "description"
  InstantiationParams = instantiationParamsType,
  };
  Method to create he created... the app returned will not be usable for a while, but you can get the jobs for her and for the status of charging

  VAPP app = Vcc. InstantiateVappTemplate (stuff);

• FQDNs for ESX environment when DNS servers are VMS within the ESX environment

  Hello

  I was wondering,

  When the implementation of a new infrastructure from scratch, with an ESX cluster from scratch

  and when the servers DNS themselves will run inside the cluster,

  Then, it is advisable to use IP addresses instead of the domain name COMPLETE for the right ESX environment?

  Here's what I've done so far:

  -installed 1 ESX host

  -installed donain controller as VM

  -installed PSC and VCSA

  -created the new cluster

  -installed the second ESX host, added to the cluster.

  I installed a VM DC as the first thing after the installation of the initial ESX host, I could have started using the domain name COMPLETE for the ESX environment at this time.

  However, I didn't do it.

  For installation of the VCSA and when you add ESX hosts to the cluster, I used IP addresses instead of the FQDN names.

  It seems stupid and dangerous for me to use domain COMPLETE the ESX hosts themselves, because the domain controller is running in the cluster.

  So I used IP addresses only to ensure the ESX HA cluster and the characteristics of heartbeat stay ok if something were to happen to the DNS server.

  However, the VCSA installation and when you add hosts to the cluster,.

  the MISTLETOE gave me a warning, indicating that it is preferable to provide a FULL domain instead of an IP address name.

  I am of the opinion that if you have no physical DNS servers, it is not a good idea.

  My opinion is that when your nameservers inside the ESX cluster itself and you do not have 2 redundant external DNS servers, so it is not wise to use the FQDN for your ESX hosts, PSC and VCSA setup.

  In my view, using the property intellectual property is much safer in this case.

  I was wondering what is your angle on it.

  Do you see the same way, or have different opinions?

  Hi smetter,.

  It is advisable to have a working DNS for vSphere environment however the use of DNS for things like vSphere HA have been removed in more recent versions of the product. Refer to the section of the guidelines of the general network of this document for more details: https://www.vmware.com/files/pdf/techpaper/vmw-vsphere-high-availability.pdf

  With this in mind I wouldn't be worried about use of FULL domain for the addition of services like the ESX host, etc.. Failure where HA would be restarting the virtual computer, there is no dependency on DNS so it will continue to work as expected and, subject to the availability of resources the virtual machine starts on another host.

  According to your vSphere licenses, you may also like to consider the implementation of anti-affinity DRS VM to keep your DNS Appart servers and on different hosts. This can prevent your servers DNS are declining when the failure of a host. You must have Enterprise edition or later for this.

  Kind regards.

• Root user cannot create VMS within the Resource Pool after you rename the Cluster

  Currently, vCenter manages two clusters. I renamed a single cluster and the root user seems now are not allowed to create a new Virtual Machine in resource pools to the title of the group with the changed name. I tried to change the name of the cluster to its original name... no luck.

  The root user can still create a VM under the individual cluster nodes, but not in a resource pool.

  The cluster that has not been renamed yet can be managed completely with the root user. Resource pools it allow me to create a virtual machine.

  I found this last issue and checked on each cluster node that the ACEDataRoleId is-1 for each section: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1031192

  I am at a loss, any help would be greatly appreciated! Thank you!

  I think it's a bug. When I created a new data center and migrate all nodes in cluster about him, the permissions problem I was experiencing did not follow.

  Thank you for your help.

• Management of VMs: Which one to use, "hosts and Clusters" or "models and virtual computers.

  Hi all

  As the subject says, when you manage virtual machines, which is better to use? Hosts and Clusters? Models and virtual computers?

  It's our facility:

  Previously we had only been using "Hosts and Clusters" manage all of our virtual machines. We organize objects of the individual within vApps and Resource Pools. We had also installation on these both parent objects permissions for who has access to what.

  Basically, we have about 12 members. Everyone has their own virtual machines that they use for training, etc. We manage centralized via AD with users and groups user access. We also have some users assigned to some hosts to maintain the level of things between the two hosts. Our license does not DRS, BTW.

  I just replaced our server vCenter in preparation for our 4.1 vSphere upgrade later this year, Yes, we are on vSphere 4.0 currently. So I went ahead and 'computers models and virtual"allowing to create user folders, gave users access and placed virtual machines of all users within these folders. (I heard recently that the use of the hosts and Clusters was semantically incorrect). Even if they have access to their folder, they cannot create a virtual machine because they cannot access a host. A computer file virtual and models can be assigned to a host?

  I didn't assign permissions to each user in order to add to each host, because I didn't want others to mess with other virtual machines. All users previously red access only, but sinc the virtual machines and templates folders are not assigned to any host, they can get in their folder to create and manage their virtual machines.

  Then, I go on this wrong all the models and virtual computers and do I just keep using our hosts and Clusters of installation above permissions groups?

  Any advice on the semantics in this would be appreciated.

  Thank you

  Johnathan

  All,

  I solved my problems.

  Check book Scott Lowes ' Mastering VMware vSphere 4 "Chapter 9, he described the use of Resource Pools to the VM group under the view of the hosts & Clusters. Using the same names as the files under VMs & models and adding the same permissions, I was able to force every user to use their own folder under VMs & templates and only their Resource Pool under hosts & Clusters. So now the two views reflect the objects of each user and their access controls are correct.

  Items to remove this Lessines:

  Use Of Resource Pools under host & Clusters to manage the default host for users.

  Files under VMs & models allows you to manage virtual machines model announcement for each user (simple view).

  Thanks for the help,

  Johnathan

• vCloud 1.5 Org Networking internal and external IP

  Hello

  I build a vcloud environment and one of the requirements of our team is that they can for their workstations RDP in their VMs within vCloud. Each Member of the team will have several copies of the same virtual machines that are running in several TIME that needs to be closed because of obvious name conflicts since all machines will be identical.

  What Type of Org network I create to accomplish this requirement?

  

  

  

  We have this configuration by creating a network within the vApp and assignment of an address 192.168.10.xxx to each of the virtual machine inside the vApp.  We use an external-Direct network between the network of vApp and organizational network with a Pool of IP to assign NAT IP addresses for the external face of the VSE (virtual router) and each virtual computer inside the vApp.  This allows the virtual machine is talking to eachother through the 192.168.10.0 network and is accessible from desktop users through the external IP address assigned.

  We save the network inside the vApp settings so our users not to modify them when they deploy a copy of their cloud.

  I hope this helps.

  Eric

• Design/implementation of Nexus 1000V

  Hi team,

  I have a premium partner who is an ATP on Data Center Unified Computing. He has posted this question, I hope you can help me to provide the resolution.

  I have questions about nexus 1KV design/implementation:

  -How to migrate virtual switches often to vswitch0 (in each ESX server has 3 vswitches and the VMS installation wizard will only migrate vswicht0)? for example, to other vswitchs with other vlan... Please tell me how...
  -With MUV (vmware update manager) can install modules of MEC in ESX servers? or install VEM manually on each ESX Server?
  -Assuming VUM install all modules of MEC, MEC (vib package) version is automatically compatible with the version of vmware are?
  -is the need to create port of PACKET-CONTROL groups in all THE esx servers before migrating to Nexus 1000? or only the VEM installation is enough?
  -According to the manual Cisco VSM can participate in VMOTION, but, how?... What is the recommendation? When the primary virtual machines are moving, the secondary VSM take control? This is the case with connectivity to all virtual machines?
  -When there are two clusters in a vmware vcenter, how to install/configure VSM?
  -For the concepts of high availability, which is the best choice of design of nexus? in view of the characteristics of vmware (FT, DRS, VMOTION, Cluster)
  -How to migrate port group existing Kernel to nexus iSCSI?... What are the steps? cisco manual "Migration from VMware to Cisco Nexus 1000V vSwitch" show how to generate the port profile, but
  How to create iSCSI target? (ip address, the username/password)... where it is defined?
  -Assuming that VEM licenses is not enough for all the ESX servers, ¿will happen to connectivity of your virtual machines on hosts without licenses VEM? can work with vmware vswitches?

  I have to install nexus 1000V in vmware with VDI plataform, with multiple ESX servers, with 3 vswitch on each ESX Server, with several machinne virtual running, two groups defined with active vmotion and DRS and the iSCSI storage Center

  I have several manuals Cisco on nexus, but I see special attention in our facilities, migration options is not a broad question, you you have 'success stories' or customers experiences of implementation with migration with nexus?

  Thank you in advance.

  Jojo Santos

  Cisco partner Helpline presales

  Thanks for the questions of Jojo, but this question of type 1000v is better for the Nexus 1000v forum:

  https://www.myciscocommunity.com/Community/products/nexus1000v

  Answers online.  I suggest you just go in a Guides began to acquire a solid understanding of database concepts & operations prior to deployment.

  jojsanto wrote:
  Hi Team,
  I have a premium partner who is an ATP on Data Center Unified Computing. He posted this question, hopefully you can help me provide resolution.
  I have questions about nexus 1KV design/implementation:
  -How migrate virtual switchs distint to vswitch0 (in each ESX server has 3 vswitches and the installation wizard of VMS only migrate vswicht0)?? for example others vswitchs with others vlan.. please tell me how...
  [Robert] After your initial installation you can easily migrate all VMs within the same vSwitch Port Group at the same time using the Network Migration Wizard.  Simply go to Home - Inventory - Networking, right click on the 1000v DVS and select "Migrate Virtual Machine Networking..."   Follow the wizard to select your Source (vSwitch Port Groups) & Destination DVS Port Profiles
  -With VUM (vmware update manager) is possible install VEM modules in ESX Servers ??? or must install VEM manually in each ESX Server?
  [Robert] As per the Getting Started & Installation guides, you can use either VUM or manual installation method for VEM software install.
  http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/getting_started/configuration/guide/n1000v_gsg.html
  -Supposing of VUM install all VEM modules, the VEM version (vib package) is automatically compatible with build existen vmware version?
  [Robert] Yes.  Assuming VMware has added all the latest VEM software to their online repository, VUM will be able to pull down & install the correct one automatically.
  
  
  -is need to create PACKET-MANAGEMENT-CONTROL port groups in ALL esx servers before to migrate to Nexus 1000? or only VEM installation is enough???
  [Robert] If you're planning on keeping the 1000v VSM on vSwitches (rather than migrating itself to the 1000v) then you'll need the Control/Mgmt/Packet port groups on each host you ever plan on running/hosting the VSM on.  If you create the VSM port group on the 1000v DVS, then they will automatically exist on all hosts that are part of the DVS.
  -According to the Cisco manuals VSM can participate in VMOTION, but, how? .. what is the recommendation?..when the primary VMS is moving, the secondary VSM take control?? that occurs with connectivity in all virtual machines?
  [Robert] Since a VMotion does not really impact connectivity for a significant amount of time, the VSM can be easily VMotioned around even if its a single Standalone deployment.  Just like you can vMotion vCenter (which manages the actual task) you can also Vmotion a standalone or redundant VSM without problems.  No special considerations here other than usual VMotion pre-reqs.
  -When there two clusters in one vmware vcenter, how must install/configure VSM?
  [Robert] No different.  The only consideration that changes "how" you install a VSM is a vCenter with multiple DanaCenters. VEM hosts can only connect to a VSM that reside within the same DC.  Different clusters are not a problem.
  -For High Availability concepts, wich is the best choices of design of nexus? considering vmware features (FT,DRS, VMOTION, Cluster)
  [Robert] There are multiple "Best Practice" designs which discuss this in great detail.  I've attached a draft doc one on this thread. A public one will be available in the coming month. Some points to consider is that you do not need FT.  FT is still maturing, and since you can deploy redundany VSMs at no additional cost, there's no need for it.  For DRS you'll want to create a DRS Rule to avoid ever hosting the Primar & Secondary VSM on the same host.
  -How to migrate existent Kernel iSCSI port group to nexus? .. what are the steps? in cisco manual"Migration from VMware vSwitch to Cisco Nexus 1000V" show how to generate the port-profile, but
  
      how to create the iSCSI target? (ip address, user/password) ..where is it defined?
  [Robert] You can migrate any VMKernel port from vCenter by selecting a host, go to the Networking Configuration - DVS and select Manage Virtual Adapters - Migrate Existing Virtual Adapter. Then follow the wizard.  Before you do so, create the corresponding vEth Port Profile on your 1000v, assign appropriate VLAN etc.  All VMKernel IPs are set within vCenter, 1000v is Layer 2 only, we don't assign Layer 3 addresses to virtual ports (other than Mgmt).  All the rest of the iSCSI configuration is done via vCenter - Storage Adapters as usual (for Targets, CHAP Authentication etc)
  -Supposing of the licences of VEM is not enough for all ESX servers,, ¿will happen to the connectivity of your virtual machines in hosts without VEM licences? ¿can operate with vmware vswitches?
  [Robert] When a VEM comes online with the DVS, if there are not enough available licensses to license EVERY socket, the VEM will show as unlicensed.  Without a license, the virtual ports will not come up.  You should closely watch your licenses using the "show license usage" and "show license usage " for detailed allocation information.  At any time a VEM can still utilize a vSwitch - with or without 1000v licenses, assuming you still have adapters attached to the vSwitches as uplinks.
  I must install nexus 1000V in vmware plataform with VDI, with severals Servers ESX, with 3 vswitch on each ESX Server, with severals virtual machinne running, two clusters defined with vmotion and DRS active and central storage with iSCSI
  I have severals cisco manuals about nexus, but i see special focus in installations topics, the options for migrations is not extensive item, ¿do you have "success stories" or customers experiences of implementation with migrations with nexus?
  [Robert] Have a good look around the Nexus 1000v community Forum.   Lots of stories and information you may find helpful.
  Good luck!
  

• #AVCA vCloud AIR and private Cloud

  If our customers have a few SDDC (private Cloud) in its data center if there's opportunity to create the DR site in vCloud Air and replicate all virtual machines to the cloud.

  If after that a disaster in SMV primary location should be available for the customer? (I predict customer should have a specific configuration and product for the replication of all virtual machines of their datacenter to vCloud Air?)

  Sebastian

  vTechnology Notes

  Hi Sebastian,.

  Yes, vCloud Air Disaster Recovery allows to easily backup and catering for your workloads cloud virtualized (and not virtualized using one of our third party partners), using management tools you already use on-Prem when your customer subscribes to vCloud Air Disaster Recovery, they will be able to select vCloud Air as a backup destination for their VMs within vCloud Director (see link below for a tutorial video demonstration of this action).  vCloud Air Disaster Recovery using vSphere replication to manage failover and failback of the virtual machines.  It does not require a separate, purchase everything necessary to facilitate backup and restore is included in the price of subscription vCloud Air Disaster Recovery.

  If the client experiences a disaster, they will be able to turn the virtual machines that they were back up to the cloud (up to 15 minutes RPO), in the Air of vCloud.  They have 30 days to use their ability subscribed free of charge, with the possibility of adding more resources, if necessary.

  I am will broadcast a webcast tomorrow, March 3, at 11 am PST to talk about DR based on a cloud and vCloud Air if you want more information: Cloud Computing Webcasts | Air by VMware vCloud

  Here are a few resources:

  http://vCloud.VMware.com/using-vCloud-air/tutorials http://vCloud.VMware.com/using-vCloud-air/tutorials http://vCloud.VMware.com/using-vCloud-air/tutorialsCloud Computer tutorials | Air by VMware vCloud (scroll down to the section of disaster recovery to see the demonstration video)

  Cloud Computing Disaster Recovery: Air by VMware vCloud  (General page)

  Thank you

  John

  AVCA , #ACVA

• Put virtual machines inside the VMkernel port group

  Hello

  Network for administrators of VMware SIAS layout:

  "You can not put VMs within that group of port because it is made especially for a VMkernel port."

  However, I use ESXi 5.5 and is able to put normal interface of VM inside the vmk port group. (I only created 1 vmk port group so all virtual machines in the same group with the vmkernel interface)

  May I know if this is a new feature, or something is wrong?

  Thank you!

  This may be possible with distributed switches not with standard switches.

• On-site application move to vCloud Air

  Hello

  Is it possible to move applications easily on site, VM or vApps to vCloud Air?

  Kind regards

  BA

  Absolutely, the benefits of vCloud Air include compatibility and portability of bidirectional load with vSphere environments.   With our tool, vCloud connector, users can easily migrate VMS and vAPPs to vCloud Air and then back if so chosen.

• Migrando vSphere 5.0 5.5 para servidores also e

  Olá Senhores, tudo bem?

  Alguem aqui ja precisou migrar vSphere 5.0 5.5 para, mas also migrando as hosts in new para VMS (servidores but new)?

  Who could tutor na net sober isso OU documentacao da Vmware?

  POI seria o seguinte básicamente.

  Cluster com 4 Servidores, 50 VMS cluster neste e das VMS em some TIME with Betclic are many. MIGRAR como then as VMS cluster 5.0 para o 5.5, whereas estes VAPP atual?

  Obrigado!

  Ivanildo Galvão

  Ivanildo,

  Antes prosseguir, confirms to vCenter e unico para os o have to clusters, caso afirmativo, segue some exemplos:

  1. VAPP o Exportar e import no cluster, very essa atividade pode demorar muito, POI novo size das depende MV;

  2 perform o seguinte ko principle: VMware KB: move a VMware vCenter Operations Manager VAPP from one cluster to another

  O KB acima fala VAPP vCOPs, mas a idéia e a mesma para outro VAPP, wave resumidamente, voce desliga any as VMs do VAPP, migra as cluster of virtual machines para o novo, criar VMs 'vazias"com nightclubs don't thin paralytic, export o VAPP com as thin VMs 'vazias" (o be bastante rapido), imported no cluster of novo, numbers a VM "vazia" thin , migra as VMs originais para o VAPP, confirmed an order of inicializacao das VMs no VAPP e depois e so iniciar o VAPP.

• How to get the length of the string a vm?

  Hello

  I'm trying to automate some consolidation of virtual machines and would like to add script. I have over 800 virtual machines manually would not work.

  I would like to

  $allVApps = get-CIVApp

  foreach ($CIVm to ($allVApps |)) Get - CIVM)) {}

  find the number of channels and if greater than 8 consolidate them.

  }

  Someone has this practice? or something else?

  I'm in a cloud environment vSphere 5.5, installed latest powercli.

  Thank you

  Don't know why this does not work for others, but what I posted before work for me.  Here is a more complete version of how get the those of VAPP VM.  There are no doubt more direct ways, but that how I made it so far:

  1. get the VAPP

  $vApp = get-CIvApp-name 'Test-VAPP.

  2. get the VMS of vApp

  $VMs = $vApps.ExtensionData.Children.vm

  3. get the ones for the VM first in the list of $VMs:

  $VMs [0]. VCloudExtension.any.VirtualDisksMaxChainLength

  This last command returns 18 for me which is the "Length of the string" value in the properties of the Virtual Machine to the virtual machine in the vCD UI.

  I hope this helps.

• vcops-admin is missing

  Hello

  using vcops 5.8.2 on vCenter 5.5U1b that I can't not to start the VAPP due to EGG the VAPP properties which seem not work in vCenter 5.5.u1b. Now remove the virtual machines of the TIME does not help because the vApps must be configured with an IP address at start-up.

  He has had similar problems in other versions of vCOPS and there are a few KBs you can follow in order to solve these problems ( KB VMware: manage a VMware vCenter Operations Manager 5.x deployment where the vApp is broken ). They suggest that what I tried: remove the VMs of vApp, start them. They go abit further and will tell you how to manually configure the IP address of the shell. However, these KB articles are completely outdated. I managed to find out that there is a vaim_config_net in vCOPS 5.8.x (if I remember it's good) script that can be used to change the ip address of Analytics as well as the virtual machine of the user interface.

  In the former article after you configure the IP address, they suggest to run vcops-admin fix in the virtual machine to the user interface in order to re - link (in my case the first time link) the vm ui with the analytical vm for the VPN tunnel that is being built between those two vms can come and vCOPS service can start (previously, there is no way to start the web service and change the configuration from there). Is the only problem: the ship vcops-admin seems to be retired from vCOPS 5.8.x and there seems to be no replacement.

  Nobody knows:

  1. an alternative workaround for the problem

  2. the replacement of the vcops-admin tool?

  Greetings

  vcops-admin is still there in 5.8.x. You run Su UI VM admin?

• When the suspension/resumption blue screens Windows Hyper-V VM in ESXi 5.5

  ESX to virtualize ESXi and Windows Hyper-V machines for training scenarios. We have dozens (or even hundreds) of these virtual machines in use in a large farm of ESX host at any given time. Students are able to suspend their virtual machines at any time and come back later. It worked flawlessly on ESXi 5.1. Our troubles started when we went to ESXi 5.5. After the upgrade, Windows Hyper-V guests began to break up with a blue screen during the process of suspension/resumption. We have restored 5.1 on two of our boxes and the problem stopped. We may be forced to return all the servers to 5.1, but are really hoping to find a fix or a workaround. We are opening a case with VMware, but thought we ask here as well.

  
  Comments
  
  

  • We have the latest version of ESXi 5.5, build 1892794.
  • BSOD comments were held on all ESX hosts, we have. We have two server hardware configurations that are very similar (details below) and the BSOD occur with equal frequency on both.
  • BSOD happens in 2012 Windows R2 and Windows 2008 R2 VMs.
  • EDIT: BSOD occur if the two "hypervisor.cpuid.v0 = FALSE" is configured and the Hyper-V role is installed. No BSOD that Hyper-V is deleted or if happen "hypervisor.cpuid.v0 = FALSE" is deleted.
  • The "hypervisor.cpuid.v0 = FALSE" parameter is used to make Hyper-V think it runs on native hardware. Without it, Windows knows it is running in a virtual machine and the BSOD go. But Hyper-V won't start nested VMs. I wish we didn't need the arrangement, but, alas, we do.
  • We have never seen a BSOD that was triggered by a suspension/recovery.
  • Not every interruption/resumption will cause a BSOD. During testing, we see a BSOD about 20% of the time that a suspension/resumption is carried out.
  • This happens on ESXi hosts whether they are occupied or not. We took a server out of rotation of isolated tests and saw the exact same behavior.
  • There are various BSOD messages. The most common is 'IRQL_GT_ZERO_AT_SYSTEM_SERVICE' with a stop of 0x0000004A code. But there are several others.
  • We thought it might have something to do with the bug of processor Intel E5 (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2073791). However, we use E5 V1 processors, not V2. We have updated to the latest Dell BIOS (2.2.3) just in case. It made no difference.
  • We tried to turn off all the power settings in the BIOS of the server, as well as within ESX. This includes any definition performance max and disabling C States. No difference.
  • We have disabled all of the features available in the BIOS of the virtual machines, including all the caching options. No difference.
  • We use the following parameters to enable nested Virtualization:
    • CPU/MMU hardware
    • VHV. Enable = TRUE
    • Hypervisor.CPUID.v0 = FALSE
  • We tried to use "windowsHyperVGuest" as the identifier for OS invited instead of the above parameters. Nested virtualization has worked well, but the BSOD is still produced at the same rate.
  • EDIT: we tried the upgrade virtual machines since version 9 to version 10 of hardware equipment. This did not help.
  • EDIT: we tried the VMware Tools upgrade from version 9.0.0.782409 to 9.4.6.1770165. This did not help.
  • We tried allowing the CPU performance counter virtualization in virtual machines. No help.
  • We came home two of our servers to 5.1 and the BSOD disappeared completely. No other changes been made to the servers and virtual machines. Just go back to 5.1 fixes the problem.
  • We have noticed a dramatic amount of time difference to both versions of ESXi to suspend these VMs. ESXi 5.1 suspends these VMs within 2-3 seconds, while ESXi 5.5 takes 30 seconds to a minute. Certainly, something very different happens during the process of suspension. Suspend time 5.5 are longer or not a BSOD occurs.

  Our material

  • Dell PowerEdge R720xd OR Dell PowerEdge r.620
  • BIOS version: 2.2.3
  • Processors: 2 - Intel Xeon E5-2670 0 @ 2.60 GHz
  • RAM: 384GB (16 GB (buffered) synchronous DDR3 DIMMS matched Dell 24)
  • Controller: PERC H710P Mini 1 GB memory NVRAM
  • OS disc: 2-240GB S3500 SSD drives in a RAID 1 (Slot 00-01) mirror
  • VM storage drive: 7-480GB S3700 SSD in a RAID5 with a HS spare dedicated (Slot 02-09)
  • 1 - Intel 2 p X 540/2 p I350 rNDC
  • 1 - Intel Gigabit 4 p I350-t adapter

  The obvious solution is to roll back to 5.1. However, we completely independent questions with 5.1 (one topic for another post) that we don't have with 5.5 and prefer to stay with 5.5. But these BSOD is a deal breaker. Help or direction to solve the BSOD will be greatly appreciated!

  In some cases, a single byte stored in the checkpoint file is outdated.  This only affects nested customers.  During the recovery of a Hyper-V OS management from a corrupt checkpoint, a variety of BSOD can result.

  You must file a request for assistance for an express patch with a fix for the PR 1289485.

• Redundancy of the workspace

  How can I make my Horizon Workspace deployment highly available in the event of failure?  There are 5 VMs to vApp, but none of them are there to provide redundancy for the others.  I'm afraid that the workspace is a single point failure for my environment to view giant.  I saw a "addvm" command... should I just run which, for all 5 mV in the vApp and then I'll have 10VMs with each VM with compensation for redundancy?  Or it does not work like that?

  T

  Today, with the data - will, Yes, we have redundancy. Basically, a set of users are assigned to each data - going. If this goes data fails, these users will not be able to access the data horizon features. We actively try to fix this in our future versions.

  You mentioned that you use view integration, which should not have any how reliance on data - will go down. Please let us know if you are using data to horizon as well. If so, we should call for webex and we can guide you through a few ways of redundancy using HA etc.