Currently Viewing Posts Tagged virtualbox

Another way to move Virtualbox VDI to Proxmox VE

There is another way to do the importing Virtualbox VDI to Proxmox VE 3.5-8.

Similar to my previous post.

Step 1, Copy the VDI into the Proxmox VE host

No need to covert the VDI file to RAW format. Just copy the vdi file into the local folder. For me, I will just put it at /root/testing.vdi

Step 2, Create a new VM in Proxmox

On the “OS” tab, choose “Do not use any media”

On the “Hard Disk” tab, choose “local-lvm”, as storage, Disk size is any size you want, for example, 8GB. Format, choose “Raw disk image (raw)”, On CPU and Memory, choose the same as the Virtualbox settings.

Confirm to create the new VM.

Step 3, Detach and Remove the Hard Disk

Say my VM ID is 109, choose Virtual Machine 109, Hardware, Hard Disk, choose “Detach” button.

Detach the Hard Disk

At this point, the hard disk will be listed as “Unused Disk.” It still exists but is not attached to the system. To destroy it completely, select the Unused Disk and click Remove again; and confirm when prompted.

Continue reading “Another way to move Virtualbox VDI to Proxmox VE”

Move Virtualbox VDI to Proxmox VE System

I have some Virtualbox virtual machine on my desktop. Now I have Proxmox VE 5.3-8 installed on a separate machine. So I would like to move the VM to Proxmox.

Let me list the existing installation.

  • My Desktop, Windows 10 Pro version 1809.
  • Virtualbox 6.0.4 r128413
  • Guest VM inside of Virtualbox is Ubuntu 18.04 with 1G memory and 20GB disk space.
  • Proxmox VE 5.3-8, VM and LXC are stored in the local-lvm

 

Step 1, Located the vdi file and convert it to RAW format

Virtualbox vdi file location

Check the settings of the virtual machine, storage, and located the location of the vdi file. Mine is in the d:\Virtualbox VM\

Then open a command prompt window, enter the following command to convert the vdi file to raw image file.

d:
cd "program files\oracle\virtualbox"
vboxmanage clonehd --format RAW "d"\virtualbox vm\ubuntu 18.04 (122)\ubuntu 18.04.vdi" d:\testing.img

After a while the new image file is ready. The time depends on the size of your VM. Maybe 10 minutes or half an hour.

Converting

Continue reading “Move Virtualbox VDI to Proxmox VE System”

How to Solve the Virtualbox Bridged Adapter Problem

It is a problem I met since Virtualbox 5.0.4. I can not make the guest OS communicate with Internet or Host, even the IP address is correct. It is similar to the Virtualbox bug of bridged connection, which is fixed in Virtualbox 5.0.6.  So, installed the latest version of Virtualbox on my Windows 7 64bit.

The guest OS is Ubuntu 14.04 64bit. I upgrade my installation to Virtualbox 5.0.6. So the following are based Virtualbox 5.0.6.

When I tried to run yum update to do a update, it can not connect to the repos. And the wired thing is it is using IPv6 address. And actually I don’t have IPv6 implement in my LAN.

The network adapter information as below, looks normal.

ifconfig-info

The first time I run the command of yum update, it said another app is currently holding the yum lock. I don’t know why, and saw no process in memory by top command. So I just delected the lock file /var/run/yum.pid.

locked-by-yum-pid

Continue reading “How to Solve the Virtualbox Bridged Adapter Problem”

VirtualBox resize hard disk error: VBOX_E_NOT_SUPPORTED

There is a error when I tried to resize the VirtualBox hard disk, or vdi file.

Progress state: VBOX_E_NOT_SUPPORTED

VBoxManage.exe: error: Resize hard disk operation for this format is not implemented yet!

 

The command I used to resize vdi file is :

vboxmanage modifyhd "e:\virtual_disk.vdi" --resize 20000

The original size is 8Gb. I want to increase it to 20GB.

 

I did a lot of search and found the problem and solution.

The format of VDI file is not supported by resize function.

Continue reading “VirtualBox resize hard disk error: VBOX_E_NOT_SUPPORTED”

Virtualbox 4.3.14 errors

I installed the latest version of Virtualbox on the official web site.

It is virtualbox 4.3.14-95030. When I installed and try to run the program, it displayed the following errors.

Error In supR3HardenedWinReSpawn

 

VMBox Error

 

If you met same errors as me, go to download the Virtualbox 4.3.15

Download link

 

Here is the details of the problem.

Virtualbox 4.3.14 conflicts with anti-virus packages.

Oracle VM VirtualBox 4.3.10

VirtualBox is a must have on my Windows 7.  I installed Centos 6 32bit and 64bit testing guest system in it. And also retired Windows XP. So, keep Oracle VM VirtualBox updated is very important. Here is a new release of VirtualBox 4.3.

  • VMM: more work on improving the emulation of certain MSR registers on certain host CPUs (e.g. bugs #12734, #12736, #12744, #12748, #12686, #12770)
  • VMM: fixed single-stepping for real-mode guests (VT-x without unrestricted guest execution) and some I/O instructions (bug #12636)
  • VMM: fixed a potential problem with COW pages if nested paging is not available
  • GUI: Mac OS X: experimental native full screen support for Mountain Lion and Mavericks (bug #12292)
  • GUI: Mac OS X: removed the mini-toolbar minimize button which doesn’t work under Mac OS X full screen mode anyway
  • GUI: experimental HID LEDs synchronization for Windows and Mac OS X hosts: fixed keyboard re-synchronization if the feature is disabled (as done by default; bug #12758)
  • GUI: fixed a potential crash when opening the preferences menu (bug #12862)
  • OVF: fixed a crash of the VirtualBox Manager when re-starting guest export (bug #12586)
  • 3D support: several fixes
  • HGCM: fixed a problem with saved states which could cause several guest misbehavior after a VM was started from a saved state
  • Storage: fixed a bug preventing to compact differential snapshots under certain conditions
  • VBoxSVC: fixed a segmentation fault on Linux hosts if a very long path exists under /dev (bug #12760)
  • API: fixed guest misbehavior under certain conditions if a storage medium was attached or removed at VM runtime
  • Windows installer: make the –silent parameter work again (bug #12764)
  • Mac OS X Networking: prevent local traffic (VM-to/from-host) from leaking to wire (bug #12750)
  • Windows Additions: fixed the environment for guest processes (4.3.8 regression; bug #12782)
  • Windows Additions/WDDM: fixed divide by zero exception with multiple guest screens under certain conditions
  • Windows Additions/WDDM: fixed crashes with 2D video acceleration enabled (4.3.8 regression; bug #12745)
  • Linux Additions: install correctly on Ubuntu guest systems with a /usr/lib64 directory (bug #12513)
  • X11 Additions: fix for the VBoxClient process not exiting correctly (bug #12348) and consuming too much processor time

virtualbox

Click here to get the latest installation package at official site.

This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU

It is a strange error that I encountered installing Centos 6.4 64bit into Virtual Box.

The CPU is AMD A8-3870.  8GB Memory

Host OS is Windows 7 64bit.

VirtualBox is 4.3.6, latest version on Jan 15, 2014.

I have no problem to install Centos x86 version into this VirtualBox. Only when I tried to install the 64bit, the error stops me.

virtualbox-error

The CPU is 64bit. I did enabled the related CPU features in BIOS. I know someone has installation problem of 64bit OS just because of this.

What is the solution of this error?

Continue reading “This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU”

Chromium OS for VirtualBox

Google announced that new Ultrabook, Chromebook Acer C7 yesterday. It is $199.00, available in US and UK now.
It is the cheapest Chromebook, comparing with Samsung Chromebook from $249 to $449.
Acer C7 has Inter Core CPU, 2GB memory,3 USB ports, 1 HDMI, 1 VGA, 11.6 inch screen, 4 cell battery with 3.5 hours.
It is good choice for light book.
I am thinking about to have a try on VirtualBox. I did find the place to download at Hexxeh nightly build.
I download the virtualbox zip file. It is a image file.

Continue reading “Chromium OS for VirtualBox”

Prepare CentOS 6.3 within VirtualBox

For testing purpose, I need a CentOS 6.3. So I download CentOS DVD image. Installed it in VirtualBox as web server.
Note: The network of guest system is using bridged, which allow the guest access internet, and also allow the computer in Lan can access the guest system.
The installation is simple, no problem. I would like to share my experience I met later.
1) Prepare the network
Only lo, or loopback is active. I can not access Internet from the CentOS.
eth0 is not showing when I run ifconfig command.

Continue reading “Prepare CentOS 6.3 within VirtualBox”

VirtualBox 4.1.22 and VirtualBox 4.2 released

VirtualBox 4.1.22 is the latest maintenance release or VirtualBox 4.1.
There are following changes:
VMM: fixed a potential host crash triggered by shutting down a VM when another VM was running (only affected 32-bit hosts and 64-bit OS X hosts, 4.1 regression, bug #9897)
VMM: fixed a potential host crash under a high guest memory pressure (seen with Windows 8 guests)
VMM: respect RAM preallocation while restoring saved state.
VMM: fixed handling of task gates if VT-x/AMD-V is disabled
Storage: fixed audio CD passthrough for certain media players
USB: don’t crash if a USB device is plugged or unplugged when saving or loading the VM state (SMP guests only)
RTC: fixed a potential corruption of CMOS bank 1
Mac OS X hosts: installer fixes for Leopard (4.1.20 regression)
Windows Additions: fixed memory leak in VBoxTray (bug #10808)
After upgrade my 4.1.20 to 4.1.22, no automatic upgrade from 4.1.22 to 4.2. You have to download the 4.2 manually and install it.
VirtualBox 4.2.0 is released on 2012-09-13. It is a major update, with following new features.
Improved Windows 8 support, in particular many 3D-related fixes
GUI: VM groups (bug #288)
GUI: expert mode for wizards
GUI: allow to alter some settings during runtime
Support for up to 36 network cards, in combination with an ICH9 chipset configuration (bug #8805)
Resource control: added support for limiting network IO bandwidth; see the manual for more information (bug #3653)
Added possibility to start VMs during system boot on Linux, OS X and Solaris; see the manual for more information (bug #950)
Added experimental support for Drag’n’drop from the host to Linux guests. Support for more guests and for guest-to-host is planned. (bug #81)
Added support for parallel port passthrough on Windows hosts
Enhanced API for controlling the guest; please see the SDK reference and API documentation for more information

Continue reading “VirtualBox 4.1.22 and VirtualBox 4.2 released”

  • Archives