similar to: RFB connection with XenAPI Viewer

I'm able to connect to my xenserver using virsh like so and I see the VMs. [jdrews at flynx ~]$ virsh -c xenapi://root at 192.168.1.23?no_verify=1 list Enter root's password for 192.168.1.23: Id Name State ---------------------------------------------------- Struct did not contain expected field memory_overhead. Struct did not contain expected field

Hi, These patches enhance XenAPI for pvSCSI. Basically, I implemented XenAPI for pvSCSI according to the patch of XenAPI document which I sent before. However, I renamed the class name of virtual SCSI devices to "DSCSI". As for the patch of XenAPI document, I''m going to send it next week. Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards,

Hi, I want install libvirt on my ubuntu11.04, and I want to test using libvirt to manage a xenserver, after download the tar and extract them when in this step : ./configure --with-esx --with-xenapi --prefix=/opt/libvirt .... checking for xen_vm_start in -lxenserver... no configure: error: You must install the XenServer Library to compile XenAPI driver with -lxenserver ..... I get this

Hi, I am using XEN-4.1.2 and linux-2.6.32 as dom0. After I upgraded stackless python from 2.5 to 2.7 (and rebuilt xen). XenAPI became unusable, I spent some time to investigate XenAPI,py, it looks fine. So, I guess xend has problem with python 2.7, because it always returned method unknown. Do I have to tweak xend to let it support python 2.7? Thanks, Eric /root # python Python 2.7.5 Stackless

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding *_create_handle() function is removed from each driver. In many cases this change eliminates a struct *_framebuffer

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding *_create_handle() function is removed from each driver. In many cases this change eliminates a struct *_framebuffer

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding *_create_handle() function is removed from each driver. In many cases this change eliminates a struct *_framebuffer

Hi Mike and Jon, If I do this: dpkg -S /usr/lib/python2.7/dist-packages/XenAPI.py then I can see that the XenAPI python package is in fact xcp-xapi. This is quite annoying, because I will need it when building OpenStack nova, but xcp-xapi depends on the Xen hypervisor, which I don't care about when building Openstack. Said in another way: I'd like to avoid having to put

I trying to right a module that will control xen function from perl but i''m having a issue trying to understand what need to be send to the function (VM ref) create (session_id s, VM record args) from xenapi.pdf. Can someone please give me a snippet of what i should be passing to the function. I search Google but nothing came with that helped. -- View this message in context:

hi all, why we implement VM_metrics.VCPUs_utilisation as the proportion of all cpu time? Then XenAPI client (xm) can not get the accumulated cpu_time of each vcpu. I recommend we make VM_metrics.VCPUs_utilisation just the cpu_time which is maintained by hypervisor. Then XenAPI client (xm) not only can get the accumulated cpu_time of each vcpu, but also can calculate the proportion by getting

On Tuesday, December 30, 2014 13:01:57 SilverTip257 wrote: > On Tue, Dec 30, 2014 at 9:58 AM, Marcelo Roccasalva < > > marcelo-centos at irrigacion.gov.ar> wrote: > > On Tue, Dec 30, 2014 at 11:46 AM, Bill Gee <bgee at campercaver.net> wrote: > > > Hello everyone - > > > > > > I am trying to use virt-viewer to connect to KVM virtual machines

Hello, guys! I am doing some experiment to control XenServer with libvirt, when I define a domain, it always fails and gives the following message: error: Failed to define domain from /root/new.xml error: internal error: Couldn't get VM information from XML so I diving into the souce and found it always fails at network creating, and the code in libvirt-1.3.5\src\xenapi\xenapi_utils.c,

Package: xen-utils-common Version: 3.2.0-2 Severity: wishlist --- Please enter the report below this line. --- PAM is the only middle to have an authentification with XenAPI. Without python-pam, Xend silently refuses the authentication and the client have an authentication error. With python-pam it works great. Perhaps it should be intersting to have python-pam as a dependency ? --- System

Package: xen-utils-common Version: 3.2.0-2 Severity: normal --- Please enter the report below this line. --- This bug is a duplicate of the bug #487249, but I tagged it as wishlist and I have no answer about it. But I think it should be interesting to correct it, sorry for this. PAM is the only middle to have an authentification with XenAPI. Without python-pam, Xend silently refuses the

On Tue, Dec 30, 2014 at 9:58 AM, Marcelo Roccasalva < marcelo-centos at irrigacion.gov.ar> wrote: > On Tue, Dec 30, 2014 at 11:46 AM, Bill Gee <bgee at campercaver.net> wrote: > > > Hello everyone - > > > > I am trying to use virt-viewer to connect to KVM virtual machines running > > on a > > CentOS7 host. It works great when running directly on

I originally posted this to the xenapi mailing list but i dont think many are on there... here''s my question. My first attempt at this, trying to get php to interface with /var/run/xend/xen-api.sock (or even 127.0.0.1:9363 for that matter). I can make a connection to both the unix socket and the inet socket and write/read data. The problem is i always get the same responce back, also

http://bugs.freedesktop.org/show_bug.cgi?id=13257 Summary: using nouveau on NV17 kills the KDE VNC server Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

A little while ago I changed my UPS to Leibert and installed NUT. Everything worked as expected. Today I tried to use the MultiLink Viewer icon from the desktop, but it simply accepted the root password without apparently doing anything. I can run the viewer directly (as root) from a file manager. The icon is owned by me, but the application is set to run as root. I suspect that the

Folks: I am unable to get my opensolaris sn-b85 domU to start up in an opensolaris sn-b85 dom0. I am booted to xvm. Other systems, such as Fedora 8, WinXP Pro, W2k3 server, W2k8 server and Windows Vista startup normally. I have used the following to build the domU: # mkfile -n 25g /solhvm/solhvm.img # ls -l /solhvm total 269 -rw------T 1 root root 26843545600 Jul 7 10:37 solhvm.img

--- autobuild.sh | 40 +++++++++++++++++++++++++++++++++++ autogen.sh | 65 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 105 insertions(+), 0 deletions(-) create mode 100755 autobuild.sh diff --git a/autobuild.sh b/autobuild.sh new file mode 100755 index 0000000..8a90a78 --- /dev/null +++ b/autobuild.sh @@ -0,0 +1,40 @@ +#!/bin/sh +#oVirt viewer autobuild