similar to: understanding dom0 usage memory

Hi, I have started the xen kernel with parameter dom0_mem=300M. xm info | grep total total_memory : 2045 Name ID Mem VCPUs State Time(s) Domain-0 0 300 2 r----- 292.1 FTP 822 1 56.7 LDAP 1 822 1 r----- 541.3 NFS1 822 1 14.8 NFS2 822 1 1.4 For the

Hello, I am running a functional Xen 4.0 platform. The objective is the project I am currently running is to replace 4 VMWare ESX by 4 Xen 4.0 hypervisors. I have been able to reproduce all the core VMWare features in Xen (but better of course =D) except memory overcommitment. I know this feature has been included since Xen 3.3 but I have found almost no information about it. When I try to

Hi List, I get the following error when trying to create a new vm. There is 1024MB total physcial memory on the machine with 320MB used. Error: I need 1045876KiB, but dom0_min_mem is 1048576 and shrinking to 1048576 KiB would leave only 1021888 KiB free. Thanks in advance M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

On 27/08/15 10:42, Muzaffer Tolga Ozses wrote: > Please check permissions as this sounds like a permissions issue m I am confused then. /home/vmail/Maildir is 700 for vmail:vmail. If dovecot-lda runs as vmail then there's no problem, if it runs as root it shouldn't face problems either. How can I determine which user dovecot-lda runs under? Thanks, -- Paulo Matos

i have: class Library << ActiveRecord::Base has_many :books end class Book << ActiveRecord::Base belongs_to :library end in my controller i have: render :xml=> Library.find(:all).to_xml(:include=>books) but, i would like put a condition in the books ( e.: pages >= 100 ) i would like to create a xml with all Libraries, but books with pages more than 100) How to

Hi, I have setup postfix master.cf to use dovecot-lda to deliver (using -m) all messages to PreInbox: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -a ${recipient} -d ${user}@${nexthop} -m PreINBOX And enabled lda_mailbox_autocreate. The message I have now it: Aug 27 10:02:29 lda(): Info:

I _think_ there is a problem with the license as well: Z3 is MIT, so clang would have to be released with Z3's license. On Tue, 12 Feb 2019, 09:24 Roman Lebedev via cfe-dev <cfe-dev at lists.llvm.org wrote: > On Tue, Feb 12, 2019 at 4:13 PM Paulo Matos via cfe-dev > <cfe-dev at lists.llvm.org> wrote: > > > > Hello, > > > > I am trying to run scan-build

Having said that, /home/vmail should be owned by vmail, however dovecot-lda should have write access so 700 is a bad idea. On 27/08/2015 3:00 PM, "Muzaffer Tolga Ozses" <tolga at ozses.net> wrote: > ps aux | grep lda > On 27/08/2015 2:58 PM, "Paulo Matos" <paulo at matos-sorge.com> wrote: > >> On 27/08/15 10:42, Muzaffer Tolga Ozses wrote: >>

On 29/08/15 11:31, Timo Sirainen wrote: > On 27 Aug 2015, at 12:07, Paulo Matos <paulo at matos-sorge.com> wrote: >> >> Aug 27 10:02:29 lda(): Info: msgid=<dae42d0cf57bf4496a3dd53e162f8281 at localhost.localdomain>: save failed to open mailbox PreINBOX: Mailbox can't be created > > I have no idea how you could get that error message. Looking at the code I

On Tue, 12 Feb 2019, 14:32 Paulo Matos <pmatos at linki.tools wrote: > > > On 12 February 2019 18:59:21 CET, Mikhail Ramalho < > mikhail.ramalho at gmail.com> wrote: > >I _think_ there is a problem with the license as well: Z3 is MIT, so > >clang > >would have to be released with Z3's license. > > I don't think that's a problem. You are not

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use

Sure this is more likely a gcc bug. However, same toolchain compiled without any problems a week ago. Also, in some organizations, upgrading gcc is very hard if not impossible. On Fri, Jul 22, 2016 at 11:11 AM, Paulo Matos via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On 22/07/16 20:08, Welson Sun via llvm-dev wrote: > > This is gcc4.8.0 compiling HEAD synced on

I don't remember anything other that what I've written in the bug João has mentioned. Probably something like this patch http://llvm.org/bugs/show_bug.cgi?id=14410#c6 ? 2013/2/20 João Matos <ripzonetriton at gmail.com>: > I think so. There have been other reports lately related to this being > wrong. > > http://llvm.org/bugs/show_bug.cgi?id=14410 > > CC'ing

Hi, I am slightly stuck in a corner case I don't know how to debug. I have an optimus setup in a dell xps 9560 with a discrete gpu nvidia geforce 1050 (Pascal - NV130). I installed Fedora and if I do not boot with nouveau.modeset=0, then the computer crashes as soon as I try to start Xorg (I have disabled wayland). So, gdm starts but then as soon as I get into i3 or gnome, the computer

On Thu, Aug 20, 2015 at 8:41 am, Steffen Kaiser < skdovecot at smail.inf.fh-brs.de [skdovecot at smail.inf.fh-brs.de] > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 19 Aug 2015, Paulo Matos wrote: >> You can't change the name of the INBOX - the INBOX is always the INBOX. >> But you can choose the name of the target mailbox. > > How do I do that?

Hi, during some experiments with many guests I get crashing Dom0s because of too less memory. Actually the OOM killer goes ''round and kills random things, preferably qemu-dm''s ;-) The box in question has 128GB of memory, I start with dom0_mem=8192M (or 16384M, doesn''t matter). I also used "dom0_mem=8192M,min:1536M", but that didn''t make any

I''ve installed Xen Hypervisor 3.0.3 (CentOS 5.7, i386) inside Virtualbox 4.1.16 (Mageia 1, i686) and have noticed that Dom0 is consuming 85% of the memory allocated to the VM (1GB) so I''d like to reduce this as much as possible in order to make more room for one or two VM''s. Is there a minimum amount of vRAM that can/should be allocated to Dom0 (using the dom0_mem boot

+LLVMdev On Aug 4, 2012, at 9:45 AM, João Matos wrote: > Charles Davis did a lot of work on Win64 SEH support in LLVM, check commits r131652-r132880. > > As I haven't tested it yet, what exactly is broken? It's not finished yet. All the stuff for assembly code that uses Win64 EH is done, but not the code-gen-side stuff (cf. Win64Exception class in CodeGen). I was about to

Hi, I have setup message filtering and for example, I might move a message which a given sender to folder special/. This folder is created and shows up twice in INBOX/special/ and special/. They are however exactly the same folder. If I subscribe to one I am automatically subscribed to the other and viceversa. Not too happy with this configuration. I have a feeling this is related to