Podcasts about hyper v

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

This Christmas, strap in for three hours of vulnerabilities, patches, and the occasional existential crisis about holiday skeleton crews. This megacut compiles every 2025 episode of Patch [FIX] Tuesday, featuring Automox security engineers Ryan Braunstein, Henry Smith, Seth Hoyt, Mat Lee, and Tom Bowyer breaking down the year's most critical security updates.What's inside:All 12 Patch [FIX] Tuesday episodes from January through December 2025macOS and Apple security updatesZero-days, CVEs, and actively exploited vulnerabilitiesCandid discussions on Hyper-V escapes, SSH hijacking chains, React RCE, and moreWhether you're catching up on a year of patches or need something smarter than carols for a long holiday drive or late-night remediation – this compilation has you covered.

Segment 1: Interview with Rob Allen It's the Year of the (Clandestine) Linux Desktop! As if EDR evasions weren't enough, attackers are now employing yet another method to hide their presence on enterprise systems: deploying tiny Linux VMs. Attackers are using Hyper-V and/or WSL to deploy tiny (120MB disk space and 256MB memory) Linux VMs to host a custom reverse shell and reverse proxy. In this segment, we'll discuss strategies and mitigations to battle this novel technique with Rob Allen from Threatlocker. Segment Resources: Pro-Russian Hackers Use Linux VMs to Hide in Windows Russian Hackers Abuse Hyper-V to Hide Malware in Linux VMs Qilin ransomware abuses WSL to run Linux encryptors in Windows This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Segment 2: Topic - Threat Modeling Humanoid Robots We're entering the age of human-shaped robots, so it seems like a good time to talk about the fact that they ALREADY HAVE CVEs assigned to them. I guess this isn't a terrible thing - John Connor might have had an easier time if he could simply hack the terminators from a distance... Resources https://www.unitree.com/H2 (watch the video!) China's humanoid robots get factory jobs as UBTech's model scores US$112 million in orders The big reveal: Xpeng founder unzips humanoid robot to prove it's not human Exploit Allows for Takeover of Fleets of Unitree Robots - Security researchers find a wormable vulnerability 100-page Paper: The Cybersecurity of a Humanoid Robot 5-page Paper: Cybersecurity AI: Humanoid Robots as Attack Vectors Amazingly, $300 smart vacuums have some of the same exact vulnerabilities and backdoors built into them as the $16,000 humanoid robots! The Day My Smart Vacuum Turned Against Me Segment 3: Weekly News Finally, in the enterprise security news, A $435M venture round A $75M seed round a few acquisitions the producer of the movie Half Baked bought a spyware company AI isn't going well, or is it? maybe we just need to adopt it more slowly and deliberately? ad-blockers are enterprise best practices firewalls and VPNs are security risks, according to insurance claims could you power an entire house with disposable vapes? All that and more, on this episode of Enterprise Security Weekly. Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-433

Segment 1: Interview with Rob Allen It's the Year of the (Clandestine) Linux Desktop! As if EDR evasions weren't enough, attackers are now employing yet another method to hide their presence on enterprise systems: deploying tiny Linux VMs. Attackers are using Hyper-V and/or WSL to deploy tiny (120MB disk space and 256MB memory) Linux VMs to host a custom reverse shell and reverse proxy. In this segment, we'll discuss strategies and mitigations to battle this novel technique with Rob Allen from Threatlocker. Segment Resources: Pro-Russian Hackers Use Linux VMs to Hide in Windows Russian Hackers Abuse Hyper-V to Hide Malware in Linux VMs Qilin ransomware abuses WSL to run Linux encryptors in Windows This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Segment 2: Topic - Threat Modeling Humanoid Robots We're entering the age of human-shaped robots, so it seems like a good time to talk about the fact that they ALREADY HAVE CVEs assigned to them. I guess this isn't a terrible thing - John Connor might have had an easier time if he could simply hack the terminators from a distance... Resources https://www.unitree.com/H2 (watch the video!) China's humanoid robots get factory jobs as UBTech's model scores US$112 million in orders The big reveal: Xpeng founder unzips humanoid robot to prove it's not human Exploit Allows for Takeover of Fleets of Unitree Robots - Security researchers find a wormable vulnerability 100-page Paper: The Cybersecurity of a Humanoid Robot 5-page Paper: Cybersecurity AI: Humanoid Robots as Attack Vectors Amazingly, $300 smart vacuums have some of the same exact vulnerabilities and backdoors built into them as the $16,000 humanoid robots! The Day My Smart Vacuum Turned Against Me Segment 3: Weekly News Finally, in the enterprise security news, A $435M venture round A $75M seed round a few acquisitions the producer of the movie Half Baked bought a spyware company AI isn't going well, or is it? maybe we just need to adopt it more slowly and deliberately? ad-blockers are enterprise best practices firewalls and VPNs are security risks, according to insurance claims could you power an entire house with disposable vapes? All that and more, on this episode of Enterprise Security Weekly. Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-433

Segment 1: Interview with Rob Allen It's the Year of the (Clandestine) Linux Desktop! As if EDR evasions weren't enough, attackers are now employing yet another method to hide their presence on enterprise systems: deploying tiny Linux VMs. Attackers are using Hyper-V and/or WSL to deploy tiny (120MB disk space and 256MB memory) Linux VMs to host a custom reverse shell and reverse proxy. In this segment, we'll discuss strategies and mitigations to battle this novel technique with Rob Allen from Threatlocker. Segment Resources: Pro-Russian Hackers Use Linux VMs to Hide in Windows Russian Hackers Abuse Hyper-V to Hide Malware in Linux VMs Qilin ransomware abuses WSL to run Linux encryptors in Windows This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Segment 2: Topic - Threat Modeling Humanoid Robots We're entering the age of human-shaped robots, so it seems like a good time to talk about the fact that they ALREADY HAVE CVEs assigned to them. I guess this isn't a terrible thing - John Connor might have had an easier time if he could simply hack the terminators from a distance... Resources https://www.unitree.com/H2 (watch the video!) China's humanoid robots get factory jobs as UBTech's model scores US$112 million in orders The big reveal: Xpeng founder unzips humanoid robot to prove it's not human Exploit Allows for Takeover of Fleets of Unitree Robots - Security researchers find a wormable vulnerability 100-page Paper: The Cybersecurity of a Humanoid Robot 5-page Paper: Cybersecurity AI: Humanoid Robots as Attack Vectors Amazingly, $300 smart vacuums have some of the same exact vulnerabilities and backdoors built into them as the $16,000 humanoid robots! The Day My Smart Vacuum Turned Against Me Segment 3: Weekly News Finally, in the enterprise security news, A $435M venture round A $75M seed round a few acquisitions the producer of the movie Half Baked bought a spyware company AI isn't going well, or is it? maybe we just need to adopt it more slowly and deliberately? ad-blockers are enterprise best practices firewalls and VPNs are security risks, according to insurance claims could you power an entire house with disposable vapes? All that and more, on this episode of Enterprise Security Weekly. Show Notes: https://securityweekly.com/esw-433

Segment 1: Interview with Rob Allen It's the Year of the (Clandestine) Linux Desktop! As if EDR evasions weren't enough, attackers are now employing yet another method to hide their presence on enterprise systems: deploying tiny Linux VMs. Attackers are using Hyper-V and/or WSL to deploy tiny (120MB disk space and 256MB memory) Linux VMs to host a custom reverse shell and reverse proxy. In this segment, we'll discuss strategies and mitigations to battle this novel technique with Rob Allen from Threatlocker. Segment Resources: Pro-Russian Hackers Use Linux VMs to Hide in Windows Russian Hackers Abuse Hyper-V to Hide Malware in Linux VMs Qilin ransomware abuses WSL to run Linux encryptors in Windows This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Segment 2: Topic - Threat Modeling Humanoid Robots We're entering the age of human-shaped robots, so it seems like a good time to talk about the fact that they ALREADY HAVE CVEs assigned to them. I guess this isn't a terrible thing - John Connor might have had an easier time if he could simply hack the terminators from a distance... Resources https://www.unitree.com/H2 (watch the video!) China's humanoid robots get factory jobs as UBTech's model scores US$112 million in orders The big reveal: Xpeng founder unzips humanoid robot to prove it's not human Exploit Allows for Takeover of Fleets of Unitree Robots - Security researchers find a wormable vulnerability 100-page Paper: The Cybersecurity of a Humanoid Robot 5-page Paper: Cybersecurity AI: Humanoid Robots as Attack Vectors Amazingly, $300 smart vacuums have some of the same exact vulnerabilities and backdoors built into them as the $16,000 humanoid robots! The Day My Smart Vacuum Turned Against Me Segment 3: Weekly News Finally, in the enterprise security news, A $435M venture round A $75M seed round a few acquisitions the producer of the movie Half Baked bought a spyware company AI isn't going well, or is it? maybe we just need to adopt it more slowly and deliberately? ad-blockers are enterprise best practices firewalls and VPNs are security risks, according to insurance claims could you power an entire house with disposable vapes? All that and more, on this episode of Enterprise Security Weekly. Show Notes: https://securityweekly.com/esw-433

Hackers Weaponize Windows Hyper-V to Hide Linux VM and Evade EDR Detection

Hackers use Windows Hyper-V to evade EDR detection Critical Cisco UCCX flaw lets attackers run commands as root The Louvre's video security password was reportedly Louvre  Huge thanks to our sponsor, ThreatLocker Imagine having the power to decide exactly what runs in your IT environment — and blocking everything else by default. That's what ThreatLocker delivers. As a zero-trust endpoint protection platform, ThreatLocker fills the gaps traditional solutions leave behind, giving your business stronger security and control. Don't just react to threats — stop them with ThreatLocker. Find the stories behind the headlines at CISOseries.com.

Stay ahead of September 2025 Patch Tuesday. Automox experts Ryan Braunstein, Henry Smith, and Seth Hoyt break down three high-impact items you need to act on now: Hyper-V privilege escalation, XAML/Phone Link elevation paths, and an NTFS remote code execution.You'll get:Clear patch priorities and timing.Likely attack paths and real-world detection tips.Hardening moves: WDAC/AppLocker, least privilege, Phone Link controls, and removing Hyper-V where it's not needed.How to use the Automox console to group at-risk devices, push updates, disable features, and verify compliance.Subscribe, share with your team, and tighten your local attack surface today.

Join Automox cybersecurity experts Ryan Braunstein and Mat Lee for August 2025's Patch [FIX] Tuesday, covering a Hyper-V privilege escalation, an Azure Virtual Machines spoofing flaw, and four serious SQL Server vulnerabilities. Learn how attackers could chain virtualization and cloud exploits, why crafted VHDX files and spoofed certificates are dangerous, and the ongoing threat of SQL injection. Includes recommendations for hardening databases, improving certificate management, and reducing lateral movement risks in virtualized environments.

In Episode 182 of The Citrix Session, host Bill Sutton and Citrix's Todd Smith dive into the expanded capabilities of XenServer 8.4, Citrix's enterprise-grade hypervisor. No longer just for Citrix workloads, XenServer is now fully supported for all workloads under both Citrix Platform Licensing and UHMC—making it a strong contender for organizations exploring alternatives to VMware and Hyper-V.

AP Tests, Hyper-V, Notepad, Google, Nova Scotia, NHI, Bond, Josh Marpet, and more on the Security Weekly News. Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn-480

AP Tests, Hyper-V, Notepad, Google, Nova Scotia, NHI, Bond, Josh Marpet, and more on the Security Weekly News. Show Notes: https://securityweekly.com/swn-480

AP Tests, Hyper-V, Notepad, Google, Nova Scotia, NHI, Bond, Josh Marpet, and more on the Security Weekly News. Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn-480

AP Tests, Hyper-V, Notepad, Google, Nova Scotia, NHI, Bond, Josh Marpet, and more on the Security Weekly News. Show Notes: https://securityweekly.com/swn-480

It's Week D, do you know where your preview update is? 23H2 is out - 24H2, not so much! No surprises in the new features list, but are more new features on the way? Windows New text actions in Click to Do - Practice in Reading Coach and Read with Immersive Reader - in Dev and Beta (24H2) Find cloud-based (OneDrive-based) photos using Semantic search - Comes to EEA, Snapdragon X only for now, Dev and Beta Voice access improvements - add words to custom dictionary - Dev and Beta Updated green screen UI - latest Canary build, from today Minor update to the Beta/23H2 channel, no new features Ubuntu 25.04 is out and there's a native Arm64 ISO (!) and BitLocker support Hands-on with WSL (which is stuck at 24.xx) and in Hyper-V on a Copilot+ PC Is dual-boot even possible on Arm? (Yet) Friday night update to identity caused accounts to be marked as leaked for 50,000 partner accounts AI We're in a new wave: Microsoft 365 Copilot updated, new Agent Store and more on the way Copilot Vision is now free for everyone in Microsoft Edge Google is giving Gemini Advanced/Google One AI Premium away for free to US college students Google estimates its Gemini AI chatbot had 35M DAUs and 350M MAUs worldwide as of last month while ChatGPT had 160M DAUs and 600M MAUs (Erin Woo/The Information) Perplexity is coming to Samsung and Motorola phones - and Microsoft is apparently coming to Motorola too Antitrust It's getting real - 20 years after US v. Microsoft, Big Tech is finally getting a reckoning Google has now lost two major US antitrust cases in less than a year US v. Google (search): DOJ wants Judge to break up Google US v. Google (ads): Google found to have another illegal monopoly What's the "right" outcome for Chrome and Google's ad businesses? OpenAI says it would be happy to buy Chrome from Google- hilarious Google just killed Privacy Sandbox, cites regulatory climate Apple, Meta fined by EU for not conforming to the DMA Apple Intelligence is no longer "available now" (Siri: Is it raining?) Xbox/gaming Elder Scrolls IV Remastered lands on Xbox, PC, PS5 and Game Pass Xbox app arrives on LG smart TVs It's (back) on: Nintendo Switch 2 pre-orders rescheduled to April 24 with no price change And the demand is higher than expected, Nintendo says Tips and Picks Tip of the week: It's time to look at Google Fi again HARDWARE pick of the week: Microsoft keyboards and mice are back, baby RunAs Radio this week: Agentic AI for IT Pros with Tim Warner Brown liquor pick of the week: Dark Harmony No. 3 Black IPA Cask Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsor: spaceship.com/twit

It's Week D, do you know where your preview update is? 23H2 is out - 24H2, not so much! No surprises in the new features list, but are more new features on the way? Windows New text actions in Click to Do - Practice in Reading Coach and Read with Immersive Reader - in Dev and Beta (24H2) Find cloud-based (OneDrive-based) photos using Semantic search - Comes to EEA, Snapdragon X only for now, Dev and Beta Voice access improvements - add words to custom dictionary - Dev and Beta Updated green screen UI - latest Canary build, from today Minor update to the Beta/23H2 channel, no new features Ubuntu 25.04 is out and there's a native Arm64 ISO (!) and BitLocker support Hands-on with WSL (which is stuck at 24.xx) and in Hyper-V on a Copilot+ PC Is dual-boot even possible on Arm? (Yet) Friday night update to identity caused accounts to be marked as leaked for 50,000 partner accounts AI We're in a new wave: Microsoft 365 Copilot updated, new Agent Store and more on the way Copilot Vision is now free for everyone in Microsoft Edge Google is giving Gemini Advanced/Google One AI Premium away for free to US college students Google estimates its Gemini AI chatbot had 35M DAUs and 350M MAUs worldwide as of last month while ChatGPT had 160M DAUs and 600M MAUs (Erin Woo/The Information) Perplexity is coming to Samsung and Motorola phones - and Microsoft is apparently coming to Motorola too Antitrust It's getting real - 20 years after US v. Microsoft, Big Tech is finally getting a reckoning Google has now lost two major US antitrust cases in less than a year US v. Google (search): DOJ wants Judge to break up Google US v. Google (ads): Google found to have another illegal monopoly What's the "right" outcome for Chrome and Google's ad businesses? OpenAI says it would be happy to buy Chrome from Google- hilarious Google just killed Privacy Sandbox, cites regulatory climate Apple, Meta fined by EU for not conforming to the DMA Apple Intelligence is no longer "available now" (Siri: Is it raining?) Xbox/gaming Elder Scrolls IV Remastered lands on Xbox, PC, PS5 and Game Pass Xbox app arrives on LG smart TVs It's (back) on: Nintendo Switch 2 pre-orders rescheduled to April 24 with no price change And the demand is higher than expected, Nintendo says Tips and Picks Tip of the week: It's time to look at Google Fi again HARDWARE pick of the week: Microsoft keyboards and mice are back, baby RunAs Radio this week: Agentic AI for IT Pros with Tim Warner Brown liquor pick of the week: Dark Harmony No. 3 Black IPA Cask Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsor: spaceship.com/twit

It's Week D, do you know where your preview update is? 23H2 is out - 24H2, not so much! No surprises in the new features list, but are more new features on the way? Windows New text actions in Click to Do - Practice in Reading Coach and Read with Immersive Reader - in Dev and Beta (24H2) Find cloud-based (OneDrive-based) photos using Semantic search - Comes to EEA, Snapdragon X only for now, Dev and Beta Voice access improvements - add words to custom dictionary - Dev and Beta Updated green screen UI - latest Canary build, from today Minor update to the Beta/23H2 channel, no new features Ubuntu 25.04 is out and there's a native Arm64 ISO (!) and BitLocker support Hands-on with WSL (which is stuck at 24.xx) and in Hyper-V on a Copilot+ PC Is dual-boot even possible on Arm? (Yet) Friday night update to identity caused accounts to be marked as leaked for 50,000 partner accounts AI We're in a new wave: Microsoft 365 Copilot updated, new Agent Store and more on the way Copilot Vision is now free for everyone in Microsoft Edge Google is giving Gemini Advanced/Google One AI Premium away for free to US college students Google estimates its Gemini AI chatbot had 35M DAUs and 350M MAUs worldwide as of last month while ChatGPT had 160M DAUs and 600M MAUs (Erin Woo/The Information) Perplexity is coming to Samsung and Motorola phones - and Microsoft is apparently coming to Motorola too Antitrust It's getting real - 20 years after US v. Microsoft, Big Tech is finally getting a reckoning Google has now lost two major US antitrust cases in less than a year US v. Google (search): DOJ wants Judge to break up Google US v. Google (ads): Google found to have another illegal monopoly What's the "right" outcome for Chrome and Google's ad businesses? OpenAI says it would be happy to buy Chrome from Google- hilarious Google just killed Privacy Sandbox, cites regulatory climate Apple, Meta fined by EU for not conforming to the DMA Apple Intelligence is no longer "available now" (Siri: Is it raining?) Xbox/gaming Elder Scrolls IV Remastered lands on Xbox, PC, PS5 and Game Pass Xbox app arrives on LG smart TVs It's (back) on: Nintendo Switch 2 pre-orders rescheduled to April 24 with no price change And the demand is higher than expected, Nintendo says Tips and Picks Tip of the week: It's time to look at Google Fi again HARDWARE pick of the week: Microsoft keyboards and mice are back, baby RunAs Radio this week: Agentic AI for IT Pros with Tim Warner Brown liquor pick of the week: Dark Harmony No. 3 Black IPA Cask Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsor: spaceship.com/twit

It's Week D, do you know where your preview update is? 23H2 is out - 24H2, not so much! No surprises in the new features list, but are more new features on the way? Windows New text actions in Click to Do - Practice in Reading Coach and Read with Immersive Reader - in Dev and Beta (24H2) Find cloud-based (OneDrive-based) photos using Semantic search - Comes to EEA, Snapdragon X only for now, Dev and Beta Voice access improvements - add words to custom dictionary - Dev and Beta Updated green screen UI - latest Canary build, from today Minor update to the Beta/23H2 channel, no new features Ubuntu 25.04 is out and there's a native Arm64 ISO (!) and BitLocker support Hands-on with WSL (which is stuck at 24.xx) and in Hyper-V on a Copilot+ PC Is dual-boot even possible on Arm? (Yet) Friday night update to identity caused accounts to be marked as leaked for 50,000 partner accounts AI We're in a new wave: Microsoft 365 Copilot updated, new Agent Store and more on the way Copilot Vision is now free for everyone in Microsoft Edge Google is giving Gemini Advanced/Google One AI Premium away for free to US college students Google estimates its Gemini AI chatbot had 35M DAUs and 350M MAUs worldwide as of last month while ChatGPT had 160M DAUs and 600M MAUs (Erin Woo/The Information) Perplexity is coming to Samsung and Motorola phones - and Microsoft is apparently coming to Motorola too Antitrust It's getting real - 20 years after US v. Microsoft, Big Tech is finally getting a reckoning Google has now lost two major US antitrust cases in less than a year US v. Google (search): DOJ wants Judge to break up Google US v. Google (ads): Google found to have another illegal monopoly What's the "right" outcome for Chrome and Google's ad businesses? OpenAI says it would be happy to buy Chrome from Google- hilarious Google just killed Privacy Sandbox, cites regulatory climate Apple, Meta fined by EU for not conforming to the DMA Apple Intelligence is no longer "available now" (Siri: Is it raining?) Xbox/gaming Elder Scrolls IV Remastered lands on Xbox, PC, PS5 and Game Pass Xbox app arrives on LG smart TVs It's (back) on: Nintendo Switch 2 pre-orders rescheduled to April 24 with no price change And the demand is higher than expected, Nintendo says Tips and Picks Tip of the week: It's time to look at Google Fi again HARDWARE pick of the week: Microsoft keyboards and mice are back, baby RunAs Radio this week: Agentic AI for IT Pros with Tim Warner Brown liquor pick of the week: Dark Harmony No. 3 Black IPA Cask Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsor: spaceship.com/twit

It's Week D, do you know where your preview update is? 23H2 is out - 24H2, not so much! No surprises in the new features list, but are more new features on the way? Windows New text actions in Click to Do - Practice in Reading Coach and Read with Immersive Reader - in Dev and Beta (24H2) Find cloud-based (OneDrive-based) photos using Semantic search - Comes to EEA, Snapdragon X only for now, Dev and Beta Voice access improvements - add words to custom dictionary - Dev and Beta Updated green screen UI - latest Canary build, from today Minor update to the Beta/23H2 channel, no new features Ubuntu 25.04 is out and there's a native Arm64 ISO (!) and BitLocker support Hands-on with WSL (which is stuck at 24.xx) and in Hyper-V on a Copilot+ PC Is dual-boot even possible on Arm? (Yet) Friday night update to identity caused accounts to be marked as leaked for 50,000 partner accounts AI We're in a new wave: Microsoft 365 Copilot updated, new Agent Store and more on the way Copilot Vision is now free for everyone in Microsoft Edge Google is giving Gemini Advanced/Google One AI Premium away for free to US college students Google estimates its Gemini AI chatbot had 35M DAUs and 350M MAUs worldwide as of last month while ChatGPT had 160M DAUs and 600M MAUs (Erin Woo/The Information) Perplexity is coming to Samsung and Motorola phones - and Microsoft is apparently coming to Motorola too Antitrust It's getting real - 20 years after US v. Microsoft, Big Tech is finally getting a reckoning Google has now lost two major US antitrust cases in less than a year US v. Google (search): DOJ wants Judge to break up Google US v. Google (ads): Google found to have another illegal monopoly What's the "right" outcome for Chrome and Google's ad businesses? OpenAI says it would be happy to buy Chrome from Google- hilarious Google just killed Privacy Sandbox, cites regulatory climate Apple, Meta fined by EU for not conforming to the DMA Apple Intelligence is no longer "available now" (Siri: Is it raining?) Xbox/gaming Elder Scrolls IV Remastered lands on Xbox, PC, PS5 and Game Pass Xbox app arrives on LG smart TVs It's (back) on: Nintendo Switch 2 pre-orders rescheduled to April 24 with no price change And the demand is higher than expected, Nintendo says Tips and Picks Tip of the week: It's time to look at Google Fi again HARDWARE pick of the week: Microsoft keyboards and mice are back, baby RunAs Radio this week: Agentic AI for IT Pros with Tim Warner Brown liquor pick of the week: Dark Harmony No. 3 Black IPA Cask Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsor: spaceship.com/twit

It's Week D, do you know where your preview update is? 23H2 is out - 24H2, not so much! No surprises in the new features list, but are more new features on the way? Windows New text actions in Click to Do - Practice in Reading Coach and Read with Immersive Reader - in Dev and Beta (24H2) Find cloud-based (OneDrive-based) photos using Semantic search - Comes to EEA, Snapdragon X only for now, Dev and Beta Voice access improvements - add words to custom dictionary - Dev and Beta Updated green screen UI - latest Canary build, from today Minor update to the Beta/23H2 channel, no new features Ubuntu 25.04 is out and there's a native Arm64 ISO (!) and BitLocker support Hands-on with WSL (which is stuck at 24.xx) and in Hyper-V on a Copilot+ PC Is dual-boot even possible on Arm? (Yet) Friday night update to identity caused accounts to be marked as leaked for 50,000 partner accounts AI We're in a new wave: Microsoft 365 Copilot updated, new Agent Store and more on the way Copilot Vision is now free for everyone in Microsoft Edge Google is giving Gemini Advanced/Google One AI Premium away for free to US college students Google estimates its Gemini AI chatbot had 35M DAUs and 350M MAUs worldwide as of last month while ChatGPT had 160M DAUs and 600M MAUs (Erin Woo/The Information) Perplexity is coming to Samsung and Motorola phones - and Microsoft is apparently coming to Motorola too Antitrust It's getting real - 20 years after US v. Microsoft, Big Tech is finally getting a reckoning Google has now lost two major US antitrust cases in less than a year US v. Google (search): DOJ wants Judge to break up Google US v. Google (ads): Google found to have another illegal monopoly What's the "right" outcome for Chrome and Google's ad businesses? OpenAI says it would be happy to buy Chrome from Google- hilarious Google just killed Privacy Sandbox, cites regulatory climate Apple, Meta fined by EU for not conforming to the DMA Apple Intelligence is no longer "available now" (Siri: Is it raining?) Xbox/gaming Elder Scrolls IV Remastered lands on Xbox, PC, PS5 and Game Pass Xbox app arrives on LG smart TVs It's (back) on: Nintendo Switch 2 pre-orders rescheduled to April 24 with no price change And the demand is higher than expected, Nintendo says Tips and Picks Tip of the week: It's time to look at Google Fi again HARDWARE pick of the week: Microsoft keyboards and mice are back, baby RunAs Radio this week: Agentic AI for IT Pros with Tim Warner Brown liquor pick of the week: Dark Harmony No. 3 Black IPA Cask Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsor: spaceship.com/twit

Windows Server is back! Directions on Microsoft analyst Jim Gaynor and Mary Jo Foley delve into the new features and capabilities coming with Windows Server 2025 worth knowing about, including new Active Directory and security features, GPU partitioning for Hyper-V, hotpatching – and the Azure services you need to use them.

Join Automox's cybersecurity experts as they discuss the latest Patch Tuesday updates, focusing on vulnerabilities in Active Directory, Hyper-V, and macOS 15.2. They highlight the importance of staying updated and the evolving threat landscape, particularly with the rise of phishing attacks and the need for robust security measures in enterprise environments.

Ce mois-ci Yann nous parle de la disponibilité de NAbox pour de nouvelles plateformes de virtualisation ! Si votre hyperviseur est basé sur KVM ou Hyper-V, vous pouvez maintenant déployer NAbox !Worm et ARP sont maintenant inclus avec Cloud Volumes ONTAP sans coûts additionnels.VMware vCloud fondation est supporté avec NetAppTrident 24-06 supporte SnapMirror et les ONTAP Tools pour VMware supportent ActiveSync !Ne ratez pas les NetApp Insider's club et NetApp Insight Xtra !NFS supporte maintenant NFS-over-TLS et bien sûr on parle de NetApp Insight !Yann Bizeul (Linked-In)Guillaume Sowinski (Linked-In)Yves Weisser (Linked-In)

Wie sieht die Virtualisierungs-Landschaft im Jahr 2024 aus? Und mit welcher Lösung erfüllen Sie Ihre individuellen Anforderungen am effizientesten? Unsere Virtualisierungs-Experten Lukas Stadler, Florian Müller und Jonas Sterr nehmen Sie mit auf einen Streifzug durch VMware, Hyper-V und Proxmox und besprechen die Vorzüge und Besonderheiten ihres jeweiligen Fachgebiets. Viel Spaß beim Hören!

Gene Leyzarovich, Founder at JetStor shares insights on the evolution of data storage from tapes and magnetic disks to modern flash and hybrid systems. We discuss the significant impact of the Broadcom and VMware acquisition on licensing costs, prompting many organizations to explore alternatives like Proxmox and Hyper-V.

In this episode of the Security Swarm Podcast, host Andy and recurring guest, Paul, talk about the challenges and opportunities organizations face amidst the Broadcom acquisition of VMware. They discuss the steep price hikes for VMware licenses and the security vulnerabilities recently discovered in VMware products.   This acquisition has prompted many businesses to consider alternative solutions, and the episode provides a comprehensive overview of the available options within the Microsoft ecosystem. They cover a range of migration strategies, including moving to the Microsoft ecosystem through Azure, Azure Stack HCI, and on-premises Hyper-V solutions.  Andy and Paul offer valuable insights into ensuring a secure and seamless transition away from VMware, making this episode essential listening for IT professionals navigating these significant changes.  Key takeaways: Broadcom's Acquisition of VMware is Causing Major Disruption due to massive license cost increases of 300-500% for many organizations.  Microsoft Hyper-V is a Viable Alternative to VMware. It offers a mature, enterprise-ready hypervisor that can be a cost-effective replacement for VMware.  Azure Stack HCI Provides an On-Premises VMware Alternative. It provides a hyperconverged infrastructure solution with Hyper-V at the core, along with integration to Azure services for management and modernization.  Security pitfalls can arise when organizations rush to migrate away from VMware due to the Broadcom situation. Proper planning, understanding the security posture of the new platform, and ensuring critical configurations like backup are in place are essential to mitigate risks.  Timestamps: (02:51) - Vulnerabilities in VMware  (07:30) - Migrating to the Microsoft Ecosystem  (13:38) - On-Premises Microsoft Options  (38:45) - Security Considerations for Migrations  (44:52) - Pragmatic Approach to Platform Selection  Episode Resources: Microsoft and Broadcom to Support License Portability  Paul's article on options for migrating from VMware to Microsoft  VMware Sandbox Escape Bugs 

Sich die Virtualisierungs-Distribution Proxmox anzuschauen, ist nicht nur sinnvoll, wenn man zufällig gerade von VMware weg möchte. Auch zum Zusammenfassen eines Haufens Smart-Home-Raspis auf einer einzigen Kiste ist es geeignet, oder einfach für Testinstallationen von Betriebssystemen und Software. Die c't-Kollegen Niklas Dierking und Peter Siering haben nicht nur Artikel zum Thema Proxmox geschrieben, sondern sie sind auch zu Gast in dieser Folge des c't uplink. Wir sprechen darüber, was Proxmox kann, woraus es besteht, für wen es sich eignet und mehr. Unseren Proxmox-Schwerpunkt lesen Sie in c't 9/2024.

Windows Server is back! Directions on Microsoft analyst Jim Gaynor and Mary Jo Foley delve into the new features and capabilities coming with Windows Server 2025 worth knowing about, including new Active Directory and security features, GPU partitioning for Hyper-V, hotpatching – and the Azure services you need to use them.

Windows Server is back, baby! Directions on Microsoft analyst Jim Gaynor and Mary Jo Foley delve into a lot of the new goodies coming with Windows Server 2025. Hotpatching, new Active Directory and security features, GPU partitioning for Hyper-V and more are slated to arrive later this year. Here's what IT pros need to know.

Microsoft fixes critical flaws in Windows Kerberos, Hyper-V

Welcome to episode 240! It's a doozy this week! Justin, Ryan, Jonathan and Matthew are your hosts in this supersized episode. Today we talk about Google Gemini, the GCP sales force (you won't believe the numbers) and Google feudalism. (There's some lovely filth over here!) Plus we discuss the latest happenings over at HashiCorp, Broadcom, and the Code family of software. So put away your ugly sweaters and settle in for episode 240 of The Cloud Pod podcast - where the forecast is always cloudy!  Titles we almost went with this week:

In today's episode, hosts Andy Leonard and Frank La Vigne catch up on their recent activities, including Frank's presentations at the Red Hat Summit Connect. They discuss the event and the focus on AI and government agencies. Frank also shares his experiences with a new product called Ansible Lightspeed with Watson code assist, which is enhancing the use of large language models.Moving on, Andy and Frank talk about their home lab projects. They both express their excitement for building a powerful system that allows them to explore AI capabilities locally. While Andy's lab is focused on AI, Frank is delving into the world of Red Hat OpenShift and containers to expand his knowledge. They discuss the importance of hands-on learning and the practicality of setting up a home lab.The conversation takes an interesting turn as they discuss Andy's initial miscalculation with the GPU size and his daughter starting college, leading to budget changes. Frank shares his hardware journey over the past year, including his experience with the Apple Silicon M2 computer and its incredible performance.Tune in to this episode of "Data Driven" to hear more about the Red Hat Summit, the latest developments in AI, and the adventures of building a home lab. So grab your favorite beverage, sit back, and get ready to dive into the world of data-driven insights!LinksRed Hat OpenShift AI in Higher Education Webinar https://qrcodes.at/aidata-edu-webinar-oct19Show Notes[00:00:45] Red Hat holds an annual summit, usually in Boston, featuring sessions for developers.[00:05:16] Recounting difficulty using AI engines, but eventually having success. Mistake of underestimating GPU capacity.[00:07:08] This 8 gig memory is supernatural, like a cool oasis at a conference.[00:09:48] The text discusses trying different operating systems on an old device, including Fedora and Chrome OS Flex.[00:15:17] This machine has 96 gigs and can run multiple VMs.[00:17:12] The author plans to install Hyper V on Windows Server to run multiple Linux VMs, eventually migrating to Red Hat Enterprise Linux. They are waiting for a developer license key.[00:19:46] The person is setting up a NAS to store and access files from different devices. They currently use OneDrive as a temporary solution.

In today's episode, Andy has a special guest from our product development team at Hornetsecurity - Jean Paul (JP) Callus. The episode goes into an insightful discussion on how threats have morphed over the years. Andy and Jean Paul recount the days when backup primarily served as a safety net against accidental data loss and hardware failures. Fast forward to today, and backups have become a key weapon in the fight against ransomware and other sophisticated attacks.  Tune in to discover the power of modern backups in the ever-evolving world of cybersecurity and how organizations can establish seamless data protection measures, ensuring minimal data loss and downtime in the face of cyber threats.  Timestamps: (2:16) – Ransomware continues to drive backup and recovery decisions. (10:10) – How has the industry traditionally mitigated ransomware and how are things done now?  (14:13) – Revisiting the 3-2-1 backup strategy and adding an extra “1”  (16:10) – Cloud backups and WORM (Write Once Read Many) states.  (19:10) – What other backup technologies play a role in security?  (23:43) – Deduplication, Immutability, and Backup  Episode resources: Podcast EP01: We Used ChatGPT to Create Ransomware Podcast EP05: What is Immutability and Why Do Ransomware Gangs Hate it? Hornetsecurity Ransomware Attack Survey VM Backup V9 The Backup Bible  Find Andy on LinkedIn, Twitter or Mastadon Find Jean Paul on LinkedIn This SysAdmin Day, win with Hornetsecurity!  If you are a System/IT Admin and use Hyper-V or VMware, celebrate with us by signing up & trialling VM Backup V9 for a chance to win a Pixel Tablet! Find out more information here. 

Move on-premises VMware or Hyper-V workloads to the cloud with Azure Migrate. Discover and assess your VMs, generate a business case for moving Windows and Linux VMs into Azure, and use integrated tools to replicate and migrate your VMs into production running on Azure. Get Extended Security Updates until October 2026 along with upgrade rights to a supported Windows Server release if you're migrating Windows Server 2012 VMs to Azure.   Azure expert, Matt McSpirit, gives a quick overview of how to migrate your VMware virtual machines to Azure. ► QUICK LINKS: 00:00 - Introduction 00:31 - Prerequisites 01:12 - VM discovery 03:15 - Discovered servers 04:12 - New business case assessment 05:55 - Create an assessment to migrate VMs into Azure 06:54 - Replicate VMs into Azure 08:35 - Run test migrations 09:14 - Migrate VMs into production 09:47 - Wrap up ► Link References: Set up permissions in Azure at https://aka.ms/VMwarePrereqs Details to migrate complete VMware environments and run them in Azure at https://aka.ms/AVSmechanics For expert migration help go to https://azure.com/AMMP ► Unfamiliar with Microsoft Mechanics? As Microsoft's official video series for IT, you can watch and share valuable content and demos of current and upcoming tech from the people who build it at Microsoft. • Subscribe to our YouTube: https://www.youtube.com/c/MicrosoftMechanicsSeries • Talk with other IT Pros, join us on the Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog • Watch or listen from anywhere, subscribe to our podcast: https://microsoftmechanics.libsyn.com/podcast ► Keep getting this insider knowledge, join us on social: • Follow us on Twitter: https://twitter.com/MSFTMechanics • Share knowledge on LinkedIn: https://www.linkedin.com/company/microsoft-mechanics/ • Enjoy us on Instagram: https://www.instagram.com/msftmechanics/ • Loosen up with us on TikTok: https://www.tiktok.com/@msftmechanics

Bret and Matt are joined by Corey Quinn to talk about AWS and containers.Corey Quinn is the Chief Cloud Economist at the Duckbill Group. You may have seen or heard some of his in-depth AWS content, including his Last Week in AWS newsletter and blog, Corey's podcast Screaming in the Cloud and the AWS Morning Brief, or his highly produced YouTube videos on the Last Week in AWS channel. Corey runs the Duckbill Group, a company of people focused on helping clients understand and manage their cloud spend. If I had to describe Corey in a sentence, he's a quick thinking AWS expert who is one part cloud strategist, and one part sarcasm. The inspiration for this show came from his blog series, focused on all the ways to run containers on AWS, which is to say there's a lot. Dozens of ways, in fact, which I took as a testament to how containers have won the cloud as the primary way to package and deploy software to servers. Now, the hard part for us is to figure out which method we're going to choose for running those containers. We go on lots of tangents, but overall it was a fun conversation and I hope you enjoy this episode.Live recording of the complete show from May 4, 2023 is on YouTube (Ep. #214).★Topics★The Cloud Resume ChallengeLast Week in AWS17 ways to run containers on AWS17 MORE ways to run containers on AWSSupport this show and get exclusive benefits on Patreon, YouTube, or bretfisher.com!★Join my Community★New live course on CI automation and gitops deploymentsBest coupons for my Docker and Kubernetes coursesChat with us and fellow students on our Discord Server DevOps FansGrab some merch at Bret's Loot BoxHomepage bretfisher.comCreators & Guests Bret Fisher - Host Cristi Cotovan - Editor Beth Fisher - Producer Matt Williams - Host Corey Quinn - Guest (00:00) - Intro (07:19) - 17 Ways to Run Containers on AWS (09:57) - If you're using the cloud, use the cloud! (13:32) - Data loss and it's only on the internet forever (17:58) - Recommended ways to run containers on AWS (22:49) - Biggest burn on people's AWS bills (29:33) - Docker Desktop on top of AWS EC2 in Windows and do you need bare metal? (30:13) - Bare metal required for Hyper-V (32:39) - AWS App Runner (40:26) - Services AWS has dropped (41:39) - Workloads inside the container; where the container should run (44:13) - Building experience...hands-on projects vs getting certifications (55:31) - Migrating. Leaving Kubernetes. (01:00:57) - Chat GPT Star Wars jokes

Gallery in File Explorer, Bing in SwiftKey, Ubisoft+ Multi Access Bing/AI Samsung allegedly is considering replacing Google Search with Bing. Can they even do that? Bing chatbot comes to Swiftkey and Microsoft Start. And now you can remove the Bing button from Swiftkey. Sound familiar? Microsoft is all-in on AI hardware Microsoft brings more AI to developers ahead of Build Amazon announces Bedrock generative AI tool for developers. Speaking of which, where's Apple in all this? Windows 11 New Dev channel build: remove time/date from the system tray, "new" hover behavior on search New Beta channel build: Content Adaptive Brightness Control (CABC) on plugged in PCs, a PC maker-enabled feature - plus RDC redesign for Windows 11 Photo Gallery view comes to File Explorer in Insider Program This isn't the first time a Photos app feature has shown up elsewhere this year Surface Microsoft can't seem to escape the trap of its one successful Surface design Xbox Minecraft Legends, more on tap for Xbox Game Pass Ubisoft+ Multi Access comes to Xbox The exodus from 343 Industries continues Microsoft: just kidding on the latest Xbox Dashboard UI Sega buys Rovio for the same reason Microsoft wants AB Tips & Picks Tip of the week: Hyper-V or Windows Sandbox? App pick of the week: Xbox Game Pass Ultimate/Xbox app for Windows 11 RunAs Radio this week: Project Zero Trust with George Finney Brown liquor pick of the week: Woodford Reserve Hosts: Paul Thurrott, Richard Campbell, and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsors: Miro.com/podcast meraki.cisco.com/twit cachefly.com

Gallery in File Explorer, Bing in SwiftKey, Ubisoft+ Multi Access Bing/AI Samsung allegedly is considering replacing Google Search with Bing. Can they even do that? Bing chatbot comes to Swiftkey and Microsoft Start. And now you can remove the Bing button from Swiftkey. Sound familiar? Microsoft is all-in on AI hardware Microsoft brings more AI to developers ahead of Build Amazon announces Bedrock generative AI tool for developers. Speaking of which, where's Apple in all this? Windows 11 New Dev channel build: remove time/date from the system tray, "new" hover behavior on search New Beta channel build: Content Adaptive Brightness Control (CABC) on plugged in PCs, a PC maker-enabled feature - plus RDC redesign for Windows 11 Photo Gallery view comes to File Explorer in Insider Program This isn't the first time a Photos app feature has shown up elsewhere this year Surface Microsoft can't seem to escape the trap of its one successful Surface design Xbox Minecraft Legends, more on tap for Xbox Game Pass Ubisoft+ Multi Access comes to Xbox The exodus from 343 Industries continues Microsoft: just kidding on the latest Xbox Dashboard UI Sega buys Rovio for the same reason Microsoft wants AB Tips & Picks Tip of the week: Hyper-V or Windows Sandbox? App pick of the week: Xbox Game Pass Ultimate/Xbox app for Windows 11 RunAs Radio this week: Project Zero Trust with George Finney Brown liquor pick of the week: Woodford Reserve Hosts: Paul Thurrott, Richard Campbell, and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsors: Miro.com/podcast meraki.cisco.com/twit cachefly.com

Gallery in File Explorer, Bing in SwiftKey, Ubisoft+ Multi Access Bing/AI Samsung allegedly is considering replacing Google Search with Bing. Can they even do that? Bing chatbot comes to Swiftkey and Microsoft Start. And now you can remove the Bing button from Swiftkey. Sound familiar? Microsoft is all-in on AI hardware Microsoft brings more AI to developers ahead of Build Amazon announces Bedrock generative AI tool for developers. Speaking of which, where's Apple in all this? Windows 11 New Dev channel build: remove time/date from the system tray, "new" hover behavior on search New Beta channel build: Content Adaptive Brightness Control (CABC) on plugged in PCs, a PC maker-enabled feature - plus RDC redesign for Windows 11 Photo Gallery view comes to File Explorer in Insider Program This isn't the first time a Photos app feature has shown up elsewhere this year Surface Microsoft can't seem to escape the trap of its one successful Surface design Xbox Minecraft Legends, more on tap for Xbox Game Pass Ubisoft+ Multi Access comes to Xbox The exodus from 343 Industries continues Microsoft: just kidding on the latest Xbox Dashboard UI Sega buys Rovio for the same reason Microsoft wants AB Tips & Picks Tip of the week: Hyper-V or Windows Sandbox? App pick of the week: Xbox Game Pass Ultimate/Xbox app for Windows 11 RunAs Radio this week: Project Zero Trust with George Finney Brown liquor pick of the week: Woodford Reserve Hosts: Paul Thurrott, Richard Campbell, and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsors: Miro.com/podcast meraki.cisco.com/twit cachefly.com

Gallery in File Explorer, Bing in SwiftKey, Ubisoft+ Multi Access Bing/AI Samsung allegedly is considering replacing Google Search with Bing. Can they even do that? Bing chatbot comes to Swiftkey and Microsoft Start. And now you can remove the Bing button from Swiftkey. Sound familiar? Microsoft is all-in on AI hardware Microsoft brings more AI to developers ahead of Build Amazon announces Bedrock generative AI tool for developers. Speaking of which, where's Apple in all this? Windows 11 New Dev channel build: remove time/date from the system tray, "new" hover behavior on search New Beta channel build: Content Adaptive Brightness Control (CABC) on plugged in PCs, a PC maker-enabled feature - plus RDC redesign for Windows 11 Photo Gallery view comes to File Explorer in Insider Program This isn't the first time a Photos app feature has shown up elsewhere this year Surface Microsoft can't seem to escape the trap of its one successful Surface design Xbox Minecraft Legends, more on tap for Xbox Game Pass Ubisoft+ Multi Access comes to Xbox The exodus from 343 Industries continues Microsoft: just kidding on the latest Xbox Dashboard UI Sega buys Rovio for the same reason Microsoft wants AB Tips & Picks Tip of the week: Hyper-V or Windows Sandbox? App pick of the week: Xbox Game Pass Ultimate/Xbox app for Windows 11 RunAs Radio this week: Project Zero Trust with George Finney Brown liquor pick of the week: Woodford Reserve Hosts: Paul Thurrott, Richard Campbell, and Mikah Sargent Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsors: Miro.com/podcast meraki.cisco.com/twit cachefly.com

In this episode I talk with Dustin Milberg, Field CTO at InterVision. InterVision is strategic service provider focused on helping commercial and public sector organizations transform their technology strategy, improve risk management and gain a competitive edge. InterVision look to solve crucial IT challenges by delivering the right technology, deployed on the right premises and managed through the right service model. The specialize in datacenter and professional services around Resiliency, Cloud, Communications, Infrastructure and more. Dustin and I talk about the evolution of what it is to be a modern day Service Provider in a world where hybrid cloud rules and security and data protection is paramount to their clients. InterVision was founded in 1993 and is head quartered out of Santa Clara, California, United States. ☑️ But me a coffee? - https://ko-fi.com/gtwgt ☑️ Technology and Technology Partners Mentioned: VMware, Hyper-V, Nutanix, Veeam, Microsoft, AWS, Azure, Kubernetes, Containers, Storage, Networking, DRaaS, BaaS, Security ☑️ Raw Talking Points: History and founding First 10 years + CAD begins Early days of hosting Transitioning through hosting to infrastructure to virtualisation to cloud Acquisitions - Bluelock Public Cloud Services AWS and Azure Security and Ransomeware Managed vs Unmanaged Ransomware, backup and DR Optimizing workloads question Power of the Data Platforms ☑️ Web: https://intervision.com/ ☑️ Interested in being on #GTwGT? Contact via Twitter @GTwGTPodcast or go to https://www.gtwgt.com ☑️ Subscribe to YouTube: https://www.youtube.com/@GTwGTPodcast?sub_confirmation=1 ☑️ Music: https://www.bensound.com

In this episode I talk with Yan Ness, Chief Executive Officer at Verge.io. Verge.io is a single piece of hyper-converged virtualization software that makes it easy to use existing resources to create secure multi-tenant private clouds. Verge.io provides a simpler way to virtualize data centers and end IT infrastructure complexity. The company's Verge OS software is the first and only fully integrated virtual cloud software stack to build, deploy and manage virtual data centers. Verge-OS delivers significant capital savings, increased operational efficiencies, reduced risk, and rapid scalability. Yan and I talk about the shift from traditional de-coupled platforms like VMware and how even the Public Cloud is overly complex. Through simplicity of the stack, Verge.io is able to allow service providers and organizations function without the hassles associated with standard hardware platforms. Verge.io was borne from YottaByte, founded in 2010 as a replacement for on-premises infrastructure. Eventually, YottaByte rebranded to Verge.io and is head quartered out of Greater Detroit Area, Great Lakes. ☑️ But me a coffee? - https://ko-fi.com/gtwgt ☑️ Technology and Technology Partners Mentioned: VMware, KVM, Hyper-V, Nutanix, Veeam, Microsoft, AWS, Azure, Kubernetes, Containers, Storage, Networking ☑️ Raw Talking Points: Lead with the product Early years starting up... ISP/Dial Up to colo cloud - comparison Retirement Encapsulation of the datacenter above storage Art of simplcity Yottabyte Technology Virtualizing the Datacenter holistically Cost pressures of AWS/Azure Public cloud Verge.io Stack? Install? VMware replacement and Migrations Scale The Verge.io Recipe Engine Management and Dashboard and API MSP and SP space vs on-prem Modern Platforms Kubevirt Kubernetes Profile and impact of Verge.io ☑️ Web: https://verge.io ☑️ Sign up for a 14 day Test Drive: https://www.verge.io/test-drive ☑️ Interested in being on #GTwGT? Contact via Twitter @GTwGTPodcast or go to https://www.gtwgt.com ☑️ Subscribe to YouTube: https://www.youtube.com/@GTwGTPodcast?sub_confirmation=1 ☑️ Music: https://www.bensound.com

We've got Microsoft MVP Eric Siron for a conversation about the end of Hyper-V Server (the free SKU of Hyper-V). Again, to confirm, we're talking about the free SKU of Hyper-V. The normal paid SKUs - the well-known role within Windows Server - will be remaining. This announcement came abruptly and was something of a shock to many people. Hyper-V server was the primary test/dev hypervisor for many organizations, not to mention it was great for licensing in VDI scenarios. News of its untimely demise has created some angst in the community. Many IT Pros see this move by Microsoft as a way to takeaway a great free tool and use the situation to start pushing Azure Stack HCI, which many organizations are not ready to adopt at this time. The good news is that Hyper-V Server 2019 is going to continue to be supported until its extended support lifecycle runs out in 2029. This means that many organizations will have plenty of time to migrate to an alternative. What do you think? Is this change going to be impactful for you? Let us know! In this episode on free Hyper-V: What is Hyper-V Server? - 2:10 Is Hyper-V Server being discontinued? - 11:04 Where do Hyper-V Server users go from here? - 18:15 What are some alternatives to Hyper-V Server? - 21:49 Resources for Hyper-V Server: Hyper-V Server on the DOJO Azure Stack HCI on the DOJO ESXi Hypervisor on the DOJO Link to Communities Thread discussing Hyper-V Server's discontinuation Hyper-V Server Lifecycle Episode with Ben Armstrong on Hyper-V Server Episode with Ben Armstrong on AKS on Azure Stack HCI Client Hyper-V vs. Virtualbox - Which is Best for You? Azure Stack HCI Webinar on the DOJO For more on this episode on free Hyper-V > 

In this episode I talk with Boyan Krosnov Chief Product Officer and co-founder at StorPool. StorPool a market leading Software defined storage vendor, offering reliable and speedy storage platforms with a focus on low latency throughput... covering Public and private clouds platforms, servicing managed cloud and Service providers as well as enterprises, and SaaS vendors. Boyan an myself talk about how StorPool leverages an agnostic approach to hardware to allow StorPool to run across multiple hardware platforms and configurations while still maintaining reliable and speedy storage and how they have ridden the alternative new age IT stacks to success. StorPool was founded in 2011 and is Head Quartered out of the Sofia, Bulgaria. ☑️ Technology and Technology Partners Mentioned: Block Storage, Storage, NVMe, Object Storage, Kubernetes, VMware, KVM, Hyper-V, OpenStack, Cloudstack, Software Defined Storage ☑️ Raw Talking Points: MSP Angle Cloud Platforms SDS 2.0 Hows it designed and architected Filesystem? Object Storage Based? Pooling of capacity and performance Standard storage, storage and compute PERFORMANCE methodology IOPS/Latency/Storage Consumption Decreasing latency Proper Benchmarking Resiliency Failure domains/resolution Differential? Storage Protocols Distributed Storage? Running on any hardware Future of storage with public cloud and more managed data platforms Continuous Improvement process New-Age IT Stacks ☑️ Web: https://storpool.com/ ☑️ Interested in being on #GTwGT? Contact via Twitter @GTwGTPodcast or go to https://www.gtwgt.com ☑️ Music: https://www.bensound.com

This week we look at 5 mistakes people make with their TV Settings and how to fix them and long time listener Jerry documents his transition from the Insteon Home Hub to Home Assistant. We have no email but we do discuss some of the week's news in an episode that includes a discussion about Mead, Bourbon, Beer, and Moonshine!  News: Harman Kardon Citation MultiBeam 1100 soundbar boasts Dolby Atmos audio Roku welcomes Apple Music to its lineup Alexa can tell you when your security camera detects a person or package Wyze takes on Ecobee, Nest with new room sensors for its smart thermostat 5 mistakes everyone makes with LG OLED TVs, and how to fix them Thanks to their irresistible combination of futuristic, super-slim designs and consistently outstanding picture quality, LG OLED TVs have become the darlings of the high-end TV world – they're not only among the best OLED TVs, but the best TVs of any kind. The problem is that few TVs are set up to deliver their best possible viewing experience out of the box, so if you haven't picked the right settings, you're not getting the most from your TV. So let's look here at some of the most common set up mistakes LG OLED owners make that may be stopping them from getting the viewing experience they deserve. Full article here… Cheat Sheet for Insteon Replacement with HomeAssistant (2.0)  Like many I was shocked to see my Insteon hub with a permanent red light and my expensive IOT  devices inoperative.   A good number of ex-Insteon users are looking to other implementations of home management system  and I soon discovered that HomeAssistant does work with Insteon Devices. The help pages are well done and explain the procedures well. I am back up and running with HomeAssistant following the  instructions, but it is not simple and here are some of the fine points.  The definitive solution involves either the HomeAssistant server hardware or a Rasberry Pi with the  software installed. You can run the system using Virtual system implement ations such as Microsofts's  Hyper-V or VirtualBox.   I suggest you try Virtual Box before you decide to buy dedicated hardware. I found the Hyper-V  unusable, as I have with other implementations, but the VBox works… though was not stable enough in  my hands for a permanent install.  So with Ara's financing I bought a Raspberry Pi on Amazon with the additional bits and pieces you NEED:  mico-SD card for the system; mini-HDMI connector for a display as well as getting a mouse and  keyboard to attach and of course an ethernet cable. Here are the nice install instructions:  https://www.home-assistant.io/installation/raspberrypi/  The set-up is self generated and you really just follow the questions.   If you did this right, the home screen will appear on any web browser populated by a lot of devices you never thought you had, including the hub..  Each of these will then show up on your home screen which is your interface, as well as on your smart  phone. My goal was to get the cameras that I use in my astronomical observatory to work, which I did https://www.astrobin.com/users/jerryyyyy/  There are many viable “canned” interfaces and contingency programming and the home page is entirely  customizable… I am still learning and a real time sink. The biggest problem is initializing some devices. The hub interface seems worthless as it never showed  all my devices and I basically had to add them back in one by one. I made a spreadsheet with the MAC  address and set fixed IP addresses for many… If you do not know what I am talking about when I  mention MAC addresses or IP addresses, you will be in trouble because you need to mess with your  router and set up “fixed IP addresses” for some devices… also cameras have BOTH Wi-Fi and Ethernet  MAC Addresses… On the other hand, if you know what I am talking about, this is a piece of cake.  My to-do list:  Get the motion sensor up and running (Appears to be impossible).  See if there is a way to pan work the cameras (Maybe learning more Python).  Get the GPS location off my iPhone into the system… yes you can get this through the App.  Find some good models for home pages and automations… there are tons but hard to choose.  The one I have is pretty basic.  Bottom line, all in all this is a viable option if you are familiar with the basics of networking.  Essential Afterthought: How to back-up your installation. I learned that to shut down the Pi you do not  pull the power cord… you go to the Linux shell and “sudo halt” luckily my install came back after that  adventure. You can backup and reinstall the SD card contents using Win32 Disk Imager:  https://sourceforge.net/projects/win32diskimager/  If you put this system together, you do not want to lose it!  

Welcome to the second of a two-part series on the management and tooling ecosystem for Hyper-V, for on-prem and hybrid cloud. In part one, our host Andy Syrewicze and guest Eric Siron discussed the traditional on-prem Hyper-V management tools at length. This included tools such as Hyper-V Manager, PowerShell, and Failover Cluster Manager amongst others. In part two, the guys peer into the modern era and the future of virtualization management in the Microsoft space. For example, Windows Admin Center is Microsoft's next generation Windows Server management tool, but how does it stack up to managing Hyper-V? Where does Azure Arc fit in? Are they ready for prime-time? All these questions and more are covered in the episode! Join the webinar How Azure Stack HCI is forcing changes in your datacenter In this episode on Hyper-V management tools for hybrid cloud: Hyper-V management and Windows Admin Center - 0:52 Where does Windows Admin Center work best? - 8:14 What is Azure Arc? - 12:00 Which Hyper-V Management tool should you use and when? - 14:30 Resources for Hyper-V Management Tools Eric's Windows Admin Center eBook Introduction to Windows Admin Center on the DOJO Learn more about Azure Arc on the DOJO IT Pro resources at the DOJO The DOJO Forums Webinar on Azure Stack HCI

When we sat down to record this episode we ended up in a situation like we did with our episode with Ben Armstrong, too much content for one episode! To those familiar with Hyper-V, this likely doesn't come as a surprise being we're discussing the various management tools that are available for Hyper-V, along with the overall management story for Microsoft's hypervisor. In this episode, we sit down with Eric Siron to discuss modern day usage of the traditional Hyper-V management tools which include: Hyper-V Manager Failover Cluster Manager PowerShell System Center Virtual Machine Manager (SCVMM) In the next episode, we'll focus on the new management tools for Hyper-V such as Windows Admin Center and Azure Arc. In this episode Hyper-V Management vs. VMware Management - 2:05 An example of management assumptions for VMware admins trying Hyper-V - 8:43 Networking woes in Windows Server - 12:12 Why choice of tools is a strength of Hyper-V - 17:12 Thoughts on System Center Virtual Machine Manager - 24:08 An example of where VMM does NOT fit - 28:00 Resources for Hyper-V Management Tools Andy's Hyper-V Datacenter Deployment Script Andy's VMware Datacenter Deployment Script PowerShell Direct Ben Armstrong on Twitter Ben Armstrong as a Guest on the Sysadmin Dojo Podcast talking about Hyper-V Webinar on Azure Stack HCI

At Black Hat USA 2021, two researchers presented how they used their own fuzzer designed for hypervisors to find a critical vulnerability in Microsoft Azure.    Ophir Harpaz and Peleg Hadar join The Hacker Mind to discuss their journey from designing a custom hypervisor fuzzer to identifying a vulnerability within Hyper-V and how their new research tool, hAFL1, can benefit others looking to secure cloud architectures.

This week on the podcast, Dan gives an update on his Hyper-V work with Vagabond and shares a funny log line he found, and Kyle shares some thoughts on making Hiera and eYAML more secure. Show Notes Vagabond and Hyper-V @ 5:30 PIA Servlet Log @ 16:15 Compare Report Failures @ 20:00 eYAML Keys @ 23:00

This week on the podcast, Dan talks about his 8.59 testing experience, testing Hyper-V for PeopleSoft Images, and Kyle and Dan discuss compare reports from the Update Manager. Show Notes GitHub CoPilot @ 4:00 PeopleTools 8.59 Bugs? @ 11:30 Hyper-V and Vagabond @ 17:00 Compare Reports and the PUM @ 24:30 Core 7.50 Compare Release