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

Hyper-V support. #131

Closed
wants to merge 7 commits into from
Closed

Hyper-V support. #131

wants to merge 7 commits into from

Conversation

KitsuneDev
Copy link

Hey guys,
Just adding Hyper-V support. Can anyone test it please??
Thank you,
Gabriel

KitsuneDev and others added 6 commits April 16, 2017 23:42
TEST PENDING.
Actually, to prevent (default) timeout during install.
@KitsuneDev
Copy link
Author

I know the SSH setup has been uploaded with the code, but this makes hyper-v building possible and speeds up the build process on other Virtualization Solutions, as the download isn't needed.

@jbarnett-r7
Copy link
Contributor

Hey @GabrielTK Thanks for this PR. I don't have a HyperV instance readily available to test this with, but I'll try to get one set up. Excited to test it out.

@jbarnett-r7 jbarnett-r7 self-assigned this May 2, 2017
@jbarnett-r7 jbarnett-r7 removed their assignment May 10, 2017
@khuongduybui
Copy link

I don't know what you tried to do with KitsuneDev@8dfd08f but I still got the corrupted file issue. You are putting more than 1.4MB into a "Floppy Drive" image and Windows Server 2008 cut off the file. 👎

@KitsuneDev
Copy link
Author

Makes Sense... Will see what can be done. Thanks for pointing that out, I didn't actually remember Floppy Disk limits.

@josharmentrout1
Copy link

Getting hung up on "Waiting for SSH to become available..."
Build 'hyperv-iso' errored: Timeout waiting for SSH.

==> Some builds didn't complete successfully and had errors:
--> hyperv-iso: Timeout waiting for SSH.

==> Builds finished but no artifacts were created.

@bwatters-r7
Copy link

@josharmentrout1 that's (unfortunately) a really common error. In the past, the most common reason I get that error is when I screw up the networking and my build machine can talk to the hypervisor, but not the the VM. Sadly, there are a bunch of reasons that error might pop up, from errant network connections to a catastrophic VM creation failure. If it were me, I'd run through this troubleshooting process:
Is the VM created?
Can you power it on?
Does the VM have an IP address?
Is port 22 listening/ssh service running?
Can you ping it?
Can you netcat port 22 from your build machine?

@busterb
Copy link
Member

busterb commented Apr 25, 2019

Let's focus on #332 for this feature

@busterb busterb closed this Apr 25, 2019
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.

None yet

6 participants