search for: 2048m

...mem=size option for memdisk The only thing i have found is mem=size Mark available memory above this point as Reserved. But i'm not sure if this is accurate and i'd like to understand the purpose of this option I am PXE booting a LENOVO machine which fails unless i add mem=2048m and i am trying to better understand what this is doing so I can better understand why this works but leaving it out fails. sincerely, John Cutler

...CentOS Linux (3.18.25-19.el7.x86_64) 7 (Core)) > * CentOS Linux (3.10.0-327.13.1.el7.x86_64) 7 (Core) > > It works as expected with no issues. > > > > But when booting as dom0 using the xen hypervisor > * CentOS Linux, with Xen hypervisor > > tested with dom0_mem=2048M,max:2048M (as well as 1024M) > > the problems occur as I have describe. > This probably isn't it, but there was a problem I was having where the workaround was to give the dom0 4096M+ so that 64 bit references were used instead of 32 bit. You could try that and see what happens. --...

...its.xen.org/people/mayoung/EL6.xen on my centos6 server. I am running 2.6.32-131.12.1.el6.xendom0.x86_64 kernel available from the same place. 'xl info' reports about available memory as follows: total_memory : 24567 free_memory : 3698 xen_commandline : dom0_mem=2048M and in xend-config.sxp I have: (dom0-min-mem 256) (enable-dom0-ballooning no) (total_available_memory 0) Now one would think that I should have 2048M memory for dom0, right? I started from there, but when starting domUs it has been reduced to 1140M even though I think ballooning is disabled and...

...gt; * CentOS Linux (3.18.25-19.el7.x86_64) 7 (Core)) > * CentOS Linux (3.10.0-327.13.1.el7.x86_64) 7 (Core) > > It works as expected with no issues. > > > > But when booting as dom0 using the xen hypervisor > * CentOS Linux, with Xen hypervisor > > tested with dom0_mem=2048M,max:2048M (as well as 1024M) > > the problems occur as I have describe. Thanks Nathan. It looks then like this may be an issue with upstream Xen, then. Would you be willing to re-post this bug report (with the information that it works running the same kernel on native) to xen-users? I ca...

...98 top: last pid: 431; load averages: 0.00, 0.00, 0.00 up 0+00:28:49 14:09:31 107 processes: 1 running, 106 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 62M Active, 18M Inact, 33M Wired, 40K Cache, 17M Buf, 891M Free Swap: 2048M Total, 2048M Free Notice all of the faults on vmstat and all of the processes are sleeping. I'm trying a cvsup again but I think something was borken. Any ideas? Thanks. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http:/...

Dear mailinglist, I own a Gigabyte motherboard GA 970A UD3 with IOMMU support. Since the update XSA-36 (also part of the latest debian wheezy pkg), the IO-Virtualisation does not work any more as discussed on this mailinglist [0] and [1]. I like to ask, if there is an "official" solution in sight. I''m not sure about my alternatives. How "dangerous" is the

...;): SELECT concat('*:storage=', quota, 'M') AS quota_rule FROM accounts WHERE username = 'mailuser1' AND domain = 'mydomain.com' AND sendonly = false; Jan 14 15:07:10 auth: Debug: master userdb out: USER 1124466689??? mailuser1 at mydomain.com quota_rule=*:storage=2048M auth_token=c0af49e6da382961494c74d54add28b3a077f23c Jan 14 15:07:10 imap-login: Info: Login: user=<mailuser1 at mydomain.com>, method=PLAIN, rip=213.225.33.38, lip=173.212.231.229, mpid=5347, TLS, session=<MpKNj2t/V7XV4SEm> Jan 14 15:07:10 imap(mailuser1 at mydomain.com): Debug: Load...

...*:storage=', quota, 'M') AS quota_rule FROM accounts WHERE >> username = 'mailuser1' AND domain = 'mydomain.com' AND sendonly = false; >> Jan 14 15:07:10 auth: Debug: master userdb out: USER 1124466689 >> mailuser1 at mydomain.com quota_rule=*:storage=2048M >> auth_token=c0af49e6da382961494c74d54add28b3a077f23c >> Jan 14 15:07:10 imap-login: Info: Login: >> user=<mailuser1 at mydomain.com>, method=PLAIN, rip=213.225.33.38, >> lip=173.212.231.229, mpid=5347, TLS, session=<MpKNj2t/V7XV4SEm> >> Jan 14 15:07:10...

Hi, I am trying to create a VM with the IVSHMEM feature, and I specify the device using qemu command line argument in my XML by using the pass through tag as follows: <qemu:commandline> <qemu:arg value='-device ivshmem,size=2048M,shm=fd:/mnt/huge/map_1:0x0:0x40000000:/dev/zero:0x0:0x3fffc000:/var/run/.ivshmem_metadata_config_2:0x0:0x4000'/> </qemu:commandline> This seemingly does not work as I get this error: Internal error process exited while connecting to monitor: qemu-system-x86_64: -device ivshmem,size=2...

Hi, I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. How to write the XML file?

...n the list. On Wed, Sep 9, 2015 at 9:40 PM, <john_cutler at dell.com> wrote: > Gene, > > Thank you for your response I have a follow up to that. > > I have 2 different machines using the same pxe boot for both machines > machine A fails at pxe boot if i don?t have mem=2048m while machine b > will fail if it contains mem=2048m Not entirely surprising though certainly disappointing. How it fails would be nice to know. Have you considered other values too, perhaps "mem=1024m"? > Since both machines have 4+GB of ram I am trying to understand what th...

...there appears to be very little going on on the system. eg., root at server5:/tmp# /usr/local/bin/top last pid: 3828; load avg: 4.29, 3.95, 3.84; up 6+23:11:4407:12:47 79 processes: 78 sleeping, 1 on cpu CPU states: 73.0% idle, 0.0% user, 27.0% kernel, 0.0% iowait, 0.0% swap Memory: 2048M phys mem, 32M free mem, 16G total swap, 16G free swap PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND 784 root 17 60 -20 88M 632K sleep 270:03 13.02% nfsd 2694 root 1 59 0 1376K 672K sleep 1:45 0.69% touch 3814 root 5 59 0 30M 3928...

...anagesieve-login: Fatal: pool_system_realloc(4294967296): Out of memory dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 10157 returned error 83 (Out of memory (service managesieve-login { vsz_limit=1024 MB }, you may need to increase it)) --snap I've increased of 2048M and the same above. then with 4096 M happens the following --snip dovecot: managesieve-login: Panic: epoll_ctl(add, 61538840) failed: Bad file descriptor dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 9777 killed with signal 6 (core dumps disabled) --snap How can o...

By natively, I take it using kernel /vmlinuz (vs kernel /xen) Not yet, but working on setting up such an environment. (At this time, I was using virt-install to reproduce the problem, and the original server we are testing on did not support kvm but the 2nd server does). On 2016-04-12 03:26 AM, George Dunlap wrote: > On Mon, Apr 11, 2016 at 9:14 PM, Nathan Coulson <nathan at

...I get an out of memory exception: Not enough memory is available, and dom0 cannot be shrunk any further Each of my domains only uses 256 so I thought there would be sufficient memory for 4 :-/ I am also using ZFS (maybe this is causing problems?) and have tried using the kernel flag: dom0_mem=2048M Any ideas? Thanks, Christian

...ase, I still do not get to allocate my 1.1 GB, and I am at a loss explaining why. The help pages for memory() also do not explain what actually happens with the command line options min-vsize and max-vsize, or at least did not prepare me for the following odd observation. If I specify min-vsize=2048M, then I do not get to read in more than 384 MB of data; it is as if the allocation of a minimum of 2 Gig of RAM actually reduces the amount available. If I specify max-vize=2048M, then I can at least read my data, but still run out of memory trying to run my spatial regression. In other words,...

...concat('*:storage=', quota, 'M') AS quota_rule FROM accounts WHERE > username = 'mailuser1' AND domain = 'mydomain.com' AND sendonly = false; > Jan 14 15:07:10 auth: Debug: master userdb out: USER 1124466689 > mailuser1 at mydomain.com quota_rule=*:storage=2048M > auth_token=c0af49e6da382961494c74d54add28b3a077f23c > Jan 14 15:07:10 imap-login: Info: Login: > user=<mailuser1 at mydomain.com>, method=PLAIN, rip=213.225.33.38, > lip=173.212.231.229, mpid=5347, TLS, session=<MpKNj2t/V7XV4SEm> > Jan 14 15:07:10 imap(mailuser1 at m...

..., quota, 'M') AS quota_rule FROM accounts WHERE > >> username = 'mailuser1' AND domain = 'mydomain.com' AND sendonly = false; > >> Jan 14 15:07:10 auth: Debug: master userdb out: USER 1124466689 > >> mailuser1 at mydomain.com quota_rule=*:storage=2048M > >> auth_token=c0af49e6da382961494c74d54add28b3a077f23c > >> Jan 14 15:07:10 imap-login: Info: Login: > >> user=<mailuser1 at mydomain.com>, method=PLAIN, rip=213.225.33.38, > >> lip=173.212.231.229, mpid=5347, TLS, session=<MpKNj2t/V7XV4SEm> >...

Yes, that is what I did and it all works apart from the error message on the server about the missing home dir The doc seems to indicate that a home dir is needed. Thanks, Leo On 12/1/19 8:42 pm, Stephan Bosch wrote: > > Op 11/01/2019 om 15:27 schreef subscription1: >> I made a mistake when I moved dovecot to a new server and only >> specified mail_location instead of

Hi, I want to use this qemu command '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on' with libvirt but i can't find the 'mem-path' and 'share' in the documentation. because the vhost-user backend based on 'share=on' parameter and libvirt support vhostuser i guess there maybe another way to support this parameter? this is...