= libvirt.open('xen:///')
print(conn.getFreeMemory())
134217728
Thanks for all your help!
Hany
On Fri, Jun 12, 2009 at 10:44 AM, Daniel P. Berrange berra...@redhat.comwrote:
On Thu, Jun 11, 2009 at 02:37:57PM -0400, Hany Fahim wrote:
Thanks Daniel,
Is it fair to assume this fix may appear
Hany
On Thu, Jun 11, 2009 at 4:46 AM, Daniel P. Berrange berra...@redhat.comwrote:
On Wed, Jun 10, 2009 at 07:28:51PM -0400, Hany Fahim wrote:
Hey Daniel,
Here is the output of 'xm list' from both machines:
I wanted the 'xm info' output actually
Regards,
Daniel
--
|: Red Hat
Thanks Daniel,
Is it fair to assume this fix may appear in the next release of libvirt?
Hany
On Thu, Jun 11, 2009 at 2:28 PM, Daniel P. Berrange berra...@redhat.comwrote:
On Thu, Jun 11, 2009 at 02:13:17PM -0400, Hany Fahim wrote:
My apologies. Here it is:
Xen 3.3:
[r...@node1 ~]# xm
below 0.5.0 such
as 0.4.6, it works like a charm.
Is there anything else I could try?
Hany
On Mon, Jun 8, 2009 at 7:04 AM, Daniel P. Berrange berra...@redhat.comwrote:
On Sun, Jun 07, 2009 at 02:02:20PM -0400, Hany Fahim wrote:
Hi,
I'm currently running a few servers with CentOS 5.3 (i386
0x8e681f0 xen://node3/)
Hany
On Mon, Jun 8, 2009 at 12:34 PM, Daniel P. Berrange berra...@redhat.comwrote:
On Mon, Jun 08, 2009 at 12:20:12PM -0400, Hany Fahim wrote:
Hey Daniel,
Thanks for the reply. The strange thing is, libvirt isn't even attempting
to
establish a connection
Yep, that did it. It works when using xen+tls as the transport. Thanks for
your help Daniel.
Hany
On Mon, Jun 8, 2009 at 12:53 PM, Daniel P. Berrange berra...@redhat.comwrote:
On Mon, Jun 08, 2009 at 12:47:30PM -0400, Hany Fahim wrote:
Hey Daniel,
Sorry, I should have mentioned that. Yes, I
Hi,
I'm currently running a few servers with CentOS 5.3 (i386) with the stock
Xen version:
# rpm -q kernel-xen xen libvirt
kernel-xen-2.6.18-92.1.22.el5
kernel-xen-2.6.18-128.1.6.el5
xen-3.0.3-80.el5_3.2
libvirt-0.6.3-1
libvirt was compiled from the src RPM from libvirt.org to run on i386
