Bug 823758
Summary: | p2v client should have largest number restrictions for CPU and Memory settings | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Cui Lei <lcui> |
Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.1 | CC: | cwei, joherr, juzhou, jwu, mzhan, ptoscano, rbalakri, rjones, tzheng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | P2V | ||
Fixed In Version: | libguestfs-1.28.1-1.33.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 06:56:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Cui Lei
2012-05-22 05:17:55 UTC
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. *** Upstream commits: 1189d5919e4b3edceaa6a58b914ae29123754074 e7833a5eea350ca3579d1f9e6702e116b45572fc Ignore comment 7. The correct commits are: b1336f26e6a4a643eefd7422e8cd2d4520b1a565 1189d5919e4b3edceaa6a58b914ae29123754074 Tested with: libguestfs-1.28.1-1.36.el7.x86_64 virt-v2v-1.28.1-1.36.el7.x86_64 livecd-p2v-201505191242.iso 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. https://rhn.redhat.com/errata/RHBA-2015-2183.html |