search for: 1048576

...8192 00230000 Private 4096 00240000 Private 1114112 00350000 Private 643072 00400000 Image 1642496 ..hronicles\game.exe 517632 2/24/08 23:48:38 005A0000 Private 1114112 006B0000 Private 1114112 007C0000 Private 1114112 008D0000 Private 1048576 009D0000 Private 1114112 00AE0000 Private 1114112 00BF0000 Private 1048576 00CF0000 Private 1048576 00DF0000 Private 1048576 00F20000 Private 1048576 01020000 Private 1048576 01120000 Private 1048576 01220000 Private 1114112 01330000 Private...

...out from 15 test users to 250 production users. Thanks for your help. PS: Raw logs are also attached below. -dp write(1, " * 1 0 7 9 5 F E T C".., 2050) = 2050 mmap64(0x00000000, 7356416, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFD800000 munmap(0xFE602000, 1048576) = 0 munmap(0xFE502000, 1048576) = 0 munmap(0xFE402000, 1048576) = 0 munmap(0xFE302000, 1048576) = 0 munmap(0xFE202000, 1048576) = 0 munmap(0xFE102000, 1048576) = 0 munmap(0xFE002...

How can I tell if this is normal behaviour? Oracle imports are horribly slow, an order of magnitude slower than on the same hardware with a slower disk array and Solaris 9. What I can look for to see where the problem lies? The server is 99% idle right now, with one database running. Each sample is about 5 seconds. I''ve tried setting kernel parameters despite the docs saying that

...s@redhat.com>: > Gandalf, is there an XVA file publically available (pref. not > too big) that we can look at? I can try to provide one, but it's simple: # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 ---------- 0/0 42353 1970-01-01 01:00 ova.xml ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000001.checksum ---------- 0/0 1048576 1970-01-01 01:00 Ref:...

...ilable (pref. not > >> too big) that we can look at? > > > > I can try to provide one, but it's simple: > > > > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 > > ---------- 0/0 42353 1970-01-01 01:00 ova.xml > > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 > > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum > > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 > > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000001.checksum > > ---------- 0...

...there an XVA file publically available (pref. not >> too big) that we can look at? > > I can try to provide one, but it's simple: > > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 > ---------- 0/0 42353 1970-01-01 01:00 ova.xml > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000001.checksum > ---------- 0/0 1048576 1...

...there an XVA file publically available (pref. not > > too big) that we can look at? > > I can try to provide one, but it's simple: > > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 > ---------- 0/0 42353 1970-01-01 01:00 ova.xml > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000001.checksum > ---------- 0/0 1048576 1...

...gt;> too big) that we can look at? >> > >> > I can try to provide one, but it's simple: >> > >> > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 >> > ---------- 0/0 42353 1970-01-01 01:00 ova.xml >> > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 >> > ---------- 0/0 40 1970-01-01 01:00 >> Ref:175/00000000.checksum >> > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 >> > ---------- 0/0 40 1970-01-01 01:00 >> Ref:175/00000001.c...

...there an XVA file publically available (pref. not > > too big) that we can look at? > > I can try to provide one, but it's simple: > > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 > ---------- 0/0 42353 1970-01-01 01:00 ova.xml > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000001.checksum > ---------- 0/0 1048576 1...

...centos.alt.x86_64 Please have a look at below guest logs, [root at hvmc6 ~]# uname -a Linux hvmc6 3.4.50-8.el6.centos.alt.x86_64 #1 SMP Fri Jun 21 03:14:22 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root at hvmc6 ~]# xenstore-ls memory initial-reservation = "1193984" initial-target = "1048576" static-max = "16777216" target = "1048576" dynamic-min = "1048576" dynamic-max = "1048576" memory-offset = "-258100" [root at hvmc6 ~]# dmesg | grep -i balloon xen/balloon: Initialising balloon driver. xen-balloon: Initialising balloon driver....

...ion from the system and deleted LUN using Navisphere user interface. After rebooting system, I still see SAN mappings in system. Here is the affected partition mappings .... ============================== cat /proc/partitions ============================== major minor #blocks name 8 16 1048576 sdb 8 48 1048576 sdd 8 80 1048576 sdf 8 112 1048576 sdh ============================ When I try to print information using parted, I am getting the following information .... ========================================================================================= #parte...

On 2017-11-15 21:24, Richard W.M. Jones wrote: > On Wed, Nov 15, 2017 at 09:07:12PM +0100, Max Reitz wrote: >> On 2017-11-15 21:06, Gandalf Corvotempesta wrote: >>> 2017-11-15 20:59 GMT+01:00 Max Reitz <mreitz@redhat.com>: >>>> Well, you can't just add support to qemu-img alone either. Every image >>>> format supported by qemu-img is one

...~ # xl migrate app01 host01 migration target: Ready to receive domain. Saving to migration stream new xl format (info 0x0/0x0/1076) Loading new save file <incoming migration stream> (new xl fmt info 0x0/0x0/1076) Savefile contains xl domain config xc: progress: Reloading memory pages: 53248/1048576 5% xc: progress: Reloading memory pages: 105472/1048576 10% <snip> xc: progress: Reloading memory pages: 996352/1048576 95% xc: progress: Reloading memory pages: 1048810/1048576 100% migration target: Transfer complete, requesting permission to start domain. migration receiver stream...

Hi all. I use LXC on Centos 7 x86-64, with libvirt version 1.2.6 and 1.2.12 My container has bridged network: # virsh dumpxml test1 <domain type='lxc'> <name>test1</name> <uuid>518539ab-7491-45ab-bb1d-3d7f11bfb0b1</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memtune> <hard_limit unit='KiB'>1048576</hard_limit> <soft_limit unit='KiB'>1048576</soft_limit> <swap_hard_limit unit='KiB'>2097152</...

I am creating some custom nagios plugins and I am scraping data from xen using the nagios command: /usr/sbin/xentop -b -i 2 -d1 I am trying to get the network tx / rx data, however I think I am missing something here. NETTX(k) NETRX(k) So total network bandwidth is 1048576 k if the above header from xentop is true. So I am wondering why the output for each vm exceeds the theoretical max, Is it really not measured in kilobits, or maybe there is something screwy with the counters? Any help is much appreciated. If I add up all my vm values for RX I get: 5527563 k T...

...c/grub.conf: kernel /vmlinuz-2.6.18-164.11.1.el5 ro root=LABEL=/ elevator=deadline quiet - On sysctl.conf # Special network params net.core.rmem_default = 8388608 net.core.wmem_default = 8388608 net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 1048576 4194304 16777216 net.ipv4.tcp_wmem = 1048576 4194304 16777216 # Disable netfilter on bridges. net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 # Virtual machines special kernel params vm.swappiness = 0...

...> 0 0 >> >> #### this is a part from /proc/self/mountinfo ######## >> 33 20 0:23 / /home/builds ro,relatime - cifs //10.30.20.61/builds >> ro,sec=ntlm,unc=\\10.30.20.61\builds,username=,uid=0,noforceuid,gid=0,noforcegid,addr=10.30.20.61,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1 >> 32 20 0:24 / /home/platform ro,relatime - cifs //10.30.20.61/platform >> ro,sec=ntlm,unc=\\10.30.20.61\platform,username=,uid=0,noforceuid,gid=0,noforcegid,addr=10.30.20.61,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1 >> >> and a...

...NFS server). Here's what happens when I copy several large ISOs into a user's home directory who's logged onto that server: $ quota Disk quotas for user ulrick (uid 1000): Filesystem blocks quota limit grace files quota limit grace /dev/sdc1 68896 921600 1048576 3147 0 0 $ cp -v /mnt/home/images/CentOS-6.* . `/mnt/home/images/CentOS-6.2-i386-netinstall.iso' -> `./CentOS-6.2-i386-netinstall.iso' `/mnt/home/images/CentOS-6.3-i386-bin-DVD1.iso' -> `./CentOS-6.3-i386-bin-DVD1.iso' sdc1: warning, user block quota e...

I am trying to use the "shared mem size" parameter in Samba 2.0.4b, but the size reported by smbstatus does not match the value I am using. Without the parameter, the default is 1MB, and the size reported by smbstatus is indeed 1048576. However, when I set the value of "shared mem size" to 5242880 (5MB), smbstatus says 879608. Is smbstatus not reporting the actual size, or is this accurate and the shared memory size has actually been reduced instead of increased? Thanks. -- ------------------------------------------...

...25.1 2 1 306221931 295316847 2 0 2032754 13732515 98294764 1149168400 0 slave4 --b--- 276 0.0 4194304 25.1 4194304 25.1 2 1 19094 7796 2 0 19290 25627 487620 357648 0 wbsrvcs-60 --b--- 12 0.0 1048576 6.3 2097152 12.5 2 1 1576 8 2 0 2460 6237 109949 83874 0 wbsrvcs-84 --b--- 12 0.0 1048576 6.3 2097152 12.5 2 1 1573 8 2 0 2433 6688 109973 88770 0 For the red part,...