search for: domain_c

...igned-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 05abea47f4dc -r 31b98feb0eb6 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Mon Apr 18 17:21:44 2011 +0100 +++ b/tools/libxl/xl_cmdimpl.c Mon Apr 18 17:23:51 2011 +0100 @@ -1354,7 +1354,7 @@ static int create_domain(struct domain_c int migrate_fd = dom_info->migrate_fd; int fd, i; - int need_daemon = 1; + int need_daemon = daemonize; int ret, rc; libxl_waiter *w1 = NULL, *w2 = NULL; void *config_data = 0; @@ -1537,7 +1537,7 @@ start: libxl_domain_unpause(ctx, domid); ret = d...

Changes since v1: - Removed libxl vncviewer related dependencies - The vncviewer function was modified to accept a domid instead of domspec; - main_vncviewer was updated to reflect the new use. - A domain_create structure is now passed to the parse_config_data where required/feasible (NULL otherwise) - xl restore now have long options for vncviewer/vncviewer-autopass; docs updated. - Updated vnc logic to depend on create_domain tools/libxl/xl_cmdimpl.c | 50 ++++++++++++++++--------------- docs/...

...------------------------------------------------------------------------------------- winbind enum users = Yes winbind enum groups = Yes winbind use default domain = no winbind trusted domains only = no # The "idmap domains" has been deprecated in 3.4 # idmap domains = DOMAIN_A DOMAIN_B DOMAIN_C # Next two lines restored in 3.4 - but prob don't need idmap uid = 30000-59999 idmap gid = 30000-59999 idmap config DOMAIN_A:backend = ldap idmap config DOMAIN_A:readonly = no idmap config DOMAIN_A:default=no idmap config DOMAIN_A:ldap_base_dn = ou=domain_a,ou=idmap,o=mydomain.com idmap con...

...incorrect password on one of the satellite computers (B & C) when connecting, but I am sure passwords etc are correct. Another symptom is that listing the trusted domains on computer A shows Trusted domains list: none Trusting domains list: DOMAIN_B domain controller is not responding DOMAIN_C domain controller is not responding I do not have WINS browsing working across domain as yet, but do not think that is an issue as net lookup (host / dc / master) all give the correct answer. I do see some interesting entries in /var/log/messages like ... nmbd[13580]: [2005/09/14 11:48:...

...------------------------------------------------------------------------------------- winbind enum users = Yes winbind enum groups = Yes winbind use default domain = no winbind trusted domains only = no # The "idmap domains" has been deprecated in 3.4 # idmap domains = DOMAIN_A DOMAIN_B DOMAIN_C # Next two lines restored in 3.4 - but prob don't need idmap uid = 30000-59999 idmap gid = 30000-59999 idmap config DOMAIN_A:backend = ldap idmap config DOMAIN_A:readonly = no idmap config DOMAIN_A:default=no idmap config DOMAIN_A:ldap_base_dn = ou=domain_a,ou=idmap,o=mydomain.com idmap con...

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

The following series implements libxl_domain_config_init as per the libxl API requirement that each type has an init function. The first function does this in an open coded manner and is proposed for Xen 4.2. The second function is RFC only since it moves the definition of this type into the IDL and makes the required infrastructure updates t...

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

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 vast majority of the code is in second patch. The first patch merely changes the xenstore key name used by hvmloader to store the buffer address.