Voroxpete

joined 2 years ago
[–] Voroxpete@sh.itjust.works 15 points 23 hours ago (1 children)

I hate to break it to you, but Americans are the only ones who can save America.

Nothing we do will make the slightest bit of difference if your people don't come together and save yourselves.

The rapture is not coming. There's no Superman waiting to swoop down from on high. You have to stand up and do the hard work of fixing your problems. Stop waiting for someone else to do it for you.

[–] Voroxpete@sh.itjust.works 9 points 2 days ago

It's not about winning, it's about making them clearly state their intentions.

[–] Voroxpete@sh.itjust.works 5 points 2 days ago

It's important to never let the monsters hide behind their masks. They want passive compliance; never give it to them.

[–] Voroxpete@sh.itjust.works 17 points 2 days ago

What tariffs? This pathetic sack of shit keeps changing his mind about whether or not he's even imposing any.

[–] Voroxpete@sh.itjust.works 1 points 2 days ago (1 children)

So, unfortunately, this latest update seems to have created a lot of issues. First off, MobaXTerm support appears to be borked. Second, attempting to connect directly to LXC containers throws an error because I haven't linked a WSL2 instance for X11, even though X forwarding is not enabled for the connection.

[–] Voroxpete@sh.itjust.works 1 points 3 days ago

I'd suggest maybe testing with a plain Debian or Fedora install. Just enable KVM and install virt-manager, and create the environment that way.

[–] Voroxpete@sh.itjust.works 8 points 3 days ago* (last edited 3 days ago)

Good resources to start with:

Remember that small acts of resistance build big acts of resistance. Every time someone stands up, a few more people stand up next time. Don't sit around waiting for "the revolution" or "the general strike" or whatever other thing feels "big enough" to you. At that point you might as well just be waiting for the rapture. You build heaven one brick at a time.

And equally importantly, getting involved in the small acts of resistance gets you connected to the people who are doing things. The first part of organized resistance is organizing and that's never going to happen by sharing a meme or two. You need to get into the Signal chats, and the person to person networks where the real action is being talked about, mostly offline. So signing up to protest against book removals at your local n library might not feel like "doing enough" but it's how you get started. Things will move from there.

Search around for any kind of leftist resistance happening in your area, no matter how small. Get involved at the local level. It will make a difference.

[–] Voroxpete@sh.itjust.works 6 points 3 days ago (1 children)

Does someone need to sit this guy down and explain the concept of linear time to him?

[–] Voroxpete@sh.itjust.works 15 points 3 days ago* (last edited 3 days ago)

Unfortunately, militaries are built around getting people to follow orders regardless of how they feel about them.

Many of the Russian soldiers invading Ukraine had Ukrainian family members.

[–] Voroxpete@sh.itjust.works 3 points 4 days ago* (last edited 4 days ago) (2 children)

Unfortunately I'm not very familiar with Cloudstack or Proxmox; we've always worked with KVM using virt-manager and Cockpit.

Our usual method is to remove the default hard drive, reattach the qcow file as a SCSI device, and then we modify the SCSI controller that gets created to enable queuing. I'm sure at some point I should learn to do all this through the command line, but it's never really been relevant to do so.

The relevant sections look like this in one our prod VMs:

<disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/XXX.qcow2' index='1'/>
      <backingStore/>
      <target dev='sdb' bus='scsi'/>
      <alias name='scsi0-0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='scsi' index='0' model='virtio-scsi'>
      <driver queues='6'/>
      <alias name='scsi0'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</controller>

The driver queues='X' line is the part you have to add. The number should equal the number of cores assigned to the VM.

See the following for more on tuning KVM:

[–] Voroxpete@sh.itjust.works 13 points 4 days ago

Yeah, I was briefly starting to like him again. Reality always comes crashing back in at some point.

[–] Voroxpete@sh.itjust.works 7 points 4 days ago* (last edited 4 days ago) (7 children)

What are your disk settings for the KVM environments? We use KVM at work and found that the default configuration loses you a lot of performance on disk operations.

Switching from SATA to SCSI driver, and then enabling queues (set the number equal to your number of cores) dramatically speeds up all disk operations, large and small.

On mobile right now but I'll try to add some links to the KVM docs later.

view more: next ›