Join this episode for more Stories from the EUC Road as Sean Donahue (Nutanix) and Al Solorzano (E360) tackle this all too familiar question. But does it have to an \u201cOR\u201d statement? Can you have an \u201cAND\u201d statement instead? Tune in to learn more about performance in EUC, happy employees and how you might sleep better at night in the age of Malware and Ransomware.<\/p><\/oembed>

Resources<\/p>

Hyper-V 2016

A
徽章 +7
Hyper-V 2016何时兼容？
该主题已关闭以供评论

43个答复

乔恩
秩
UserLevel 6
徽章 +29
我们的总体管理程序支持政策在这里：



//www.jhbzcj.com/support/support-faqs/#hyhypervisor-support



TLDR- ga的90天
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
A
徽章 +9
你好，约翰，



您是否有有关升级过程的信息？我们在看一个简单的一键吗？另外，我们是否可以使用纳米服务器，如果是这样，则该过程与普通的一键式升级相同吗？



亲切的问候

\n

\nDo you have any information on the upgrade process? Are we looking at a rather simple One-Click? Also, will we be able to use Nano-server, and if so is the process the same as an normal One-Click upgrade?

\n

\nKind Regards","quoteUsername":"Aanuka","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
乔恩
秩
UserLevel 6
徽章 +29
TBD。我们一直在尝试以不同的迭代方式进行技术预览，并且我们将看到MS一旦产品的实际发布的内容。
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
C
徽章 +1
大家好，

你好乔恩，



Windows Server 2016 RTM关于群集安装的任何更新？

我们有一个NX-3000，我们希望使用最后一个Windows Server操作系统重新安装一个集群。



我们可以提供有关Fresh安装的文档吗？

After a crash we have previously need full reinstall cvm with a nutanix support operator and it's not a OneClick process .



非常感谢您的宝贵帮助。



哈瓦愉快。



问候。

\nHello Jon,

\n

\nAny update about Cluster install with Windows server 2016 RTM ?

\nWe have a NX-3000 and we want reinstall a cluster with the last windows server operating system.

\n

\nCan we have some documentation about fresh install ?

\nAfter a crash we have previously need full reinstall cvm with a nutanix support operator and it's not a OneClick process 🙂 .

\n

\nThanks you so much for your precious help.

\n

\nHava a nice day.

\n

\nRegards.","quoteUsername":"CloudFirst","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
乔恩
秩
UserLevel 6
徽章 +29
Windows 2016尚未得到支持，我们仍在研究详细信息。



一旦完成了我们需要做的事情，我们就会通过基础支持这样做，因此该过程将与基础现场安装指南保持一致。



乔恩
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

\n

\nOnce we're done with what we need to do on our side, we'd support doing this through Foundation, so the process would be aligned with the field installation guide for Foundation.

\n

\nJon","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
C
徽章 +1
嗨，乔恩，



感谢你的及时回复。



听起来对我的团队不利。



当我阅读兼容性指南时，我可以看到：




  • Microsoft Major/Minor版本（如2012 R2）得到了立即支持，质量保证在软件发布日期后的90天内有资格


Windows Server 2016 RTM已发布Oct12，是10月12日 + 3个月？

您认为2017年1月会很好吗？



如果您有有关时间表的任何信息，我得到了:)



非常感谢乔恩



祝你今天过得愉快。

问候。

\n

\nThanks for your prompt reply.

\n

\nSounds Bad for my team.

\n

\nWhen i read compatibility guide i can see :

\n

\n

    \n
  • Microsoft major\/minor releases (like 2012 R2) are Supported immediately and QA qualified within 90 days of the software GA release date<\/ul>

    \nWindows server 2016 RTM has released oct12 , it's oct 12 + 3 month ?

    \nYou think it will be good in January 2017 ?

    \n

    \nIf you have any information about timeline i got it :)

    \n

    \nThanks you so much Jon

    \n

    \nHave a nice day.

    \nRegards.","quoteUsername":"CloudFirst","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
乔恩
秩
UserLevel 6
徽章 +29
请记住，Windows 2016通常是一个很大的更新，并且在架构上进行了许多更改（例如Nano等）。



一般的想法是，我们将尝试在最初的90天内进行技术预览，以便人们可以在非生产设置中开始使用它。全部支持可能需要花费更长的时间，仅仅是因为我们想为生产设置做正确的选择，而不是赶其。



这种思想与我们要交谈的大多数客户也是如此，因为其余的生态系统都不匆忙（例如备份供应商，抗病毒，监测剂和其他相关代理商）需要先赶上。
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

\n

\nThe general thinking is we're going to try to get a Tech Preview out in the first 90 days, so people can start using it in non-production settings. Full support may take a little longer than that, simply because we want to get it right for production setups, rather than rush it in.

\n

\nThis line of thought lines up with what most customers we talk to want to do as well, they aren't in a rush because of all of the rest of their ecosystem (like backup vendors, anti virus, monitoring agents, and other related agents) needs to catch up first.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
A
徽章 +7
当Asterix 5.0可用时，我们是否有时间范围？

它是否具有Hyper-V的任何修复程序



如果我们现在要在3个节点群集上部署2012R2，我们是否可以通过从群集中提取节点，重新成像到2016年并再次加入群集来升级到2016年？

\ndoes it has any fixes for Hyper-V

\n

\nIf we were to deploy 2012R2 now on a 3 nodes cluster, will we be able to upgrade to 2016 by pulling a node from the cluster, re-imaging to 2016 and joining back the cluster again?","quoteUsername":"alexxdavid","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
乔恩
秩
UserLevel 6
徽章 +29
RE Hyper V升级

TBD，我会在他们的最初2美分的情况下向工程询问



重新Asterix发布日期

十个目标是接下来的30天或更短。我的感觉是，这将是“青少年”名称的一天，但仍然是TBD。它是一个大型，大的发行版，因此有很多非工程作品需要同时排队。



重新修复了Hyper-V

与任何版本一样，我们一直在修复和增强事物，您是否想要针对Hyper-V进行固定/增强的特定内容？
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
RE Hyper V upgrade<\/b>

\nTBD, I'll ask engineering on their initial 2 cents about this

\n

\nRE Asterix Release Date<\/b>

\nTenative target is the next 30 days or less. My feeling is that it will be a day with \"teen\" in the name, but still TBD. Its a big, big, big release, so theres lot of non-engineering stuff that needs to come in line at the same time.

\n

\nRE Fixes for Hyper-V<\/b>

\nAs with any release we're always fixing and enhancing things, is there something specific you're looking for to be fixed\/enhanced for Hyper-V?","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
A
徽章 +7
“ Tenative Target是接下来的30天或更短的目标。我的感觉是，这将是“少年”的“名字”，“

那是十一月的“青少年”还是十二月的“青少年”？



对于Hyper-V而言，除了Wodners，我们将如何通过3个节点群集升级到2016年。2016年具有滚动升级功能，但由于群集存储已经格式化，我们仍然会错过某些功能等功能。



http://myvirtualcloud.net/?p=8310

希望第2部分将具有一些特定于V的特定功能



我们还可以搬到AHV进行新的设置，但即使这样，我们也会为我们带来挑战：




  • 使用我们的Veeam备份服务器执行备份的能力
  • 使用我们的APC UPS干净地关闭服务器（仍然找不到一种简单而有记录的方法来从APC UPS中执行此操作）


一个3层的基础有缺点，但我看不出3个节点Nutanix群集将如何实现（实际上甚至有更多的节点）



现在，我们有3台服务器运行Hyper-V，在停电上，30分钟后，我们将Live Live从一台服务器迁移，然后将其关闭以给我们提供更多的运行时，再过30分钟后，发生相同的情况直到那里发生相同的情况仅剩20-30分钟，然后关闭所有VM，然后也关闭最后一个服务器。恢复电源后，所有服务器都会自动加电和重新平衡，而无需我ping服务器或存储。我认为使用CVM做这件事是自杀的...

\nIs that a November \"teen\" or a December \"teen\"?

\n

\nNothing in particular for hyper-v but wodnering how we will be able to upgrade to 2016 with a 3 node cluster. 2016 has a rolling upgrade feature but we would still be missing out on some features like REFS etc as the cluster storage would have already been formatted.

\n

\nhttp:\/\/myvirtualcloud.net\/?p=8310<\/a>

\nHoping that Part 2 will have some Hyper-V specific features

\n

\nWe could also move to AHV for our new setup but even that would create a challenge for us namely:

\n

\n
乔恩
秩
UserLevel 6
徽章 +29
重新Asterix日期

我看到你开了我的幽默笑话。在内部，我们正在瞄准11月的月份，但这是一个非常非常大的发行版，因此我们希望正确地进行。



Re Hyper-V 2016

我已经将其转发给我们的PM for Hyper-V，因此他可以更详细地回应CC雷蒙



这是我的2美分：请记住，Hyper-V 2016是Microsoft绝对庞大的新版本，从根本上讲，这将对Nutanix的整合方式有所不同。有很多事情要考虑；但是，最大的是Microsoft的DDA，这是他们的PCI PassThrough版本。



如您所知，Nutanix在ESXI，AHV和Xenserver上使用SAS控制器的直接PCI传递。Hyper-V在2012 R2中没有相同的功能，因此我们目前采用了另一种方法。多年来，我们一直在大声疾呼PCI传球，以标准化我们支持的所有四个恶棍之间的磁盘连接方法，而微软现在允许在2016年进行此操作。



也就是说，与ESXI和AHV不同，它不仅是一个简单的传递，还需要访客OS内核来支持启用DDA的设备，因此我们不得不修补这些设备，这需要一些资格时间。



这只是我们必须努力正确启用2016年的一个低悬挂示例。



重新使用特定功能

您在寻找具体的东西吗？还是要系统做今天不做的事情？我很乐意代表您调查或倡导，请告诉我。



re veeam + ahv

过去，我们谈到了这一点，球在Veeam的法庭上。



RE APC + AHV

APC需要做一些工作来增强其PowerChute网络关闭产品，这确实是这样做的最好方法。我会请我们的联盟人们看看我们是否已经与他们合作。



重新关闭序列

是的，对于Nutanix（或大多数SDS产品），这将是一个挑战关闭。
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
RE Asterix Date<\/b><\/u>

\nI see you caught my dry humor joke. Internally we're targetting the month of November, but this is a really, really big release, so we want to get it right.

\n

\nRE Hyper-V 2016<\/b><\/u>

\nI've forwarded this over to our PM for Hyper-V, so he can respond in more detail cc Raymon<\/a>

\n

\nHere's my 2 cents: Keep in mind that Hyper-V 2016 is an absolutely massive new release from Microsoft, which will fundamentally have different considerations for how Nutanix integrates. There are many things to consider; however, the largest is Microsoft's DDA, which is their version of PCI Passthrough.

\n

\nAs you might know, Nutanix uses direct PCI Passthrough of the SAS controller on ESXi, AHV, and XenServer. Hyper-V does not have this same capability in 2012 R2, so we take a different approach currently. We've been clamoring for PCI passthrough for years, to standardize the disk connectivity approach between all four hypervisors we support, and Microsoft is now allowing this in 2016.

\n

\nThat said, Unlike ESXi and AHV, it isn't just a simple passthrough, it requires guest OS kernel changes to support the DDA-enabled devices, so we've had to patch those in, which takes some qualification time.

\n

\nThat's just one low hanging example of what we've got to work through to get 2016 enabled correctly.

\n

\nRE Hyper-V specific features<\/b><\/u>

\nAre you looking for something specifically? Or wanting the system to do something it doesn't today? I'm happy to investigate or advocate on your behalf, just let me know.

\n

\nRE Veeam + AHV<\/b><\/u>

\nWe've talked about this in the past, the ball is in Veeam's court on this one.

\n

\nRE APC + AHV<\/b><\/u>

\nAPC would need to do work to enhance their PowerChute network shutdown product, that's really the best way to do that. I'll ask our alliances folks to see if we're working with them already.

\n

\nRE Shutdown sequence<\/b><\/u>

\nYes, that would be a challenge with Nutanix (or most SDS products), as in your 3 node cluster, its N+1, so you'd be able to do that with one node, then the whole thing would need to be gracefully shutdown.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
A
徽章 +7
你好乔恩



来自任何反馈雷蒙关于滚动集群升级？
乔恩
秩
UserLevel 6
徽章 +29
我给他和PM团队发送了一封电子邮件，以对此进行一些澄清。我敢打赌，“是”，但是再次，这是微软的大规模大规模转变，我觉得这将很棘手。期待工程的发展。
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
乔恩
秩
UserLevel 6
徽章 +29
产品管理中的消息是，是的，这是支持2012年至2016年滚动升级的计划。由于该功能尚未完成，我们必须等待一点才能确切地查看它的外观
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
Jefflongley
UserLevel 2
徽章 +5
只是将我的名字添加到渴望看到这一点的人列表中；我一直坚持实施我们的新障碍，因为我很快就会获得2016年“从开始”，而不是稍后升级该块。
A
徽章 +7
我也是！

尤其是如果必须将容器格式化为“一开始”的参考！我认为不可能从NTFS升级到REF，而不会销毁群集，因此我们为什么也在等待。



现在，如果AHV得到Veeam的支持，我们将不会等待

\nEspecially if the container has to be formatted as REFS from the get go! I don't think it will be possible to upgrade from NTFS to REFS without destroying the cluster first hence why we are waiting as well.

\n

\nNow if AHV had VEEAM support we wouldn't be waiting 😛","quoteUsername":"alexxdavid","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
乔恩
秩
UserLevel 6
徽章 +29
重新文件系统

嗯，什么？该容器现在不使用NTF格式化，也不是任何其他Windows文件系统，因此即使我们愿意，我们也无法使用Refs格式化。



从协议的角度，使用SMB3呈现容器。文件系统上的实际格式是Windows的。



就像从运行XFS或ZFS文件系统的Linux框或类似的内容中进行SMB共享，​​协议和基础文件系统不会耦合在一起。



恢复

您的句子相反...更像Veeam获得了AHV的支持，让您阅读您的内容。简而言之，我们在等他们，而不是相反。
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
RE File system<\/b><\/u>

\neh, what? The container is not formatted with NTFS now, nor any other windows file system, so we couldn't format it with REFS even if we wanted to.

\n

\nThe container is presented, from a protocol perspective, with SMB3. The actual formatting on the filesystem is invisable to windows.

\n

\nMuch like doing a SMB share from a linux box running a XFS or ZFS file system, or ext or something like that, the protocol and the underlying file system are not coupled together.

\n

\nRE Veeam<\/b><\/u>

\nYou've got that sentence in reverse ... more like if Veeam had AHV support, and let you read into that what you will. Very simply put, we're waiting on them, not the other way around.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
A
徽章 +7
理解！我认为该容器是作为存储到Windows群集的存储空间的，我们需要将其格式化！这是有道理的，只要Nutanix将支持集群升级升级，那么我们就不必再等待时间并部署2012 R2并升级了。如果我们这样做，与2016年完整安装相比，我们会缺少从升级到2012 R2的任何功能吗？
乔恩
秩
UserLevel 6
徽章 +29
它作为存储群呈现给群集，但其SMB3卷，而不是需要格式化的块设备。



至于升级等，尚未定义，我们知道我们要支持滚动升级，但是正如我在先前的一篇文章中提到的那样，我们尚未完成2016年的工作，因此我们将有更多的清晰度去那里。
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

\n

\nAs far as upgrades and such, thats not defined yet, we know we want to support rolling upgrades, but as I mentioned in a prior post, we haven't completed the work on 2016 yet, so we'll have more clarity as time goes on there.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Mikasa
徽章 +1
任何进度有任何更新吗？现在几乎没有90天的商标。
乔恩
秩
UserLevel 6
徽章 +29
Mikasa- 感谢您伸出援手，对您就可以了。



这仍然是一项正在进行的工作。微软改变了我们需要处理的一吨，因此我们花时间做对了。





与您的Nutanix帐户团队合作，以获取何时将其投射到降落的详细信息，但是在这个公共论坛中，我会简单地说，我们正在努力，试图将其推开，至少在Tech上至少在日历Q1 2017年结束时预览。所有日期都可能会根据内部进度进行更改，但以这种方式看起来。
乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
Mikasa<\/a> - Thanks for reaching out, right you are.

\n

\nThis is still a work in progress. Microsoft's changed a TON that we need to deal with, so we're taking the time to do it right.

\n

\n

\nWork with your Nutanix account team to get the forward looking details on when we project this to land, but in this public forum I'll simply say, we're working on this, trying to get this off the ground, at least in tech preview at minimum, by end of calendar Q1 2017. All dates subject to change based on internal progress, but its looking that way.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +1
关于支持性的任何更新此线程吗？
l
徽章 +2
我们很想在Nutanix平台上看到Hyper-V 2016。这是通知更新 /跟踪进度的最佳地方吗？
d
徽章 +1
支持Hyper-V 2016和Windows Server 2016的任何更新？如果说Hyper-V我们仍然继续使用2012版，我们可以将客户端作为MS Windows 2016吗？
Mikasa
徽章 +1
Desmondgooi这是我们目前的设置2012R2管理程序，除了SCVMM之外的所有内容，还需要2012年的时间，以与Nutanix平台一起播放。运行完美。



由于缺乏有关2016年管理程序支持的更新而感到非常失望。我们的目标是从2016年开始，因为我们在购买时愚蠢地呆在90天的声明中。
desmondgooi<\/a> This is our current setup, 2012r2 hypervisors with '16 on everything apart from SCVMM that also requers 2012 to play nice with the Nutanix platform. Runs perfectly.

\n

\nVery disapointed with the lack of updates regarding the 2016 Hypervisor support. We'd aimed to be up on 2016 from the get go as we foolishly belived the 90day statement when making the purchase.","quoteUsername":"Mikasa","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu