similar to: [PATCH] mini-os: Simple xenbus watch support

I sent this patch directly to Gregor, and neglected to CC this list. Sorry about that. I''d like to make it so that there is no need to modify any Mini-OS source files when extending it with an application. All that is required is a change to Makefile, and a small change to kernel.c, printf.c, and string.c. I have enclosed the patch. With this patch, one could write an application in a

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

add xenbus token support and separate watch event queues Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> # HG changeset patch # User Samuel Thibault <samuel.thibault@eu.citrix.com> # Date 1200582503 0 # Node ID 112c1180720c87a0bfa99142399e3ef3f79f1711 # Parent 33d1c7f9217a1c915afe01fe822811ce69b3a90f add xenbus token support and separate watch event queues diff -r

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!''

hi, has anyone attempted to add grant tables, blockfront or netfront support to mini-os recently? Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am having an issue getting a DomU to boot properly. There is never any indication of a stop error or kernel panic, it simply hangs after "Starting crond [ OK ]" and never continues. I''ve included my mkinitrd and output from xm create... please help! ##### XENBUS errors ##### XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050

This patch ports the Linux implementation of xenbus, in order to do that very simple threading support is introduced. Apart of that numerous fixes for 64 bit are included. Mini-os now compiles (for 64bit) but requires memory management and threading fixes before it works as well as 32bit version. Gregor _______________________________________________ Xen-devel mailing list

From: Julia Lawall <julia at diku.dk> The kernel.h macro DIV_ROUND_UP performs the computation (((n) + (d) - 1) / (d)) but is perhaps more readable. An extract of the semantic patch that makes this change is as follows: (http://www.emn.fr/x-info/coccinelle/) // <smpl> @haskernel@ @@ #include <linux/kernel.h> @depends on haskernel@ expression n,d; @@ ( - (n + d - 1) / d +

Hi, I need to get the exact downtime for doing a live migration with ms precision. (I am not bothered about whole migration time which is close to 1 minute.. I need to measure the live migration downtime during which the DomU is out of service.. the figure quoted in the xen documentation says it as ~60 ms.. ) I hope someone must have tried to measure this before. Can you suggest me ideas

Hi Konrad, I just tried linux-3.4-rc0 (linus his tree, last commit f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your tree pulled on top of that: branch stable/for-ingo-3.4.v2 (required for dom0 to boot) branch stable/for-jens-3.4 branch stable/for-jens-3.4-bugfixes Hypervisor is xen-4.1.3-rc1-pre linux 3.3 vanilla works fine Booting dom0 goes fine, but

hi, it seems I no longer need to pin l1 pages when running with writable page tables in xen-unstable -- e.g. I can now pin a l2 table without having pinned its l1 descendants first, without Xen complaining. Do I understand things correctly? thanks, Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

include/xen/xenbus.h nicely declares struct xenbus_driver''s ''ids'' member as pointer to const... As usual, written and tested on 2.6.25-rc3 and made apply to the 2.6.18 tree without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2008-02-26/drivers/xen/blkback/xenbus.c

Hi, This patch series fixes the S3 resume of a domain running xenstored and a frontend over xenbus (xen-netfront in my use case). As device resume is happening before process resume, the xenbus frontend resume is hanging if xenstored is not running, thus causing a deadlock. This patch series is fixing that issue by deferring the xenbus frontend resume when we are running xenstored in that same

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error

Add a semaphore to protect gnttab_list from exhaustion, and disable callbacks during allocation/free. Fix the network frontend accordingly. Signed-off-by: Samuel Thibault <samuel.thibault@citrix.com> diff -r bb961bda7eff extras/mini-os/gnttab.c --- a/extras/mini-os/gnttab.c Sun Nov 25 21:24:48 2007 +0000 +++ b/extras/mini-os/gnttab.c Mon Nov 26 11:50:31 2007 +0000 @@ -18,6 +18,7 @@

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

After a guest is live migrated, the xen-netfront driver emits a gratuitous ARP message, so that networking hardware on the target host's subnet can take notice, and public routing to the guest is re-established. However, if the packet appears on the backend interface before the backend is added to the target host's bridge, the packet is lost, and the migrated guest's peers become

Hello I have a lot of problem using the xenbus api (in xen-3.0-testing). I had to modify the network backend driver (file netback.c), and each call to a xenbus function in a virtual machine make my machine reboot (not the virtual, the real machine). for example, I ''ve add this line of code (wich is useless):

When xen_emul_unplug=never is specified on kernel command line reading files from /sys/hypervisor is broken (returns -EBUSY). It is caused by xen_bus dependency on platform_pci and platform_pci isn''t initialized when xen_emul_unplug=never is specified. Fix it by allowing platform_pcii to ignore xen_emul_unplug=never, and do not intialize xen_[blk|net]front instead. Signed-off-by: Igor