forked from joefitzgerald/packer-windows
-
Notifications
You must be signed in to change notification settings - Fork 439
Open
Description
I'm trying to add a builder for proxmox and managed to get halfway.
Here's my current builder for windows_7.
Issues I have:
- drivers
- constant copy of downloaded iso's to proxmox
- boot order
Drivers
- packer's proxmox plugin's documentation is not easy to understand
- it took a while to figure out how add all the ISOs
- windows7 always get's stuck requiring a driver
- I thought it was a harddisk driver, but in my builder I supplied every possible combination of harddisks: ide/sata/virtio/scsi, raw/qcow2/vmdk
- yet windows7 wants a driver, but does not say for what:
- supplying viostor and vioscsi doesn't do anything
- I thought I'm crazy, so I used the same win7.iso and manually created a promox vm and the result is:
| IDE | SATA | VIRTIO | SCSI | |
|---|---|---|---|---|
| local:raw | ✓ | ✓ | viostor | vioscsi |
| local:qcow | ✓ | ✓ | viostor | vioscsi |
| local:vmdk | ? | ✓ | viostor | vioscsi |
| local-zfs:raw | ? | ✓ | viostor | vioscsi |
- so drivers work?
- Maybe it wants a driver for something else?
- my manual win install worked without any additional drivers
- Any ideas?
Constant copy
- every run packer copies the ISOs to promox, win7 iso is 3gb, so every time it is copied.
- temp solution is:
"iso_url": "https://fedora.......iso",becomes"iso_file": "local:iso/[sha256].iso" - is there a better way?
Boot Order
- there are three CDs - windows iso, unattended files, fedora's virtio drivers
- I have to constantly change boot order in order to hit the windows iso
- is there a better way?
Keep in mind I started using packer 6h ago, so my config might not be great.
If I manage to get it working I plan to submit a pull request.
Metadata
Metadata
Assignees
Labels
No labels
