Terms Of Service
Be awesome! Be kind, gentle, friendly, positive, and polite!
White Hat only!
Not for business use!
Intended for education and fun!
Active participation in this thread's discussion is required!
Open source software only, both on MetalVPS and for connecting to MetalVPS!
No Service Level Agreement (SLA)!
No refunds!
Crunchbits TOS also applies!
Sorry, but repeating from TOS:
Active participation in this thread's discussion is required!
Since nobody seems to be using anything beyond a minimal amount of disk, what difference would it make if we added an additional eight 1 TB accounts? And somebody actually could use their full allocation if they wanted.
What do you think?
Thanks to @cpsd for replying here in the thread and to one other Neighbor for replying privately. I'd be grateful if our other Neighbors chimed in. I hope for unanimous consent on this one. Thanks again!
Since nobody seems to be using anything beyond a minimal amount of disk, what difference would it make if we added an additional eight 1 TB accounts? And somebody actually could use their full allocation if they wanted.
Just like cpu bursts, storage bursts upto 200 percent or 1 TB. Default being 500 GB. That would be quite interesting
your use case for crunchy;
running proxy servers, dns servers, a minecraft server (if the resources sufficient), bunch of api's probably, telegram/discord bots. i literally just love hosting as many stuff as i can fit into a server
estimated CPU, RAM, Disk, and Bandwidth usage;
2cores and 4gigs of ram would be ideal 1-2tb of bandwidth would be enough but really ill just run possible services based off the given resources so im fine with anything
open source OS and OS version that you will use to connect to crunchy; plus
debian 10/11/12- ubuntu 18/20/22 (preferably debian 12)
indicia of your commitment to our beautiful Low End, to computer learning and fun, and to open source.
im willing to share everything i'll be learning in the process and helping others enjoy and learn as much as i do!
Please feel free to include additional items in support of your sign up request.
your use case for crunchy;
running proxy servers, dns servers, a minecraft server (if the resources sufficient), bunch of api's probably, telegram/discord bots. i literally just love hosting as many stuff as i can fit into a server
estimated CPU, RAM, Disk, and Bandwidth usage;
2cores and 4gigs of ram would be ideal 1-2tb of bandwidth would be enough but really ill just run possible services based off the given resources so im fine with anything
open source OS and OS version that you will use to connect to crunchy; plus
debian 10/11/12- ubuntu 18/20/22 (preferably debian 12)
indicia of your commitment to our beautiful Low End, to computer learning and fun, and to open source.
im willing to share everything i'll be learning in the process and helping others enjoy and learn as much as i do!
Please feel free to include additional items in support of your sign up request.
umm if you want to get one you need to pay 1.01$ and if i remember correctly all slots were filled?
Also, there might be one VPS which seems to be still running but which, as of a few days ago, stopped sending and receiving network data. Has someone given up on his VPS? Thanks!
@Not_Oles said:
Hey Guys! I'm thinking a Nodeupdate and a reboot might be good. So, reboot coming soon, unless I hear from somebody who has an issue. Thanks!
Nobody seems to have any issue. So, okay, here we go! I will post a report afterwards. Thanks!
chronos@penguin:~/servers/crunchbits/crunchy$ date -u; ping -c 2 xx.xx.xx.xx
Tue Jul 2 11:29:54 PM UTC 2024
PING xx.xx.xx.xx (xx.xx.xx.xx) 56(84) bytes of data.
64 bytes from xx.xx.xx.xx: icmp_seq=1 ttl=45 time=62.5 ms
64 bytes from xx.xx.xx.xx: icmp_seq=2 ttl=45 time=61.1 ms
--- xx.xx.xx.xx ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 61.082/61.800/62.519/0.718 ms
chronos@penguin:~/servers/crunchbits/crunchy$
root@crunchy:~# cd bashvm
root@crunchy:~/bashvm# date; bash bashvm.sh
Tue Jul 2 11:33:27 PM UTC 2024
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: 1
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: s
Id Name State
--------------------------------
1 vm105-crunchy running
2 vm107-crunchy running
3 vm102-crunchy running
4 vm106-crunchy running
5 vm100-crunchy running
6 vm103-crunchy running
7 vm104-crunchy running
8 vm101-crunchy running
- vm1-crunchy shut off
- vm2-crunchy shut off
root@crunchy:~# date
Tue Jul 2 11:41:33 PM UTC 2024
root@crunchy:~#
As of July 2 11:41:33 PM UTC 2024 all the bashvm VPSes seem to have auto-restarted okay. Although not posted here, I can see VPS network activity. @subenhon had a couple of hand made VPSes which might need restarting by hand or a cron job set up to restart them.
The single VPS I mentioned yesterday that had seemed to stop network activity did resume yesterday, shortly after I posted about it, and long before today's reboot.
Congrats to @babywhale for bashvm, which is doing a great job! Congrats and thanks to @crunchbits for wonderful Crunchy!
Okay, a very quick glance suggests that everything might be working okay. Congrats to Crunchy and bashvm!
Please let me know about any problems! Thanks very much!
Last login: Fri Jul 26 17:47:18 2024 from 187.189.238.2
root@crunchy:~# date -u; uname -r
Fri Jul 26 06:07:09 PM UTC 2024
5.15.0-117-generic
root@crunchy:~# cd bashvm
root@crunchy:~/bashvm# bash bashvm.sh
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: 1
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: s
Id Name State
--------------------------------
1 vm104-crunchy running
2 vm100-crunchy running
3 vm103-crunchy running
4 vm101-crunchy running
5 vm107-crunchy running
6 vm102-crunchy running
7 vm106-crunchy running
8 vm105-crunchy running
- vm1-crunchy shut off
- vm2-crunchy shut off
What might happen if we were to swap one of your VPSes for a Crunchy VPS? No Bitcoin would be needed.
Crunchy is sold out now. We could do some more Crunchy VPSes, but only if every existing neighbor unanimously consented to the overselling. So far I think only two neighbors have consented.
Crunchy still seems to be running great! Thanks to @crunchbits for wonderful Crunchy! Thanks to @babywhale for wonderful BashVM!
root@crunchy:~/bashvm# date
Sat Aug 17 03:37:34 AM UTC 2024
root@crunchy:~/bashvm# w
03:37:35 up 21 days, 9:42, 2 users, load average: 1.50, 1.58, 1.57
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/8 187.189.238.2 00:36 3.00s 0.01s 0.00s w
subenhon pts/9 tmux(781768).%0 Wed14 2days 5:08m 0.00s /bin/bash ./start_ubuntu20_gui.sh
root@crunchy:~/bashvm# bash bashvm.sh
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: 1
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: s
Id Name State
--------------------------------
1 vm104-crunchy running
2 vm100-crunchy running
3 vm103-crunchy running
4 vm101-crunchy running
5 vm107-crunchy running
6 vm102-crunchy running
7 vm106-crunchy running
8 vm105-crunchy running
- vm1-crunchy shut off
- vm2-crunchy shut off
[ . . . ]
What might happen if we were to swap one of your VPSes for a Crunchy VPS? No Bitcoin would be needed.
Crunchy is sold out now. We could do some more Crunchy VPSes, but only if every existing neighbor unanimously consented to the overselling. So far I think only two neighbors have consented.
Crunchy still seems to be running great! Thanks to @crunchbits for wonderful Crunchy! Thanks to @babywhale for wonderful BashVM!
root@crunchy:~/bashvm# date
Sat Aug 17 03:37:34 AM UTC 2024
root@crunchy:~/bashvm# w
03:37:35 up 21 days, 9:42, 2 users, load average: 1.50, 1.58, 1.57
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/8 187.189.238.2 00:36 3.00s 0.01s 0.00s w
subenhon pts/9 tmux(781768).%0 Wed14 2days 5:08m 0.00s /bin/bash ./start_ubuntu20_gui.sh
root@crunchy:~/bashvm# bash bashvm.sh
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: 1
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: s
Id Name State
--------------------------------
1 vm104-crunchy running
2 vm100-crunchy running
3 vm103-crunchy running
4 vm101-crunchy running
5 vm107-crunchy running
6 vm102-crunchy running
7 vm106-crunchy running
8 vm105-crunchy running
- vm1-crunchy shut off
- vm2-crunchy shut off
[ . . . ]
Looks like you are going to get into really big trouble -- if you are not there already -- and if what you are posting isn't fake. I don't envy your position. Nevertheless, I hope everything somehow will turn out okay for you, eventually, somehow!
I think Crunchy is running okay. When you log in, Ubuntu says a reboot is needed. My personal preference is to update and reboot frequently, just to make sure that the lastest updates are installed and running. Sometimes, when on a Node where other guys have VMs, maybe reboots could be a little less frequent so as not to bother everybody? Notably, after the last reboot, all the VMs successfully auto-restarted, but some guys didn't seem to bother restarting services inside their VMs. Thus, network I/O went way down as you can see in the vnstat output below.
Of course, as you can see from this thread, Crunchy has enjoyed several reboots previously. Maybe you're right to suggest that it could be time for another reboot even if there might seem to be a substantial adverse impact on services that guys are running. Please let me know what you guys think about another reboot.
I usually check on Crunchy multiple times every day. Here below is the result of today's two recent check-ins. Please let me know what you guys think about the checks. Should I run additional checks beyond what I now am doing? And, about vm100. Is something wrong there, or is it just really nice that someone actually is using his allocated resources? Maybe our vm100 Neighbor might want to comment here?
Thanks for your interest, Mike, and thanks for your comments! Thanks to Crunchbits for wonderful Crunchy! Thanks to @babywhale for BashVM! Thanks to all the guys using Crunchy!
chronos@penguin:~/servers/crunchbits/crunchy$ cat 20240818-check-in
root@crunchy:~# date
Sun Aug 18 04:32:22 AM UTC 2024
root@crunchy:~# w
04:32:24 up 22 days, 10:37, 2 users, load average: 1.33, 1.49, 1.59
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/8 187.189.238.2 03:36 0.00s 0.02s 0.00s w
subenhon pts/9 tmux(781768).%0 Wed14 3days 6:57m 0.00s /bin/bash ./start_ubuntu20_gui.sh
root@crunchy:~# last | head
root pts/8 187.189.238.2 Sun Aug 18 03:36 still logged in
root pts/8 187.189.238.2 Sat Aug 17 22:07 - 03:01 (04:54)
root pts/8 187.189.238.2 Sat Aug 17 00:36 - 05:31 (04:54)
root pts/8 187.189.238.2 Fri Aug 16 17:51 - 19:00 (01:09)
root pts/8 187.189.238.2 Fri Aug 16 17:46 - 17:50 (00:04)
root pts/8 187.189.238.2 Thu Aug 15 16:53 - 03:03 (10:09)
root pts/8 187.189.238.2 Thu Aug 15 16:50 - 16:51 (00:00)
root pts/10 187.189.238.2 Wed Aug 14 21:08 - 02:47 (05:38)
subenhon pts/9 tmux(781768).%0 Wed Aug 14 14:41 still logged in
subenhon pts/8 xxx.xxx.xxx.xxx Wed Aug 14 14:40 - 22:56 (08:15)
root@crunchy:~# vnstat -i enp1s0f1
Database updated: 2024-08-18 04:30:00
enp1s0f1 since 2024-03-04
rx: 8.22 TiB tx: 9.24 TiB total: 17.45 TiB
monthly
rx | tx | total | avg. rate
------------------------+-------------+-------------+---------------
2024-07 3.55 TiB | 3.49 TiB | 7.04 TiB | 23.13 Mbit/s
2024-08 1.21 TiB | 1.19 TiB | 2.40 TiB | 14.22 Mbit/s
------------------------+-------------+-------------+---------------
estimated 2.19 TiB | 2.14 TiB | 4.33 TiB |
daily
rx | tx | total | avg. rate
------------------------+-------------+-------------+---------------
yesterday 102.93 GiB | 96.78 GiB | 199.71 GiB | 19.86 Mbit/s
today 19.66 GiB | 19.33 GiB | 38.99 GiB | 20.67 Mbit/s
------------------------+-------------+-------------+---------------
estimated 104.84 GiB | 103.09 GiB | 207.93 GiB |
root@crunchy:~#
root@crunchy:~# date
Sun Aug 18 06:41:57 PM UTC 2024
root@crunchy:~# w
18:41:59 up 23 days, 46 min, 2 users, load average: 1.33, 1.47, 1.51
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/8 187.189.238.2 18:41 7.00s 0.01s 0.00s w
subenhon pts/9 tmux(781768).%0 Wed14 4days 7:57m 0.00s /bin/bash ./start_ubuntu20_gui.sh
root@crunchy:~# last | head
root pts/8 187.189.238.2 Sun Aug 18 18:41 still logged in
mikewaza pts/8 xxx.xxx.xxx.xxx Sun Aug 18 15:06 - 15:07 (00:00)
mikewaza pts/8 xxx.xxx.xxx.xxx Sun Aug 18 15:04 - 15:04 (00:00)
root pts/8 187.189.238.2 Sun Aug 18 03:36 - 04:33 (00:57)
root pts/8 187.189.238.2 Sat Aug 17 22:07 - 03:01 (04:54)
root pts/8 187.189.238.2 Sat Aug 17 00:36 - 05:31 (04:54)
root pts/8 187.189.238.2 Fri Aug 16 17:51 - 19:00 (01:09)
root pts/8 187.189.238.2 Fri Aug 16 17:46 - 17:50 (00:04)
root pts/8 187.189.238.2 Thu Aug 15 16:53 - 03:03 (10:09)
root pts/8 187.189.238.2 Thu Aug 15 16:50 - 16:51 (00:00)
root@crunchy:~# top -b -n 1 | head -n 15
top - 18:44:50 up 23 days, 49 min, 2 users, load average: 1.32, 1.40, 1.47
Tasks: 225 total, 1 running, 224 sleeping, 0 stopped, 0 zombie
%Cpu(s): 17.2 us, 1.6 sy, 0.0 ni, 81.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 64084.4 total, 5011.3 free, 17457.2 used, 41615.9 buff/cache
MiB Swap: 4096.0 total, 4096.0 free, 0.0 used. 45903.3 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1944 libvirt+ 20 0 8897880 4.1g 25188 S 112.5 6.6 17893:22 qemu-system-x86
781782 subenhon 20 0 5609356 4.1g 20656 S 12.5 6.5 477:34.02 qemu-system-x86
1951 root 20 0 0 0 0 S 6.2 0.0 2239:46 vhost-1944
2801 libvirt+ 20 0 8929372 4.1g 24884 S 6.2 6.6 3061:24 qemu-system-x86
931711 root 20 0 10480 3972 3368 R 6.2 0.0 0:00.01 top
1 root 20 0 168472 14032 8312 S 0.0 0.0 1:36.35 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.36 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
root@crunchy:~# vnstat -i enp1s0f1
Database updated: 2024-08-18 18:45:00
enp1s0f1 since 2024-03-04
rx: 8.28 TiB tx: 9.29 TiB total: 17.57 TiB
monthly
rx | tx | total | avg. rate
------------------------+-------------+-------------+---------------
2024-07 3.55 TiB | 3.49 TiB | 7.04 TiB | 23.13 Mbit/s
2024-08 1.27 TiB | 1.25 TiB | 2.52 TiB | 14.43 Mbit/s
------------------------+-------------+-------------+---------------
estimated 2.22 TiB | 2.17 TiB | 4.39 TiB |
daily
rx | tx | total | avg. rate
------------------------+-------------+-------------+---------------
yesterday 102.93 GiB | 96.78 GiB | 199.71 GiB | 19.86 Mbit/s
today 81.75 GiB | 80.39 GiB | 162.14 GiB | 20.63 Mbit/s
------------------------+-------------+-------------+---------------
estimated 104.64 GiB | 102.90 GiB | 207.54 GiB |
root@crunchy:~# ps aux | grep 1944 | grep -v grep
libvirt+ 1944 53.9 6.5 8897880 4327796 ? Sl Jul26 17897:45 /usr/bin/qemu-system-x86_64 -name guest=vm100-crunchy,debug-threads=on -S -object {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-vm100-crunchy/master-key.aes"} -machine pc-q35-6.2,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram -accel kvm -cpu host,migratable=on -m 4096 -object {"qom-type":"memory-backend-ram","id":"pc.ram","size":4294967296} -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 79d86e0d-96f6-4111-8ed3-fb229c1f50c8 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=36,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=20,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device pcie-root-port,port=21,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 -device pcie-root-port,port=22,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 -device pcie-root-port,port=23,chassis=8,id=pci.8,bus=pcie.0,addr=0x2.0x7 -device pcie-root-port,port=24,chassis=9,id=pci.9,bus=pcie.0,multifunction=on,addr=0x3 -device pcie-root-port,port=25,chassis=10,id=pci.10,bus=pcie.0,addr=0x3.0x1 -device pcie-root-port,port=26,chassis=11,id=pci.11,bus=pcie.0,addr=0x3.0x2 -device pcie-root-port,port=27,chassis=12,id=pci.12,bus=pcie.0,addr=0x3.0x3 -device pcie-root-port,port=28,chassis=13,id=pci.13,bus=pcie.0,addr=0x3.0x4 -device pcie-root-port,port=29,chassis=14,id=pci.14,bus=pcie.0,addr=0x3.0x5 -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -blockdev {"driver":"file","filename":"/var/lib/libvirt/images/debian-12-generic-amd64.qcow2","node-name":"libvirt-3-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-3-format","read-only":true,"discard":"unmap","driver":"qcow2","file":"libvirt-3-storage","backing":null} -blockdev {"driver":"file","filename":"/var/lib/libvirt/images/vm100-crunchy.qcow2","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-2-format","read-only":false,"discard":"unmap","driver":"qcow2","file":"libvirt-2-storage","backing":"libvirt-3-format"} -device virtio-blk-pci,bus=pci.4,addr=0x0,drive=libvirt-2-format,id=virtio-disk0,bootindex=1 -device ide-cd,bus=ide.0,id=sata0-0-0 -netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=39 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:6c:8f:8c,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=34,server=on,wait=off -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -audiodev {"id":"audio1","driver":"spice"} -spice port=5901,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0,audiodev=audio1 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 -object {"qom-type":"rng-random","
root 1951 6.7 0.0 0 0 ? S Jul26 2239:57 [vhost-1944]
root 1955 0.0 0.0 0 0 ? S Jul26 6:38 [kvm-pit/1944]
root@crunchy:~#
chronos@penguin:~/servers/crunchbits/crunchy$
Hello! How about an update, upgrade, and reboot tomorrow, maybe about 16 hours from now? If anybody has a problem with tomorrow, please let me know. I will post here before I do the reboot and again after. I hope everyone is enjoying Crunchy! Thanks @crunchbits!
root@crunchy:~# date -u
Thu Aug 22 07:59:54 PM UTC 2024
root@crunchy:~# systemctl reboot
root@crunchy:~# Connection to xxx.xxx.xxx.xxx closed by remote host.
Connection to xxx.xxx.xxx.xxx closed.
chronos@penguin:~/servers/crunchbits/crunchy$ sleep 300
chronos@penguin:~/servers/crunchbits/crunchy$ `head -n 1 login`
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-119-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Thu Aug 22 08:07:05 PM UTC 2024
System load: 0.71 Processes: 237
Usage of /: 16.4% of 3.66TB Users logged in: 0
Memory usage: 13% IPv4 address for enp1s0f1: xxx.xxx.xxx.xxx
Swap usage: 0% IPv6 address for enp1s0f1: xxxx:xxxx:xxxx:xxxx::xxxx
Temperature: 36.0 C IPv6 address for enp1s0f1: xxxx:xxxx:xxxx:xxxx::xxxx
* Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
just raised the bar for easy, resilient and secure K8s cluster deployment.
https://ubuntu.com/engage/secure-kubernetes-at-the-edge
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
3 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm
Last login: Thu Aug 22 19:59:41 2024 from xxx.xxx.xxx.xxx
root@crunchy:~# date -u
Thu Aug 22 08:07:13 PM UTC 2024
root@crunchy:~# cd bashvm
root@crunchy:~/bashvm# bash bashvm.sh
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: 1
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: s
Id Name State
--------------------------------
1 vm102-crunchy running
2 vm100-crunchy running
3 vm105-crunchy running
4 vm101-crunchy running
5 vm104-crunchy running
6 vm106-crunchy running
7 vm103-crunchy running
8 vm107-crunchy running
- vm1-crunchy shut off
- vm2-crunchy shut off
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: q
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: q
Exiting.
root@crunchy:~/bashvm# logout
Connection to xxx.xxx.xxx.xxx closed.
chronos@penguin:~/servers/crunchbits/crunchy$
Looks like a few Ubuntu updates and a minor version bump are available for Crunchy.
Unless somebody has an issue with a reboot, probably I will run the updates and reboot about 12 or 14 hours from now. I will post here again before I update and reboot.
@Not_Oles said: Unless somebody has an issue with a reboot, probably I will run the updates and reboot about 12 or 14 hours from now. I will post here again before I update and reboot.
Good morning!
I guess it might be time to try the update, upgrade. And then the reboot. So, here we go!
root@crunchy:~# date -u; systemctl reboot
Tue Sep 3 05:14:17 PM UTC 2024
root@crunchy:~# Connection to xxx.xxx.xxx.xxx closed by remote host.
Connection to xxx.xxx.xxx.xxx closed.
chronos@penguin:~/servers/crunchbits/crunchy$
chronos@penguin:~/servers/crunchbits/crunchy$ `head -n 1 login`
Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-119-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Tue Sep 3 05:21:35 PM UTC 2024
System load: 0.54 Processes: 231
Usage of /: 16.4% of 3.66TB Users logged in: 0
Memory usage: 14% IPv4 address for enp1s0f1: xxx.xxx.xxx.xxx
Swap usage: 0% IPv6 address for enp1s0f1: xxxx:xxxx:xxxx:xxxx::x
Temperature: 36.0 C IPv6 address for enp1s0f1: xxxx:xxxx:xxxx:xxxx::x
* Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
just raised the bar for easy, resilient and secure K8s cluster deployment.
https://ubuntu.com/engage/secure-kubernetes-at-the-edge
Expanded Security Maintenance for Applications is not enabled.
0 updates can be applied immediately.
3 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm
New release '24.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
Last login: Tue Sep 3 17:08:51 2024 from xxx.xxx.xxx.xxx
root@crunchy:~# date
Tue Sep 3 05:21:50 PM UTC 2024
root@crunchy:~# cd bashvm
root@crunchy:~/bashvm# bash bashvm.sh
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: 1
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: s
Id Name State
--------------------------------
1 vm101-crunchy running
2 vm100-crunchy running
3 vm105-crunchy running
4 vm106-crunchy running
5 vm107-crunchy running
6 vm104-crunchy running
7 vm102-crunchy running
8 vm103-crunchy running
- vm1-crunchy shut off
- vm2-crunchy shut off
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: q
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: q
Exiting.
root@crunchy:~/bashvm#
Now we might be ready to run do-release-upgrade. . . .
Unless you guys really want to go from twenty-two to twenty-four, I am going to chicken out. Recently I had a lot of fun bumping through a few changes which seemed to be required when installing BashVM on Debian sid instead of Debian 12. BashVM and virsh and libvirt and qemu work great, but there's really a lot in there.
Being conservative on a machine which others are using, I prefer not to do the release upgrade without having a chance to test on an identical setup in advance.
Given that Crunchy only has until November 8, which is coming up soon, the present 22.04.4 seems okay for the time being.
Always delighted to consider other points of view. Happy to do-release-upgrade if all our Crunchy Neighbors unanimously agree to accept the risk.
Thanks again to @crunchbits for wonderful Crunchy! Thanks again to @babywhale for wonderful BashVM! Thanks again to all the guys who are enjoying Crunchy VMs! Special thanks to @sh97 for being a great guy and a prime contributor to the entire Low End!
Comments
Sorry, but repeating from TOS:
Also, please:
Thanks to @cpsd for replying here in the thread and to one other Neighbor for replying privately. I'd be grateful if our other Neighbors chimed in. I hope for unanimous consent on this one. Thanks again!
I hope everyone gets the servers they want!
@Not_Oles said
Just like cpu bursts, storage bursts upto 200 percent or 1 TB. Default being 500 GB. That would be quite interesting
blog | exploring visually |
Achievable by offering 2 cents worth of information or opinion, ten times.
blog | exploring visually |
yea lol
Hi again oles, is this offer still up? i'd love to grab one of your free servers
your ed25519 ssh public key;
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEU3AifpA2MLoycSxSdJZOVmohMzPgDtsHdFInknzlPC [email protected]
links to your website, github, other online profiles, etc.;
https://github.com/meower1
your use case for crunchy;
running proxy servers, dns servers, a minecraft server (if the resources sufficient), bunch of api's probably, telegram/discord bots. i literally just love hosting as many stuff as i can fit into a server
estimated CPU, RAM, Disk, and Bandwidth usage;
2cores and 4gigs of ram would be ideal 1-2tb of bandwidth would be enough but really ill just run possible services based off the given resources so im fine with anything
open source OS and OS version that you will use to connect to crunchy; plus
debian 10/11/12- ubuntu 18/20/22 (preferably debian 12)
indicia of your commitment to our beautiful Low End, to computer learning and fun, and to open source.
im willing to share everything i'll be learning in the process and helping others enjoy and learn as much as i do!
Please feel free to include additional items in support of your sign up request.
umm if you want to get one you need to pay 1.01$ and if i remember correctly all slots were filled?
Hey Guys! I'm thinking a Nodeupdate and a reboot might be good. So, reboot coming soon, unless I hear from somebody who has an issue. Thanks!
I hope everyone gets the servers they want!
Also, there might be one VPS which seems to be still running but which, as of a few days ago, stopped sending and receiving network data. Has someone given up on his VPS? Thanks!
I hope everyone gets the servers they want!
Nobody seems to have any issue. So, okay, here we go! I will post a report afterwards. Thanks!
I hope everyone gets the servers they want!
As of July 2 11:41:33 PM UTC 2024 all the bashvm VPSes seem to have auto-restarted okay. Although not posted here, I can see VPS network activity. @subenhon had a couple of hand made VPSes which might need restarting by hand or a cron job set up to restart them.
The single VPS I mentioned yesterday that had seemed to stop network activity did resume yesterday, shortly after I posted about it, and long before today's reboot.
Congrats to @babywhale for bashvm, which is doing a great job!
Congrats and thanks to @crunchbits for wonderful Crunchy! 
Any issues, please let me know! Best wishes!
I hope everyone gets the servers they want!
Hello!
Maybe it might be time for another update and reboot for the Ubuntu OS which is running on Crunchy.
Anybody have any special need for stability right now, or can I just go ahead with the update and reboot?
Thanks! Special thanks to @crunchbits for wonderful Crunchy! And to @babywhale for bshvm!
Tom
I hope everyone gets the servers they want!
Starting the update and upgrade and reboot. . . .
I hope everyone gets the servers they want!
Okay, a very quick glance suggests that everything might be working okay. Congrats to Crunchy and bashvm!
Please let me know about any problems! Thanks very much!
I hope everyone gets the servers they want!
Hello @Not_Oles, I want to buy this VPS via Bitcoin, can you do it?
Hi @ExAjiMag!
What might happen if we were to swap one of your VPSes for a Crunchy VPS? No Bitcoin would be needed.
Crunchy is sold out now. We could do some more Crunchy VPSes, but only if every existing neighbor unanimously consented to the overselling. So far I think only two neighbors have consented.
Crunchy still seems to be running great! Thanks to @crunchbits for wonderful Crunchy!
Thanks to @babywhale for wonderful BashVM! 
I hope everyone gets the servers they want!
What if you want to swap with this VPS?
bruh
Wow!
Wow x 2!
Looks like you are going to get into really big trouble -- if you are not there already -- and if what you are posting isn't fake. I don't envy your position. Nevertheless, I hope everything somehow will turn out okay for you, eventually, somehow!
I hope everyone gets the servers they want!
I see I missed the above, more neighbours are welcome!
Thanks for replying! I appreciate your being welcoming to more neighbors.
Also,
I think Crunchy is running okay. When you log in, Ubuntu says a reboot is needed. My personal preference is to update and reboot frequently, just to make sure that the lastest updates are installed and running. Sometimes, when on a Node where other guys have VMs, maybe reboots could be a little less frequent so as not to bother everybody? Notably, after the last reboot, all the VMs successfully auto-restarted, but some guys didn't seem to bother restarting services inside their VMs. Thus, network I/O went way down as you can see in the
vnstatoutput below.Of course, as you can see from this thread, Crunchy has enjoyed several reboots previously. Maybe you're right to suggest that it could be time for another reboot even if there might seem to be a substantial adverse impact on services that guys are running. Please let me know what you guys think about another reboot.
I usually check on Crunchy multiple times every day. Here below is the result of today's two recent check-ins. Please let me know what you guys think about the checks. Should I run additional checks beyond what I now am doing? And, about vm100. Is something wrong there, or is it just really nice that someone actually is using his allocated resources? Maybe our vm100 Neighbor might want to comment here?
Thanks for your interest, Mike, and thanks for your comments!
Thanks to Crunchbits for wonderful Crunchy! 
Thanks to @babywhale for BashVM! 
Thanks to all the guys using Crunchy! 
I hope everyone gets the servers they want!
Hello! How about an update, upgrade, and reboot tomorrow, maybe about 16 hours from now? If anybody has a problem with tomorrow, please let me know. I will post here before I do the reboot and again after. I hope everyone is enjoying Crunchy! Thanks @crunchbits!
I hope everyone gets the servers they want!
Good afternoon! Just finished
apt-get updateandapt-get upgrade.Now for the reboot.
I hope everyone gets the servers they want!
I hope everyone gets the servers they want!
Looks like everything might be pretty much okay. Please let me know about any issues!
Thanks for Crunchy @crunchbits!
Thanks for BashVM @babywhale! 
I hope everyone gets the servers they want!
Hello!
Looks like a few Ubuntu updates and a minor version bump are available for Crunchy.
Unless somebody has an issue with a reboot, probably I will run the updates and reboot about 12 or 14 hours from now. I will post here again before I update and reboot.
Thanks! And special thanks to @crunchbits for beautiful Crunchy!
Special thanks to @babywhale for BashVM! 
Best wishes!
Tom
I hope everyone gets the servers they want!
Good morning!
I guess it might be time to try the update, upgrade. And then the reboot. So, here we go!
Best!
Tom
I hope everyone gets the servers they want!
Looks like the update/upgrade went okay. Now for the reboot. . . .
I hope everyone gets the servers they want!
Looks like the reboot went okay too!
I hope everyone gets the servers they want!
Upgrade to 24.04 when
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
Now, more about the version upgrade. It's from what we are running now,
to
So, 22.04 to 24.04.1.
Ubuntu recommends the update / upgrade that we just did prior to running
do-release-upgrade. Please see https://ubuntu.com/server/docs/how-to-upgrade-your-release .Now we might be ready to run do-release-upgrade. . . .
Unless you guys really want to go from twenty-two to twenty-four, I am going to chicken out. Recently I had a lot of fun bumping through a few changes which seemed to be required when installing BashVM on Debian sid instead of Debian 12. BashVM and virsh and libvirt and qemu work great, but there's really a lot in there.
Being conservative on a machine which others are using, I prefer not to do the release upgrade without having a chance to test on an identical setup in advance.
Given that Crunchy only has until November 8, which is coming up soon, the present 22.04.4 seems okay for the time being.
Always delighted to consider other points of view. Happy to
do-release-upgradeif all our Crunchy Neighbors unanimously agree to accept the risk.Thanks again to @crunchbits for wonderful Crunchy!
Thanks again to @babywhale for wonderful BashVM! 
Thanks again to all the guys who are enjoying Crunchy VMs! 
Special thanks to @sh97 for being a great guy and a prime contributor to the entire Low End! 
I hope everyone gets the servers they want!