search for: xs_get_domain_path

...: tip user: cl349@firebug.cl.cam.ac.uk date: Wed Sep 14 10:47:48 2005 summary: Add methods to read/write Vm/Domain store entries. I created domU and got the messages: # xm create -c vm2.cfg Using config file "vm2.cfg". Started domain bl3-6vm2-rhel4 xenconsole: xs_get_domain_path(): No such file or directory Here is /var/log/xend-debug.log: ERROR: do_evtchn_op: HYPERVISOR_event_channel_op failed: -1 "/var/log/xend-debug.log" 142L, 7195C 1,1 Top val = resource.render(self) File "/usr/lib/python/xen/web/resource.py", line 5...

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

Dear Xen community, I have Xen 3.0 installed on RedHat Linux Enterprise RHEL4U2. "xend install" runs fine with no error messages. However, when I start "xm cr guest-vmx.conf" I do not get any new window open for the new guest OS. "xm list" shows that the vmx has started and seems to be working fine (just for testing, when I type "xterm" an X window

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.

...s_daemon_open_readonly at VERS_4.0 4.16.0 - xs_daemon_rundir at VERS_4.0 4.16.0 - xs_daemon_socket at VERS_4.0 4.16.0 - xs_daemon_socket_ro at VERS_4.0 4.16.0 - xs_debug_command at VERS_4.0 4.16.0 - xs_directory at VERS_4.0 4.16.0 - xs_domain_open at VERS_4.0 4.16.0 - xs_fileno at VERS_4.0 4.16.0 - xs_get_domain_path at VERS_4.0 4.16.0 - xs_get_permissions at VERS_4.0 4.16.0 - xs_introduce_domain at VERS_4.0 4.16.0 - xs_is_domain_introduced at VERS_4.0 4.16.0 - xs_mkdir at VERS_4.0 4.16.0 - xs_open at VERS_4.0 4.16.0 - xs_path_is_subpath at VERS_4.0 4.16.0 - xs_read at VERS_4.0 4.16.0 - xs_read_watch at VERS_4....

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

Hi, Anybody (Christian?) could please tell me if we can get the support for registering watch with /proc/xen/xenbus? (..OK, I know that we will change it this /proc stuff to a device soon) So far we can only do read/write/rm. I really miss the xen watch feature. Many thanks, Hieu _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some extraneous node creation. Patch 2 modifies creation of the hvmloader key in xenstore and adds

Hi all, this is the long awaited patch series to add xen device model support in qemu; the main author is Anthony Perard. Developing this series we tried to come up with the cleanest possible solution from the qemu point of view, limiting the amount of changes to common code as much as possible. The end result still requires a couple of hooks in piix_pci but overall the impact should be very

...ls/libxl/libxl_xshelp.c index 6286d02..f59eee7 100644 --- a/tools/libxl/libxl_xshelp.c +++ b/tools/libxl/libxl_xshelp.c @@ -95,6 +95,11 @@ char * libxl_xs_read(struct libxl_ctx *ctx, xs_transaction_t t, char *path) char *libxl_xs_get_dompath(struct libxl_ctx *ctx, uint32_t domid) { char *s = xs_get_domain_path(ctx->xsh, domid); + if (!s) { + XL_LOG_ERRNO(ctx, XL_LOG_ERROR, "failed to get dompath for %lu", + domid); + return NULL; + } libxl_ptr_add(ctx, s); return s; } -- 1.5.6.5 _______________________________________________ Xen-devel ma...

...ULL) { - libxl_ptr_add(ctx, ptr); + libxl_ptr_add(gc, ptr); return ptr; } return 0; } -char *libxl_xs_get_dompath(libxl_ctx *ctx, uint32_t domid) +char *libxl_xs_get_dompath(libxl_gc *gc, uint32_t domid) { + libxl_ctx *ctx = libxl_gc_owner(gc); char *s = xs_get_domain_path(ctx->xsh, domid); if (!s) { XL_LOG_ERRNO(ctx, XL_LOG_ERROR, "failed to get dompath for %" PRIu32, domid); return NULL; } - libxl_ptr_add(ctx, s); + libxl_ptr_add(gc, s); return s; } -char **libxl_xs_directory(libxl_ctx *ct...

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual