search for: remote_dom

...one. [2006-05-18 14:48:06 xend.XendDomainInfo] ERROR (XendDomainInfo:1432) Exception in alloc_unbound(11) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1430, in createChannel return xc.evtchn_alloc_unbound(dom=self.domid, remote_dom=0) error: (22, ''Invalid argument'') [2006-05-18 14:48:06 xend.XendDomainInfo] ERROR (XendDomainInfo:196) Domain construction failed Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 189, in create vm.initDoma...

hi all, I have a doubt. about event channel of xen, a piece of code here " evtchn_bind_interdomain() { struct domain *ld= current->domain }", it is used to bind domain A and domain B but why it is always current->domain ? -- ---------------------------------------------------------- regards, yandong _______________________________________________ Xen-devel mailing list

...0 ) @@ -132,7 +140,7 @@ static long evtchn_alloc_unbound(evtchn_ spin_lock(&d->evtchn_lock); if ( (port = get_free_port(d)) < 0 ) - ERROR_EXIT(port); + ERROR_EXIT_DOM(port, d); chn = evtchn_from_port(d, port); rc = xsm_evtchn_unbound(d, chn, alloc->remote_dom); @@ -186,11 +194,11 @@ static long evtchn_bind_interdomain(evtc lchn = evtchn_from_port(ld, lport); if ( !port_is_valid(rd, rport) ) - ERROR_EXIT(-EINVAL); + ERROR_EXIT_DOM(-EINVAL, rd); rchn = evtchn_from_port(rd, rport); if ( (rchn->state != ECS_UNBOUND) ||...

...struct evtchn_alloc_unbound *alloc_unbound = arg; + PRE_MEM_READ("EVTCHNOP_alloc_unbound", + (Addr)&alloc_unbound->dom, sizeof(alloc_unbound->dom)); + PRE_MEM_READ("EVTCHNOP_alloc_unbound", + (Addr)&alloc_unbound->remote_dom, + sizeof(alloc_unbound->remote_dom)); + break; + } + default: + if ( compat ) + bad_subop(tid, layout, arrghs, status, flags, + "__HYPERVISOR_event_channel_op_compat", cmd); + else + bad_subop(tid, layout, arrghs,...

...t;+ while (dom != NULL) { >+ n = dom->next; >+ if (dom->is_dead) >+ remove_domain(dom); >+ dom = n; > } > } > > static void handle_tty_read(struct domain *dom) > { > ssize_t len; >- xcs_msg_t msg; >- >- msg.type = XCS_REQUEST; >- msg.u.control.remote_dom = dom->domid; >- msg.u.control.msg.type = CMSG_CONSOLE; >- msg.u.control.msg.subtype = CMSG_CONSOLE_DATA; >- msg.u.control.msg.id = 1; >- >- len = read(dom->tty_fd, msg.u.control.msg.msg, 60); >+ char msg[80]; >+ struct ring_head *inring = >+ (struct ring_head *)(dom-...

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

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 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) *

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) *

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) *

Hi Andi, 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

Hi Andi, 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

Hi Andi, 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

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-rc7 + your patches + the last batch of pv_ops patches I posted. This patch generally restricts itself to Xen-specific parts of the tree, though it does make a few small changes elsewhere. These patches include: - some helper routines for allocating address space and walking pagetables - Xen

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-rc7 + your patches + the last batch of pv_ops patches I posted. This patch generally restricts itself to Xen-specific parts of the tree, though it does make a few small changes elsewhere. These patches include: - some helper routines for allocating address space and walking pagetables - Xen

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) *

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) *