Preconditions
VMware vSphere 6.5
Windows Server 2016
What I did:
I have installed windows server on ESXi.
I'm trying to install vCenter Server Appliance(VCSA) from the above windows server using vcsa-ui-installer(win32).
Expected Behaviour
The progress bar in stage 1 progresses.
Actual Behaviour
The proglas bar in stage 1 stops at 0%.
I checked it out.
'Deploy VM' task fails due to timeout
A vCenter Server VM is registered on ESXi, but it is deleted after a timeout.
There are no noticeable error messages in the VCSA installation log.
What can I do to resolve this behavior?
You have to make sure that the windows server you are installing directly accesses the ESXi server. If there is no DNS in your environment, you can solve the problem by typing IP address in system name section in vcenter setup.
When installing over Windows, pay attention to IP and name resolution issues. I think you have a problem with DNS.
https://www.tayfundeger.com/vcenter-server-appliance-vcsa-6-5-kurulumu-bolum-1.html
https://www.tayfundeger.com/vcenter-server-appliance-vcsa-6-5-kurulumu-bolum-2.html
Related
I have installed the latest versions of Virtualbox v.5.2.6 and Vagrant v.2.0.1 on the windows machine with the Intel-Core-i5-4210U-Processor #1.70Ghz 2.40Ghz. I have added the homestead box by running the command:
vagrant box add laravel/homestead
But, on running the vagrant up it runs fine until this point:
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within the
configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that Vagrant
had when attempting to connect to the machine. These errors are
usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes. Verify
that authentication configurations are also setup properly, as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
On running the vagrant ssh-config I get:
Host homestead-7
HostName 127.0.0.1
User vagrant
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile C:/Users/MyUser/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
ForwardAgent yes
I have looked around and tried out different things, among others, to uninstall and install again both vagrant and virtualbox, but couldn't find any solution. How can I get this working?
I made VM Ubuntu 16.04 with one network adapter "network bridge" and second adapter "internal network". ClickHouse DBMS installed by default.
Test call within slave Ubuntu curl 'http://localhost:8123/' returns Ok.
But the same call from master Windows host returns nothing :(
Telnet and browser from master OS on http://assignedIP:8123 returns ERR_CONNECTION_REFUSED.
At the same time pings slave Ubintu from master OS and opposite are successful.
How to setup VM's network properly to be able to call ClickHouse on port 8123 from master OS?
Found it!
Have to change
<listen_host>::1</listen_host>
to
<listen_host>::</listen_host>
in /etc/clickhouse-server/config.xml
Could you please check Unbutu firewall status. If it is up, bring it down and try.
I installed proxmox 4.1 on virtual box and after installationI received the following :
welcome to the proxmox virtual environment.please use your web browser to configure this server - connect to:
https://192.168.56.101:8006
but while trying this https://192.168.56.101:8006 in the browser it is not working
can someone advice !
Check if the VirtualBox Machine Network Adapter is in Bridge Mode. And check that your host and the vm are in the same IP rank (Ex: Windows: 192.168.1.50 & Proxmox: 192.168.1.70)
Your network adapter in VirtualBox has been set to host-only. If you want to connect to it with your PC you'd better set-up bridged networking.
Also when you've did that, change your /etc/hosts file on the Proxmox hosts so that it won't give you any errors while setting up the webserver or any optional clusters.
Okay so I have my actual laptop which has vmware player installed. I am running lubuntu as a virtual machine and I installed django on the virtual machine and am testing my app so I did python manage.py runserver and I can access the app by visiting 127.0.0.1:8000 from my VM, however, If I go to 127.0.0.1:8000 from the actual computer (not the VM), it says 'chrome could not connect to 127.0.0.1:8000'.. Any idea how to fix it?
You can try running the server on 0.0.0.0
python manage.py runserver 0.0.0.0:8000
The IP address 0.0.0.0 means "all IP addresses on the local machine" (or all IPv4 addresses on the local machine).
Next, you will need the ip address of your VM. Visting http://<ip_address_of_vm>:8000 on other computers should access the django development server on your VM.
Note: If your VM only has an internal IP (e.g. 192.168.x.x) then only computers on the same network can visit the VM.
I was able to get #Kerberos answer to work. (not enough points to comment so I'm adding it as a seperate answer).
I am running Ubuntu 12.04 LTS in a guest OS in VMWare. The host laptop is running Windows 8.
As mentioned by Kerberos, in VMWare, go to Player ==> Manage ==> Virtual Machine Settings...
On the Hardware tab, select Network Adaptor, then select the radio button for Bridged: Connect directly to the physical network. Select OK
In the VM, the network connection information should now have the same IP address of the host OS internet connection. In my case: 192.168.1.141 (yours will vary).
In the VM, start Django using python manage runserver 192.168.1.141:8000
Using this method, I am able to access the webserver running in the VM at this IP address from within the VM, from host machine, and from other systems on the same 192.168.1.xxx network.
to access virtual machine (guest) from outside the host computer, you have to set the guest network mode to bridge
Bridge-mode connects the guest to the actual network so that other machines can connect to it
WHAT AM I TRYING TO DO
Trying to setup a VCAP on a UBUNTU SERVER VM on my machine by following the steps mentioned at https://github.com/cloudfoundry/vcap/
WHAT IS THE ISSUE
Things seemed to be working fine but at step5 (https://github.com/cloudfoundry/vcap/#step-5-validate-that-you-can-connect-and-tests-pass) I got an exception while trying to execute the following command - vmc target api.vcap.me
The exception that I see on my console is:
Host is not available or is not valid: 'http://api.vcap.me'
Would you like see the response? [yN]: y
HTTP exception: Errno::ECONNREFUSED:No connection could be made because the target machine actively refused it. - connect(2)
ANY OTHER RELEVANT INFO
For some earlier experiments I was using MicroCloud (provided as a download by CloudFoundry). I am having issues in pointing my VMC to this Microcloud as well.
On the Micro Cloud console I see the following message:
To access your Micro Cloud Foundry instance, use:
vmc target http://api.agoel.cloudfoundry.me
When I run this vmc command from the Ruby Command Prompt setup on my Windows7 I get following error:
Host is not available or is not valid: 'http://api.agoel.cloudfoundry.me'
Would you like see the response? [yN]: y
HTTP exception: Errno::ETIMEDOUT:A connection attempt failed because the connected party did not properly respond after a period of time, or
ost has failed to respond. - connect(2)
WHATS DOES VMC INFO DISPLAY
I ran vmc info command on command prompt. It displayed following info
VMware's Cloud Application Platform
For support visit support DOT cloudfoundry DOT com
Target: http:// api DOT cloudfoundry DOT com (v0.999)
Client: v0.3.18
User: ankitgoel1987#gmail.com
Usage: Memory (1.1G of 2.0G total)
Services (2 of 16 total)
Apps (2 of 20 total)
MY SETUP DETAILS
Windows7 running on 4GB RAM
Microcloud from Cloudfoundry already installed (this was done as part of some other exercise. My recent experiment requires me to setup a Ubuntu server with VCAP on it. So this MicroCloud should not really matter)
vmc 0.3.18 (installed on my Windows7 machine)
ruby 1.9.2p290 (2011-07-09) [i386-mingw32]
add in your hosts files the following entry:
IP_of_ubuntu_server vcap.me api.vcap.me
If you want to avoid having to edit your hosts file every time you deploy a new app and depending on what virtualisation platform you are using you may be able to forward all traffic on port 80 for your own computer on to the VM.
*.vcap.me is set to resolve to 127.0.0.1 so this is an ideal solution. To do this you should set the network settings to NAT rather than Bridged (maybe you have done this already) and then set port 80 to forward to the IP of the guest OS. In VMWare Fusion for example this is as simple as editing a settings file.