Hi,
I'm running CentOS 6.2 x86_64 as xen guest on a CentOS 5.7 dom0.
The host is running 2.6.18-274.7.1.el5xen, the guest
2.6.32-220.2.1.el6.x86_64.
Memory for domU is set to 1024 MB and xm list shows these 1024 MB.
But free -m on the guest system shows only 652 MB.
When I set up a CentOS 5.x
Friday, I moved our servers to a new co-lo facility and ran into an
interesting problem with virtual machines.
I did an orderly shutdown of the CentOS 6.3 host, and it in turn suspends
all the guests. It took about an hour and a half to move and fire up the host.
The guests,
On Wed, 2013-01-02 at 00:53 -0800, Robert Dinse wrote:
Friday, I moved our servers to a new co-lo facility and ran into an
interesting problem with virtual machines.
I did an orderly shutdown of the CentOS 6.3 host, and it in turn suspends
all the guests. It took about an hour and a
On Wed, Jan 2, 2013 at 3:29 AM, s...@cyon.ch wrote:
Hi,
I'm running CentOS 6.2 x86_64 as xen guest on a CentOS 5.7 dom0.
The host is running 2.6.18-274.7.1.el5xen, the guest
2.6.32-220.2.1.el6.x86_64.
Memory for domU is set to 1024 MB and xm list shows these 1024 MB.
But free -m on the
On Wed, Jan 2, 2013 at 3:53 AM, Robert Dinse nan...@eskimo.com wrote:
Friday, I moved our servers to a new co-lo facility and ran into an
interesting problem with virtual machines.
I did an orderly shutdown of the CentOS 6.3 host, and it in turn suspends
all the guests. It took
On Wed, January 2, 2013 03:53, Robert Dinse wrote:
Friday, I moved our servers to a new co-lo facility and ran into
an interesting problem with virtual machines.
I did an orderly shutdown of the CentOS 6.3 host, and it in
turn suspends all the guests. It took about an hour and a
On Wed, Jan 2, 2013 at 9:41 AM, James B. Byrne byrn...@harte-lyne.cawrote:
I ran into this situation several times whilst testing KVM and the
lessons I learned from the experiences can be summarized as:
1. Never allow the kvm hypervisior to handle guests during a host
shutdown. Use 'virsh
I thank everyone for their input. I prefer to have the guests suspend
rather than shutdown because many of my customers start things up manually and
get annoyed when they come back to find them not running. Most of the time
it is for a simple reboot of the host to make a new kernel or some
On Wed, January 2, 2013 12:51, SilverTip257 wrote:
On Wed, Jan 2, 2013 at 9:41 AM, James B. Byrne
byrn...@harte-lyne.cawrote:
I ran into this situation several times whilst testing KVM and the
lessons I learned from the experiences can be summarized as:
1. Never allow the kvm hypervisior
