The RC1 of VMware Server v2.0 is now out and available, and the product keeps getting more impressive with each pre-release iteration. I already discussed here some of the new features that arrive with the RC1 release. But there is one in particular that stands out a truly impressive.

• VSS support for in-VM quiescing. First and foremost, this has been the "holy grail" for backups for a long time. Being able to leverage the in-VM VSS provider to quiesce the virtual machine before taking a VM-level backup means that your Exchange/SQL/AD databases and others of a transactional nature will return from a restore in good shape. This is new technology that we're starting to see across the board as critical for snapping backups of these key servers without being forced to use in-VM backup software. Keep an eye on this (and in the ESX product as well as other platforms) as a key feature needed by all environments.

The web-based interface gets a bit smarter with this release as well. Although I yet remain a bigger fan of the client-based application used with the previous release, the web-based tool gets a bit faster, renders more appropriately, and best of all in this release uses the VMware Remote Console as an out-of-band app (i.e. not within the web page).

The other new features will be useful for you, depending on what you need to accomplish with them. Support for SCSI pass-through means that generic devices like tape backups can be pulled into the virtual machine, but there doesn't appear to be direct LUN access into the VM just yet. VM Communication Interface support, which I'll admit is a feature I don't yet understand from a technical perspective, appears to provide faster inter-VM communication, which is an incentive to increasing your percentage of virtualized computers. USB 2.0 is now supported, as is greater level of permissioning and role-based access.

I use the Linux version of VMware Server, running atop Red Hat, and have been for years now. I find it to be a lot faster than the version that runs atop a full Microsoft server installation. So, I can't comment on how things have changed for the Microsoft version.

But, for those that run the Linux version, or are considering moving to this product, seriously give Linux a consideration. VMware's installer for Linux is just fantastic, and the upgrade process is effectively transparent. Being not a Linux expert (I dabble), I've found the experience to be well worth the effort.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (4) | TrackBacks (0)

Its all over the news wire, so you've probably caught this info already elsewhere. But, I did just get off the horn with an insider buddy of mine with some added information. According to some of the digging done by my source, although the timing of the firing seems strange -- it was done essentially during Microsoft's Worldwide Partner Conference -- there doesn't appear to be any linkages between the two.

As mentioned in Keith Ward's (from Virtualization Review) excellent analysis here, I think VMware's been experiencing a positioning problem that gets suddenly more tenuous with the release of Hyper-V:

It should be a very interesting earnings call on July 22, when Maritz will talk with journalists and analysts for the first time as president of VMware. I wouldn't be surprised if he announces price cuts across the board for VMware products, as that is the chief complaint about VMware.

As I've already mentioned in my post here, VMware's excessive hypervisor price is in need of coming down with the market pressure Microsoft is bringing to bear. My advice in that post that's worth repeating is to be careful with any virtualization purchases over the next 12-24 months. You might find the end of this phase in the game with some very different pricing structures.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

Peter Bruzzese over at InfoWorld interviewed me recently to talk about the differences between Microsoft's now-released Hyper-V and the long-standing ESX virtualization product from VMware. I'm an unabashed fan of Hyper-V from the perspective of economics, so my thoughts on each product's TCO are exposed in this article.

Specifically, Peter asked Microsoft's group product manager Patrick O'Rourke as well as myself to respond to a comment from Sun's Senior Director of xVM Vijay Sarathy. One of those responses I find particularly interesting:

Hyper-V only addresses Windows-based servers despite the fact that most datacenters are incredibly heterogeneous and require support for more than just Windows workloads. Aren't you underestimating the complexity and diversity of your customers' datacenters?

O'Rourke: No we're not. Our customers make sure we know their datacenter needs and provide us input on how we can help. So far they're telling us Windows Server 2008 has been a big help. As for Windows Server 2008 Hyper-V, it allows customers to consolidate applications running Novell SLES 10. As for Red Hat, Microsoft and Red Hat both realize the importance of virtualization and interoperability needs of our joint customers, and we are actively discussing how to support Red Hat Enterprise Linux on Windows Server 2008 Hyper-V.

Shields: Hyper-V doesn't address only Windows-based VMs. It supports SLES as well. Microsoft's support for additional Linux OSes is muted because Microsoft hasn't seen the demand for it. They're demanding a rock-stable virtualization platform that supports some of their workloads. Why do a poor job being all things to everyone when you can do a great job fixing a specific market segment?

Going along this road further, SCVMM [System Center Virtual Machine Manager] includes support for managing the Xens and ESXs of the world. Let those virtualization platforms do the oddball OS virtualizing, and let Microsoft handle its own product stable.

Although I was later corrected in the comments that SCVMM will not support Xen with this release, I find it interesting that large numbers of people still see heterogeneity as a major factor in deciding on a virtualization platform. And yet, the vast majority of virtualized environments are mostly homogeneous (and I'm not just saying Windows here).

Let me ask you the question: For the servers you plan to virtualize or have already virtualized, what percentage of each OS are they made up of? Mostly Microsoft? Mostly Linux? Or, evenly distributed?

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

BUMPED: With the release of VMware Server 2.0 RC, I figured it useful to bump this post from early in the year. If you download the RC and plan to use it for hosting virtual machines, you'll want to disable debugging so that the VMs operate with decent speed.

By default with VMware Server 2.0 Beta, debugging mode is enabled for all hosted virtual machines. This has been the case with every VMware beta product that I can remember. The problem with debugging mode is that it significantly slows down the performance of all on-board virtual machines so much as to make them unusable.

This time, however, there is no easy way to disable it. However, I have found the following workaround for users who host VMware Server on Linux...

 
Continue reading BUMPED: Disabling Debugging in VMware Server 2.0 Beta RC...

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (3) | TrackBacks (0)

I received an email last night from VMware announcing that the bits for VMware Server RC1 should be posted to www.vmware.com some time today. New features that you can expect to see with RC1 are:

• Volume Shadow Copy Service (VSS): Properly backup the state of the Windows virtual machines when using the snapshot feature to maintain data integrity of the applications running inside the virtual machine.
• Virtual Machine Communication Interface (VMCI): Support for fast and efficient communication between a virtual machine and the host operating system and between two or more virtual machines on the same host.
• Support for SCSI pass-through (generic) devices: Allows for SCSI devices such as tape backup devices to be connected to virtual machines.
• Expand disk capacity on the fly: Allows for adding new SCSI hard disks and controllers to a running virtual machine.
• Firefox 3 as a supported browser for the management interface.
• Remote Client Devices: Access devices such as CD-ROMs that are not physically connected to the host via VMware Remote Console

I don't know about you, but I've been waiting for this update for a while.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

Microsoft has given me the OK to announce that Hyper-V officially releases today! It'll take a while for Microsoft to get the bits up on the web site, but for now you can grab all the information you need to prepare at this web site.

Here's what you can expect to be new and improved in RTM over RC1:

• Improvements in performance.
• Improvements in networking features.
• Improved guest support for Windows XP SP2, Vista x64, and SMP installations of many OSs.

The above improvements are worded softly for now, but what should strike you as an interesting proof of concept is that IIS servers for the MSDN and TechNet sites have both been running off of Hyper-V for an extended period of time. So, if you've been using MSDN and TechNet for the past few weeks, then you're interacting with Hyper-V hosted workloads.

More information on the downloads as I get it...

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

You've heard me pontificate before on what I see as the impending commoditization of hypervisors across all vendors. VMware's first-mover advantage gained them a number of years of hyper-profit before second-movers like Citrix and Microsoft began making their way into the market. The most impending movement about to occur is Microsoft's dropping of Hyper-V into the playing field for the low cost of $28.

(Actually, one could argue that their cost for the hypervisor is effectively "free", since the regular editions of Windows Server 2008 include it. The "w/o Hyper-V" editions are technically priced at around $28 less)

Chris Wolf continues down this line of thinking with an article and accompanying video over at SearchServerVirtualization.com where he develops an even stronger argument. He writes:

In the near term, I expect all vendors, including VMware, to offer free versions of their hypervisors. If you think hell will freeze over before VMware offers a free version of ESX Server, think again. Sure, there isn't a hypervisor today that matches ESX feature for feature, but the alternatives don't have to. In many cases, a hypervisor that is just "good enough" for a particular task and less expensive will win out, especially for less-critical workloads. Whether they want to admit it publicly or not, all hypervisor vendors realize that developing best-in-class management is key to winning the hypervisor war. Indeed, regardless of their unique intrinsic value, hypervisors are becoming commoditized.

But there's more to this argument than just seeing into the future. Chris continues his discussion with a very important suggestion to organizations considering a move to virtualization: Prepare financially for the change. If the price of hypervisors is due to decrease, then you and your organization shouldn't consider full cost as an option for software purchase. Chris continues:

With hypervisor prices expected to drop, don't lock your organization into a lengthy licensing deal. What could look like a steal today could easily be viewed as a ripoff in a few months. By 2009 several major vendors will ship enterprise-ready hypervisors; locking yourself into a licensing contract beyond 2009 will likely result in a lost opportunity for significant savings.

Chris suggests that discounts of 20% to 50% on today's hypervisor purchases - especially large purchases with with long-term committments - shouldn't be considered inappropriate. If you're about to lock-in to a virtualization platform in the near term, you don't want to be caught holding the bag with an expensive solution that others paid pennies on the dollar because they waited.

Or, alternatively, consider waiting for Microsoft's solution to arrive in the next few months. Even Microsoft doesn't consider Hyper-V to be the highest-end solution for all workloads. But it does position the product as a lesser-cost solutionf for 2nd and 3rd tier servers with lower expectations of uptime (think WSUS servers, SCCM servers, other infrastructure servers that can afford to go down from time to time).

Ultimately, the moral here is: Be smart with any virtualization platform purchases over the next 12-24 months.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

Keith over at Virtualization Review posted some thoughts about a new revelation that I think we didn't know about Hyper-V. Namely, the knowledge that Hyper-V as of now doesn't support NIC teaming.

He points to a comment from Scott Lowe, who believes this to be a major problem with Hyper-V. Though, I think I disagree. Microsoft is not positioning Hyper-V to be a top-end virtualization solution. There's proof of this in how Microsoft positions System Center Virtual Machine Manager. SCVMM is designed to work with all the major forms of virtualization (Hyper-V, ESX, Xen, etc), and Microsoft is telling people overtly that they should leave their workloads of highest criticality on an enterprise platform like ESX. But what they're also saying is that for low-risk workloads, use Hyper-V -- because its cheaper.

Considering this, do we really care that Hyper-V doesn't support NIC teaming? I seem to think not. NIC teaming in my history has always caused more problems than it solved, breaking more network connections than it saved. And today's network cards, especially those on server class systems, are exceptionally resilient.

What are your opinions? Do we need it? Is this a critical omission? Or, will you be moving to Hyper-V anyway?

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (6) | TrackBacks (0)

Tom Valovic over at Virtualization Review magazine pens an interesting (albeit short) comment about VMware's current positioning and how it resembles that of previous notorious companies like WordPerfect Banyan, and DEC. What he's trying to get across through a comment he presents is that:

I realize that it's a tradition in the computer industry, but I find it a little disappointing to see virtualisation giant VMware following the same competitive marketing obsession that made industry powerhouses of Banyan Systems, WordPerfect, Digital Equipment and Novell. Each of those companies, at one time, were considered absolutely dominant in their own markets and gradually lost those positions partially by focusing on the elegant engineering of their original product set and failing to recognise the point at which customers began to take that function for granted.

This comment initially came from Kevin Fogarty over at Computerworld, specifically from this post. Although this is my impression entirely, I feel somewhat similar in what I see coming out of VMware's product stable of late. Namely, too much money for products that have rough equivalents now available for a significantly lower price point.

I've talked a lot before about what I call "the commoditization of virtualization", the process whereby those companies with the second-mover's advantage bring about sufficient alternate products to market that drives down the price. The most specific of these is Hyper-V, soon to release from Microsoft. It is the impression of this blogger, especially after hearing what I've heard out of Tech Ed last week, that Hyper-V's technology and price point are about to be a significant problem for VMware upon release.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

With Hyper-V's final release soon upon us, you might consider keeping up to date on all the virtualization news that relates to Microsoft you can. In support of that, Microsoft now releases a monthly newsletter on virtualization topics to which you can subscribe from this link.

The newsletter intends to discuss...

"...the latest headlines related to virtualization and highlight the benefits of this hot technology. Great newsletter features will include columns and blog entries by our team of Microsoft virtualization experts, showcase of customers success stories, spotlight on virtualization solutions and scenarios... and will provide our readers with a wealth of virtualization resources."

I signed up for my copy today.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

I was interviewed not long ago by Amy Kucharik over at SearchNetworking.com about my recent book The Shortcut Guide to Selecting the Right Virtualization Solution, which you can freely download from Parallels.

In that interview, we talk about the types of virtualization available today, how virtualization impactst the typical IT network environment, and some elements you should consider when you're thinking about making the jump.

The whole interview turned out really well, but there are two questions that really strike me:

Do you see any one type of virtualization as more interesting or useful than the others?

Shields: Actually two I see are where we're going. First, paravirtualization, like what we see in Hyper-V and Xen, as well as early experimental support in ESX 3.5, is where we're going. The early types of hardware virtualization that used emulation had to do so because of paravirtualization's need for OS recompilation and/or on-board hardware extensions. These capabilities are now becoming pervasive, so I see emulation going away in the long run because of its now-unnecessary levels of resource overhead. The other nifty tech that I think gets too little press is OS virtualization, typified by Parallels Virtuozzo Containers. This is great tech with an exceptionally small overhead and some very specific benefits that you don't get anywhere else. If you haven't heard of Virtuozzo or OS virtualization, definitely check out the book, as it talks about some of those benefits in detail.

One of the goals of your book is to help readers understand where they will and won't get the best return on a virtualization investment. Are there particular places where you would caution against using virtualization?

Shields: Big one: Don't implement highest-end virtualization solutions when you don't need to. Some virtualization solutions have very high-end platforms that appear to solve all the world's IT problems. But they're also stupendously expensive. If you don't need the uptime or the super-high reliability, then you may not need to spend the extra cash. Also, beware the market effects of virtualization commoditization. We're only now starting to see enough quality entrants into the virtualization ecosystem that market forces will begin driving down the prices. Those early adopters are the ones most likely to see problems with this. Be aware of the impending commodity status of virtualization platforms, and consider your purchase carefully.

Read the full interview at: http://searchnetworking.techtarget.com/news/interview/0,289202,sid7_gci1313304,00.html#

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

Back in the early days of virtualization (and probably still today) consultancies everywhere would sell you a package whereby they'd tell you which of your servers would make good virtualization candidates and which would not.

What they didn't tell you was that those services mainly used free tools -- like PerfMon -- that you already had at your disposal. Nowadays, we know more about virtualization and what types of performance characteristics make good candidates (rather than just saying "Terminal Servers won't work"). You just need to know what those PerfMon characteristics are.

Microsoft helps the process by providing a three-step process to assist you with understandinging and determining virtualization candidates. The process is pretty easy:

1. Server Inventory - collect information regarding all existing servers across your network
2. PerfMon Capture - capture performance counters including CPU, Disk and Network Utilization of each server that you want to consider virtualizing (note: we recommend you run this for at least a few days if not a few weeks so you can capture all the "peaks and valleys" of utilization)
3. Virtualization Candidates Reporting - generate a report with virtualization candidacy recommendations

Even better, they provide the tools to make all of this extremely easy. Just install, run, and go. Learn more about the MAP (Microsoft Assessment and Planning) tool at this web site: http://blogs.technet.com/mapblog/archive/2008/04/23/how-to-series-for-microsoft-assessment-and-planning-part-1-server-virtualization.aspx

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

If you're further along with your virtualization deployment than with just the MAP, you may be interested in knowing about Microsoft's Virtualization Cookbooks. These cookbooks provide a step-by-step approach for configuring virtualization for numerous architectures. You can get them all from: http://www.microsoft.com/downloads/details.aspx?FamilyID=1dba286b-9ec9-4a6c-b682-823affcd5a1b&DisplayLang=en

Here's the list:

• Backup and Recovery using Microsoft Virtual Server 2005 R2 Service Pack 1 and Acronis True Image 9.1 Enterprise Edition
• Deployment Cookbook: Branch Office--Microsoft System Center Virtual Machine Manager Microsoft Virtual Server 2005 R2 Service Pack 1
• Deployment Cookbook: High Availability with Virtual Server Host Clustering
• Deployment Cookbook: Hosted Backup--Microsoft System Center Data Protection Manager 2007 and Microsoft Virtual Server 2005 R2 Service Pack 1
• Deployment Cookbook: Offsite Backup--Microsoft System Center Data Protection Manager 2007 and Microsoft Virtual Server 2005 R2 Service Pack 1
• Deployment Cookbook: Onsite Backup--Microsoft System Center Data Protection Manager 2007 and Microsoft Virtual Server 2005 R2 Service Pack 1
• Microsoft System Center Data Protection Manager 2007, Microsoft Virtual Server 2005 R2 Service Pack 1, and Microsoft System Center Virtual Machine Manager
• Microsoft Virtual Server 2005 R2 Service Pack 1 and Microsoft System Center Virtual Machine Manager
• Mobile User Access of Applications. Terminal Server running on virtual machines using Microsoft Virtual Server 2005 R2 Service Pack 1
• Quick Migration with Virtual Server Host Clustering Windows Server 2003 Enterprise Edition & Microsoft Virtual Server 2005 R2 Service Pack 1

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

VizionCore announced last week the first enterprise-class performance monitoring solution designed specifically for large virtualization deployments. If you're a user of VMware's VirtualCenter, you know that it includes nominal performance monitoring tools within the Virtual Infrastructure Client. But for large deployments, you also know that those tools are limited in the scope of what they can provide you.

VizionCore's vCharter Pro toolset assists greatly with the process of watching, alerting, and actioning on performance conditions within your virtual machines. Specifically, it enables:

• Single web-based "pane-of-glass" view shows activity and performance at the VirtualCenter, data center, resource pool, cluster, ESX Server, virtual machine and storage levels
• Scales to support thousands of virtual machines and multiple VirtualCenter deployments
• Automated alarms and alerts on performance issues and potential bottlenecks
• "Understands" components of the VMware platform and can "roll-up" problems at lower levels into higher-level alarms
• Datastore predictive monitoring helps determine when more storage will be required
• "Raw" metrics can be combined into "derived" metrics for higher-level information
• Database of metrics provide historical trending.
• Vizioncore vCharter Pro is available immediately from Vizioncore's worldwide channel partner network.

Read more at: http://www.vizioncore.com/vCharterPro/

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

From Systems Management News:

A recent Microsoft study shows that retail environments are starting to make the push into virtualization as well. These are traditionally slow-moving markets due to their extended reach (everybody's a remote site!). So, seeing this move on their part illustrates where we are in the virtualization adoption curve. Space and cost are big drivers here. From the survey:

The survey found that nearly half of the participating retailers (49 percent) are using virtualization within their store locations to help them save money, while 46 percent are using it to better respond to issues and failures of applications and systems, and 43 percent said virtualization helps them save space. Energy savings were also a factor--31 percent of respondents cited green incentives as driving their purchase of virtualization technology.

According to Geoff Thomas, general manager of Microsoft's U.S. Retail and Hospitality Group, for large retail chains, adding just one more server or application per store can be costly. "That is why virtualization is an attractive alternative, as more than 50 percent of retailers surveyed had between three and 10 servers in each of their stores already," he said.

Among the 29 percent of respondents who are not using virtualization, one quarter (25 percent) said their company is considering it. Among those not considering implementing virtualization technologies, more than half said the main reason is cost.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

Its been a while since I've blogged about BlueLane's neat concept in virtual security. So, when last week I received a press release about their v4.2 upgrade, I checked out the new feature set.

What I found was a great image, shown above that explains well how BlueLane's concept goes far in protecting virtual machines against security threats. Think about the "eggs in one basket" problem you have when you consolidate virtual machines onto smaller numbers of hosts. Doing this means an attack has fewer touchpoints, any of which can cause greater levels of damage. But, with a security screen in place like BlueLane, monitoring and protecting those fewer touchpoints can actually improve overall security.

You can see from the image above where BlueLane positions itself directly above the hypervisor. It scans traffic in and out of machines and strips away any known problems. This is particularly useful in virtualization environments that host older OSs or applications that may no longer have good levels of patching available by the manufacturer.

Check it out. BlueLane's 4.2 upgrade includes an app firewall in addition to its traditional scanning abilities. You can read more about the update at this site: http://virtualization.com/news/2008/04/21/blue-lane-releases-virtualshield-4.2/

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

If you're like me in that you create VMware ESX demo environments within VMware Workstation, you may have recently discovered that the upgrade to v3.5 has some odd quirks. Specifically, with many processor classes, although you can build the environment you are no longer able to boot any virtual machines. The ESX server simply halts when you attempt to click the green VCR button to start the VM.

Well, I did a little digging into this problem recently and discovered that there are some upgrades to 3.5 that improve its performance but eliminate our VM-in-a-VM friend. I wrote about it in this week's MCPmag.com quickTIP:

According from a document from xtravirt.com, this new hardware-assisted virtualization support may enhance virtualization, but it also comes at a price. The document reads, "ESX 3.5 enables support of new Hardware Assisted Virtualization [a function which requires chipset support] which may not exist in the majority of chips currently in circulation."

The document goes on to mention that AMD Quad Core "Greyhound" chipsets have been successfully tested to work with VM-in-a-VM. But these chipsets are relatively new, and so it's likely you don't have them in your current environment.

Are you having the same troubles? If so, let us know. Specifically, the processor type and class you're using that either works or does not work.

Digg it!

Sphere it!

Del.icio.us

Reddit!

Newsvine

Posted by Greg Shields | Permalink | Comments (0) | TrackBacks (0)

Keith Ward over at Virtualization Review pens a piece comparing the downtimes that occur when Hyper-V attempts a Quick Migration and ESX completes a VMotion. Keith has some excellent points associated with the problems of extended migration times, but there's one area where I think he needs to add extra emphasis. Keith mentions:

With that caveat in mind, it's a fascinating demo. It shows a Quick Migration of a Windows Server 2003 VM from one physical machine to another. At the same time, a Microsoft Dynamics client is trying to access a database residing on the VM. Through a constant ping of the VM, we can see how a) the connection to the VM is dropped for a time, and b) how the Dynamics client fails in its attempt to get the database information (an error box pops up, showing a TCP failure). Shortly thereafter, another popup informs us that the VM has actually been deleted! It's re-started a few moments later. In addition, a network file copy that was initiated on the VM also failed during the Quick Migration.

The video is, naturally, a worst-case scenario, but from what I saw, it could (and will) happen sometimes. The question for those