This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Get parameters from dom0 to domu on domu start

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Get parameters from dom0 to domu on domu start
From: Eugene Istomin <eastman@xxxxxxx>
Date: Wed, 27 Jul 2011 11:10:57 +0300
Delivery-date: Wed, 27 Jul 2011 08:14:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: EDSS
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/4.6.1 (Linux/; KDE/4.6.5; x86_64; ; )

I have a question about dom0<->domu xenstore interaction.

Assume, we have some pv domu with some logic inside 
"if grep -Fxq "echo noop > \/sys\/block\/$DISK\/queue\/scheduler" 
  echo "$DISK exist in $INIT_BOOTLOCAL" 
  echo "echo noop > \/sys\/block\/$DISK\/queue\/scheduler" >> 
fi "

'Cos of many gw/mtu/zabbix/bacula parameters we need to know all of this 
parameters on domu side before init 1. Assume we have some xenstore custom 
structure in xenstore, that describes thoose parameters.

Is it possible to run some custom script from dom0 on domu start which:
1) get some extra info form config file (network name, domain name, etc)
2) copy some parameters from one xenstore tree (custom) to another 

AFAK 1) is resolved by extra=".." in xm/xl config
What about 2)?

Best regards,
Eugene Istomin

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>