Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi friends, i have some Theorytical problem about RHEV P2V.
1st: I wanna try for P2V in RHEV 3.0. I am looking for the flowchart for the same and I cant get help from google also. So can anyone please share some relevent flowchart or any working Theory or Working diagram of P2V.
2nd: I'd like to know that minimum how many systems are required for P2V ?
I mean as per my understing i'll need the following systems:
system 1 for RHEV-H
system 2 for RHEV-M
System 3 for accessing the RHEVM (i.e. Laptop with Windows 7)
system 4 conversion server for P2V client
system 5 P2V client (system of which the image is being created)
So am I going in right direction ? Do I really need minimum 5 systems for P2V ? because i am not using more than 1 system for RHEV-H.
3rd: Lets say i'll be able to convert the image of the system (system5), then where this P2V client image is being stored ? Is it taking space from RHEV-M (System2) or from Conversion server (system4) ?
FYI: I have created the /ISO directory and /export partition on RHEV-M (system2) as a NFS storage
Please let me know if i was NOT able to make you understand my post.
Hi friends, i have some Theorytical problem about RHEV P2V. 1st: I wanna try for P2V in RHEV 3.0. I am looking for the flowchart for the same and I cant get help from google also. So can anyone please share some relevent flowchart or any working Theory or Working diagram of P2V.
There are documents posted on the Red Hat knowledgebase website. You can access them with your RHN user ID. Since those are pay-for documents, please go to Red Hat and log in to view them.
Quote:
2nd: I'd like to know that minimum how many systems are required for P2V ?
So am I going in right direction ? Do I really need minimum 5 systems for P2V ? because i am not using more than 1 system for RHEV-H.
RHEV is a commercial, PAY FOR product. If you're under the 60 day evaluation period, you can contact Red Hat. Not sure there is a minimum, but they can tell you what the requirements are. Some of the services may be able to run on the same system, and won't need a separate, physical/virtual host. Again, the Red Hat website has information: https://www.redhat.com/promo/rhev3/sysreq.html
Quote:
3rd: Lets say i'll be able to convert the image of the system (system5), then where this P2V client image is being stored ? Is it taking space from RHEV-M (System2) or from Conversion server (system4) ?
FYI: I have created the /ISO directory and /export partition on RHEV-M (system2) as a NFS storage
Please let me know if i was NOT able to make you understand my post.
Should wind up on the M system, I believe. But again, you should contact Red Hat for support questions relating to a product you're paying for. Also, you rarely post follow-ups to your questions, or reply to what folks ask you. Saying "thanks" or even acknowledging folks have tried to help you wouldn't be a bad thing.
Hi friends, i have some Theorytical problem about RHEV P2V.
1st: I wanna try for P2V in RHEV 3.0. I am looking for the flowchart for the same and I cant get help from google also. So can anyone please share some relevent flowchart or any working Theory or Working diagram of P2V.
You create the bootable CD with virt-p2v, boot up your host with it, and it will read the machine's drives and push an image with preloaded virtio drivers to the v2v/p2v machine.
Quote:
2nd: I'd like to know that minimum how many systems are required for P2V ?
I mean as per my understing i'll need the following systems:
system 1 for RHEV-H
system 2 for RHEV-M
System 3 for accessing the RHEVM (i.e. Laptop with Windows 7)
system 4 conversion server for P2V client
system 5 P2V client (system of which the image is being created)
You need a working RHEV setup (RHEV-Manager plus a set of hosts it manages)
You also need a v2v/p2v machine, which can be a VM in this setup, or you can use the RHEV-M machine for that.
Then of course you need the client machine, which is being converted and your own workstation, because that is where you are sitting after all
Quote:
3rd: Lets say i'll be able to convert the image of the system (system5), then where this P2V client image is being stored ? Is it taking space from RHEV-M (System2) or from Conversion server (system4) ?
The "conversion server will place the VM image and ovf in RHEV Export domain, from which you can import the VM into RHEV.
Quote:
FYI: I have created the /ISO directory and /export partition on RHEV-M (system2) as a NFS storage
the VM will end up in this export domain you created.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.