hyper - v 2016

一个
徽章 ＋７
Hyper-V 2016什么时候可以兼容?

    43个回复

    乔恩
    排名
    Userlevel 6
    徽章 + 29
    我们的通用hypervisor支持政策如下:

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

    TLDR -从GA开始90天
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    一个
    徽章 + 9
    嗨,约翰,

    你是否有关于升级过程的信息?我们看到的是一个相当简单的一键点击吗?另外，我们可以使用Nano-server吗?如果可以的话，这个过程和普通的一键升级是一样的吗?

    亲切的问候
    \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发布的产品一旦进入GA。
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    C
    徽章 ＋1
    你好,
    你好乔恩,

    关于Windows server 2016 RTM的集群安装有任何更新吗?
    我们有一个NX-3000，我们想重新安装一个集群与最后的windows服务器操作系统。

    能给我们一些关于新安装的文档吗?
    一个fter 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，我们仍在研究细节。

    一旦我们完成了我们这边需要做的事情，我们将通过基金会来支持这样做，所以这个过程将与基金会的现场安装指南保持一致。

    乔恩
    JonKohler |技术总监，工程，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
    嗨,乔恩,

    感谢您的及时回复。

    听起来对我的团队不利。

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

    • 微软的主要/次要版本(如2012 R2)立即得到支持，并在软件GA发布日90天内通过QA认证

    Windows server 2016 RTM已经发布了10月12日，是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总的来说是一个很大的更新，在架构上有很多变化(比如纳米等)。

    一般的想法是，我们将尝试在前90天推出技术预览，这样人们就可以开始在非生产环境中使用它。完全支持可能需要更长的时间，只是因为我们想让它正确的生产设置，而不是匆忙。

    这一思路也符合我们所说的大多数客户想要做的事情，他们并不着急，因为他们生态系统的其他部分(如备份供应商、反病毒、监控代理和其他相关代理)需要首先赶上来。
    JonKohler |技术总监，工程，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"}}}">
    一个
    徽章 ＋７
    我们有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升级
    待定，我会问一下工程师关于他们最初的2分

    RE Asterix发布日期
    暂定目标是未来30天或更短的时间内。我的感觉是有一天会有“青少年”在名字里，但仍然待定。这是一个非常、非常、非常重要的发布，因此有很多非工程的东西需要同时上线。

    RE修复Hyper-V
    和任何版本一样，我们总是在修复和增强一些东西，有没有什么特定的东西，你正在寻找修复/增强Hyper-V?
    JonKohler |技术总监，工程，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"}}}">
    一个
    徽章 ＋７
    暂定目标是未来30天或更短的时间内。我的感觉是，将来会有一天名字里会有“青少年”这个词，
    那是十一月的"teen"还是十二月的"teen"?

    对于hyper-v来说没有什么特别的，只是想知道我们将如何用3节点集群升级到2016年。2016年有一个滚动升级的特性，但是我们仍然会错过一些特性，比如REFS等，因为集群存储已经被格式化了。

    http://myvirtualcloud.net/?p=8310
    希望第2部分会有一些Hyper-V特有的特性

    我们也可以移动到AHV为我们的新设置，但即使这样也会为我们创造一个挑战，即:

    • 使用我们的VEEAM备份服务器执行备份的能力
    • 使用我们的APC UPS干净地关闭服务器(仍然没有找到一个简单的和文档化的方法从APC UPS做到这一点)

    一个3层的基础设施有它的缺点，但我看不出这是如何与一个3节点的nutanix集群(实际上甚至有更多的节点)

    现在我们有3个服务器运行hyper - v和停电,30分钟后,我们的生活从一台服务器迁移所有虚拟机,然后关闭它给我们更多的运行时,另一个30分钟后,同样的情形发生,直到只剩下20 - 30分钟,然后所有的虚拟机都关闭,最后服务器是关闭。当电源恢复时，所有服务器将自动上电并重新平衡，而无需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
    是阿斯泰里克斯日期
    看来你听懂我的冷幽默了。在内部，我们的目标是11月，但这是一个非常非常重要的发布，所以我们希望它是正确的。

    再保险hyper - v 2016
    我已经把这个转发给我们Hyper-V的PM，这样他可以回复更详细的抄送Raymon

    以下是我的两点意见:记住Hyper-V 2016是一个绝对巨大的新发布来自微软，这将从根本上对Nutanix如何集成有不同的考虑。有很多事情需要考虑;然而，最大的是微软的DDA，这是他们版本的PCI Passthrough。

    您可能知道，Nutanix使用ESXi、AHV和XenServer上的SAS控制器的直接PCI Passthrough。Hyper-V在2012 R2中没有这个功能，所以我们目前采取了不同的方法。多年来，我们一直在呼吁PCI直通，以标准化我们支持的所有四个hypervisor之间的磁盘连接方法，而微软现在在2016年允许了这一点。

    也就是说，不像ESXi和AHV，它不仅仅是一个简单的直通，它需要客户OS内核的更改来支持dda支持的设备，所以我们不得不修补这些，这需要一些时间。

    这只是一个很简单的例子，说明我们要让2016年正常运转，还需要做些什么。

    RE Hyper-V特定功能
    你在找什么特别的东西吗?或者希望系统做一些它今天没有做的事情?我很乐意为你调查或辩护，请告诉我。

    RE Veeam + AHV
    我们以前讨论过这个问题，这次是维姆的问题。

    4 . Re apc + ahv
    APC需要改进他们的PowerChute网络关闭产品，这是最好的方法。我将询问我们的盟友，看看我们是否已经在与他们合作。

    重新关闭序列
    是的，对于Nutanix(或大多数SDS产品)来说，这是一个挑战，因为在您的3个节点集群中，它是N+1，所以您可以用一个节点做到这一点，然后需要优雅地关闭整个系统。
    JonKohler |技术总监，工程，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"}}}">
    一个
    徽章 ＋７
    嗨乔恩

    任何的反馈Raymon关于集群滚动升级?
    乔恩
    排名
    Userlevel 6
    徽章 + 29
    我给他和项目经理团队发了一封电子邮件，以澄清这一点。我敢打赌“是的”，但是，这是微软的一个巨大的巨大的转变，我有一种感觉，这将是棘手的。期待工程部的成果。
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    乔恩
    排名
    Userlevel 6
    徽章 + 29
    来自产品管理部门的消息是，是的，这是支持从2012年到2016年滚动升级的计划。因为这个功能还没有完成，我们还需要等待一段时间才能看到它到底是什么样子
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    JeffLongley
    Userlevel 2
    徽章 ＋5
    只是把我的名字加到渴望看到这个的人的名单里;我一直在推迟执行我们的新区块，因为我宁愿“从一开始”就在2016年，而不是在晚些时候升级区块。
    一个
    徽章 ＋７
    我也是!
    特别是当容器必须从一开始就被格式化为REFS的时候!我认为如果不先摧毁集群，从NTFS升级到REFS是不可能的，因此我们也在等待。

    如果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
    是文件系统
    呃,什么?容器现在不是用NTFS格式化的，也不是任何其他的windows文件系统，所以即使我们想要，也不能用REFS格式化它。

    从协议的角度介绍了SMB3的容器。文件系统上的实际格式化对窗口是不可见的。

    就像从运行XFS或ZFS文件系统或ext之类的linux机器上进行SMB共享一样，协议和底层文件系统并没有耦合在一起。

    再保险Veeam
    你把这句话写反了…更像是Veeam有AHV的支持，让你去理解你想要的。简单地说，是我们在等他们，而不是他们在等我们。
    JonKohler |技术总监，工程，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"}}}">
    一个
    徽章 ＋７
    理解!我认为这个容器是作为存储呈现给Windows集群的，我们需要格式化它!这是有道理的，只要Nutanix支持集群滚动升级，那么我们就不必再等待更多的时间，部署2012 R2并在之后进行升级。如果我们这样做，从升级到2012 r2，与完整安装的2016 r2相比，我们会错过任何功能吗?
    乔恩
    排名
    Userlevel 6
    徽章 + 29
    它作为存储呈现给集群，但是它的SMB3卷，而不是需要格式化的块设备。

    至于升级之类的，这还没有定义，我们知道我们想要支持滚动升级，但正如我在之前的帖子中提到的，我们还没有完成2016年的工作，所以随着时间的推移，我们会有更多的明确。
    JonKohler |技术总监，工程，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-谢谢你的帮助，没错。

    这项工作仍在进行中。微软改变了我们需要处理的一个TON，所以我们正在花时间做正确的事情。


    与Nutanix帐户团队工作的前瞻性细节当我们项目土地,但在这个公共论坛我就简单地说,我们正在努力,试图让这个离地面,至少在技术预览版至少年底日历2017年一季度。所有的日期都可能根据内部进展而改变，但它看起来是这样的。
    JonKohler |技术总监，工程，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
    徽章 ＋２
    我们也希望Hyper-V 2016能够出现在Nutanix平台上。这是通知更新/跟踪进度的最佳地点吗?
    D
    徽章 ＋1
    支持Hyper-V 2016和Windows Server 2016的任何更新?如果让我们说hyper-v，我们仍然使用2012版本，我们能把客户端作为MS windows 2016吗?
    Mikasa
    徽章 ＋1
    desmondgooi这是我们当前的设置，除了要求2012年与Nutanix平台兼容的SCVMM之外，所有配置都带有'16 '的2012r2虚拟机管理程序。完美运行。

    对2016 Hypervisor支持缺乏更新感到非常失望。我们的目标是从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"}}}">

    回复


    Baidu