Welcome to the ClearVM Help Center
The ClearOS Knowledge Base contains free and paid articles dealing with best practices, implementation guides and outlines, real-world deployment considerations, troubleshooting techniques and tools, and support beyond.
It contains Howto documents designed to implement features. It also contains initiatives and helpful documentation for developers including prototyping, skunkworks, and works in progress.
Frequently used Knowledge Base sections:
Yes you can, it’s not needed anymore. But please make sure to initialize at least one hard drive before you try to reboot the server or it won’t come up again (a bootloader is installed on the hard drive during the drive initialization, which is required for the server to boot).
You can initialize the hard drive before or after you remove the USB/CD, but make sure to do it before you do a reboot to avoid having to insert the USB/CD again.
Once it has completed you don’t need the ISO/CD/USB anymore.
Yes, you can use for example wget or cURL to download the LIVEvisor ISO.
Yes, log in to the management console you can make a snapshot and then download that snapshot to your computer
You should probably not log in to the LIVEvisor at all. All management is be done by signing in to the centralized management system – hosts and guests will be available for management there. That said, if you want to look around inside the LIVEvisor that’s fine just sign in with user:root pass:witsbits (it only works from the server console).
The LIVEvisor virtual machine monitor is KVM (Kernel-based Virtual Machine).
The virtual machine container format is qcow2 – the native format for KVM/QEMU.
Yes, you can bring it into Witsbits management later. Read more about imports.
Turn off the VM and click Start in the GUI. Then select the new configuration and click Power On.
To prevent any risk of data corruption or inconsistency in the snapshot we tell the hypervisor to pause the source VM until the snapshot process has completed. This leads to the source VM briefly being unavailable when a snapshot is taken.
Some older BIOSes has a bug in their APCI handling which in some cases prevent your server from booting the LIVEvisor. The symptom appears at kernel boot similar to
ata1 failed to identify I/O error err_mask=0x4
/bin/sh: can't access tty; job control turned off (initramfs)
First make sure you have the latest LIVEvisor. Then start your server and hit Tab on your keyboard when the boot screen appears. Now, add
(add a space between the old parameters and noapic) to the end of the command-line and press Enter to continue the boot process.
Check your BIOS and set accordingly:
USB Flash Drive emulation type: Hard Drive
Many of the pre-configured VMs are configured with a root filesystem partion of 10GB. To utilize the capacity you selected when you launched the VM you may create a 2nd (3rd, 4th etc.) partition from inside your guest operating system.
To partition Linux guest operating systems, type: “fdisk /dev/vda” To partition Windows guest operating systems, use Disk Manager Note: the first partition is used by the operating system.
In order to maintain good performance using Witsbits, software virtualization should not be used. Some BIOS has virtualization set to disabled by default. How to enable hardware virtualization in BIOS:
The LIVEvisor ISO is imprinted with an identifier unique to your account at the time of download. When a server is started with your LIVEvisor ISO it will automatically connect it with your account. Thus, you should never share your LIVEvisor media or ISO with anyone else (it’s not dangerous, but their servers will pop up in your account).
Witsbits Director collects and stores only information necessary to be able to provide management capabilities to your physical and virtual infrastructure. The collected data includes, hardware utilization, hardware configuration, hardware health, hardware status, virtual machine utilization, virtual machine configuration, virtual machine health, virtual machine status and software versions.
By using the VM backup function you will upload a snapshot of your virtual machine container to Witsbits’ Servers. The Virtual Machine Container is the virtual hard drive of your virtual machine and holds all and any data you have stored while operating the virtual machine.
**ANDROSoft* on February 26, 2014 at 6:35 pm said: Enlarge the partition to use all space:
fdisk -u /dev/vda.
p to print the partition table, take note of the number, start, end, type of vda1.
Delete it: d Recreate it: n with same number (1), start and type but with a bigger end (taking care not to overlap with other partitions). Try to align things on a megabyte boundary that is for end, make it a multiple of 2048 minus 1.
Then w to write and q to quit.
The partition table will have been modified but the kernel will not be able to take that into account as some partitions are mounted.
So you’ll need to reboot. The system should boot just fine.
Once rebooted, resize the filesystem so it spreads to the extent of the enlarged partition:
Which for ext4 will work just fine even on a live FS.