I followed the steps below, but I'm getting an error.
Install Virtual Box (version 5.0.0) running on Windows 7 host machine.
Install Ubuntu server version 14.04.02 on it.
git clone https://github.com/openstack-dev/devstack.git
cd devstack; cp samples/local.conf .
After that i ran ./stack.sh but came with this error after running for approx 30 minutes:
2015-07-21 20:04:18.841 | ERROR (ConnectionRefused): Unable to establish connection to 10.0.2.15:8774/v2/c199aa06389a4c8c85dffddad18fce1b/flavors/… 2015-07-21 20:04:20.433 | + exit 1 deb#Devstack:~/devstack$
Please help me in resolving the issue
Try re-running the stack. Thats the best hack i found for DevStack debugging.
You need to do some specific network settings in virtual box to overcome this error.
From the Network section, change Attached to to Bridged Adapter, Adapter Type to Paravirtualized Network (virtio-net) and Promiscuous Mode to Allow All.
Check Enable Nested VT-x/AMD-v from System > Processor .
Select USB Tablet as the Pointing Device from System > Motherboard.
Then restart the virtual machine and check ifconfig for a new IP, add it in local.conf and then try install script again.
It should work this time :-)
Related
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
I am currently following the Coral Dev Board configuration guide using a MacOS machine running Catalina as my host machine. As per the instructions, for me to use the MDT command line tools on my specific host machine I must manually configure mdt. I used the following guide step-by-step but end up with the following error when I try to connect to the board.
Waiting for a device...
Connecting to jumbo-goose at 192.168.0.78
Key not present on jumbo-goose -- pushing
It looks like you're trying to connect to a device that isn't connected
to your workstation via USB and doesn't have the SSH key this MDT generated.
To connect with `mdt shell` you will need to first connect to your device
ONLY via USB.
Cowardly refusing to attempt to push a key to a public machine.
I would greatly appreciate if someone would be able to assist me in debugging this issue. I have reflashed my device a few times so I am unsure where the issue is emerging.
On the Coral Dev Mini I had similar issues with generating ssh keys, especially when I switched from a Windows to Linux machine. The easiest was (though not as secure) is to follow these steps and allows ssh with a password. First you will need to connect with a USB cable.
https://serverpilot.io/docs/how-to-enable-ssh-password-authentication/
To edit use sudo nano /etc/ssh/sshd_config
The key is to set: PasswordAuthentication yes
Check the sha25sum of the key file transferred to the dev board is the same as on MacOS, mine didn't match i.e the cut and paste wasn't quite right. With key file transferred manually using a SD card it worked first time on mdt devices/mdt shell commands.
When I am trying to add a new Network Interface for Host only network, Virtual Box version :Version 5.0.22 r108108.
I am getting a following error:
Could not find Host Interface Networking driver! Please reinstall.
Result Code:
E_FAIL (0x80004005)
Component:
HostNetworkInterfaceWrap
Interface:
IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
Reinstall the Virtual Box and restart your system.
open virtual box -> select the default virtual machine-> setting -> network -> change host-only to bridged networking -> start virtual machine -> Open docker quickStart Terminal to connect
You must reinstall the driver.
Go to device manager, you will find an "unknown driver" missing then update it by pointing to this link:
C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf
Existing answers didn't help me, but this did:
Open the Network tab of your VirtualBox settings.
Cycle through all Adapter tabs and make sure none of them points to something non-existent, even if the adapter is disabled.
For disabled adapters, enable them, set to Not attached, then disable again.
Save.
UPD: that didn't solve it. The solution was to reinstall VirtualBox like #ArpitArgarwal suggests, but simply repairing it didn't help. What helped was:
Manually uninstall existing VirtualBox.
Install VirtualBox, starting the installer with admin privileges.
1.Open Virtual Box with Run as administrator. Then it showing below snapshot error: 0x80004005 belongs to Failed to open a session for the virtual machine. Check with this error correct or not.
http://commandstech.com/how-to-resolve-failed-to-open-a-session-for-the-virtual-machine-error-code-0x80004005/
5.Now, the issue may be solved. If an issue is still pending then close it Virtual Box. Then open with Headless start option. It means that Restart the Virtual Box.
In some cases, (worked for me) running and getting the latest update of vbox fix the problem. And got the Host Interface Networking driver automatically installed.
The update I run was:
VirtualBox-6.0.14-133895-Win
Follow the below settings and it will allow you to configure Host-only Adapter-
Open VirtualBox Manager
Click on "File" -> "Host Network Manager"
Click on "Create".
Now you can select "Host-only Adapter" from Network tab of a VM.
Note: Screenshot taken from VirtualBox 6.0
I'm running virtualbox 4.1 on Debian. If I try to start a VM with a bridged NIC I get this error:
error: Failed to open/create
the internal network 'HostInterfaceNetworking-eth0' (you might need to
modprobe vboxnetflt to make it accessible) (VERR_PERMISSION_DENIED).
VBoxManage: error: Failed to attach the network LUN
(VERR_PERMISSION_DENIED) VBoxManage: error: Details: code
NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole,
callee
System: Linux localhost.localdomain 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
Virtual Box Version: 4.1.18_Debianr78361
The VM starts with a NAT NIC config.
The weirdest thing is if I export this VM and import it to another user, it works. The other user I tested with was the user I usually use for running auto started virtual machines. But I cant remember doing anything special setting this user up. It is only in its own group and no others. I tried to create a new user and import the VM, but I get the same error as above. I've tried purging virtual box, and completely deleting my conf but it does not work. I just cant figure out what the diff is.
Any help appreciated.
The solution for me was to install virtualbox-4.0 from linux mint. I believe that is actually a downgrade from what in debians repos. Probably packaged different too. Still don't know how the heck I was getting the error I was getting...
sudo apt-get install -f virtualbox-4.0
sudo /etc/init.d/vboxdrv setup
Ok, here's a very short and to the point question. When trying to import a virtual PC 2004 Windows 2003 Server VM in VM Workstation 6.0.2 I'm getting an error 'unable to determine guest operating system'. Soo how to fix?
From here:
Make sure that that the VM is not currently running in VMware Server.
Make sure that VMware Server does not have a lock on the VM’s files. You have have to stop all VMware Server Services and/or reboot the (VMWare) server.
Make sure you have appropriate permissions to the VM’s files.
This is a fairly generic error from VMware Converter so I would try the following:
Step 1. Make sure you are running the latest version of VMware Converter. Updates seem to come pretty often for this tool.
Step 2. Check the VMware Converter log file. More often than not you will find the source of your problem here.