Talk:Physical-to-Virtual
 | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Casing, title edit
"Physical-to-Virtual"? Shouldn't it be "Physical-to-virtual"? --Mortense (talk) 11:03, 13 April 2013 (UTC)
Not accurate edit
P2V is not the migration of servers. Any computer that has a primary disk drive may have that drive imaged and the image "restored" on a new computer. If that new computer is virtual then this constitutes a P2V migration. However there is nothing unique or even significant about the P2V form of migration. You can also have P2P, V2V, V2P etc - are all fundamentally the same operation. Regarding the relevance to servers, it has become common practice in recent years for business servers to be implemented as VMs, as this offers many advantages that we need not discuss here. That does not mean that these operations are confined to servers. Apple Mac users for example have for many years (i.e. since Intel Macs first appeared) been creating Windows VMs so they can run Windows software. VMs are also used in testing. In many cases the easiest way to create a VM is to migrate or otherwise clone an existing image. AFAIK it is common for server admins to spawn new VMs by cloning an existing VM, but it is not particularly common to spawn a server VM using P2V. — Preceding unsigned comment added by 109.249.184.144 (talk) 12:42, 29 December 2020 (UTC)