I've stumbled on this issue after installing and configuring cloudstack 4.4.
I'm trying to setup cloudstack wiht VMWARE hypervisor, i've followed all the step from the cloudstack documentation, but I have 2 issues.
can not start the System Storage VM it fails?
When I add a template or ISO on cloudstack the ISO does not upload?
I will try to explain the configuration I have:
cloudstack 4.4 is installed on CentOS 6.5
Hypervisor VMware esxi5.5
VCenter server
Primary storage iSCSI vmfs
Secondsry NFS (seperate from cloudstack)
If anyone can help me or point me to what the issue might be I would greatly appreciate it. Thanks!
On your Management Server, run one of the following cloud-install-sys-tmplt command to retrieve and decompress the system VM template. If your secondary storage mount point is not named /mnt/secondary, substitute your own mount point name.
/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/
secondary -u http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova -h vmware -s -F
When the script has finished, unmount secondary storage and remove the created directory
umount /mnt/secondary
rmdir /mnt/secondary
Related
I have google cloud VM with Ubuntu installed along with various services and libraries. I need to make a similar bootable VM with the same OS and all the data, libraries etc in the already configured VM. How do I clone the VM with these requirements?
I tried to create an image from the already existing VM and could not SSH into it.
So I retraced my installations step by step trying to figure out which step is breaking the image.
I created an Ubuntu(18.04) VM and used that to create an image. The instance I created using the image did allow me to SSH into.
Next installed Ubuntu desktop and xorg server and created an image after that. Using that image, I created a new VM and tried to SSH into it.
But unfortunately, the SSH connection could not be established. So I think it is these installations that are causing the error if it is not some sort of system error.
Below are the exact commands I ran to install these after creating an Ubuntu(18.04) VM:
sudo passwd username
sudo su -
passwd
apt update && apt upgrade -y
adduser username root
adduser username admin
adduser username sudo
apt-get install ubuntu-desktop -y
apt-get install xserver-xorg-video-dummy
nano /etc/X11/xorg.conf
and pasted the following into the .conf file
Section "Device"
Identifier "Configured Video Device"
Driver "dummy"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
HorizSync 31.5-48.5
VertRefresh 50-70
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1600x900"
EndSubSection
EndSection
After this state, I created the image using which I could not instantiate a VM that I could SSH into.
Since you have your VM ready and running; backup your image as per this GCP document. Follow the guidelines before you begin the process which were mentioned in the document like updating Google cloud CLI setting default region and zone and for general image guidelines.
Few networking features may require guest operating system mode. You can also check how to export a custom image to cloud storage.
You can also consider the Snapshot Approach.
Follow this process in order to create the image exactly as the one you have already set up and you know is working correctly. As you may already know, this is a custom image so they are available only to your Cloud project. You can create a custom image from boot disks and other images if you would like also. Then, use the custom image to create an instance.
I will also suggest you to give a look at this document which would give you a deeper knowledge on the task.
Regards,
Just spin up a new container from a disk snapshot, if you need an exact copy. And if you cannot SSH, you may either not have a SSH public key provisioned, no external IP assigned, or :22 closed.
gcloud ssh always works. One can as well provision project-wide SSH keys, which all VM in the project will inherit then. The documentation below: About VM metadata explains this all in detail.
My personal favorite are rather startup scripts, which describe the configuration, instead of copying it.
And it's not so difficult to get started with these: cat ~/.bash_history > rocky8_startup.sh. In a software-defined data-center, it might make sense to use software-defined configurations (one simply cannot alternate the installation per VM instance, when starting with a disk snapshot).
xserver-xorg-video-dummy is questionable, because one can enable display device -but unless recording the screen, this driver might still suffice; eg. for VNC sessions.
I'm trying to move an old Win2008 server from KVM to VMware ESXi 6.7.
I realize the Win2008 VM is old and beyond EoS but need to keep this in place for now and is in a VLAN that is not internet accessible.
I tried to follow recommendations from Convert qcow2 to vmdk and make it ESXi 6.0 Compatible and steps I found on the web:
Shutdown VM on KVM
qemu-img convert -p -f qcow2 -O vmdk win2008.qcow2 win2008.vmdk using qemu v4.2.1
vmkfstools -i win2008.vmdk -d thin win2008_v2.vmdk on the VMware host
Attach the newly created win2008_v2.vmdk file to a newly created guest with default settings
However I'm stuck with a Windows Error Recovery: Windows failed to start. A recent hardware or software change might be the cause. screen at boot up.
I tried to use some conversion options like qemu-img convert -p -f qcow2 -O vmdk -o adapter_type=lsilogic,subformat=streamOptimized,compat6 win2008.qcow2 win2008.vmdk and tried moving between the 3 available scsi controllers (LSI Logic SAS, LSI Logic Parallel, VMware Paravirtual) to no avail.
When I boot the guest in Safe mode, I see a bunch of sys files get loaded properly until it's stuck after Loaded: \Windows\system32\drivers\crcdisk.sys.
Does anyone have an idea on how to move this guest properly? Any other conversion options to try? Driver install on the running guest (in KVM) first?
Note I'm not running vCenter.
Do you try to use VMware Converter Tool ? I think that is the easy way to move your server to VMware. You can download the tool it is free.
https://www.vmware.com/products/converter.html
When attempting to create a VM on EC2 with an Ubuntu 16.04 AMI ami-835b4efa, I see the following:
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Error creating machine: Error running provisioning: Unable to verify the Docker daemon is listening: Maximum number of retries (10) exceeded
This issue goes away if I create a VM using Ubuntu 14.04 with AMI ami-fc4f5e85. I've seen this in the past and thought it was just a fluke. It's happened enough times today repeatedly that I'm thinking there's some issue here. Any thoughts on why the above fails with Ubuntu 16.04? I can use 14.04 for now but would like to upgrade in the not too distant future and still use Docker Machine for managing my VMs.
I downloaded the latest version of Docker Toolbox for OSX today to take that off the table as a possible issue.
Check if this is similar to issue 2533 where:
What worked for me was adding a --amazonec2-ami param and setting it to
aws's Ubuntu 14.04 LTS image: ami-fce3c696
Since you are usiing Ubuntu 16.04, check the Amazon EC2 AMI Locator to try a similar option with the right AMI. It can depend on your region.
what version of docker and docker-machine? Whats in the logs on the machine? If docker-machine version 0.12.0, build 45c69ad and docker version 17.06.0-ce then its probably this issue in docker-machine: https://github.com/docker/machine/issues/4156
How can I compile and run Libvirt-snmp on VMware Vsphere ESXi? Can somebody guide with step by step procedure.
I tried to followed steps mentioned on Libvirt Website
but I guess they are for Linux distribution. Because I could not execute ./configure command.
After searching on Google I found a similar question which tells that I need to create a VIB and than install that VIB. Now I have no idea about creating VIB. Can somebody please guide me on this.
Can somebody guide with step by step procedure.
As a workaround
1. Have a Linux VM and create a nfs share
2. Install and configure the required tool. [in your case, the libvirt] in the linux VM in the nfs share. Note the export path and variables
3. Mount the nfs share as NAS volume in ESXi
4. Give a soft link to the mounted nas volume to /usr/bin in ESXi
5. Create corresponding directory tree under /usr/local/lib as required by the tool and link them too to the nfs share.
And you are good to run the tool.
Now I have no idea about creating VIB
Simply put, VIB is VMware Infrastructure Bundle which is the allowed method to push pgms inside ESXi. You can use ar command to create a vib from a rpm and use vib author too to push the module inside ESXi.
Hope it helps
I have a question about asterisk, I know that I can install asterisk on EC2, but my questions is:
Its possible install AsteriskNOW on Amazon EC2? if not, why? and where its the best possible server or solution for install this
thanks
AsteriskNow is a complete distribution based on CentOS available as an ISO file. There doesn't appear to be an EC2 AMI available for it so you would have to build an image yourself.
Here's an overview of the process for Oracle Linux which boils down to:
Install AsteriskNow onto a VirtualBox or VMWare instance locally.
Configure all the EC2 specifics (This is the fiddly bit)
Export that virtual machine as a VMDK.
Copy the VMDK to S3
Import the VMDK to an EBS volume and launch on Amazon EC2.
Before you export you will have to make sure AsteriskNow has a kernel that supports EC2. In CentOS this would be the Xen kernel but I don't know if Asterisk would supply one, which means compiling. The PV-GRUB docco also covers a lot of what can and can't be used on EC2. If it doesn't work out of the box it will take some Linux smarts to figure it all out.
It will probably take a number of exports/imports to get it running. Once you have it up on EC2 you can turn that instance into an AMI to quickly create clones in the future without going through the whole export/import process.
can you not just download the ISO directly?
ubuntu#ip-172-31-14-19:~/iso$
ubuntu#ip-172-31-14-19:~/iso$ wget -v https://downloads.asterisk.org/pub/telephony/asterisk-now/AsteriskNow-1013-current-64.iso
--2017-11-17 05:52:53-- https://downloads.asterisk.org/pub/telephony/asterisk-now/AsteriskNow-1013-current-64.iso
Resolving downloads.asterisk.org (downloads.asterisk.org)... 76.164.171.238, 2001:470:e0d4::ee
Connecting to downloads.asterisk.org (downloads.asterisk.org)|76.164.171.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1343909888 (1.3G) [application/x-iso9660-image]
Saving to: ‘AsteriskNow-1013-current-64.iso’
AsteriskNow-1013-curr 100%[======================>] 1.25G 1.79MB/s in 9m 54s
2017-11-17 06:02:48 (2.16 MB/s) - ‘AsteriskNow-1013-current-64.iso’ saved [1343909888/1343909888]
ubuntu#ip-172-31-14-19:~/iso$
https://downloads.asterisk.org/pub/telephony/asterisk-now/