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

vsphere-iso: error creating vm: Invalid configuration for device '2'. #10431

Closed
mikemadeja opened this issue Dec 29, 2020 · 2 comments
Closed
Labels

Comments

@mikemadeja
Copy link

Overview of the Issue

When trying to deploy more than one drive on the same controller with vsphere-iso, I get "vsphere-iso: error creating vm: Invalid configuration for device '2'."

The only way around this is declaring a new disk_controller_type for each hard drive. What I found out with this resolution is if I try to make a hard drive share the controller, the device 'x', increments by 1. Something seems off with how controllers are deployed. Is it even possible to have one controller but multiple disks with paravirtual?

Reproduction Steps

Declare "disk_controller_type": ["pvscsi"]

Then call for two hard drives under storage. They should be default use Index 0 if I read it correctly.

"storage": [
{
"disk_size": 102400,
"disk_thin_provisioned": true
},
{
"disk_size": 10240,
"disk_thin_provisioned": true
}
],

Steps to reproduce this issue

Packer version

From 1.6.6

Simplified Packer Buildfile

https://pastebin.ubuntu.com/p/sfWdcmVMKT/

Operating system and Environment details

Windows 10 Enterprise

Log Fragments and crash.log files

What I see is in VCenter is the same error
"Invalid configuration for device '2'."

@mikemadeja mikemadeja added the bug label Dec 29, 2020
@sylviamoss
Copy link
Contributor

Same as #10430

@ghost
Copy link

ghost commented Feb 4, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked as resolved and limited conversation to collaborators Feb 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants