解决了

VMware / Unidesk / XenDesktop / Nutanix

C
徽章 ＋３
大家好，

我们目前在Unidesk 2.1下运行XenDesktop 5.6环境，只有一个主要问题需要解决。使用uniddesk, VMDX磁盘(包含层信息)被分类为非持久驱动器。因此，当重新启动Virtual Destkop VM时，上电进程可以在10-15分钟之间进行对话——如果这些磁盘是持久的——上电速度要快得多。我读到(但找不到链接)这已经被认为是VMware的问题，目前正在解决-谁能透露一下VMware什么时候会解决这个问题

干杯
达蒙
图标

最好的答案dlink72014年2月8日21:53

\n
\nI haven't heard of any update from VMware. The only work around today is to create small containers for the VM's.
\n
\nHere are two links explaining the current issue for people that might not know.
\n
\nhttp:\/\/www.unidesk.com\/support\/kb\/unidesk-configuration-considerations-nfs-based-storage-including-nutanix-your-boot-images
\n
\nhttp:\/\/nutanix.blogspot.ca\/2013\/10\/unidesk-on-nfs-taking-about-minute-to.html","className":"post__content__best_answer"}">
查看原始
\n
\nWe currently run our XenDesktop 5.6 Environment with Unidesk 2.1 and have only one main issue that we would like to see resolved. With Unidesk the VMDX disks (which contain the layer information) are classed as non-persistent drives. As a result when re reboot the Virtual Destkop VM the power on process can talk anywhere between 10-15 minutes - if these disks were persistent - power on is considerably quicker. I have read (ut unable to find the link) that this has been accepted as a VMware issues and currently being worked on - Can anyone shead some light on this as to when VMware will be resolving the problem
\n
\nCheers
\nDamon","quoteUsername":"CampbellDNZ","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

14日回复

dlink7
Userlevel 4
徽章 +19
嗨CampbellNZ

我还没有听到来自VMware的任何更新。目前唯一的解决方法是为VM创建小型容器。

这里有两个链接，解释了当前的问题，可能有人不知道。

http://www.unidesk.com/support/kb/unidesk-configuration-considerations-nfs-based-storage-including-nutanix-your-boot-images

http://nutanix.blogspot.ca/2013/10/unidesk-on-nfs-taking-about-minute-to.html
\n
\nI haven't heard of any update from VMware. The only work around today is to create small containers for the VM's.
\n
\nHere are two links explaining the current issue for people that might not know.
\n
\nhttp:\/\/www.unidesk.com\/support\/kb\/unidesk-configuration-considerations-nfs-based-storage-including-nutanix-your-boot-images
\n
\nhttp:\/\/nutanix.blogspot.ca\/2013\/10\/unidesk-on-nfs-taking-about-minute-to.html","quoteUsername":"dlink7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
R
徽章 ＋5
过去几周我一直在使用此问题的VMware / Nutanix / Unidesk，目前具有VMware / Nutanix的开放案例（14445911002/00011020）。

我可以确认这个问题是关于VMware的，他们已经意识到了(PR# 913980)。不幸的是，与我一起工作的支持工程师否认这是VMware的问题，似乎不急于帮助我或提供更多的信息(声称涉及机密信息)。我向他提供了这里提供的两个链接，以及Nutanix工程师的信息和回复。

此时，问题在那里，努力提高努力解决这个问题，以解决其客户（以及对他们而这样做的赞誉）。我被告知下一个NOS发布（3.5.3）将减轻这个问题并最终在4.x周围设计。

编辑：
刚刚收到VMware关于这个问题的官方回复。

抱歉延迟回复。我想向您提供最多的信息。您正在遇到的问题已被确定为我们的NFS堆栈中的设计问题。
解决此问题的解决需要完全重写，这可能不会发生，直到至少是下一个主要版本，这是一个2015年的球场。我很抱歉更新并不更有利，但我希望你有VMware的官员问题上的问题而不是来自博客的二手信息。如果您有任何进一步的疑虑或问题，请告诉我。
\n
\nI can confirm that the issue is with VMware and that they are aware of it (PR# 913980). Unfortunately the support engineer I was working with denied it was a VMware issue and did not seem eager to assist me or provide more information (stated there was confidential information involved). I offered him both of the links provided here, as well as information and responses from Nutanix engineers.
\n
\nAt this point, the issue is there, and Nutanix is stepping up in order to resolve this issue for its customers (and kudos to them for doing so). I was informed that the next NOS release (3.5.3) will mitigate the issue and ultimately design around it in 4.x.
\n
\nEDIT:
\nJust received an official reply from VMware on this issue.
\n
\nSorry for the delay in responding. I wanted to provide you with the most up to date information. The issue which you are experiencing has been identified as a design issue within our NFS stack.<\/i>
\nThe resolution of this problem requires a full re-write which likely will not occur until at least the next major release, which has a ballpark 2015. I'm sorry the update is not more favorable, but I wanted you to have the VMware's official stance on the issue instead of second hand information from a blog. If you have any further concerns or questions, please let me know.<\/i>","quoteUsername":"ryanogburn","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
一个
排名
Userlevel 1
徽章 ＋７
NOS 3.5.3现已推出
dlink7
Userlevel 4
徽章 +19
从3.5.3的一些快速测试中，如果你把Bootlayersarchive分解成独立的容器，你可以得到大约50%的改进。我的测试用的是vSphere 5.5和128台式机。这将是你的里程可能会有所不同。这将取决于vSphere需要扫描多少文件。
米
徽章 ＋６
我想知道他们的NFS堆栈中还有哪些其他设计问题?我注意到NFS以下Nutanix路上快照慢比我老iSCSI SAN删除,和眩晕时间可达6秒——这导致我的VMware 5.5更新管理器断开期间vcenter备份(如必须在不同的vm如果使用VC设备)。

这对客户数据库服务器和相关应用服务器来说是一个可怕的暗示，我正在认真考虑再次实现iSCSI(我相信您可以用Nutanix做得很好)，因为我认为VMware NFS是非常脆弱的。
\n
\nThat is a scary implication for customer database servers and their related application servers, and I'm seriously considering implementing iSCSI again (as I believe you can do as well with Nutanix) because I think VMware NFS is flaky as hell.","quoteUsername":"millennia","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
dlink7
Userlevel 4
徽章 +19
我会鼓励您使用基于Nutanix的快照，并留在可能性的Nutanix NFS上。

基于管理程序的快照存在局限性。基于KB的低于KB状态的快照“对虚拟机的性能产生负面影响。”

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009402
\n
\nThere are limitations around hypervisor based snapshots. The below KB states hypervisor based snapshots \"Negatively impacts the performance of a virtual machine.\"
\n
\nhttp:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?language=en_US&cmd=displayKC&externalId=1009402","quoteUsername":"dlink7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
V
徽章 ＋６
只是好奇，但它不会更好的只是创建vdisks和创建数据存储上的iscsi undesk ?

在容量为500G的容器uniddesk -ds01中创建iscsi lun uniddesk -ds01

create name= uniddesk -ds01 ctrname = uniddesk -ds01 max-capacity=500
\n
\nCreate an iscsi lun called unidesk-ds01 in a container called unidesk-ds01 that is 500G in size
\n
\nncli vdisk create name=unidesk-ds01 ctr-name=unidesk-ds01 max-capacity=500","quoteUsername":"vedeht","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
米
徽章 ＋６
Nutanix快照对于保护整个vm来说非常棒(而且非常快)，但是当你需要更细粒度的恢复(比如文件恢复)时，使用依赖于VMware快照的第三方备份工具通常会更好。
期待Nos4.0，因为Nutanix保护功能似乎很大，我注意到Veeam会随着Nutanix的融合增加，所以也许我也可以试图查看它是否解决了VMware上的快照蓝调。
\nLooking forward to NOS4.0 as there appear to be big improvments in the Nutanix Protect features, and I note Veeam have an increased convergence with Nutanix, so maybe I try that product as well to see if it solves my snapshot blues on VMware.","quoteUsername":"millennia","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
dlink7
Userlevel 4
徽章 +19
veeam很棒，如果你有时间，我们有一个联合网络研讨会，如果你有时间，

http://itblooppressure.com/2014/04/13/blue-yellow-green-nutanix-and-veam-paint-by-number-disaster-recovery/

-DL.
\n
\nhttp:\/\/itbloodpressure.com\/2014\/04\/13\/blue-yellow-green-nutanix-and-veeam-paint-by-number-disaster-recovery\/
\n
\n-DL","quoteUsername":"dlink7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
D
徽章 ＋３
有机会在某个地方截然吗？
dlink7
Userlevel 4
徽章 +19
回复在这里

http://www.veeam.com/videos/select-vmware-hyper-v-protection-data-center-4076.html.
一个
徽章 ＋２
我也遇到过同样的问题。我在VMware和Nutanix上工作了好几个月，都遇到了稳定性问题。如果我在任何一个虚拟机上做一个Vmware快照，它会使主机CPU激增，Vcenter中的统计数据将消失，任何连接到正在被快照的虚拟机的人将断开连接。我也使用undesk，当这种情况发生时，缓存点会被破坏。

在我的uniddesk环境中，我小心地不让每个数据存储上有超过25个VM，但是我在一个数据存储上有一个传统的非持久视图环境。由于重置失败，它已经积累了数百个孤立的文件夹。我清理了所有的文件夹，发现了明显的不同，但仍然不是完美的。

我更新到Nutanix 3.5.3，事情更好，但仍然不完美。Cassandra服务耗尽内存的问题，我有问题，所以我必须手动重启它。
在上周的维护期间，我利用这个机会对ESXi进行了更新。我更新到5.1.0,1743533，快照问题消失了。现在他们的行为和我习惯的很像，而且主人也不像以前那样害怕了。实际上，我将使用Nutanix快照，但由于View使用快照来提供，所以我必须解决这个问题。我同意NFS在VMware上仍然存在一些问题。

我还在等待3.5.4来帮助解决Cassandra的问题，但我的环境现在稳定多了。

我也使用vshield运行bitdefender，这些vshield也似乎导致零星问题。我不知道是否有其他人使用vShield产品。
\n
\nIn my Unidesk environment, I was careful to not have more than 25 VM's per datastore, but I have a legacy non-persistent view environment all on one datastore. It had accumulated hundreds of orphaned folders from failed reprovisioning. I cleaned up all of the folders and noticed a significant difference, but still not perfect.
\n
\nI updated to Nutanix 3.5.3 and things were better, but still not perfect. I had issues with the Cassandra service running out of memory, so I've had to manually restart it.
\nDuring a maintenance period last week, I took the opportunity to update ESXi. I updated to 5.1.0, 1743533 and the snapshot issues disappeared. Now they behave much like I'm used to and the host doesn't freak out like before. I'm actually going to use the Nutanix snapshots, but since View uses snapshots to provision, I had to solve the issue. I do agree that NFS on VMware still has some issues.
\n
\nI'm still awaiting 3.5.4 to help with the Cassandra issues, but my environment is much more stable now.
\n
\nI'm also running Bitdefender using Vshield which also seems to cause sporadic issues. I don't know if anyone else out there is using a vshield product.","quoteUsername":"amerriam","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
dlink7
Userlevel 4
徽章 +19
Unidesk＆Nutanix认为已经找到了NFS错误的分辨率。目前Unidesk正在使用脚本来解决问题。如果您面临问题，请联系Unidesk支持，然后可以解决它。听起来您将重新启动桌面以获得此修复。
C
排名
徽章 ＋３
FYI，Nutanix和Unidess最近在我们自己的实验室和现有客户环境中发布了最佳实践。我们现在有最好的做法，当遵循时，为我们提供了一致的操作时间，例如电源开机和vMotion。请在我们的支持门户中查看KB1208，或使用下面的链接。

https://portal.nutanix.com/#/page/kbs/details?targetid=ka0600000008xgccau.

这KB将继续发展，因为未来的NOS和ESXi版本被发布，以提高我们今天所知道的。
\n
\nhttps:\/\/portal.nutanix.com\/#\/page\/kbs\/details?targetId=kA0600000008XgCCAU
\n
\nThis KB will continue to evolve as future NOS and ESXi versions are released that improve upon what we know today.","quoteUsername":"chad","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


Baidu