search for: 216kb

...ame" linux installation (RedHat enterprise 3.0, which they tell me is soon to be upgraded to 4.0). On windows I installed the package gplots without trouble, and it works fine. When I attempted to do the same on the unix computer, the following error message was forthcoming: downloaded 216Kb * Installing *source* package 'gplots' ... ** R ** data ** inst ** preparing package for lazy loading Loading required package: gtools Warning in library(pkg, character.only = TRUE, logical = TRUE, lib.loc = lib.loc) : there is no package called 'gtools' Error: package &...

.............done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen) (XEN) Freed 216kB init memory. (END) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

On Sun, 30 Apr 2006, Aristid Breitkreuz wrote: > I am, as said in the subject, new to this list. I have not actually used > LLVM, I tried with an older version but failed. Recently I noticed that > 1.7 came out and looked at the release notes. And there was something > that stroke me: llvm-g++ adheres to the IA64 ABI but _not for > exceptions_. I was not able to find information why

Hello, I am, as said in the subject, new to this list. I have not actually used LLVM, I tried with an older version but failed. Recently I noticed that 1.7 came out and looked at the release notes. And there was something that stroke me: llvm-g++ adheres to the IA64 ABI but _not for exceptions_. I was not able to find information why this is so and why it is necessary, so I hope you don't

...7 B = 2876336 blocks = 1404 MB indexes : 14452732 B = 28227 blocks = 14 MB 7221164 dovecot.index 10436 dovecot.index.cache 7221132 dovecot.index.log (this will be truncated after a while) - 16064 VSZ, 8012 RSS after SELECT completed - 14MB is mmaped index files - 216kB heap left of which 70kB actually in use - heap usage was 25MB VSZ/RSS constantly while syncing, but allocations were so large that libc used anonymous mmap()s so they got dropped after sync - VSZ peaked at 32MB, most likely because index file(s) were temporarily being...

...isabled > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input > to Xen) > (XEN) Freed 216kB init memory. > (XEN) no cpu_id for acpi_id 5 > (XEN) no cpu_id for acpi_id 6 > (XEN) no cpu_id for acpi_id 7 > (XEN) no cpu_id for acpi_id 8 > *(XEN) physdev.c:162: dom0: wrong map_pirq type 3* > > > ------------------------------------///------------------------------------...

...gt; > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > > > (XEN) Xen is relinquishing VGA console. > > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > input > > > to Xen) > > > (XEN) Freed 216kB init memory. > > > (XEN) no cpu_id for acpi_id 5 > > > (XEN) no cpu_id for acpi_id 6 > > > (XEN) no cpu_id for acpi_id 7 > > > (XEN) no cpu_id for acpi_id 8 > > > *(XEN) physdev.c:162: dom0: wrong map_pirq type 3* > > > > > > > >...

I''m running Xen 4.1 (4.1.3-3ubuntu1.3) on an Ubuntu 12.10 server with an AMD FX-8150 processor (8 cores) and 16 GB of RAM. When I boot the server, Xen sees only 3 GB of RAM (instead of 16 GB). If I try to create a domU with more than about 1.5 GB of RAM, the create fails with messages saying it "could not allocate memory for HVM guest". Here''s the output when I do

...(XEN) Scrubbing Free RAM: .done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 216kB init memory. (XEN) PCI add device 0000:00:00.0 (XEN) PCI add device 0000:00:02.0 (XEN) PCI add device 0000:00:02.1 (XEN) PCI add device 0000:00:1b.0 (XEN) PCI add device 0000:00:1c.0 (XEN) PCI add device 0000:00:1c.1 (XEN) PCI add device 0000:00:1d.0 (XEN) PCI add device 0000:00:1d.1 (XEN) PCI add...