Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

271
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#virtualization

2 posts2 participants1 post today
*
CryptGoat

For anyone still using or considering the free #oVirt as virtualization management platform:⚠️ Please don't. It is a broken nightmare on community life support.⚠️

After #RedHat has ended support for its commercial spin Red Hat Virtualization (RHV) last year the development of oVirt practically came to a halt.

There hasn't been an official stable release for over a year despite security issues, and numerous bugs. The official recommendation is to use nightly releases to get the latest fixes. Too bad you won't be able to roll back via DNF if an update fails because older nightly releases are gone from the repo.

And yes, nightly releases do break oVirt at times. The latest nightly causes updates to fail because of incomplete dependency changes.

The web interface of the official mailing list is offline most of the time, the documentation is a confusing and outdated mess.

Upgrades to newer Linux distribution releases such as RHEL 9 or even 10 based systems are extremely painful and not officially supported.

Move your VMs to #ProxmoxVE or any other actively maintained KVM based solution.

#Virtualization#KVM#Linux
Ariadna Vigo

A whole afternoon playing around... ok, no, that's not the word... It's been a whole afternoon banging my head against the wall that libvirt and its cousin virt-manager are.

I ended up going back to the ol' trusty shell script I use to fire up my FreeBSD and OpenBSD VMs. This is a desktop, not a server, so the VMs are on just for what I need to run on them (mostly checking portability of code I write) and then, they're shut down. No need for a socket listening in the background or a service to do who knows what.

The thing that really pissed me off was the permissions situation libvirt/libvirt-qemu got me into. I mean... wow, it silently set an ACL entry on my $HOME on its own to unilaterally give itself permissions inside my $HOME. Wow.

#linux#libvirt#virtualization
.:\dGh/:.

Apple just made #WSL a legacy technology.

news.itsfoss.com/macos-meets-l

Happy to recommend #macOS for container development. If performance and memory consumption against #Linux is negligible, then it will be my top recommendation for sure.

It's FOSS News · macOS Meets Linux with Open Source ContainerizationApple’s new open source Containerization project brings native Linux container support to macOS.
#Apple#Mac#MicrosoftWindows
ilyess

Is it me or running VMs is still a pain in the butt on #ArchLinux?

You need to install Qemu which handles virtualization pretty well, but it doesn’t come with a GUI (still? really?). Fine, install Virtual Manager, but wait! You also need to enable a systemd service. Sure, done. Oh did you add your user to the libvirtd group?

Why isn’t there a single package that takes care of all of this out of the box? Or am I doing something wrong?

#linux#askFedi#askMastodon
Replied in thread
Kevin Karhan :verified:

@k4m1 @stman yeah, according to the #RTL8139 #datasheet this is basically a very cheap 10/100M NIC designed #embedded systems and low-end/low-cost desktops, and for a device designed and sold in 2006 it made sense, given back then #Gigabit-#Ethernet and Cat.5 cabling was considered high-end.

  • And unlike contemporary / successor chips by #Intel like the famous #i210 (which is still offered as #i219 but mostly succeeded by the #i225 as a 2,5GBase-T version) is way cheaper, which pre-#RoHS - NICs being sold for like € 10 retail & brand-new....

The few issues known only affect like #Virtualization setups, a market this thing was never designed for (most likely also never tested against).

  • I'd not he surprised if a lot of cheap #ThinClients and other systems used these NICs because of the simplicity of integration, being a cheap 3,3V single-chip (+auxilliary electronics) solution and propably costling less than 10¢ on a reel of 10.000.

It's the reason why to this day we see #Realtek NICs being shipped instead of fanning-out & enabling #SoC-integrated NICs with a #MAC & #PHY instead: Because the auxilliary parts for those are more expensive than just getting a PCI(e lane) somewhere and plonking it down.

  • Maybe there have even been some really cheap, low-end #Routers / #Firewalls aiming at #SoHo customers back in those days, cuz back then 16MBit/s #ADSL2 was considered fast, and Realtek's NICs up until recently only delivered like 60-75% of the max. speed advertised, so by the time someone would notice, that gearvwould've been EoL'd anyway and those who did notice right-away never were the target audience to begin with.

Most modern NICs are more complex and demand more configuration / driver support...

TrendingLive feeds
About