similar to: Hypervisor to dom0 communication

Hello, I''m interested in establishing a communication channel between the Xen hypervisor and a dom0 userspace application. Ideally this would be a 2-way channel, with the hypervisor asynchronously notifying this application, and then (for certain types of messages) wait for a reply from the userspace consumer. To this end, I''ve been reading xen-devel posts [1], read the

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

I am trying to debug the Xen hypervisor from a second computer over the serial port, but nothing seems to work. Using mercurial, I got xen-3.2-testing.hg. I followed the steps in crashdb.txt in the docs/misc/ folder: set debug=y in Config.mk, crash_debug=y in xen/Rules.mk I also added -fno-omit-frame-pointer to these file as well. I compiled with no errors and booted with minicom connected to

''cat /proc/interrupts'' in a Linux PV domain shows interrupts starting at 256 and labelled as ''Dynamic-irq''. Are these available in a HVM domain, eg under Windows? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Last month Mark Williamson sent out a patch to unconditionally enable the trace buffer. I''d like to suggest that his patch be accepted and merged. I have performed some simple benchmarks to quantify the overhead associated with the trace buffer and calls, and found a negligable performance loss due to them. The actual number was .069%, and was gotten by timing a simple cpu-intensive

about VIRQ & PIRQ what is VIRQ  ?How VIRQ is different from PIRQ ?How VIRQ & PIRQ are related each other ? DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any

Hi all, I have a Toshiba Tecra M9 and have not been able to boot it dom0. This is running SXDE 01/08, snv79b. After booting under kmdb and setting moddebug=80000000 before booting the Solaris kernel (with help from Dan Mick), I was able to see mac_ether as the last thing loading, right after loading the e1000g driver. I cannot drop into kmdb via F1-A after it hangs. I''ve also

We need to write the irq number to GICC_DIR on the physical cpu that previously received the interrupt, but currently we are doing it on the pcpu that received the maintenance interrupt. As a consequence if a vcpu is migrated to a different pcpu, the irq is going to be EOI''ed on the wrong pcpu. This covers the case where dom0 vcpu0 is running on pcpu1 for example (you can test this

mk_pirq_info(), gsi_from_irq() and vector_from_irq() are static functions and no one is calling them. This fixed following compilation warnings : drivers/xen/events.c:134: warning: ?mk_pirq_info? defined but not used drivers/xen/events.c:180: warning: ?gsi_from_irq? defined but not used drivers/xen/events.c:190: warning: ?vector_from_irq? defined but not used Signed-off-by: Jaswinder

mk_pirq_info(), gsi_from_irq() and vector_from_irq() are static functions and no one is calling them. This fixed following compilation warnings : drivers/xen/events.c:134: warning: ?mk_pirq_info? defined but not used drivers/xen/events.c:180: warning: ?gsi_from_irq? defined but not used drivers/xen/events.c:190: warning: ?vector_from_irq? defined but not used Signed-off-by: Jaswinder

mk_pirq_info(), gsi_from_irq() and vector_from_irq() are static functions and no one is calling them. This fixed following compilation warnings : drivers/xen/events.c:134: warning: ?mk_pirq_info? defined but not used drivers/xen/events.c:180: warning: ?gsi_from_irq? defined but not used drivers/xen/events.c:190: warning: ?vector_from_irq? defined but not used Signed-off-by: Jaswinder

drivers/xen/balloon.c:50: WARNING: Use #include <linux/uaccess.h> instead of <asm/uaccess.h> drivers/xen/balloon.c:158: ERROR: else should follow close brace '}' drivers/xen/balloon.c:277: ERROR: do not use assignment in if condition drivers/xen/balloon.c:293: ERROR: code indent should use tabs where possible drivers/xen/balloon.c:364: ERROR: that open brace { should be on the

drivers/xen/balloon.c:50: WARNING: Use #include <linux/uaccess.h> instead of <asm/uaccess.h> drivers/xen/balloon.c:158: ERROR: else should follow close brace '}' drivers/xen/balloon.c:277: ERROR: do not use assignment in if condition drivers/xen/balloon.c:293: ERROR: code indent should use tabs where possible drivers/xen/balloon.c:364: ERROR: that open brace { should be on the

drivers/xen/balloon.c:50: WARNING: Use #include <linux/uaccess.h> instead of <asm/uaccess.h> drivers/xen/balloon.c:158: ERROR: else should follow close brace '}' drivers/xen/balloon.c:277: ERROR: do not use assignment in if condition drivers/xen/balloon.c:293: ERROR: code indent should use tabs where possible drivers/xen/balloon.c:364: ERROR: that open brace { should be on the

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

Hi all, xend communicates with xenstored using unix domain sockets right? So, would it be possible to convert the unix domain sockets to tcp/ip sockets and let xenstored run on a different machine? Regards, Hayawardh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Three of the patches could be squashed in one, but it makes more sense to review them as three. These patches fix the case of an PVHVM guest not being able to resume propely b/c of hitting: 142 BUG_ON(info->type != IRQT_UNBOUND && info->type != type); (in events.c) and also adds a WARN to catch situations like these. The reason for this is that the Xen python toolstack

Hello. log of the crashing boot process: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-14-xen331-linux-2.6.29-rc6-crash.txt 2.6.29-rc5 based pv_ops dom0 works on the same computer.. with the same Xen version. I tried with and without pci=nomsi. adding ''noapic'' doesn''t seem to help (I need that with 2.6.29-rc5 to make it work). Any ideas

I am currently looking at a bug report[1] which is happening when a Xen PVM guest with multiple VCPUs is running a high IO database load (a test script is available in the bug report). In experimenting it seems that this happens (or is getting more likely) when the number of VCPUs is 8 or higher (though I have not tried 6, only 2 and 4), having autogroup enabled seems to make it more likely, too

Xen patchbot -unstable wrote: ># HG changeset patch ># User cl349@firebug.cl.cam.ac.uk ># Node ID 8fe8a99b1c2a6ea88624546ab625eaa0758e3a17 ># Parent e69cbfee4011da1648718f1f5cbe8dabb956e72a >New console transport and update xenconsoled. >Add a new console interface using a seperate shared page and event channel >instead of passing the console input/output over control