search for: _guest_

...dress corresponds to a > virtual address of a host process. So, once the hypervisor knows a guest > physical page is unsued, it knows that the corresponding virtual memory of > the process doesn't need to be transferred in the 1st round. I am sorry, but I do not understand. Why cannot _guest_ simply check the struct page ref count and send them to the hypervisor? Is there any documentation which describes the workflow or code which would use your new API? -- Michal Hocko SUSE Labs

...dress corresponds to a > virtual address of a host process. So, once the hypervisor knows a guest > physical page is unsued, it knows that the corresponding virtual memory of > the process doesn't need to be transferred in the 1st round. I am sorry, but I do not understand. Why cannot _guest_ simply check the struct page ref count and send them to the hypervisor? Is there any documentation which describes the workflow or code which would use your new API? -- Michal Hocko SUSE Labs

...>virtual address of a host process. So, once the hypervisor knows a guest > >>physical page is unsued, it knows that the corresponding virtual memory of > >>the process doesn't need to be transferred in the 1st round. > >I am sorry, but I do not understand. Why cannot _guest_ simply check the > >struct page ref count and send them to the hypervisor? > > Were you suggesting the following? > 1) get a free page block from the page list using the API; No. Use a pfn walk, check the reference count and skip those pages which have 0 ref count. I suspected that...

...>virtual address of a host process. So, once the hypervisor knows a guest > >>physical page is unsued, it knows that the corresponding virtual memory of > >>the process doesn't need to be transferred in the 1st round. > >I am sorry, but I do not understand. Why cannot _guest_ simply check the > >struct page ref count and send them to the hypervisor? > > Were you suggesting the following? > 1) get a free page block from the page list using the API; No. Use a pfn walk, check the reference count and skip those pages which have 0 ref count. I suspected that...

...nt.0'/> > <address type='virtio-serial' controller='0' bus='0' port='1'/> > </channel> > > I mean, do i have to use a different port or something for each VM? The <address> element of a guest XML is related to what the _guest_ sees, not what the host provides. So it is perfectly fine for multiple guests to see the same <address> (each sees their own virtual hardware, and could care less if some other guest has similar virtual hardware). Similarly for the name of the <target> element - each guest will see the...

From: Dmitry Fleytman <dfleytma at redhat.com> V3 changes: 1. Compat macro added 2. Feature name beautification V2 changes: 1. _GUEST_ added to command and feature names 2. Live migration logic fixed Reported-by: Michael S. Tsirkin <mst at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO offload on the fly without device reinitialization. Curre...

From: Dmitry Fleytman <dfleytma at redhat.com> V3 changes: 1. Compat macro added 2. Feature name beautification V2 changes: 1. _GUEST_ added to command and feature names 2. Live migration logic fixed Reported-by: Michael S. Tsirkin <mst at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO offload on the fly without device reinitialization. Curre...

...s to a >> virtual address of a host process. So, once the hypervisor knows a guest >> physical page is unsued, it knows that the corresponding virtual memory of >> the process doesn't need to be transferred in the 1st round. > I am sorry, but I do not understand. Why cannot _guest_ simply check the > struct page ref count and send them to the hypervisor? Were you suggesting the following? 1) get a free page block from the page list using the API; 2) if page->ref_count == 0, send it to the hypervisor Btw, ref_count may also change at any time. > Is there any > d...

...address of a host process. So, once the hypervisor knows a guest >>>> physical page is unsued, it knows that the corresponding virtual memory of >>>> the process doesn't need to be transferred in the 1st round. >>> I am sorry, but I do not understand. Why cannot _guest_ simply check the >>> struct page ref count and send them to the hypervisor? >> Were you suggesting the following? >> 1) get a free page block from the page list using the API; > No. Use a pfn walk, check the reference count and skip those pages which > have 0 ref count....

Goodmorning building the latest master of XEN d9639236: Ian Campbell, xen: arm: correct return value of raw_copy_{to/from}_guest_*, raw_clear_guest For the Allwinner A20 arm board XEN is giving me this error: WARNING: ignoring attempt to set core boot address 7ff88454 on core -1 WARNING: Not kicking secondary CPUs Starting kernel ... - UART enabled - - CPU 00000000 booting - - Xen starting in Hyp mode - - Zero BSS - - Sett...

Hello. Just a quick question. Is "setvcpus $windowsVM --guest 4" supposed to work? I have qemu-guest-agent (1.6.something) running inside a windows7 vm but all i get is: virsh # setvcpus windows7 --guest 4 error: invalid argument: requested vcpu count is greater than the count of enabled vcpus in the domain: 4 > 1 The xml file looks like this: <vcpu placement='static'

On Tue 18-07-17 10:12:14, Wei Wang wrote: [...] > Probably I should have included the introduction of the usages in > the log. Hope it is not too later to explain here: Yes this should have been described in the cover. > Live migration needs to transfer the VM's memory from the source > machine to the destination round by round. For the 1st round, all the VM's > memory is

On Tue 18-07-17 10:12:14, Wei Wang wrote: [...] > Probably I should have included the introduction of the usages in > the log. Hope it is not too later to explain here: Yes this should have been described in the cover. > Live migration needs to transfer the VM's memory from the source > machine to the destination round by round. For the 1st round, all the VM's > memory is

...host process. So, once the hypervisor knows a guest > >>>>physical page is unsued, it knows that the corresponding virtual memory of > >>>>the process doesn't need to be transferred in the 1st round. > >>>I am sorry, but I do not understand. Why cannot _guest_ simply check the > >>>struct page ref count and send them to the hypervisor? > >>Were you suggesting the following? > >>1) get a free page block from the page list using the API; > >No. Use a pfn walk, check the reference count and skip those pages which > &gt...

...host process. So, once the hypervisor knows a guest > >>>>physical page is unsued, it knows that the corresponding virtual memory of > >>>>the process doesn't need to be transferred in the 1st round. > >>>I am sorry, but I do not understand. Why cannot _guest_ simply check the > >>>struct page ref count and send them to the hypervisor? > >>Were you suggesting the following? > >>1) get a free page block from the page list using the API; > >No. Use a pfn walk, check the reference count and skip those pages which > &gt...

Hello, I am just installing XCP 0.1.1 on a server with 24GB RAM Normally XCP is a 64 bits version but * *uname -a* Linux node012 2.6.27.42-0.1.1.xs0.1.1.737.1065xen #1 SMP Fri Jan 15 16:20:16 EST 2010 i686 i686 i386 GNU/Linux (not a x86_64 version !!!!) * *cat /proc/meminfo* MemTotal: 746496 kB MemFree: 384332 kB Buffers:

From: Dmitry Fleytman <dfleytma at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO offload on the fly without device reinitialization. Current Virtio specification doesn't support this requirement. The solution proposed by following spec patch is to add a new control command for this purpose. The same

From: Dmitry Fleytman <dfleytma at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO offload on the fly without device reinitialization. Current Virtio specification doesn't support this requirement. The solution proposed by following spec patch is to add a new control command for this purpose. The same

Hello, I''m using Red Hat AS 5 with Xen 3.0, and sometimes ''xm console'' does not work, the most of times when I''m trying to connect one full-virt machine with different arch from server, for example: [root@xen-5 ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1933 8

From: Dmitry Fleytman <dfleytma at redhat.com> V2 changes: 1. _GUEST_ added to command and feature names 2. Live migration logic fixed Reported-by: Michael S. Tsirkin <mst at redhat.com> One of recently introduced Windows features (RSC) requires network driver to be able to enable and disable HW LRO offload on the fly without device reinitialization. Curre...