search for: virq_dom_exc

xend cannot start with error: ...ption starting xend: ''module'' object has no attribute ''VIRQ_DOM_EXC'' Traceback (most recent call last): File "/usr/lib/python2.3/xen/xend/server/SrvDaemon.py", line 304, in run self.createFactories() File "/usr/lib/python2.3/xen/xend/server/SrvDaemon.py", line 319, in createFactories self.channelF = channel.channelFactory()...

I''ll step back to Xen stable, because of my network probs with Xen unstable. So I configured and compiled Xen 2.0.6, but I came to the following error after starting Xend: Exception starting xend: ''module'' object has no attribute ''VIRQ_DOM_EXC'' Traceback (most recent call last): File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 302, in run self.createFactories() File "/usr/lib/python/xen/xend/server/SrvDaemon.py", line 317, in createFactories self.channelF = channel.channelFactory() File...

...{ - domain_unpause(d); - return; - } - - evtchn_destroy(d); - gnttab_release_mappings(d); - domain_relinquish_resources(d); - put_domain(d); - - /* Kick page scrubbing after domain_relinquish_resources(). */ - page_scrub_kick(); - - send_guest_global_virq(dom0, VIRQ_DOM_EXC); +int domain_kill(struct domain *d) +{ + int rc = 0; + + if ( d == current->domain ) + return -EINVAL; + + /* Protected by domctl_lock. */ + switch ( d->is_dying ) + { + case DOMDYING_alive: + domain_pause(d); + d->is_dying = DOMDYING_dying; +...

...in start self.run() File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 614, in run self.listenVirq() File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 638, in listenVirq virqChan = self.channelF.virqChannel(channel.VIRQ_DOM_EXC) File "/usr/lib/python2.3/site-packages/xen/xend/server/channel.py", line 110, in virqChannel chan = VirqChannel(self, virq) File "/usr/lib/python2.3/site-packages/xen/xend/server/channel.py", line 199, in __init__ self.port = xc.evtchn_bind_virq(virq) xen.lowlevel.x...

...in start self.run() File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 614, in run self.listenVirq() File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 638, in listenVirq virqChan = self.channelF.virqChannel(channel.VIRQ_DOM_EXC) File "/usr/lib/python2.3/site-packages/xen/xend/server/channel.py", line 110, in virqChannel chan = VirqChannel(self, virq) File "/usr/lib/python2.3/site-packages/xen/xend/server/channel.py", line 199, in __init__ self.port = xc.evtchn_bind_virq(virq) xen.lowlevel.x...

...in start self.run() File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 614, in run self.listenVirq() File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 638, in listenVirq virqChan = self.channelF.virqChannel(channel.VIRQ_DOM_EXC) File "/usr/lib/python2.3/site-packages/xen/xend/server/channel.py", line 110, in virqChannel chan = VirqChannel(self, virq) File "/usr/lib/python2.3/site-packages/xen/xend/server/channel.py", line 199, in __init__ self.port = xc.evtchn_bind_virq(virq) xen.lowlevel.x...

Hello! The current MCA/MCE support in Xen is that it dumps the error and panics. In the following concept I propose here, there are two places where Xen has to react on. I) Xen receives a MCE from the CPU and II) Xen receives Dom0 instructions via Hypercall The term "self-healing" below is used in the sense of using the most propriate technique(s) to handle an error such as MPR

Two things: 1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this (and if you want a dump, do ''xm dump'' followed by ''xm destroy'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as

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 -

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

...allocated to VCPU0 but can subsequently be re-bound. + */ +#define VIRQ_TIMER 0 /* V. Timebase update, and/or requested timeout. */ +#define VIRQ_DEBUG 1 /* V. Request guest to dump debug info. */ +#define VIRQ_CONSOLE 2 /* G. (DOM0) Bytes received on emergency console. */ +#define VIRQ_DOM_EXC 3 /* G. (DOM0) Exceptional event for some domain. */ +#define VIRQ_TBUF 4 /* G. (DOM0) Trace buffer has records available. */ +#define VIRQ_DEBUGGER 6 /* G. (DOM0) A domain has paused for debugging. */ +#define VIRQ_XENOPROF 7 /* V. XenOprofile interrupt: new sample available...

...ges are console messages >- it''s just easier to ignore other messages that try to bind to >- a specific type. */ >- msg.type = XCS_MSG_BIND; >- msg.u.bind.port = PORT_WILDCARD; >- msg.u.bind.type = TYPE_WILDCARD; >+ msg.type = XCS_VIRQ_BIND; >+ msg.u.virq.virq = VIRQ_DOM_EXC; > if (!xcs_send_recv(xcs_ctrl_fd, &msg) || msg.result != XCS_RSLT_OK) { >- dolog(LOG_ERR, "xcs vind failed. Possible bug."); >+ dolog(LOG_ERR, "xcs virq bind failed. Possible bug."); > goto out_close_data; > } > >diff -r e69cbfee4011 -r 8fe8a9...

Hi Jeremy. According to your suggestion, I recreated patches for Ingo's x86.git tree. And this patch series includes Eddie's modification. Please review and forward them. (or push back to respin.) Recently the xen-ia64 community started to make efforts to merge xen/ia64 Linux to upstream. The first step is to merge up domU portion. This patchset is preliminary for xen/ia64 domU linux

Hi Jeremy. According to your suggestion, I recreated patches for Ingo's x86.git tree. And this patch series includes Eddie's modification. Please review and forward them. (or push back to respin.) Recently the xen-ia64 community started to make efforts to merge xen/ia64 Linux to upstream. The first step is to merge up domU portion. This patchset is preliminary for xen/ia64 domU linux

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *