search for: hypervisor_event_channel_op

What are the possible cases (I hope there are not many:)) that this Hypercall might fail, HYPERVISOR_event_channel_op(EVTCHNOP_send, &op)???,With an error value of "-ENOSYS (-38)" on a "HVM"? Thx, Venkat _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi all: This is my running environment: there are multiple processes, each process will create a vm by `xl restore`; after running for a long time, it will easily get error for ` HYPERVISOR_event_channel_op failed: -1`. I don''t understand much about that. Looking forward to your reply. Thanks. bruce _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

...back.o being enabled there - I''ve a fix for that). But more interestingly the build system I do also makes a variations of config entries. So there is the allmodules, allyes, allyes, but all Xen drivers are modules, etc. I found out that with: CONFIG_XEN_GNTDEV=m I get this ERROR: "HYPERVISOR_event_channel_op" [drivers/xen/xen-gntdev.ko] undefined! If I make it CONFIG_XEN_GNTDEV=y the issue disappears. Any thoughts? (FYI, if you want to do this on v3.7-rc4 please apply this patch to your tree) commit e1a982642262820d68779c06de64f8857a040f5a Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.c...

...pi_on_cpu_to_irq(int cpu, int ipi) +{ + evtchn_op_t op; + int evtchn, irq; + + mtx_lock(&irq_mapping_update_lock); + + if ( (evtchn = PCPU_GET(ipi_to_evtchn)[ipi]) == 0 ) + { + op.cmd = EVTCHNOP_bind_ipi; + op.u.bind_ipi.ipi_edom = cpu; + if ( HYPERVISOR_event_channel_op(&op) != 0 ) + panic("Failed to bind virtual IPI %d on cpu %d\n", ipi, cpu); + evtchn = op.u.bind_ipi.port; + + irq = find_unbound_irq(); + evtchn_to_irq[evtchn] = irq; + irq_to_evtchn[irq] = evtchn; + + PCPU_GET(ipi_to_evtchn)[ipi] = ev...

...yet implemented) + * + * HYPERVISOR_sched_op + * All generic sub-operations, with the exception of: + * * SCHEDOP_block -- prefer wfi hardware instruction + * + * HYPERVISOR_console_io + * All generic sub-operations + * + * HYPERVISOR_xen_version + * All generic sub-operations + * + * HYPERVISOR_event_channel_op + * All generic sub-operations + * + * HYPERVISOR_physdev_op + * No sub-operations are currenty supported + * + * HYPERVISOR_sysctl + * All generic sub-operations, with the exception of: + * * XEN_SYSCTL_page_offline_op + * * XEN_SYSCTL_get_pmstat + * * XEN_SYSCTL_pm_op + * + * HY...

...Add methods to read/write Vm/Domain store entries. I created domU and got the messages: # xm create -c vm2.cfg Using config file "vm2.cfg". Started domain bl3-6vm2-rhel4 xenconsole: xs_get_domain_path(): No such file or directory Here is /var/log/xend-debug.log: ERROR: do_evtchn_op: HYPERVISOR_event_channel_op failed: -1 "/var/log/xend-debug.log" 142L, 7195C 1,1 Top val = resource.render(self) File "/usr/lib/python/xen/web/resource.py", line 59, in render return meth(req) File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 135, i...

...e xm dmesg includes "(XEN) VMXON is done". I base my config file on example.hvm and on previous emails to this list. Unfortunately, I don''t get very far. xm create winxp.conf Error: (22, ''Invalid argument'') xend-debug.log gives me this: ERROR: do_evtchn_op: HYPERVISOR_event_channel_op failed: -1 And xend.log spews out all of the stuff below my sig. I''ve googled around and not found any obvious answers. Can anyone tell me where to start looking to fix this? Thanks, Steve Brueckner, ATC-NY [2006-05-18 14:48:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:184) XendDoma...

...%1 ; break 0x1000 ;; mov %0=r8 ;;" + : "=r" (ret) + : "i" (__HYPERVISOR_console_io), "r"(cmd), "r"(arg) + : "r14","r15","r2","r8","memory" ); + return ret; +} static inline int HYPERVISOR_event_channel_op( diff -r 0255f48b757f linux-2.6-xen-sparse/include/asm-xen/asm-ia64/hypervisor.h --- a/linux-2.6-xen-sparse/include/asm-xen/asm-ia64/hypervisor.h Sun Dec 4 19:12:00 2005 +++ b/linux-2.6-xen-sparse/include/asm-xen/asm-ia64/hypervisor.h Tue Dec 6 16:25:53 2005 @@ -52,4 +52,19 @@ #define mfn_to_pfn...

.... > Looking at the code (in Linux) I see: > 516 /* NB. We are happy to share unless we are probing. */ > 517 bind_pirq.flags = info->u.pirq.flags & PIRQ_SHAREABLE ? > 518 BIND_PIRQ__WILL_SHARE : 0; > 519 rc = HYPERVISOR_event_channel_op(EVTCHNOP_bind_pirq, &bind_pirq); > 520 if (rc != 0) { > 521 pr_warn("Failed to obtain physical IRQ %d\n", irq); > 522 return 0; > 523 } > > It would be nice if I we had included the return code :-( I've added...

Hi Jeremy, My static analyzer complains about potential memory corruption in HYPERVISOR_physdev_op() arch/x86/include/asm/xen/hypercall.h 389 static inline int 390 HYPERVISOR_physdev_op(int cmd, void *arg) 391 { 392 int rc = _hypercall2(int, physdev_op, cmd, arg); 393 if (unlikely(rc == -ENOSYS)) { 394 struct physdev_op op; 395

Hi Jeremy, My static analyzer complains about potential memory corruption in HYPERVISOR_physdev_op() arch/x86/include/asm/xen/hypercall.h 389 static inline int 390 HYPERVISOR_physdev_op(int cmd, void *arg) 391 { 392 int rc = _hypercall2(int, physdev_op, cmd, arg); 393 if (unlikely(rc == -ENOSYS)) { 394 struct physdev_op op; 395

Hi Jeremy, My static analyzer complains about potential memory corruption in HYPERVISOR_physdev_op() arch/x86/include/asm/xen/hypercall.h 389 static inline int 390 HYPERVISOR_physdev_op(int cmd, void *arg) 391 { 392 int rc = _hypercall2(int, physdev_op, cmd, arg); 393 if (unlikely(rc == -ENOSYS)) { 394 struct physdev_op op; 395

I''m having trouble switching into user mode with my domU kernel -- everytime I call __HYPERVISOR_iret, the hypervisor calls into my kernel via the registered callback handler. None of the bits in the event channel pending arrays are set. If I return via the iret call, the hypervisor immediately calls back into the handler. The user RIP never changes, so it is clearly not making forward

Hi everyone, I would like to ask what the current status of FLR, or better of FLR emulation is in latest Xen and if we can expect better support in the future. I''m asking because with xl (latest build and traditional qemu, not upstream), I always had problems with rebooting domUs which have vga cards passed through to them, because appearently they don''t get reinitialized and

This patch adds new control messages for vcpu hotplug events. Via the xm vcpu_hotplug sub-program, VCPUS in domains can be enabled/disabled when CONFIG_HOTPLUG_CPU is enabled in the target domain''s kernel. Currently there is nothing that tracks whether a VCPU is up or down. My previous [1]patch added a new per-VCPU flag (VCPUF_down) which could be used to keep track of which VCPUS are

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Hi All, We tested the xm block-attach/detach command. It repeats block-attach/detach command for DomU and pv-on-hvm on HVM Domain. (block-attach -> block-detach -> block-attach -> block-detach -> ...) The block-attach command failed when repeating 256 times. It is because the channel had not been freed in blkfront. Therefore, it remain using the event channel. This patch is