search for: 204g

...G 20G 413G 5% / tmpfs 252G 63M 252G 1% /dev/shm tmpfs 5,0M 0 5,0M 0% /run/lock efivarfs 496K 335K 157K 69% /sys/firmware/efi/efivars /dev/sda2 1,8G 204M 1,5G 12% /boot /dev/sda1 1,9G 12M 1,9G 1% /boot/efi /dev/sdb 932G 728G 204G 79% /disco1TB-0 /dev/sdc 932G 718G 214G 78% /disco1TB-1 /dev/sde 932G 720G 212G 78% /disco1TB-2 /dev/sdd 1,9T 1,5T 387G 80% /disco2TB-0 tmpfs 51G 4,0K 51G 1% /run/user/0 *gluster1:VMS 4,6T 3,6T 970G 80% /vms* /dev/fuse 128M 36K 128M 1%...

...G ? 20G ?413G ? 5% / tmpfs ? ? ? ? ? 252G ? 63M ?252G ? 1% /dev/shm tmpfs ? ? ? ? ? 5,0M ? ? 0 ?5,0M ? 0% /run/lock efivarfs ? ? ? ?496K ?335K ?157K ?69% /sys/firmware/efi/efivars /dev/sda2 ? ? ? 1,8G ?204M ?1,5G ?12% /boot /dev/sda1 ? ? ? 1,9G ? 12M ?1,9G ? 1% /boot/efi /dev/sdb ? ? ? ?932G ?728G ?204G ?79% /disco1TB-0 /dev/sdc ? ? ? ?932G ?718G ?214G ?78% /disco1TB-1 /dev/sde ? ? ? ?932G ?720G ?212G ?78% /disco1TB-2 /dev/sdd ? ? ? ?1,9T ?1,5T ?387G ?80% /disco2TB-0 tmpfs ? ? ? ? ? ?51G ?4,0K ? 51G ? 1% /run/user/0 gluster1:VMS ? ?4,6T ?3,6T ?970G ?80% /vms /dev/fuse ? ? ? 128M ? 36K ?128M ? 1% /...

...s 252G 63M 252G 1% /dev/shm > tmpfs 5,0M 0 5,0M 0% /run/lock > efivarfs 496K 335K 157K 69% /sys/firmware/efi/efivars > /dev/sda2 1,8G 204M 1,5G 12% /boot > /dev/sda1 1,9G 12M 1,9G 1% /boot/efi > /dev/sdb 932G 728G 204G 79% /disco1TB-0 > /dev/sdc 932G 718G 214G 78% /disco1TB-1 > /dev/sde 932G 720G 212G 78% /disco1TB-2 > /dev/sdd 1,9T 1,5T 387G 80% /disco2TB-0 > tmpfs 51G 4,0K 51G 1% /run/user/0 > *gluster1:VMS 4,6T 3,6T 970G 80% /vms* > /dev/fu...

...G ? 20G ?413G ? 5% / tmpfs ? ? ? ? ? 252G ? 63M ?252G ? 1% /dev/shm tmpfs ? ? ? ? ? 5,0M ? ? 0 ?5,0M ? 0% /run/lock efivarfs ? ? ? ?496K ?335K ?157K ?69% /sys/firmware/efi/efivars /dev/sda2 ? ? ? 1,8G ?204M ?1,5G ?12% /boot /dev/sda1 ? ? ? 1,9G ? 12M ?1,9G ? 1% /boot/efi /dev/sdb ? ? ? ?932G ?728G ?204G ?79% /disco1TB-0 /dev/sdc ? ? ? ?932G ?718G ?214G ?78% /disco1TB-1 /dev/sde ? ? ? ?932G ?720G ?212G ?78% /disco1TB-2 /dev/sdd ? ? ? ?1,9T ?1,5T ?387G ?80% /disco2TB-0 tmpfs ? ? ? ? ? ?51G ?4,0K ? 51G ? 1% /run/user/0 gluster1:VMS ? ?4,6T ?3,6T ?970G ?80% /vms /dev/fuse ? ? ? 128M ? 36K ?128M ? 1% /...

...s 252G 63M 252G 1% /dev/shm > tmpfs 5,0M 0 5,0M 0% /run/lock > efivarfs 496K 335K 157K 69% /sys/firmware/efi/efivars > /dev/sda2 1,8G 204M 1,5G 12% /boot > /dev/sda1 1,9G 12M 1,9G 1% /boot/efi > /dev/sdb 932G 728G 204G 79% /disco1TB-0 > /dev/sdc 932G 718G 214G 78% /disco1TB-1 > /dev/sde 932G 720G 212G 78% /disco1TB-2 > /dev/sdd 1,9T 1,5T 387G 80% /disco2TB-0 > tmpfs 51G 4,0K 51G 1% /run/user/0 > *gluster1:VMS 4,6T 3,6T 970G 80% /vms* > /dev/fu...

OSes: CentOS 5.0 x86, CentOS 4.5 x86. Hi, I have CentOS 5.0 x86 installed on an IDE HDD. [john at localhost ~]$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 224G 8.5G 204G 4% / /dev/hdc1 99M 16M 79M 17% /boot tmpfs 506M 0 506M 0% /dev/shm I want to install CentOS 4.5 x86 on another hard disk, but from my past experience, when using one installation, it also automounts the logical volumes etc of the other installation du...

...tmpfs 5,0M 0 5,0M 0% /run/lock >>>> efivarfs 496K 335K 157K 69% /sys/firmware/efi/efivars >>>> /dev/sda2 1,8G 204M 1,5G 12% /boot >>>> /dev/sda1 1,9G 12M 1,9G 1% /boot/efi >>>> /dev/sdb 932G 728G 204G 79% /disco1TB-0 >>>> /dev/sdc 932G 718G 214G 78% /disco1TB-1 >>>> /dev/sde 932G 720G 212G 78% /disco1TB-2 >>>> /dev/sdd 1,9T 1,5T 387G 80% /disco2TB-0 >>>> tmpfs 51G 4,0K 51G 1% /run/user/0 >>>&g...

...743}) = 0 25533 read(3, "[\1\220\376xM\365a\206\350^8\236\315T\265#\353\270r\201\301|f\30<2 \347\276\37T:>|\241\2403\256\203GN\316=\233N\221\313\32\3630{\255\374O\360\263\374\353l\324\206\272o['I\205+\30\351\304LG\374\202\216\260\340H\342eL\214\377\3131(@:C\202\300\354x\235D\256\355\204G\261\rT5\247lK\364\342\7\232\231\210\25o\23\275\260\325\337\17E\255\300\211\254\277k\375g\347\347\5\273\324\255\324\220A\311\305\365{,J\351DE\245\337\272JBr\243\361\r\2226\330S\354\212$b\1J\37&C\200\225U\351\335", 8192) = 176 25533 close(4) = 0 25533 close(5) = 0 25533 clock_gettime(0x7...

Sadly, I'm back with another issue. I can do a "system list --all" just fine; however, if I attempt to start the machines, I get back: maas@Bill-MAAS-cc:~$ strace -s 1024 -f -o /tmp/asdfasdf.log virsh -c vbox+ssh://gbadmin@10.20.0.1/system start PXE-client-07 error: Failed to start domain PXE-client-07 error: An error occurred, but the cause is unknown Log files on both client

...n of unplugged memory, but with > resizable memory regions and optimized migration) is available at (kept > updated): > https://github.com/davidhildenbrand/qemu.git virtio-mem > > Start QEMU with two virtio-mem devices (one per NUMA node): > $ qemu-system-x86_64 -m 4G,maxmem=204G \ > -smp sockets=2,cores=2 \ > -numa node,nodeid=0,cpus=0-1 -numa node,nodeid=1,cpus=2-3 \ > [...] > -object memory-backend-ram,id=mem0,size=100G,managed-size=on \ > -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ > -object memory-backend-ram,id=me...

...lementation (without protection of unplugged memory, but with resizable memory regions and optimized migration) is available at (kept updated): https://github.com/davidhildenbrand/qemu.git virtio-mem Start QEMU with two virtio-mem devices (one per NUMA node): $ qemu-system-x86_64 -m 4G,maxmem=204G \ -smp sockets=2,cores=2 \ -numa node,nodeid=0,cpus=0-1 -numa node,nodeid=1,cpus=2-3 \ [...] -object memory-backend-ram,id=mem0,size=100G,managed-size=on \ -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ -object memory-backend-ram,id=mem1,size=100G,managed-size=on \...

...lementation (without protection of unplugged memory, but with resizable memory regions and optimized migration) is available at (kept updated): https://github.com/davidhildenbrand/qemu.git virtio-mem Start QEMU with two virtio-mem devices (one per NUMA node): $ qemu-system-x86_64 -m 4G,maxmem=204G \ -smp sockets=2,cores=2 \ -numa node,nodeid=0,cpus=0-1 -numa node,nodeid=1,cpus=2-3 \ [...] -object memory-backend-ram,id=mem0,size=100G,managed-size=on \ -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ -object memory-backend-ram,id=mem1,size=100G,managed-size=on \...

...lementation (without protection of unplugged memory, but with resizable memory regions and optimized migration) is available at (kept updated): https://github.com/davidhildenbrand/qemu.git virtio-mem Start QEMU with two virtio-mem devices (one per NUMA node): $ qemu-system-x86_64 -m 4G,maxmem=204G \ -smp sockets=2,cores=2 \ -numa node,nodeid=0,cpus=0-1 -numa node,nodeid=1,cpus=2-3 \ [...] -object memory-backend-ram,id=mem0,size=100G,managed-size=on \ -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ -object memory-backend-ram,id=mem1,size=100G,managed-size=on \...