Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[backport v1.2] [BUG] Unable to create pc-q35 VM with Error NO PCI buses available #5785

Closed
harvesterhci-io-github-bot opened this issue May 10, 2024 · 2 comments
Assignees
Labels
area/vm-lifecycle kind/bug Issues that are defects reported by users or that we know have reached a real release need-reprioritize not-require/test-plan Skip to create a e2e automation test issue regression reproduce/always Reproducible 100% of the time require/investigate severity/1 Function broken (a critical incident with very high impact)
Milestone

Comments

@harvesterhci-io-github-bot

backport the issue #5437

@harvesterhci-io-github-bot harvesterhci-io-github-bot added area/vm-lifecycle kind/bug Issues that are defects reported by users or that we know have reached a real release need-reprioritize not-require/test-plan Skip to create a e2e automation test issue regression reproduce/always Reproducible 100% of the time require/investigate severity/1 Function broken (a critical incident with very high impact) labels May 10, 2024
@harvesterhci-io-github-bot harvesterhci-io-github-bot added this to the v1.2.2 milestone May 10, 2024
@harvesterhci-io-github-bot
Copy link
Author

harvesterhci-io-github-bot commented May 13, 2024

Pre Ready-For-Testing Checklist

  • If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
    The HEP PR is at:

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

  • For v1.2.2-rc3, please change the ui-source to external and reload the GUI.
  • Create a VM or Edit a VM from GUI, in the "Advanced Options" tab -> Show more -> Machine type should only display None or q35. VM should start with both option.
  • Is there a workaround for the issue? If so, where is it documented?
    The workaround is at:

  • Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
    The PR is at:

    • Does the PR include the explanation for the fix or the feature?

    • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
      The PR for the YAML change is at:
      The PR for the chart change is at:

  • If labeled: area/ui Has the UI issue filed or ready to be merged?
    The UI issue/PR is at:

  • If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
    The documentation/KB PR is at:

  • If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

    • The automation skeleton PR is at:
    • The automation test case PR is at:
  • If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
    The compatibility issue is filed at:

@albinsun
Copy link

Verified on v1.2.2-rc3, close as fixed.

Environment

  • Harvester
    • Version: v1.2.2-rc3
    • Profile: QEMU/KVM, 2 nodes (8C/16G/500G)
    • ui-source: External

Steps

  1. Settings -> UI -> Change ui-source to External

    image

  2. Create an image for VM creation

    image

  3. 🟢 NO more pc-q35 in Virtual Machines -> Create -> Advanced Options -> Show More -> Machine Type

    image

  4. VM with Machine Type None (via GUI)

    • 🟢 Create a VM w/ test data

      image
      image
      test data
      image

      ⚠️ None will convert to q35 implicitly

    • 🟢 Take snapshot

      image

    • 🟢 Stop

      image

    • 🟢 Restore Replace Existing

      image
      image

    • 🟢 Soft Reboot

      image
      image

    • 🟢 Pause and Unpause

      image
      image

    • 🟢 Restart

      image
      image

  5. VM with Machine Type q35 (via GUI)

    • 🟢 Create VM w/ test data

      image
      test data
      image

    • 🟢 Take snapshot

      image

    • 🟢 Stop

      image

    • 🟢 Restore Replace Existing

      image
      image

    • 🟢 Soft Reboot

      image
      image

    • 🟢 Pause and Unpause

      image
      image

    • 🟢 Restart

      image
      image

  6. VM with Machine Type pc-q35-5.2 (via Edit as YAML)

    • 🟢 Create VM and test data

      image
      image
      Can create test data
      image

    • 🟢 Take snapshot

      image

    • 🟢 Stop

      image

    • 🟢 Restore Replace Existing

      image
      image

    • 🟢 Soft Reboot

      image
      image

    • 🟢 Pause and Unpause

      image
      image

    • 🟢 Restart

      image
      image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vm-lifecycle kind/bug Issues that are defects reported by users or that we know have reached a real release need-reprioritize not-require/test-plan Skip to create a e2e automation test issue regression reproduce/always Reproducible 100% of the time require/investigate severity/1 Function broken (a critical incident with very high impact)
Projects
None yet
Development

No branches or pull requests

3 participants