tag:help.appveyor.com,2012-11-13:/discussions/problems/1247-vagrant-not-working-inside-appveyorAppVeyor: Discussion 2018-10-19T08:16:55Ztag:help.appveyor.com,2012-11-13:Comment/355992312014-12-20T23:15:13Z2014-12-20T23:15:13ZVagrant not working inside AppVeyor<div><p>Well, I don't think it's UAC - in fact, it's disabled on build
workers.</p>
<p>Try using "unstable" OS (image) - it's running build agent
interactive - maybe this could help. You can select it on
Environment tab of project settings.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/355992312014-12-21T00:00:09Z2014-12-21T00:00:09ZVagrant not working inside AppVeyor<div><p>Hi Feodor, thanks for the quick response!</p>
<p>Yes, I believe it's disabled. Also tried explicitly disabling
UAC and / or the UAC prompt (from <a href=
"http://ss64.com/nt/syntax-uac.html">http://ss64.com/nt/syntax-uac.html</a>),
but it did not help though...</p>
<p>Will try with the "unstable" OS (image) now...</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-21T01:26:28Z2014-12-21T01:26:28ZVagrant not working inside AppVeyor<div><p>FYI - I could verify that it works in general (via minimalistic
vagrant file):<br>
<a href=
"https://ci.appveyor.com/project/ukio/sample-toplevel-cookbook/build/46-appveyor">
https://ci.appveyor.com/project/ukio/sample-toplevel-cookbook/build...</a></p>
<p>So it must be something else. I'll start with increasing the
timeout a bit...</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-21T01:30:08Z2014-12-21T01:30:08ZVagrant not working inside AppVeyor<div><p>That's great, keep us posted!</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/355992312014-12-27T22:11:33Z2014-12-27T22:11:33ZVagrant not working inside AppVeyor<div><p>Experiences so far:</p>
<ul>
<li>increased the timeout for bringing up the vm to 20 minutes</li>
<li>running builds on x64 Windows Server 2012 only</li>
<li>the time for bringing up the VM varies quite a lot. I got the
vm up and running
<ul>
<li>on hyperv: somewhere between 6 and 16 minutes</li>
<li>on azure: somewhere between 16 and 26 minutes</li>
</ul>
</li>
<li>so far I only got 32-bit VMs running. The 64-bit VMs always
timed out.</li>
<li>still randomly running into timeouts while bringing up the VMs
(mostly on hyperv, azure feels more stable)</li>
<li>tried to cache the VirtualBox installation, but that doesn't
work out -> you need to run the installer to get the additional
network adapters and probably lots of other things</li>
</ul>
<p>So, current status: still trying to get a series of green stable
builds reproducably and reliably</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-27T22:49:31Z2014-12-27T22:49:31ZVagrant not working inside AppVeyor<div><p>Results with the hyperv workers are getting better. Maybe it was
a bad idea trying to cache the Vagrant installation as well, so I
removed it from the cache, and promptly got a new build time
record:</p>
<ul>
<li>5:09 for bringing up a VM on hyperv: <a href=
"https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build/164-master">
https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build...</a></li>
</ul></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-27T23:16:49Z2014-12-27T23:16:49ZVagrant not working inside AppVeyor<div><p>...and the next build on hyperv timed out again :-( <a href=
"https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build/165-master">
https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build...</a></p>
<p>There was no code / appveyor.yml change involved. So what else
could the differences be?</p>
<ul>
<li><a href=
"http://askubuntu.com/questions/246323/why-does-sshs-password-prompt-take-so-long-to-appear">
Reverese DNS resolution timing out?</a></li>
<li><a href="http://stackoverflow.com/a/23713516/2388971">Hyper-V
enabled or not</a> on the build worker</li>
<li><a href="http://stackoverflow.com/a/26482167/2388971">VT-x
enabled via BIOS</a> or not?</li>
</ul>
<p>Actually - the hyperv workers should be all exactly the same,
shouldn't they?</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-28T00:00:03Z2014-12-28T00:00:03ZVagrant not working inside AppVeyor<div><p>New record:</p>
<ul>
<li>4:11 for bringing up a VM on hyperv (using Ubuntu precise32
basebox this time): <a href=
"https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build/168-master">
https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build...</a></li>
</ul></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-28T00:03:34Z2014-12-28T00:03:34ZVagrant not working inside AppVeyor<div><p>Not bad at all!</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/355992312014-12-28T00:46:23Z2014-12-28T00:46:23ZVagrant not working inside AppVeyor<div><p>This one looks weird. I reverted back to the trusty32 box to
check if it were the culprit. Got a failed build after 22 minutes
again, but this time with a different error message:<br>
<a href=
"https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build/172-master">
https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build...</a></p>
<pre>
<code>...
default: Warning: Connection timeout. Retrying...
153 default: Warning: Connection timeout. Retrying...
154 default: Warning: Connection timeout. Retrying...
155Vagrant can't use the requested machine because it is locked! This
156means that another Vagrant process is currently reading or modifying
157the machine. Please wait for that Vagrant process to end and try
158again. Details about the machine are shown below:
159
160Name: default
161Provider: virtualbox
162Command exited with code 1</code>
</pre>
<p>The error indicates some kind of shared state, but it's also
pretty exactly at the configured boot timeout after 20 minutes.</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-29T23:41:20Z2014-12-29T23:41:20ZVagrant not working inside AppVeyor<div><p>Hi Feodor,</p>
<p>I have no luck with the ubuntu 14.04 base boxes on hyper-v build
workers. On the azure workers everything works well (it just takes
a bit longer).</p>
<p>Tried with the "ubuntu/trusty32" as well as the
"chef/ubuntu-14.04-i386" base box. In both cases it randomly (looks
like random at least) fails to connect via SSH within the given
timeout of 15 minutes.</p>
<p>Compare the latest build results from hyper-v (mostly
instable):<br>
<a href=
"https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/history">
https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/history</a><br>
...with the ones from azure (stable): <a href=
"https://ci.appveyor.com/project/tknerr/vagrant-appveyor-testing/history">
https://ci.appveyor.com/project/tknerr/vagrant-appveyor-testing/his...</a></p>
<p>What could be the differences between the azure and hyper-v
workers? Anything ssh related maybe?</p>
<p>I <a href=
"https://github.com/tknerr/vagrant-appveyor-testing/commit/aed5c7c3bd2d5d28835dbd96c5993e9001e35efb#diff-180360612c6b8c4ed830919bbb4dd459R41">
added some client-side ssh debugging</a> if the <code>vagrant
up</code> command fails. However it only <a href=
"https://ci.appveyor.com/project/ukio/vagrant-appveyor-testing/build/244-master">
reveals</a> a <code>ssh_exchange_identification: read: Connection
reset by peer</code> error, which I can't debug further client
side.</p>
<p>It would probably help to debug this via RDP. I am now <a href=
"https://github.com/tknerr/vagrant-appveyor-testing/commit/c2105c91d7913249e59c2ed3017feec2224a321f">
starting the VMs in gui mode</a> but no idea how to access the
build worker via RDP if that is possible at all.</p>
<p>Do you have any futher means on how to debug this?</p>
<p>I don't have any meta information about the build worker IDs who
are executing the builds -- maybe that would give another hint
(e.g. reveal that it always fails / succeeds on a specific hyper-v
worker).</p>
<p>Other suspects:<br>
* firewall? * disabled the windows firewall but did not help *
checked inside the ubuntu/trusty32 vm: ufw firewall is inactive and
neither fail2ban nor denyhosts is installed, so that should not be
the reason * <a href=
"http://ask.xmodulo.com/fix-slow-ssh-login-issue-linux.html">reverse
dns slowness</a>? * unlikely since the appveyor build workers
should use 8.8.8.8 which is pretty stable * however,
<code>UseDNS</code> is not explictly disabled in
/etc/ssh/sshd_config and the default is <code>yes</code>, so it
might have to do with it</p>
<p><em>sigh</em>...</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-30T00:54:21Z2014-12-30T00:54:21ZVagrant not working inside AppVeyor<div><p>@Feodor can you see this in the VirtualBox GUI? <a href=
"https://ask.openstack.org/en/question/28297/cloud-init-nonet-waiting-and-fails/">
https://ask.openstack.org/en/question/28297/cloud-init-nonet-waitin...</a></p>
<p>Not sure why it work then on the azure workers though...</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-30T02:27:27Z2014-12-30T02:27:27ZVagrant not working inside AppVeyor<div><p>You mean it might be DHCP problem? There is no DHCP on Hyper-V
environment.</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/355992312014-12-30T12:09:52Z2014-12-30T12:09:52ZVagrant not working inside AppVeyor<div><p>No, not exactly a DHCP problem, but something about the network
adapters in ubuntu 14.04, or just a desperate guess because I see
no other chance to debug this.</p>
<p>So weird it works sometimes and sometimes not, but I can't see
why.</p>
<p>Is there any possibility to RDP into a build worker? Or at least
getting screenshots of the VirtualBox GUI anyhow?</p></div>ukiotag:help.appveyor.com,2012-11-13:Comment/355992312014-12-31T03:11:12Z2014-12-31T03:11:12ZVagrant not working inside AppVeyor<div><p>Theoretically, you can RDP into build worker instance.</p>
<p>You should do three steps:<br>
1. Get know instance IP from IP-enabled NIC (say using
PowerShell).<br>
2. Update <code>appveyor</code> account password, for
example:<br></p>
<pre>
<code>$objUser = [ADSI]("WinNT://$($env:computername)/appveyor")
$objUser.SetPassword('yourpassword')</code>
</pre>
3. Allow RDP on firewall.
<p>Be aware your session will be limited with total time of build
(40 minutes). Let me know how it goes.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/355992312015-11-25T21:49:39Z2015-11-25T21:49:40ZVagrant not working inside AppVeyor<div><p>Great work to try Vagrant on AppVeyor.</p>
<p>But is it also possible to run 64bit VM's in AppVeyor?<br>
AFAIK you would need VT-X enabled (nested hypervisor) in the
AppVeyor worker instance. Can this be enabled in AppVeyor
somewhere?</p></div>Stefan Scherertag:help.appveyor.com,2012-11-13:Comment/355992312016-02-27T01:54:25Z2016-02-27T01:54:26ZVagrant not working inside AppVeyor<div><p>Also stumbled upon this issue.</p>
<p>Regarding RDB - there is an article in in the official docs
about that:<br>
<a href="https://www.appveyor.com/docs/how-to/rdp-to-build-worker">https://www.appveyor.com/docs/how-to/rdp-to-build-worker</a></p></div>andrew.pashkintag:help.appveyor.com,2012-11-13:Comment/355992312016-02-27T11:05:48Z2016-02-27T12:34:08ZVagrant not working inside AppVeyor<div><p>I was able to resolve my problem, here is the successful
build:<br>
<a href="https://ci.appveyor.com/project/AndrewPashkin/vagrant-appveyor-testing/build/10-master">
https://ci.appveyor.com/project/AndrewPashkin/vagrant-appveyor-test...</a></p>
<p>In short, I've added such configuration to my
Vagrantfile:<br></p>
<pre>
<code>config.vm.provider "virtualbox" do |vb|
vb.customize ["modifyvm", :id, "--nictype1", "Am79C973"]
end</code>
</pre>
How did I came to the solution:
<ol>
<li>First of all, I used this method, to access a build workers via
RDP:<br>
<a href="https://www.appveyor.com/docs/how-to/rdp-to-build-worker">https://www.appveyor.com/docs/how-to/rdp-to-build-worker</a></li>
<li>
<p>The other curical point was in enabling GUI for a VM:</p>
<pre>
<code>config.vm.provider "virtualbox" do |vb|
vb.gui = true
end</code>
</pre></li>
<li>
<p>Finally, I was able to see, what happens inside a VM and spot an
error<br>
(see attached screenshot). Also, I saw this <a href="https://github.com/Varying-Vagrant-Vagrants/VVV/issues/375#issuecomment-186670334">
comment</a> earlier.</p>
</li>
</ol></div>andrew.pashkintag:help.appveyor.com,2012-11-13:Comment/355992312016-02-27T11:28:57Z2016-02-27T11:29:01ZVagrant not working inside AppVeyor<div><p>Hi Andrew,</p>
<p>This is awesome! Thanks for sharing nictype1=Am79C973<br>
I'll try this.</p>
<p>Stefan</p></div>Stefan Scherertag:help.appveyor.com,2012-11-13:Comment/355992312016-02-27T12:33:08Z2016-02-27T12:33:10ZVagrant not working inside AppVeyor<div><p>It is also impossible to launch 64-bit boxes. See attached image
with the error.</p></div>andrew.pashkin