similar to: alert message from dom0 to domU

It seems that xenstore watches do not work from domU userspace (they obviously do for drivers). In some preliminary debugging of this, there are two aspects of the failure: not sending the watch to xenstore and not handling watch events for userspace watches. The former can be easily fixed by adding the missing ''case XS_WATCH:'' to xenbus_dev_write() in xenbus_dev.c. The

As any other daemon, I''d assume it should be possible to restart xenstored (i.e. if it crashed or if, during development, a fix was made to it that needs to be tested). However, as I learned after over a day of digging, things don''t work anymore after doing so: Since the watches are transient, they''re lost with the daemon going away. Right now I specifically need this in

hi, I am trying to add xenbus watch support to mini-os, but am getting into a endless loop of watches firing over and over. Below is an excerpt from the xenstore tracefile: IN 0x805acc8 20070103 19:32:18 WATCH (/local/domain/0/backend/vif/26/0/state 00043818 ) CREATE watch 0x805a8b8 OUT 0x805acc8 20070103 19:32:18 WATCH (OK ) OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m looking at building a xenstore-based watchdog, as described at http://lists.xensource.com/archives/html/xen-users/2005-07/msg00597.html However, being somewhat new to xenstore, I''d appreciate some pointers. - What portions of the xenstore namespace should I use? I''m looking for at least two settings writable by the DomUs: A flag to enable/disable the watchdog

Hey everyone, I''m trying to write a simple python program in dom0 that registers a watch on the xenstore to determine when a domU has shutdown. Is there a particular token I should use? Looking through the tools/python/xen/*.py code, I''ve come across the ''control/shutdown'' token... seems promising? My code is attached below. As is, if fails to call the

APIs such as sh_invlpg and sh_update_cr3 take a pointer to the virtual cpu on which it needs to operate as an argument. However, it appears that the call can only operate on the currently executing vcpu. Regards, K. Y _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I encountered a problem while porting Solaris as a guest OS on Xen. The problem I found is that when frontend vbd driver get unloaded, it will close the vbd interface by changing the state to XenbusStateClosed. This appears to cause the dom0 hotplug scripts to remove the vbd entry from xenstore for the domU guest, preventing the vbd from being re-attached. So, my questions are: + This

Hello, This patch allows userspace tools on a domU to setup a watch on the xenstore. It does this by intercepting XS_WATCH requests written to /proc/xen/xenbus and then re-submitting the request to the in-kernel xenstore interface, in linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_xs.c. When a callback occurs, an in-kernel function is invoked, which then reconstructs a response in the format

This patch fixes the bug that "xm reboot <domid>" can not reboot vmx domain. In xm reboot process, control panel will wait until DomU notified it. Unlike DomU, vmx domain can not passively do that, since it runs unmodified OS. This patch adds the missing logic in control panel. Any comment? Signed-off-by: Xu Dan <dan.d.xu@intel.com > Yu Ke

Ewan Mellor wrote: >> >> Ian Pratt wrote: >>> >>> >>>> I have been trying for days now to get a working nat setup with >> my >>>> domU''s using the default nat scripts. >>> Just look at what the demo CD does for a nice example of how to set up >>> NAT. >>> >>> Ian >>> >>

Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into xend, and I was wondering if you had a plan for how that should work. First example: the device tree data structure we talked about a few weeks ago. We will need to pass the config data to PPC code, probably in XendDomainInfo.initDomain(), and then pass the resulting data structure into libxc''s xc_linux_load()

Hello. Is it available a communication interface between Dom0 and DomU to get some parameteres about DomU without connection via ssh? For example i need to get information about IP addresses that are allocated in DomU. I found following mail-thread: http://xen.1045712.n5.nabble.com/How-to-get-domU-IP-address-td2510278.html Keir Fraser said about xenstore, but as i understand to use xenstore

I am new to Xen and want to provide simple communication between my DomU and Dom0 environments. I just need to be able to pass a few bytes of information back and forth between DomU and Dom0 while using some form of event management to know when an update occurs so I can act on it. At first, it appeared that using XenBus and XenStore might be the right solution for this. However, after looking

All, Is there a way to setup serial communication between dom0 and domU. The idea is to have some way of exchanging messages between dom0 and domUs. Certainly, it is possible to use s host-only network, and ssh or shared file system to exchange data. However, there could be cases where the dom0 is not networked. You may want to automate configuring domUs from dom0. Any suggestions. Arijit

After upgrading to 3.0.2 I tried rebooting a domU (a problem sometimes in 3.0.1 related to bug 514) it failed to come back up. This was in my xend.log. ("Refusing to restart to avoid loops." .... ) [2006-04-11 20:53:39 xend.XendDomainInfo] DEBUG (__init__:988) Storing domain details: {''console/ring-ref'': ''223144'', ''console/port'':

Hi there, I am new to Xen. Just began trying it out from day-before. I have a CentOS 4.4 install on my hda6 partition. And I have a openSUSE 10.2 install on my hda8 partition. For openSUSE 10.2, I chose the Xen options while installing, and so I have the xen kernels too installed. For CentOS 4.4, I downloaded the Xen 3.0.2 source and compiled from there. (I followed the instructions at this

I got a strange problem: I need to get sysinfo() data from domU in my application, running in dom0. Right now I using a userspace daemon in every domU, updating information in xenstore, and my application read this information... But I think, it really strange: why we can not get those info directly from PV kernel without going to kernel and back to userspace multiple times? Is any way to get

Signed-off-by: Jerone Young <jyoung5@us.ibm.com> -- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel