Giter Site home page Giter Site logo

Comments (31)

ramondelafuente avatar ramondelafuente commented on August 23, 2024

I updated to Vagrant Manager version 1.4.1 just now, but that still has the same issue.

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

Thanks for reporting this issue. Can you run this command in your terminal:

vboxmanage list runningvms

And find the UUID of your machine (it will be the string in between { and } next to the appropriate machine). Then run this command in your terminal:

vboxmanage showvminfo PUT_UUID_HERE --machinereadable

Replacing PUT_UUID_HERE with the UUID from the previous step.

If you can send over the output from that second command, that should help.

from vagrant-manager.

ramondelafuente avatar ramondelafuente commented on August 23, 2024

I think I might see a problem. I run on a case sensitive file-system, and the official binary is "VBoxManage", not "vboxmanage".

$ vboxmanage list runningvms
-bash: vboxmanage: command not found
$ VBoxManage list runningvms
"machine_name" {GUID}

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

That's a good catch. We'll get an update pushed out ASAP.

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

Can you check if release 1.4.2 solves your issue?

from vagrant-manager.

ramondelafuente avatar ramondelafuente commented on August 23, 2024

Unfortunately: no

$ VBoxManage list runningvms
"sweetlakephp_development" {9af9f83d-1f2e-42e4-937e-97321fd313e4}
$ VBoxManage showvminfo 9af9f83d-1f2e-42e4-937e-97321fd313e4 --machinereadable
name="sweetlakephp_development"
groups="/"
ostype="Debian (64 bit)"
UUID="9af9f83d-1f2e-42e4-937e-97321fd313e4"
CfgFile="/Users/fzz/VirtualBox VMs/sweetlakephp_development/sweetlakephp_development.vbox"
SnapFldr="/Users/fzz/VirtualBox VMs/sweetlakephp_development/Snapshots"
LogFldr="/Users/fzz/VirtualBox VMs/sweetlakephp_development/Logs"
hardwareuuid="9af9f83d-1f2e-42e4-937e-97321fd313e4"
memory=1024
pagefusion="off"
vram=16
cpuexecutioncap=100
hpet="off"
chipset="piix3"
firmware="BIOS"
cpus=1
pae="off"
longmode="on"
synthcpu="off"
bootmenu="messageandmenu"
boot1="floppy"
boot2="dvd"
boot3="disk"
boot4="none"
acpi="on"
ioapic="on"
Time offset=0rtcuseutc="on"
hwvirtex="on"
nestedpaging="on"
largepages="on"
vtxvpid="on"
vtxux="on"
VMState="running"
VMStateChangeTime="2014-05-12T13:51:49.979000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
tracing-enabled="off"
tracing-allow-vm-access="off"
tracing-config=""
autostart-enabled="off"
autostart-delay=0
defaultfrontend=""
storagecontrollername0="IDE"
storagecontrollertype0="PIIX4"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="2"
storagecontrollerportcount0="2"
storagecontrollerbootable0="on"
storagecontrollername1="SATA"
storagecontrollertype1="IntelAhci"
storagecontrollerinstance1="0"
storagecontrollermaxportcount1="30"
storagecontrollerportcount1="1"
storagecontrollerbootable1="on"
"IDE-0-0"="none"
"IDE-0-1"="none"
"IDE-1-0"="emptydrive"
"IDE-IsEjected"="off"
"IDE-1-1"="none"
"SATA-0-0"="/Users/fzz/VirtualBox VMs/sweetlakephp_development/box-disk1.vmdk"
"SATA-ImageUUID-0-0"="47be2bf1-83d8-4d51-bb53-dc8668370a0d"
natnet1="nat"
macaddress1="080027550B1A"
cableconnected1="on"
nic1="nat"
nictype1="82540EM"
nicspeed1="0"
mtu="0"
sockSnd="64"
sockRcv="64"
tcpWndSnd="64"
tcpWndRcv="64"
Forwarding(0)="ssh,tcp,127.0.0.1,2222,,22"
hostonlyadapter2="vboxnet4"
macaddress2="080027CF960B"
cableconnected2="on"
nic2="hostonly"
nictype2="82540EM"
nicspeed2="0"
nic3="none"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
hidpointing="ps2mouse"
hidkeyboard="ps2kbd"
uart1="off"
uart2="off"
lpt1="off"
lpt2="off"
audio="none"
clipboard="disabled"
draganddrop="disabled"
SessionType="headless"
VideoMode="720,400,0"@0,0
vrde="off"
usb="on"
ehci="on"
SharedFolderNameMachineMapping1="vagrant"
SharedFolderPathMachineMapping1="/Users/fzz/Projects/sweetlakephp/SweetLakePHP"
VRDEActiveConnection="off"
VRDEClients=0
vcpenabled="off"
vcpscreens=0
vcpfile="/Users/fzz/VirtualBox VMs/sweetlakephp_development/sweetlakephp_development.webm"
vcpwidth=1024
vcpheight=768
vcprate=512
vcpfps=25
GuestMemoryBalloon=0
GuestOSType="Linux26_64"
GuestAdditionsRunLevel=2
GuestAdditionsVersion="4.1.18_Debian r78361"
GuestAdditionsFacility_VirtualBox Base Driver=50,1399902722385
GuestAdditionsFacility_VirtualBox System Service=50,1399902730926
GuestAdditionsFacility_Seamless Mode=0,1399902722385
GuestAdditionsFacility_Graphics Mode=0,1399902722385

from vagrant-manager.

robjmills avatar robjmills commented on August 23, 2024

I'm having the same issue, albeit it's unrelated to case sensitivity for me:

$  > ~ which vboxmanage
/usr/bin/vboxmanage

Also running

  • OSX 10.9.2
  • Vagrant 1.6.1
  • Virtualbox 4.3.10
vboxmanage showvminfo f5765cbf-be2a-4b28-9a7f-360bac22d05b --machinereadable
name="sitem_vagrant_default_1395398274937_62302"
groups="/"
ostype="Red Hat (64 bit)"
UUID="f5765cbf-be2a-4b28-9a7f-360bac22d05b"
CfgFile="/Users/robm/VirtualBox VMs/sitem_vagrant_default_1395398274937_62302/sitem_vagrant_default_1395398274937_62302.vbox"
SnapFldr="/Users/robm/VirtualBox VMs/sitem_vagrant_default_1395398274937_62302/Snapshots"
LogFldr="/Users/robm/VirtualBox VMs/sitem_vagrant_default_1395398274937_62302/Logs"
hardwareuuid="f5765cbf-be2a-4b28-9a7f-360bac22d05b"
memory=480
pagefusion="off"
vram=8
cpuexecutioncap=100
hpet="off"
chipset="piix3"
firmware="BIOS"
cpus=1
pae="on"
longmode="on"
synthcpu="off"
bootmenu="messageandmenu"
boot1="disk"
boot2="dvd"
boot3="none"
boot4="none"
acpi="on"
ioapic="on"
Time offset=0rtcuseutc="on"
hwvirtex="on"
nestedpaging="on"
largepages="on"
vtxvpid="on"
vtxux="on"
VMState="running"
VMStateChangeTime="2014-05-12T13:36:53.201000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
tracing-enabled="off"
tracing-allow-vm-access="off"
tracing-config=""
autostart-enabled="off"
autostart-delay=0
defaultfrontend=""
storagecontrollername0="IDE Controller"
storagecontrollertype0="PIIX4"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="2"
storagecontrollerportcount0="2"
storagecontrollerbootable0="on"
storagecontrollername1="SATA Controller"
storagecontrollertype1="IntelAhci"
storagecontrollerinstance1="0"
storagecontrollermaxportcount1="30"
storagecontrollerportcount1="1"
storagecontrollerbootable1="on"
"IDE Controller-0-0"="emptydrive"
"IDE Controller-IsEjected"="off"
"IDE Controller-0-1"="none"
"IDE Controller-1-0"="emptydrive"
"IDE Controller-IsEjected"="off"
"IDE Controller-1-1"="none"
"SATA Controller-0-0"="/Users/robm/VirtualBox VMs/sitem_vagrant_default_1395398274937_62302/box-disk1.vmdk"
"SATA Controller-ImageUUID-0-0"="c1b2acc2-814c-48e3-9e5c-002f57bc2ef0"
natnet1="nat"
macaddress1="080027956067"
cableconnected1="on"
nic1="nat"
nictype1="82540EM"
nicspeed1="0"
mtu="0"
sockSnd="64"
sockRcv="64"
tcpWndSnd="64"
tcpWndRcv="64"
Forwarding(0)="ssh,tcp,127.0.0.1,2222,,22"
Forwarding(1)="tcp8080,tcp,,8080,,80"
bridgeadapter2="en0: Wi-Fi (AirPort)"
macaddress2="08002776075B"
cableconnected2="on"
nic2="bridged"
nictype2="82540EM"
nicspeed2="0"
hostonlyadapter3="vboxnet4"
macaddress3="080027BF205E"
cableconnected3="on"
nic3="hostonly"
nictype3="82540EM"
nicspeed3="0"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
hidpointing="ps2mouse"
hidkeyboard="ps2kbd"
uart1="off"
uart2="off"
lpt1="off"
lpt2="off"
audio="none"
clipboard="disabled"
draganddrop="disabled"
SessionType="headless"
VideoMode="720,400,0"@0,0
vrde="off"
usb="off"
ehci="off"
SharedFolderNameMachineMapping1="home"
SharedFolderPathMachineMapping1="/Users/robm/Clones"
SharedFolderNameMachineMapping2="data"
SharedFolderPathMachineMapping2="/Users/robm/github-repos/sitem_vagrant/data"
SharedFolderNameMachineMapping3="vagrant"
SharedFolderPathMachineMapping3="/Users/robm/github-repos/sitem_vagrant"
SharedFolderNameMachineMapping4="tmp_vagrant-puppet-3_manifests"
SharedFolderPathMachineMapping4="/Users/robm/github-repos/sitem_vagrant/manifests"
SharedFolderNameMachineMapping5="tmp_vagrant-puppet-3_modules-0"
SharedFolderPathMachineMapping5="/Users/robm/github-repos/sitem_vagrant/modules"
VRDEActiveConnection="off"
VRDEClients=0
vcpenabled="off"
vcpscreens=0
vcpfile="/Users/robm/VirtualBox VMs/sitem_vagrant_default_1395398274937_62302/sitem_vagrant_default_1395398274937_62302.webm"
vcpwidth=1024
vcpheight=768
vcprate=512
vcpfps=25
GuestMemoryBalloon=0
GuestOSType="Linux26_64"
GuestAdditionsRunLevel=2
GuestAdditionsVersion="4.2.8 r83876"
GuestAdditionsFacility_VirtualBox Base Driver=50,1399901824066
GuestAdditionsFacility_VirtualBox System Service=50,1399901860238
GuestAdditionsFacility_Seamless Mode=0,1399901824066
GuestAdditionsFacility_Graphics Mode=0,1399901824065

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

Thanks for the info, we are looking into this issue again.

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

What method are you using for folder sharing (NFS, rsync, etc). Also, here is a link to a debug build that should generate a vagrant-manager-TIMESTAMP.log file in your Documents folder:
https://www.dropbox.com/sh/st3a5y6q09w1ddx/AAB1pIeFk3pgBu2sYMaZsTCja

We have been unable to recreate this issue, so could you run this build and email the log file to: [email protected]? I would not recommend using this build permanently since it will continue to generate large log files.

from vagrant-manager.

tcsehv avatar tcsehv commented on August 23, 2024

I have the same issue.

OS X 10.9.2
Vargant 1.5.4
Virtualbox 4.3.10

vboxmanage list runningvms
"protobox-php53" {33a07309-c057-4b81-a414-0cab4118ba7c}

from vagrant-manager.

tcsehv avatar tcsehv commented on August 23, 2024

I ran the debug version and it gave me this:

2014-05-13 08:23:35.584 Vagrant Manager[1739:707] Starting Vagrant Manager
2014-05-13 08:23:35.584 Vagrant Manager[1739:707] Loaded bookmark: [33a07309-c057-4b81-a414-0cab4118ba7c] Protobox (/Users/xxx/protobox)
2014-05-13 08:23:35.688 Vagrant Manager[1739:1103] Start detecting Vagrant machines
2014-05-13 08:23:36.158 Vagrant Manager[1739:1103] Finish detecting Vagrant machines
2014-05-13 08:24:47.348 Vagrant Manager[1739:707] runVagrantAction: [33a07309-c057-4b81-a414-0cab4118ba7c] cd '/Users/xxx/protobox' && vagrant up
2014-05-13 08:25:14.781 Vagrant Manager[1739:7d0f] Start detecting Vagrant machines
2014-05-13 08:25:14.909 Vagrant Manager[1739:7d0f] Finish detecting Vagrant machines

from vagrant-manager.

Jan0707 avatar Jan0707 commented on August 23, 2024

Same issue here:

VirtualBox 4.3.8
Vagrant 1.5.4
OS X 10.9.2

from vagrant-manager.

peternijssen avatar peternijssen commented on August 23, 2024

I have the issue also:

VirtualBox 4.3.8
Vagrant 1.6.1
OS X 10.9.2
Vagrant Manager 1.4.2

from vagrant-manager.

robjmills avatar robjmills commented on August 23, 2024

Just using standard synced folders, like:

config.vm.synced_folder "~/Clones/", "/home"
config.vm.synced_folder "./data", "/data" 

Tried the debug build, and tried adding a bookmark while it was running with this output:

5-13 09:17:39.842 Vagrant Manager[10876:d603] Start detecting Vagrant machines
2014-05-13 09:17:39.970 Vagrant Manager[10876:d603] Finish detecting Vagrant machines
2014-05-13 09:17:43.402 Vagrant Manager[10876:707] runVagrantAction: [f5765cbf-be2a-4b28-9a7f-360bac22d05b] cd '/Users/robm/github-repos/sitem_vagrant' && vagrant up
2014-05-13 09:17:44.853 Vagrant Manager[10876:2113] Start detecting Vagrant machines
2014-05-13 09:17:44.981 Vagrant Manager[10876:2113] Finish detecting Vagrant machines

from vagrant-manager.

nightmare-rg avatar nightmare-rg commented on August 23, 2024

I updated from Vagrant 1.5 to Vagrant 1.6.1 and vagrantmanager detect no vm as running. With Vagrant 1.5 everything works.

from vagrant-manager.

robjmills avatar robjmills commented on August 23, 2024

Interesting, a recent ticket #8 (comment) mentions the new vagrant global-status command in 1.6. When I run this on my machine I get the following output:

id       name   provider state  directory                           
--------------------------------------------------------------------
There are no active Vagrant environments on this computer! Or,
you haven't destroyed and recreated Vagrant environments that were
started with an older version of Vagrant.

I wonder if this highlights the issue we're all having here - old vagrant boxes?

from vagrant-manager.

ramondelafuente avatar ramondelafuente commented on August 23, 2024

I think not, as the new vagrant global-status is not yet used in this version.

Nevertheless, I just recreated the box; it now shows up in global-status but I still never see it as "up" in vagrant manage.

from vagrant-manager.

ramondelafuente avatar ramondelafuente commented on August 23, 2024

Ok, W00T, I now have one running box. Does Vagrant Manage rely on the virtualbox guest additions? Because I solved an issue with that and suddenly the new box showed up.

from vagrant-manager.

robjmills avatar robjmills commented on August 23, 2024

@ramondelafuente what issue did you solve?

from vagrant-manager.

ramondelafuente avatar ramondelafuente commented on August 23, 2024

When I destroyed the box, a new basebox was used because that was updated in the meantime. The new basebox could not be started because of a missing symlink to the Virtualbox Guest additions on the guest (a problem we created, we make our own baseboxes).

I took two steps:

  1. I changed the /vagrant share to type: "nfs". I could now start the box, but not see it in Vagrant Manage.
  2. I fixed the missing symlink and started the box with the default /vagrant share, and now the box shows up in Vagrant Manage.

from vagrant-manager.

ramondelafuente avatar ramondelafuente commented on August 23, 2024

Hmm - there seems to be a lag between starting boxes and seeing them in the list; perhaps I am barking up the wrong tree with the Guest additions.

I now have two working boxes, where it took a full minute to see it as "running" in Vagrant Manage after starting the box. But it does work now. I will try destroying and re-creating more boxes later tonight.

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

Vagrant Manager does rely on the "/vagrant" folder mapping to tell the difference between Vagrant machines vs other VirtualBox machines. For NFS machines, it checks the /etc/exports file since they do not have a "/vagrant" folder mapping. This issue may be related to that, but it looks like the output of VBoxManage posted by some users has the correct folder mappings, but the machines are still not showing up. I've built another debug build that will output more information to help troubleshoot this issue.

https://www.dropbox.com/sh/3jv9l71tz8nvo2h/AABZDhsL-wLwGiV2UQWNQ_sba

If you can run that debug version of Vagrant Manager, a file should appear in your Documents folder called vagrant-manager-TIMESTAMP.log (TIMESTAMP will be a string of numbers). Send that file to [email protected], or post it on pastebin.com or something similar, rather than posting it here since it will be a pretty long file. That should help to narrow down what is causing this issue.

We are planning on taking advantage of the new global-status command available in Vagrant 1.6, but we would still like to be able to support older Vagrant versions, so I'm interested in getting to the bottom of what is happening here.

from vagrant-manager.

amitailanciano avatar amitailanciano commented on August 23, 2024

I've put together a test build that should address this issue, please download https://www.dropbox.com/s/px33c220zotd0k6/Vagrant%20Manager%201.4.3%20BETA.app.zip and post your results

from vagrant-manager.

mikebell avatar mikebell commented on August 23, 2024

Not having any luck with the latest beta version, I also don't have the log file in my Documents folder, does this build have any of the output?

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

@mikebell
@ramondelafuente
@nightmare-rg
@robjmills
@peternijssen
@Jan0707
@tcsehv

We have a new build that will hopefully resolve all of the issues in this thread. Can you guys try this build and let us know the results?

https://www.dropbox.com/sh/09soyrkhhj87hvh/AAC2xspJWhxbq8wwENoaHGGYa

from vagrant-manager.

Jan0707 avatar Jan0707 commented on August 23, 2024

Download link does not work for me. It returns a *.app.zip file which cannot be unarchived ..?

from vagrant-manager.

tcsehv avatar tcsehv commented on August 23, 2024

I think I found the problem. I don't use /vagrant as a mount point for the shared folders. The beta build doesn't solve it.

from vagrant-manager.

amitailanciano avatar amitailanciano commented on August 23, 2024

this issue has been fixed by release 1.4.3 (269a17b)

@tcsehv that is on our roadmap to address

from vagrant-manager.

peternijssen avatar peternijssen commented on August 23, 2024

I still have the problem with 1.4.3 :(

Edit: I downloaded the above build to see if I could get some debugging info. However, renaming the file from .zip to .app leads to the fact that I get a message that I cannot use the classic environment.

from vagrant-manager.

chriswayoub avatar chriswayoub commented on August 23, 2024

Send an email to [email protected] if you'd like to troubleshoot this issue offline. I can put together a debug build for you and send it there if necessary.

from vagrant-manager.

bhanu-prakashl avatar bhanu-prakashl commented on August 23, 2024

i have the issue like this below and vagrant up doesn't work....
There are no active Vagrant environments on this computer! Or,
you haven't destroyed and recreated Vagrant environments that were
started with an older version of Vagrant.

is there any version compatibility issues ?

from vagrant-manager.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.