Language:
switch to room list switch to menu My folders
Go to page: First ... 25 26 27 28 [29]
[#] Sun May 29 2022 09:48:14 EDT from darknetuser

[Reply] [ReplyQuoted] [Headers] [Print]

2022-05-28 12:48 from IGnatius T Foobar
Yeah, that'll be a pain in the neck to pull back apart after Broadcom,

like all of VMware's previous owners, realizes that it was a bad idea.




I was about to ask how profitable VMware is nowadays that containeritation is going everywhere else :-)

[#] Sun May 29 2022 09:50:46 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

Sort of odd question:

How do you bill for containers? With a VM its pretty easy. 'you get x resources, you pay me y dollars a month hosting fee". 



[#] Sun May 29 2022 16:02:18 EDT from zelgomer

[Reply] [ReplyQuoted] [Headers] [Print]

2022-05-29 13:50 from Nurb432 <nurb432@uncensored.citadel.org>
Sort of odd question:

How do you bill for containers? With a VM its pretty easy. 'you get x
resources, you pay me y dollars a month hosting fee". 


The container providers I've seen or used work the same way.

[#] Sun May 29 2022 16:18:18 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

For us "chargebacks"  to the agencies are important. We are in effect a 'hosting service' to them and they have their own budgets to pay for resource use.  ( or if they buy dedicated servers, but most have stopped doing that )

"hard" fees are of course the easiest, but when you are talking true shared resources, it gets harder. 



[#] Wed Jun 01 2022 10:25:27 EDT from DutchessMike

[Reply] [ReplyQuoted] [Headers] [Print]

I continue to use VMWare but for what I use it for (software development), there are other options.  I'm considering VirtualBox at the moment.

 



[#] Wed Jun 01 2022 16:12:12 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

kvm for the win. Both server and desktop. 



[#] Wed Jun 01 2022 17:30:26 EDT from zelgomer

[Reply] [ReplyQuoted] [Headers] [Print]

2022-06-01 20:12 from Nurb432 <nurb432@uncensored.citadel.org>
kvm for the win. Both server and desktop. 


Seconded. I've never used anything else but I like KVM so I'll ignorantly die defending it.

[#] Tue Jun 14 2022 02:14:02 EDT from darknetuser

[Reply] [ReplyQuoted] [Headers] [Print]

2022-06-01 17:30 from zelgomer
2022-06-01 20:12 from Nurb432 <nurb432@uncensored.citadel.org>

kvm for the win. Both server and desktop.


Seconded. I've never used anything else but I like KVM so I'll
ignorantly die defending it.



I have used Virtual Box on the desktop and while it was usable back in the day... if you are using Linux then KVM is just more convenient.

Also, what the Qubes distribution does with Xen is quite impresive. If you have the equipment necesary to run it you should check it out if just to see what they are doing.

[#] Tue Jun 14 2022 09:03:05 EDT from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

VirtualBox is the only one I find usable on my 'doze machine at work, because it has a NAT driver that masquerades as a userspace application. If I use anything else it gets blocked when I'm on the company VPN (which is pretty much always).

On a Linux machine, however ... nothing beats KVM.

[#] Sun Jun 19 2022 16:55:30 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

While im not fond of VB now ( especially after oracle ate them ), i agree on windows its one of the better choices you have.

I used to run it on Linux in the old days so i could have my 'shop supported windows vm', but got tired of things breaking every time a new kernel came out. And KVM was maturing about the same time.  Switched over, never looked back. On the server side, i was still using the free xenserver, but after i switched my desktop, that went out the window too. Both for consistency, and citrix was starting to pull features out of free.. Took a bit to redo things for my customers but it was worth the effort in the end. ( soon after that i moved servers to proxmox, instead of 'raw' kvm. )

On my personal machine at the office the only thing i lost was accelerated graphics inside the windows VM, but for my use case, that really didnt matter. Video was fast enough for the occasional training video we had to watch. ( now every week.. arrgh )

Tue Jun 14 2022 09:03:05 AM EDT from IGnatius T Foobar
VirtualBox is the only one I find usable on my 'doze machine at work, because it has a NAT driver that masquerades as a userspace application. If I use anything else it gets blocked when I'm on the company VPN (which is pretty much always).

On a Linux machine, however ... nothing beats KVM.

 



[#] Tue Jun 21 2022 11:37:16 EDT from LoanShark

[Reply] [ReplyQuoted] [Headers] [Print]


we've discussed that ad nauseum, but I got kinda fed up with VirtualBox. Went for native Linux boot / occasional dual boot. Never looked back. It's more difficult to set up on a laptop, satisfactorily anyway, but once you do it, it's the best way to get a *usable* Linux env--run Linux on the bare metal.

[#] Wed Jun 22 2022 16:15:00 EDT from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

Yeah. And I like it as a native environment anyway, so I might swap things around at some point and make Windows the virtual machine on top of Linux.
I'm going to be doing more stuff with our cloud team and their entire tool chain is Linux, so it might make sense. (Although the official setup guide specifies WSL2, and some really ugly hacks to make it work with our VPN, and an even uglier hack to make VS Code on Windows work inside the WSL2 filesystem ... at least one person on that team is running a real VM, and I am too.)

I just have to be sooper careful because I can't reload the machine if I brick it. Our internal IT people make you send the machine back to them and they cross-ship you a fresh one. I'm not willing to deal with that because my current machine is *way* nicer than the standard one, because it was all they could get at the time.

I think the procedure would go something like this:

1. Turn off Bitlocker
2. Create a recovery stick
3. Shrink the C: partition
4. Boot into Linux and "install alongside" Windows. I believe this means they share an EFI partition.
5. Boot the installed Linux. At this point it should be a dual boot machine.
6. Set up virtualization to run the Windows image, either directly from its old partition or by cloning it.

Cisco's really awful VPN client is probably going to throw a monkey wrench into the works, though.

[#] Wed Jun 22 2022 16:50:42 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

Dude at work just got an M1 macbook.

Found out 1/2 of what he needs isn't native ARM yet.  Including fusion, so no VMs for him.

And from what i gather Linux is not ready ( since its all proprietary stuff, and of course Apple isn't forthcoming so its all manually reverse-engineered.. ) and no KVM support on the M1 anyway.



Go to page: First ... 25 26 27 28 [29]