Posted: May 4th, 2010 | Author: Omer Segev | Filed under: General Virtualization, How To, Xen | No Comments »
Hi,
I’m currnetlly working on a large virtual environment which will run many types of operating systems. After some research, I found this Thread in the FreeBSD Forum, which deals with the installation of FreeBSD DomU on a Debian Dom0.
From the post:
The goal of this guide is to show you how to create a FreeBSD 8 installation that will run as a guest OS, without the need for a processor that supports hardware-assisted virtualization. It would go beyond the scope of this guide to explain how exactly Xen works or what the differences between PV and HVM are, suffice to say dom0 is the host OS and domU the guest OS. Although FreeBSD fully supports being a Xen domU, it is not yet very well documented and not suited for novice Xen users. Especially the lack of a Xen-aware installer or pre-built Xen-aware images make things more difficult. If you are a Xen novice, I recommend starting first with pre-built Linux images, and then trying a NetBSD domU installation, before proceeding with FreeBSD.
Hope you’ll find it useful.
Posted: November 23rd, 2009 | Author: Omer Segev | Filed under: Xen Debian | No Comments »
After rebooting one of the Dom0 at my site, all the guests came up with annoying message ‘clocksource/0: Time went backwards’.
After doing some search I found the following solution at Debian Wiki:
If a domU crashes or freezes while uttering the famous lasts words ‘clocksource/0: Time went backwards’, your domU is likely using the xen clocksource instead of its own clock ticks. In practice, this seems to be the cause of infrequent lockups under load (and/or problems with suspending). A workaround is to decouple the clock in the domU from the dom0:
In your dom0 and domU /etc/sysctl.conf add the line:
xen.independent_wallclock=1
On the dom0, edit the configuration file of the domU (e.g. /etc/xen/foobar.cfg and add (or expand) the extra-line:
extra=”clocksource=jiffies”.
These settings can be activated without rebooting the domU. After editing the configuration files, issue
sysctl -p and echo “jiffies”> /sys/devices/system/clocksource/clocksource0/current_clocksource on the domU prompt.
Because the clock won’t be relying on the dom0 clock anymore, you probably need to use ntp on the domU to synchronize it properly to the world.