To enable the use of the kernel module for VirtualBox to users other than root you need to set permissions on the same:

chmod 660 / dev / vboxdrv
chgrp adm / dev / vboxdrv

This is sufficient until the next reboot of the linux box, if we are to preserve the permissions you need to edit:

gedit / etc/udev/rules.d/40-permissions.rule s

and add the following line:

KERNEL == "vboxdrv", GROUP = "adm", MODE = "0660"

Note: As a group adm was used, but could be any.

Needless to say that many have already made the jump to the 8:04 version of Ubuntu, and will be useful this little tips for users of VMWare and in particular users through the VMWare Server Console. Those who have tried to install the Console has most likely encountered problems with libraries not found when launching the application:

$ Vmware-server-console

/ usr / lib / vmware-server-console / bin / vmware-server-console:
/ usr/lib/vmware-server-console/lib/libpng12.so.0/libpng12.so.0:
no version information available (required by / usr/lib/libcairo.so.2)

/ usr / lib / vmware-server-console / bin / vmware-server-console:
/ usr/lib/vmware-server-console/lib/libgcc_s.so.1/libgcc_s.so.1:
GCC_4.2.0 version ` 'not found (required by / usr / lib / libstdc + +. so.6)

/ usr / lib / vmware-server-console / bin / vmware-server-console:
/ usr/lib/vmware-server-console/lib/libpng12.so.0/libpng12.so.0:
no version information available (required by / usr/lib/libcairo.so.2)

/ usr / lib / vmware-server-console / bin / vmware-server-console:
/ usr/lib/vmware-server-console/lib/libgcc_s.so.1/libgcc_s.so.1:
GCC_4.2.0 version ` 'not found (required by / usr / lib / libstdc + +. so.6)

/ usr / lib / vmware-server-console / bin / vmware-server-console:
/ usr/lib/vmware-server-console/lib/libpng12.so.0/libpng12.so.0:
no version information available (required by / usr/lib/libcairo.so.2)

/ usr / lib / vmware-server-console / bin / vmware-server-console:
/ usr/lib/vmware-server-console/lib/libgcc_s.so.1/libgcc_s.so.1:
GCC_4.2.0 version ` 'not found (required by / usr / lib / libstdc + +. so.6)

It can be easily solved with the following commands:

$ Sudo ln-sf / usr/lib/libpng12.so.0
/ usr/lib/vmware-server-console/lib/libpng12.so.0/libpng12.so.0

$ Sudo ln-sf / usr/lib/libgcc_s.so.1
/ usr/lib/vmware-server-console/lib/libgcc_s.so.1/libgcc_s.so.1

Link to original source

The process of converting an image of windows from VMware to XEN is quite fast, the obstacles are to be considered pollibili few. The most important is to identify the mapping of the disk in VMware. The possibilities are two, or as a SCSI or IDE, converting the image is possible that a Windows guest does not work more xchè hardware does not support virtual XEN, more information is available on Microsoft kb314082.

If you are sure to have a mapping to an IDE device, you can proceed to conversion. To make the conversion server "vmware-vdiskmanager" with this program will get a VMWare VMDK file used for conversion. This tool is present in VMWare 5.0 and VMWare Server 1.0. The method is applicable with some modifications in VMWare ESX.

The file extension. Vmdk is used to describe your virtual disk to VMware:

1. The lone. Vmdk file that is rather tiny and contains a numer of lines of text describing the geometry and component series of files that comprise the whole. Vmdk.
2. The first. Vmdk file in a series of 2G segmented files named with trailing -0001 style numbering,
3. The last "snapshot". Vmdk file in a series (again, named with trailing -00001 style named files).
4. The latest "REDO". Vmdk file in a series of snapshots.

There is more to say about the file. Vmdk, but for our purposes this is enough. Now we proceed by identifying the file. "Vmx" parameter with the line:

scsi0: 0.fileName = windows2003.vmdk

or

ide0: 0.fileName = windows2003.vmdk

This is what we need to know, of course we take as the value of our parameter fileNane: "windows2003.vmdk".

$ Vdiskmanager vmware-windows2003.vmdk-r-t 0 Windows2003-flattened.vmdk

This creates a "single growable virtual disk" is stored in one file.

The next step is to convert our single. Vmdk file to a disk image with qemu-img belonging to the project QEMU.

$ Qemu-img convert windows-2003-flattened.vmdk windows2003.img

After the conversion process, you get a file windows2003.img ready to boot.

Unfortunately it is not finished here, the hard part comes now. When you restart the system will find differences of Microsoft hardware. You may then need to change Hardware Abstraction Layer (HAL).

Windows 2003, for example has 6 HALS:

Halmacpi.dll - ACPI Multi processor PC
Halaacpi.dll - ACPI Uniprocessor PC
Halacpi.dll - Advanced Configuration and PowerInterface (ACPI)
Halmps.dll - MPS Multiprocessor PC
Halapic.dll - MPS Uniprocessor PC
Hal.dll - Standard PC

Only one is selected and installed when you first install: WINDOWSSYSTEM32HAL.DLL.

If you can change C: boot.ini to specify "/ HAL = Hal.dll," if you use a different copy of the referenced DLLs is needed. In this case you need to do some tests as long as you do not find a HALS perfettaemnte working with our configuration HVM domu.

When you create your XEN configuration, it is appropriate to set 4 parameters critical to the functioning of HALS:

# Enable / disable HVM guest PAE, default = 0 (disabled)
pae = 0

# Enable / disable HVM guest ACPI, default = 0 (disabled)
acpi = 0

# Enable / disable HVM guest APIC, default = 0 (disabled)
apic = 0

# The number of CPUs to assign to this domu
vcpus = 1

To improve their chance of success is better to use "Standard PC" Hal.dll.

For MPS HALS, 1 enables APIC.

For ACPI HALS, 1 enables ACPI.

If you created a VMWare image of Windows with ACPI that was used enabling ACPI HAL. To change it to "Standard PC" Hal.dll, you must mount the image and replace the file:

# Mount-o loop, offset = $ ((63 * 512)), windows2003.img rw / mnt
# Find / mnt-name 'hal *. dll'-print
/ mnt/WINDOWS/ServicePackFiles/i386/halaacpi.dll
/ mnt/WINDOWS/ServicePackFiles/i386/hal.dll
/ mnt/WINDOWS/ServicePackFiles/i386/halacpi.dll
/ mnt/WINDOWS/ServicePackFiles/i386/halapic.dll
/ mnt/WINDOWS/ServicePackFiles/i386/halmacpi.dll
/ mnt/WINDOWS/ServicePackFiles/i386/halmps.dll
/ mnt/WINDOWS/system32/hal.dll
# Cp-f / mnt/WINDOWS/ServicePackFiles/i386/hal.dll
/ mnt/WINDOWS/system32/hal.dll
# Umount / mnt

Now you have an image "fixed" the drive, we can use the dd command to create a lvm logical volume to be used as Xen phy: VBD device:

# Ls-la win2003.img
-rw-r-r-1 root root 8589934592 2006-11-16 13:44 win2003.img
# Lvcreate-L 8G-n-Win2003 hda vg
# Dd if = windows2000.img of = / dev/vg/win2003-hda bs = 1M

The work is finished, you can start the new HVM domain.

Maintain synchronized time in vmware virtual machines is not entirely immediate, cmq remains an obligation to make good use of their virtual machines in production or to achieve satisfactory experience with any type of virtual machine.

Let us go to throw (in case we place the environment and host = Linux = Linux guest environment):

To make the split of a VMWare virtual disk just one command and a change to the config file of the virtual machine. Vmx. Everything must be done after you have stopped the virtual machine on which to operate.

Example in which a virtual disk split in many files preallocati from 2G:

vmware-vdiskmanager-r-t myos.vmdk my 3-split-pre.vmdk

After completing the operation (may be long enough) you must edit the file. Vmx, and replace the reference to the disk. Vmdk with the new one we specify, as in the example. Referring to the example above we have replaced:

scsi0: 0.fileName = "myos.vmdk with scsi0: 0.fileName =" my-split-pre.vmdk "

Example Files obtained from:

-rw --- 1 root root 2147221504 10 Jan 14:31 my-pre-split-f001.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f002.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f003.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:31 my-pre-split-f004.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f005.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:31 my-pre-split-f006.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:31 my-pre-split-f007.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f008.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:31 my-pre-split-f009.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:31 my-pre-split-f010.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:31 my-pre-split-f011.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f012.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f013.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f014.vmdk
-rw --- 1 root root 2147221504 10 Jan 14:30 my-pre-split-f015.vmdk
-rw --- 1 root root 3932160 10 Jan 13:28 my-pre-split-f016.vmdk
-rw --- 1 root root 873 10 Jan 13:42 my-split-pre.vmdk

Options:
-c: Creates a virtual disk, specify other options
-d: defragment the virtual disk
-n <source-disk>: rinonima the virtual disk, you must specify the new name
-q: do not log messages
-r <source-disk>: Converts the virtual disk, you must specify what to convert
x <new-capacity>: expanding the capacity of the disk as specified

Additional options:
-a <adapter>: (use with-c only) adapter type (ide, or Buslogic lsilogic)
-s <size> capacity of virtual disk
-t <disk-type>: disk type id

Disk types:
0: single growable virtual disk (single disk to increase)
1: growable virtual disk split in 2Gb files (from disk accretion to 2 Gb)
2: preallocated virtual disk (single disk preallocato)
3: preallocated virtual disk split in 2Gb files (Disk 2 Gb preallocati)