解决了

VMware/unidesk/Xendesktop/nutanix

C
徽章 +3
大家好，

目前，我们使用UNIDESK 2.1运行Xendesktop 5.6环境，并且只有一个我们希望解决的主要问题。使用Unidesk，VMDX磁盘（包含图层信息）分为非持久驱动器。结果，当重新启动虚拟destkop VM时，流程的功率可以在10-15分钟之间进行交谈 - 如果这些磁盘持续存在 - 电源会更快。我已经读过（UT无法找到链接），这已被接受为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
嗨，坎贝恩兹

我没有听说过VMware的任何更新。今天唯一的工作是为VM创建小容器。

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

http://www.unidesk.com/support/kb/unidesk-configuration-consideration-nfs-基于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（144445911002/00011020）开放案例。

我可以确认问题与VMware有关，并且他们知道它（PR＃913980）。不幸的是，我与之合作的支持工程师否认这是一个VMware问题，似乎并不渴望帮助我或提供更多信息（表示涉及机密信息）。我向他提供了这里提供的两个链接，以及Nutanix工程师的信息和响应。

在这一点上，问题已经存在，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"}}}">
A
秩
Userlevel 1
徽章 +7
NOS 3.5.3现在可用
dlink7
UserLevel 4
徽章 +19
从3.5.3的一些快速测试中，如果将bootlayersartive分为单独的容器，则可以获得50％的改进。我的测试是使用Vsphere 5.5和128台式机。您的里程可能会有所不同。这实际上取决于Vsphere必须扫描多少个文件。
m
徽章 +6
我想知道他们的NFS堆栈中还有哪些其他设计问题？我注意到NFS下的Nutanix上的快照比我的旧ISCSI SAN删除慢，而Stun Times可以达到6秒 - 这会导致我的VMware 5.5 Update Manager在备份期间从vCenter上断开连接（因为它们必须在不同的VMS上进行。如果使用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指出基于管理程序的快照“对虚拟机的性能产生负面影响”。

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
徽章 +6
只是好奇，但是仅创建vdisks并在unidesk的ISCSI上创建数据存储会表现更好吗？

在一个名为unidesk-ds01的容器中创建一个名为unidesk-ds01的ISCSI LUN，大小为500g

ncli vdisk创建名称= unidesk-ds01 ctr-name = unidesk-ds01 max-apacity = 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"}}}">
m
徽章 +6
Nutanix快照非常好（非常快），可以保护整个VM，但是当您需要更多的粒度恢复像文件时，通常最好使用依赖VMware快照的第三方备份工具。
期待NOS4.0，因为Nutanix Protect功能似乎有很大的改进，我注意到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://itbloodpressure.com/2014/04/13/blue-yelly-green-nutanix-and-veeam-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
徽章 +3
有偶然的屏幕截图吗？
dlink7
UserLevel 4
徽章 +19
答复在这里

http://www.veeam.com/videos/select-vmware-hyper-v-protection-data-center-4076.html
A
徽章 +2
我遇到了同一问题。我在VMware和Nutanix方面工作了几个月，并解决了稳定性问题。如果我在任何VM上进行了VMware快照，它将峰值CPU峰值，vCenter中的统计信息将消失，并且连接到接头的VM的任何人都会断开连接。我还使用Unidesk，当这种情况发生时，cachepoints将会腐败。

在我的UNIDESK环境中，我小心的每个数据存储都没有超过25 VM的VM，但是我在一个数据存储中都有一个旧的非遗传视图环境。它从失败的播放中积累了数百个孤儿文件夹。我清理了所有文件夹，并注意到了显着差异，但仍然不完美。

我更新了Nutanix 3.5.3，情况更好，但仍然不完美。我对Cassandra服务的记忆力不足，因此我不得不手动重新启动它。
在上周的维护期间，我借此机会更新了ESXI。我更新到5.1.0，1743533，快照问题消失了。现在，他们的行为就像我习惯了，主人不会像以前那样吓坏了。我实际上要使用Nutanix快照，但是由于View使用快照来提供，因此我必须解决该问题。我确实同意VMware上的NFS仍然存在一些问题。

我仍在等待3.5.4来帮助解决卡桑德拉问题，但是我的环境现在更加稳定。

我还使用Vshield运行BitDefender，这似乎也会引起零星的问题。我不知道其他人是否正在使用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
秩
徽章 +3
仅供参考，Nutanix和Unidesk最近根据我们自己的实验室和现有客户环境中的广泛测试发布了最佳实践。现在，我们有了一个最佳实践，当遵循遵循时，我们为诸如ON和VMOTION之类的操作提供了一致的时间。请在我们的支持门户中查看KB1208，或使用以下链接。

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

随着未来的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