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.

Sign up for GitHub

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

Jump to bottom

VmSchedulerSpaceShared throws NoSuchElementException when all Host PEs are already used #229

Closed
manoelcampos opened this issue Mar 12, 2020 · 0 comments
Closed

VmSchedulerSpaceShared throws NoSuchElementException when all Host PEs are already used #229

manoelcampos opened this issue Mar 12, 2020 · 0 comments
Assignees
@manoelcampos
Labels
bug

Comments

@manoelcampos
Copy link
Collaborator

ISSUE

Actual behavior

When trying to create a VM inside a given Host using the VmSchedulerSpaceShared and there are no free PEs available, it's thrown a NoSuchElementException. That happens because the Host´s free PEs list is empty in such a situation.

Expected behavior

The VM allocation should just fail due to lack of available PEs in the Host, instead of throwing the mentioned exception.

Specifications like the version of the project, operating system or workload file used

CloudSim Plus 5.1.3
@manoelcampos manoelcampos self-assigned this Mar 12, 2020
@manoelcampos manoelcampos changed the title VmSchedulerSpaceShared fails when checking if there is available PEs for a VM and all Host PEs were already used VmSchedulerSpaceShared throws NoSuchElementException when all Host PEs were already used Apr 7, 2020
@manoelcampos manoelcampos changed the title VmSchedulerSpaceShared throws NoSuchElementException when all Host PEs were already used VmSchedulerSpaceShared throws NoSuchElementException when all Host PEs are already used Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manoelcampos manoelcampos

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@manoelcampos