similar to: start a domain, minimal memory request.

On 04/09/2018 09:00 AM, llilulu wrote: > Hi: > I use libvirt manage virtual guest, When I start many virtual domain(my host 128G physical memory）, example, I start 100 guest, 1G per guest。sometime I will encounter "cannot allocate memory", "cannot set up guest memory \'pc.ram\'： cannot allocate memory". sometime encounter qemu process killed by system(oom),

Hi, today I noticed that one of my HVs started swapping aggressively and noticed that the two guests running on it use quite a bit more ram than I assigned to them. They respectively were assigned 124G and 60G with the idea that the 192G system then has 8G for other purposes. In top I see the VMs using about 128G and 64G which means there is nothing left for the system. This is on a CentOS 7

Hi: My libvirt is 3.4.0 and qemu is 2.9.0, My host has a big memory(128G), I run many guest on my host(80 guests), when I batch stop and start guests, some guest will crash, the qemu log is "qemu: qemu_thread_create: Resource temporarily unavailable". I search qemu code, I find qemu_thread_create just like pthread_create function. I search on internet, someone say that is a bug of

Ramón García wrote: > Based on my experience this last one (the generation of shared > libraries) is the most important performance wise, and the one that > would make a difference from a performance point of view. > > That's more or less true: generating shared libraries will improve startup time, not steady-state time. It will decrease steady-state performance (both for

On Fri, Apr 20, 2018 at 04:54:53PM -0400, Mikulas Patocka wrote: > On Fri, 20 Apr 2018, Michal Hocko wrote: > > No way. This is just wrong! First of all, you will explode most likely > > on many allocations of small sizes. Second, CONFIG_DEBUG_VM tends to be > > enabled quite often. > > You're an evil person who doesn't want to fix bugs. Steady on. There's

On Fri, Apr 20, 2018 at 04:54:53PM -0400, Mikulas Patocka wrote: > On Fri, 20 Apr 2018, Michal Hocko wrote: > > No way. This is just wrong! First of all, you will explode most likely > > on many allocations of small sizes. Second, CONFIG_DEBUG_VM tends to be > > enabled quite often. > > You're an evil person who doesn't want to fix bugs. Steady on. There's

On 16.01.2015 15:14, Michal Privoznik wrote: > On 16.01.2015 13:33, Dennis Jacobfeuerborn wrote: >> Hi, >> today I noticed that one of my HVs started swapping aggressively and >> noticed that the two guests running on it use quite a bit more ram than >> I assigned to them. They respectively were assigned 124G and 60G with >> the idea that the 192G system then has

I would prefer to see actual code to make safe schedules. With code I can see what changes one must make. I can also show in detail these changes, which would give security to the LLVM project that the proposal is viable. By contrast, without code, neither me nor LLVM project can ensure that the project will be successfully performed behind schedule. Since this is a difficult project (we are

On Wed, May 9, 2018 at 10:39 AM, Hiroshi Yamauchi <yamauchi at google.com> wrote: > > > On Tue, May 8, 2018 at 11:15 AM Daniel Berlin <dberlin at dberlin.org> wrote: > >> >> >> On Tue, May 8, 2018 at 10:38 AM, Hiroshi Yamauchi via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> ( >>> ​I came across this issue in

Below is an outline of various usage models for MCJIT that I put together based on conversations at last month's LLVM Developer Meeting. If you're using or thinking about using MCJIT and your use case doesn't seem to fit in one of the categories below then either I didn't talk to you or I didn't understand what you're doing. In any case, I'd like to see this get

On Thu 19-04-18 12:12:38, Mikulas Patocka wrote: [...] > From: Mikulas Patocka <mpatocka at redhat.com> > Subject: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM > > The kvmalloc function tries to use kmalloc and falls back to vmalloc if > kmalloc fails. > > Unfortunatelly, some kernel code has bugs - it uses kvmalloc and then > uses DMA-API on the returned

On Thu 19-04-18 12:12:38, Mikulas Patocka wrote: [...] > From: Mikulas Patocka <mpatocka at redhat.com> > Subject: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM > > The kvmalloc function tries to use kmalloc and falls back to vmalloc if > kmalloc fails. > > Unfortunatelly, some kernel code has bugs - it uses kvmalloc and then > uses DMA-API on the returned

On Thu, May 10, 2018 at 12:05 PM, Hiroshi Yamauchi <yamauchi at google.com> wrote: > > > On Wed, May 9, 2018 at 8:24 PM Daniel Berlin <dberlin at dberlin.org> wrote: > >> >> >> On Wed, May 9, 2018 at 10:39 AM, Hiroshi Yamauchi <yamauchi at google.com> >> wrote: >> >>> >>> >>> On Tue, May 8, 2018 at 11:15 AM

On Wed, May 9, 2018 at 8:24 PM Daniel Berlin <dberlin at dberlin.org> wrote: > > > On Wed, May 9, 2018 at 10:39 AM, Hiroshi Yamauchi <yamauchi at google.com> > wrote: > >> >> >> On Tue, May 8, 2018 at 11:15 AM Daniel Berlin <dberlin at dberlin.org> >> wrote: >> >>> >>> >>> On Tue, May 8, 2018 at 10:38 AM,

Hi all, After the memory leaks (bug 1967 <https://bugzilla.mindrot.org/show_bug.cgi?id=1967>) I reported in bugzilla are fixed, I also applied melton(http://lcs.ios.ac.cn/~xuzb/melton.html) to detect the potential bugs in sshd (openssh-5.9p1). The url below is the index of bug reports that are checked as real bugs manually.

Hi Samba world, Have been struggling with this for the past 10 days, we are running Samba 3.0.22 on VCS zone, we have end users saving files onto Samba mapped drive, and complained that it 5mins to save 300 files, now it takes 30 mins. There is recently a change in the topology. Before Enduser ----------- samba mapped -------------- server (local attached storage)

Hi: I encounter a promble, when I start a domain(only a blank disk, not install system), I can hotplug NIC, But I cannot hot unplug NIC. I consider the domain start from a blank disk, not install system, so the domain haven't virtio too, I suspect virtio problem. But I cann't confirm. Can any one tell me? Thanks

In the next version of the survival package I intend to make a non-upwardly compatable change to the survfit object.? With over 600 dependent packages this is not something to take lightly, and I am currently undecided about the best way to go about it.? I'm looking for advice. The change: 20+ years ago I had decided not to include the initial x=0,y=1 data point in the survfit object

https://bugzilla.mindrot.org/show_bug.cgi?id=1967 Bug #: 1967 Summary: Potential memory leak Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: unassigned-bugs at

On Dec 9, 2013, at 11:08 AM, Kaylor, Andrew <andrew.kaylor at intel.com> wrote: > Below is an outline of various usage models for MCJIT that I put together based on conversations at last month’s LLVM Developer Meeting. If you’re using or thinking about using MCJIT and your use case doesn’t seem to fit in one of the categories below then either I didn’t talk to you or I didn’t understand