Red Hat Bugzilla – Bug 823758
p2v client should have largest number restrictions for CPU and Memory settings
Last modified: 2015-11-19 01:56:29 EST
Description of problem:
In virt-p2v setting page, p2v client should have largest number restrictions for CPU and Memory settings.
As both convert to KVM and RHEV, there is Virtualization restrictions.
In current p2v client, set the "numbers of CPU" and "Memory(MB)" as 99999999, conversion (include covnerted to KVM and RHEV)could be successful.
1. KVM restrictions:
Maximum VCPUs per guest
Virtualized guests support up to a maximum of 64 virtualized CPUs in Red Hat Enterprise Linux 6.
2. RHEV 3.0:
Guest scalability: Supports up to 64 vCPU and 2TB vRAM per guest
From FEATURE GUIDE of RED HAT ENTERPRISE VIRTUALIZATION 3.0
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Load virt-p2v iso.
2. In virt-p2v setting page, both set the "number of CPU" and "Memory(MB)" as 99999999, click convert button
Conversion could be finished successfully. But start the converted guest failed, error message pop up
"Error starting domain: internal error Process exited while reading console log output: Unsupported number of maxcpus" from virt-manager.
BTW, first check the converted guest in virt-manager, the number of CPU has changed to 57599
Conversion should be refused, and hint the number have exceeded the maximum support number.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
It seems like a good idea to limit the guest #vCPUs and
memory to whatever the limits are for RHEL KVM. As far as
I recall, virt-p2v doesn't do that, but it should be a
trivial change. Probably take longer to find out what the
limits are supposed to be than to implement it :-)
*** Bug 855061 has been marked as a duplicate of this bug. ***
Ignore comment 7. The correct commits are:
After launch virt-p2v client,when I set cpu largen than 160 and memory larger than 4096000,the below waring will be showed:
Number of virtual CPUs is larger than what is supported for KVM (max: 160).
Memory size is larger than what is supported for KVM (max: 4096000).
If you ignore this warning, conversion can still succeed, but the guest may not work or may not be supported on the target.
Refer to the above comments,move the bug to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.