search for: balloons

Some virtio-win drivers contain more files than just *.{cat,inf,sys}. They are filtered out currently, which prevents the drivers from being installed by PnP. Stop filtering driver files by extension, and copy all of them instead. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v1 -> v2: - update unit test to match the changed behavior v2v/v2v_unit_tests.ml | 202

v2 -> v3 - Don't make a special case for WdfCoInstaller* files. There is a difference of opinion about whether copying these is necessary, but it seems like it is not harmful. Rich.

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat

Hi, I am using centos4 and am trying to build a source kernel dom0 with xen. I cloned a copy of the xen repository and did the following hg clone http://xenbits.xensource.com/xen-2.0.hg cd xen-2.0.hg/xen make dist cd linux-2.6.11-xen0 make ARCH=xen oldconfig make modules make modules_install make install After which point I get the following error : CC drivers/xen/balloon/balloon.o

Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html https://www.redhat.com/archives/libguestfs/2015-November/msg00065.html Currently the product variant (eg.

...ilities how auto-balloon can be combined > with host directed ballooning to yield good results in a variety of > configurations [3]. I think we're headed to the same destination here; the variant which I came up with (and suggested to Daniel and Luiz, CC'd) is similar: the guest self-balloons, giving up pages when it can, but the host sets a ceiling. This way, if the host really needs to set a limit, it can: a disobedient guest will start paging. But generally, a guest should use its judgement to balloon its own pages as it can (below the ceiling). Thoughts? Rusty.

...ilities how auto-balloon can be combined > with host directed ballooning to yield good results in a variety of > configurations [3]. I think we're headed to the same destination here; the variant which I came up with (and suggested to Daniel and Luiz, CC'd) is similar: the guest self-balloons, giving up pages when it can, but the host sets a ceiling. This way, if the host really needs to set a limit, it can: a disobedient guest will start paging. But generally, a guest should use its judgement to balloon its own pages as it can (below the ceiling). Thoughts? Rusty.

https://github.com/rwmjones/libguestfs/tree/rewrite-virtio-copy-drivers Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html

On Tue, Jul 07, 2015 at 01:36:23PM +0900, Gioh Kim wrote: > From: Gioh Kim <gurugio at hanmail.net> > > Apply mobile page migration into balloon driver. > The balloong driver has an anonymous inode that manages > address_space_operation for page migration. > > Signed-off-by: Gioh Kim <gioh.kim at lge.com> > --- > drivers/virtio/virtio_balloon.c | 3 ++

On Tue, Jul 07, 2015 at 01:36:23PM +0900, Gioh Kim wrote: > From: Gioh Kim <gurugio at hanmail.net> > > Apply mobile page migration into balloon driver. > The balloong driver has an anonymous inode that manages > address_space_operation for page migration. > > Signed-off-by: Gioh Kim <gioh.kim at lge.com> > --- > drivers/virtio/virtio_balloon.c | 3 ++

On 03.02.20 17:18, Alexander Duyck wrote: > On Mon, 2020-02-03 at 08:11 -0500, Michael S. Tsirkin wrote: >> On Thu, Jan 30, 2020 at 11:59:46AM -0800, Tyler Sanderson wrote: >>> >>> On Thu, Jan 30, 2020 at 7:31 AM Wang, Wei W <wei.w.wang at intel.com> wrote: >>> >>> On Thursday, January 30, 2020 11:03 PM, David Hildenbrand wrote: >>>

On 03.02.20 17:18, Alexander Duyck wrote: > On Mon, 2020-02-03 at 08:11 -0500, Michael S. Tsirkin wrote: >> On Thu, Jan 30, 2020 at 11:59:46AM -0800, Tyler Sanderson wrote: >>> >>> On Thu, Jan 30, 2020 at 7:31 AM Wang, Wei W <wei.w.wang at intel.com> wrote: >>> >>> On Thursday, January 30, 2020 11:03 PM, David Hildenbrand wrote: >>>

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

From: Gioh Kim <gurugio at hanmail.net> Apply mobile page migration into balloon driver. The balloong driver has an anonymous inode that manages address_space_operation for page migration. Signed-off-by: Gioh Kim <gioh.kim at lge.com> --- drivers/virtio/virtio_balloon.c | 3 ++ include/linux/balloon_compaction.h | 15 +++++++-- mm/balloon_compaction.c | 65

...alloon.h | 1 + include/sysemu/balloon.h | 10 ++- 5 files changed, 134 insertions(+), 5 deletions(-) diff --git a/balloon.c b/balloon.c index f2ef50c..a37717e 100644 --- a/balloon.c +++ b/balloon.c @@ -36,6 +36,7 @@ static QEMUBalloonEvent *balloon_event_fn; static QEMUBalloonStatus *balloon_stat_fn; +static QEMUBalloonFreePages *balloon_free_pages_fn; static void *balloon_opaque; static bool balloon_inhibited; @@ -65,9 +66,12 @@ static bool have_balloon(Error **errp) } int qemu_add_balloon_handler(QEMUBalloonEvent *event_func, - QEMUBa...

...oon driver be made capable of inflating/deflating the balloon automatically or only manually by using xm mem-set? 3. The guest OS balloon driver will have to be modified, will any modifications to xen(dom0) be required? 4. What exactly does the number of pages in high- and low-memory balloons in the balloon_stats structure and in the output of cat /proc/xen/balloon mean? 5. What is the current state of the balloon driver? Please correct me if my any of my assumptions are wrong. I''d be very grateful if someone could provide any information regarding this. Thanks, Ashutos...

Now, VM has a feature to migrate non-lru movable pages so balloon doesn't need custom migration hooks in migrate.c and compact.c. Instead, this patch implements page->mapping ->{isolate|migrate|putback} functions. With that, we could remove hooks for ballooning in general migration functions and make balloon compaction simple. Cc: virtualization at lists.linux-foundation.org Cc: Rafael

On Tue, Jun 2, 2015 at 10:27 AM, Gioh Kim <gioh.kim at lge.com> wrote: > Apply driver page migration into balloon driver. > > Signed-off-by: Gioh Kim <gioh.kim at lge.com> > --- > drivers/virtio/virtio_balloon.c | 2 ++ > fs/proc/page.c | 4 +-- > include/linux/balloon_compaction.h | 42 ++++++++++++++++------- >

On Tue, Jun 2, 2015 at 10:27 AM, Gioh Kim <gioh.kim at lge.com> wrote: > Apply driver page migration into balloon driver. > > Signed-off-by: Gioh Kim <gioh.kim at lge.com> > --- > drivers/virtio/virtio_balloon.c | 2 ++ > fs/proc/page.c | 4 +-- > include/linux/balloon_compaction.h | 42 ++++++++++++++++------- >