Submitted by hswong3i on Mon, 2012-04-30 08:20
This mini-HOWTO will guide you though installing Ubuntu Server 12.04 with minimal setup on Virtualbox 4.1.x.
Before start, you should first install latest Virtualbox from https://www.virtualbox.org/wiki/Downloads, including:
- VirtualBox platform packages
- Oracle VM VirtualBox Extension Pack
Also, download the latest Ubuntu Server 12.04 install CD from http://releases.ubuntu.com/12.04/
Submitted by hswong3i on Sat, 2011-02-05 17:51
NOTE: Refer to my legacy VirtualBox 3.1 + iSCSI on Debian Lenny mini-HOWTO, its time to update as VirtualBox 4.0.2 + Debian Squeeze.
VirtualBox 4.0.2 coming with feature "Teleportation" (aka live migration) since Virtualbox 3.1. With live migration you can port a running client from one host to another, without any service down time. It is for sure a enterprise-ready killer function (well... even KVM and QEMU already support that for some days before...). Therefore the next question should be: any pre-requirement for using VirtualBox's live migration? According to official user manual:
The two virtual machines on the source and the target must share the same storage (hard disks as well as floppy and CD/DVD images). This means that they either use the same iSCSI targets or that the storage resides somewhere on the network and both hosts have access to it via NFS or SMB/CIFS.
IMHO, iSCSI should be the best choice in this case: it is simple in architecture and faster when compare with using NFS/SMB/CIFS, it is native and simply supported by some SOHO SAN/NAS, and you may even share an entire hard disk to your virtual client machine as like as normal physical disk without abstract with NFS/SMB/CIFS (personally, this is my original and main target for using iSCSI).
Any drawback? Yes, for sure: you will not able to work with snapshot. This is because snapshot only work with *.vdi or *.vmdk
This mini-HOWTO with guide you though the installation of iSCSI target on Debian Squeeze, some demo setup for sharing your physical hard disk or a single raw file image with iSCSI, and howto setup an iSCSI hard disk within VirtualBox 4.0.2.
Submitted by hswong3i on Thu, 2010-12-23 07:37
Well the first impression of VirtualBox 4.0 (http://www.virtualbox.org/wiki/Changelog) is not bad: better UI, updated MB/HD/Audio chipset, EFI support, multiple connection with RDP, etc. BTW, it is also giving me some troubles:
Submitted by hswong3i on Tue, 2010-10-19 15:45
This mini-HOWTO will guide you though the basic installation procedure of VirtualBox Guest Addition on Fedora 13. It is a bit different with that of Debian guest but most likely similar.
P.S. Here I will assume you have a basic installation of Fedora 13 with graphic mode. Nothing else special for the initial installation.
Include online yum repository
Once Fedora 13 installation completed, login as your default user.
Go to "System -> Administration -> Add/Remove Software".
Submitted by hswong3i on Wed, 2009-12-23 17:08
NOTE: Please refer to VirtualBox 4.0.2 + iSCSI on Debian Squeeze mini-HOWTO for updated information.
VirtualBox 3.1 coming with a new feature "Teleportation" (aka live migration). With live migration you can port a running client from one host to another, without any service down time. It is for sure a enterprise-ready killer function (well... even KVM and QEMU already support that for some days before...). Therefore the next question should be: any pre-requirement for using VirtualBox's live migration? According to official user manual:
The two virtual machines on the source and the target must share the same storage (hard disks as well as floppy and CD/DVD images). This means that they either use the same iSCSI targets or that the storage resides somewhere on the network and both hosts have access to it via NFS or SMB/CIFS.
IMHO, iSCSI should be the best choice in this case: it is simple in architecture and faster when compare with using NFS/SMB/CIFS, it is native and simply supported by some SOHO SAN/NAS, and you may even share an entire hard disk to your virtual client machine as like as normal physical disk without abstract with NFS/SMB/CIFS (personally, this is my original and main target for using iSCSI).
Any drawback? Yes, for sure: you will not able to work with snapshot. This is because snapshot only work with *.vdi or *.vmdk
This mini-HOWTO with guide you though the installation of iSCSI target on Debian Lenny, some demo setup for sharing your physical hard disk or a single raw file image with iSCSI, and howto setup an iSCSI hard disk within VirtualBox 3.1.
Submitted by hswong3i on Thu, 2009-07-30 13:26
Background: I run multiple VirtualBox client within a single server. Each VirtualBox client coming with its *.vdi file for sure. Accidentally I run rm to them during migration and backup, and so some *.vdi are lose. I need to rescue them.
Most important action for rescue: unplug the server power and shut-it-down IMMEDIATELY! Try not to preform ANY write action to the target harddisk ANYMORE!
Submitted by hswong3i on Thu, 2009-02-26 16:33
There are some different between VMware network connection with VirtualBox: for VMware, all clients will able to have interconnection in both NAT and internal mode, where clients will locate within save subnet; in case of VirtualBox, all NAT network will be handled individually, where only internal mode can communicate with each others (with same "network name", which will explain later). So how to build a effective internal network for your virtual clients? The main tips is: use 2 network adapters for your clients. Let's review some background for VirtualBox's network setup.
Submitted by hswong3i on Mon, 2009-01-26 05:07
VirtualBox is an x86 virtualization software package, originally created by German software company innotek, now developed by Sun Microsystems as part of its Sun xVM virtualization platform. This mini-HOWTO will guide you though VirtualBox 2.1.0 installation on Debian Lenny/sid.
Submitted by hswong3i on Fri, 2009-01-23 11:58
There is a new release of
VirtualBox 2.1.2 for Debian Lenny on today (
Changelog for 2.1.2), and so my server need upgrade. Here is some tips for a smooth server upgrade procedure:
- Shutdown down all of your virtual clients. It is because the virtual client profile and client daemon are both required to upgrade. We will get it done after server upgrade.
- Run the following command for packages upgrade:
Submitted by hswong3i on Tue, 2009-01-06 19:07
Since I am now testing VirtualBox performance, I need to clone existing guest image for multi-testing. This mini-HOWTO will guide you though the procedure for cloning a guest storage file for a new guest, under MS Windows host.
When following the official guideline and document, using
VBoxManage clonehd command for disk clone, the result image is ALWAYS not functioning. Finally I figure out that a non-documented internal command is required:
VBoxManage internalcommands sethduuid.
Recent comments