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

Add vcpupin support #1007

Merged
merged 1 commit into from
Oct 8, 2022
Merged

Add vcpupin support #1007

merged 1 commit into from
Oct 8, 2022

Conversation

mark-i-m
Copy link
Contributor

No description provided.

@mark-i-m
Copy link
Contributor Author

Locally, when I attempt to test, I get the following error:

$ bundle exec vagrant up --provider=libvirt
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.

Bringing machine 'test_vm_test' up with 'libvirt' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

Libvirt Provider:
* The following settings shouldn't exist: cpuaffinity

Copy link
Contributor

@electrofelix electrofelix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

catching up on some older PRs, spotted a bug in how the config option was named versus referenced.

README.md Outdated
Vagrant.configure("2") do |config|
config.vm.provider :libvirt do |libvirt|
libvirt.cpus = 4
libvirt.cpuaffinitiy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo using cpuaffinity here, but cpu_affinity for the config option below. Guessing that is the source of the failure you were seeing testing locally?

@acidghost
Copy link

@mark-i-m if you're working on this PR anymore I'd be interested to finish it up

@mark-i-m
Copy link
Contributor Author

mark-i-m commented Dec 2, 2021

@acidghost Please do! I unfortunately no longer have the time :/

@electrofelix Thanks for creating this project. It's a useful tool. I wish I had time to work on it.

@github-actions
Copy link

github-actions bot commented Oct 8, 2022

Download the latest artifacts for this pull request here:

@electrofelix electrofelix added the preview-docs Triggers preview deployment of docs label Oct 8, 2022
@github-actions
Copy link

github-actions bot commented Oct 8, 2022

PR Preview Action v1.1.1
Preview removed because the pull request was closed.
2022-10-08 10:14 UTC

@github-actions github-actions bot removed the preview-docs Triggers preview deployment of docs label Oct 8, 2022
@coveralls
Copy link

Pull Request Test Coverage Report for Build 3209997547

  • -1 of 11 (90.91%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.04%) to 78.908%

Changes Missing Coverage Covered Lines Changed/Added Lines %
lib/vagrant-libvirt/action/create_domain.rb 2 3 66.67%
Totals Coverage Status
Change from base Build 3204031062: 0.04%
Covered Lines: 2514
Relevant Lines: 3186

💛 - Coveralls

@coveralls
Copy link

coveralls commented Oct 8, 2022

Pull Request Test Coverage Report for Build 3210030043

  • 10 of 14 (71.43%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.04%) to 78.908%

Changes Missing Coverage Covered Lines Changed/Added Lines %
lib/vagrant-libvirt/action/create_domain.rb 2 6 33.33%
Totals Coverage Status
Change from base Build 3204031062: 0.04%
Covered Lines: 2514
Relevant Lines: 3186

💛 - Coveralls

@github-actions
Copy link

github-actions bot commented Oct 8, 2022

Maintainers: This PR updates the documentation, please review and apply
the label 'preview-docs' if satisfied it is safe to publish.

@electrofelix electrofelix enabled auto-merge (squash) October 8, 2022 10:13
@electrofelix electrofelix merged commit 35e3730 into vagrant-libvirt:main Oct 8, 2022
mmguero pushed a commit to mmguero-dev/vagrant-libvirt that referenced this pull request Oct 10, 2022
Support tuning to pin which host CPUs the vCPUs will be pinned to.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants