Skip to content

Mhz speed not shown in import-export KVM instance #8727

Closed as not planned
Closed as not planned

Description

@pcfriek1987
ISSUE TYPE
  • Bug Report
COMPONENT NAME
Import-Export Instance
CLOUDSTACK VERSION
4.19.0
CONFIGURATION
OS / ENVIRONMENT
SUMMARY

When trying to Import a vm, I have a custom cpu offering on which I can freely fill in the CPU and memory I want, this however is not possible as for that it needs CPU cores, speed and memory. However the speed field is missing so pressing Ok gives an error now that you need to fill in a correct amount of Mhz.

STEPS TO REPRODUCE

Create a custom CPU offering on which you can define, cores/speed and memory during instance creation.
Go to Import-Export instance under Tools
Import from external KVM host
Pick any VM under unmanaged instances
Under Import instance fill in the form and pick the custom cpu offering, now fill in cores and memory and press Ok

EXPECTED RESULTS
That it would start the migration
ACTUAL RESULTS
It error-ed out with "Request failed, please enter a valid value: CPU (In Mhz)"

Activity

  1. added this to the 4.19.1.0 milestone on Feb 29, 2024
  2. self-assigned this
    on Mar 27, 2024
  3. vishesh92 commented on Mar 27, 2024

    @vishesh92
    Member

    There is an option to set speed if you select a custom offering under "Import-Export Instances".

    image

  4. vishesh92 commented on Mar 27, 2024

    @vishesh92
    Member

    @pcfriek1987 Can you confirm if this is still an issue? I am not able to reproduce this.

  5. moved this from Done to Todo in Apache CloudStack 4.19.1on Mar 27, 2024
  6. pcfriek1987 commented on Mar 27, 2024

    @pcfriek1987
    Author

    @vishesh92
    Scherm­afbeelding 2024-03-27 om 11 11 57
    Hmm your screen looks very different from mine, are you also using 4.19.0? As I still don't see any mhz here and the same error (the attached screenshot is taken from a private window in a different browser to rule out any caching).

  7. vishesh92 commented on Mar 27, 2024

    @vishesh92
    Member

    @pcfriek1987 I am using the latest 4.19 branch. I also tested on 4.19. And my view is completely different from yours.

  8. pcfriek1987 commented on Mar 27, 2024

    @pcfriek1987
    Author

    @vishesh92 How is that possible? This is what it says for me:

    Licensed under the Apache License, Version 2.0.
    CloudStack 4.19.0.0
    Report issue

    Should I upgrade in some way to get the same as you?

  9. vishesh92 commented on Mar 27, 2024

    @vishesh92
    Member

    @pcfriek1987 Can you try some other browser? Also check the browser's console log to see if there are any errors.

  10. 8 remaining items

  11. shwstppr commented on Jun 5, 2024

    @shwstppr
    Contributor

    @pcfriek1987 can you please share listServiceOfferings API output of the service offering you are using?

  12. pcfriek1987 commented on Jun 5, 2024

    @pcfriek1987
    Author

    Is this what you are looking for?

    "serviceoffering": [
      {
        "cacheMode": "none",
        "created": "2023-11-03T13:21:09+0100",
        "defaultuse": false,
        "diskofferingstrictness": false,
        "displaytext": "Custom compute offering",
        "domainid": "2e867e8c-8b1b-4bc1-9676-3e9870499b84,4831b578-04a6-4808-ba39-c21c83d616dd",
        "dynamicscalingenabled": false,
        "encryptroot": false,
        "hasannotations": false,
        "id": "145f4b33-c89b-498e-9695-5c43133408a9",
        "iscustomized": true,
        "issystem": false,
        "isvolatile": false,
        "limitcpuuse": false,
        "name": "Custom",
        "offerha": false,
        "provisioningtype": "thin",
        "rootdisksize": 0,
        "serviceofferingdetails": {
          "domainid": "6",
          "zoneid": "2"
        },
        "storagetype": "local",
        "zone": "Global",
        "zoneid": "00122c1c-89ae-4fbf-8424-e8619a787d39"
    

    But I was also missing the part where you can pick to which server it migrates.

  13. self-assigned this
    on Jun 13, 2024
  14. modified the milestones: 4.19.1.0, 4.19.2 on Jun 18, 2024
  15. vishesh92 commented on Jan 21, 2025

    @vishesh92
    Member

    @pcfriek1987 Can you try to upgrade to 4.19.1 or 4.20 and see if you are still facing the issue? I am not able to reproduce this issue.

    I am closing this issue for now, if you still face the issue please feel free to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions