This is covering the spread part of the Fandall podcast network With week number nine in the books It is now time to take a look at the futures market and dig into week number ten some Buzzy teams across the board are for this week talking some Ravens and they're upside talking Texans if they can make a surprise run towards a playoffs here to break down that with me today is Ryan Williams, he'll break down his thoughts on those Ravens the Texans the futures market in general Then I'll talk about week number ten and where my models show value over at Fandall sportsbook This is covering the spread right here on the Fandall podcast network and Fandall research My name is Jim Sonnis I am a managing editor of digital media for a Fandall research joined here as I am every Tuesday by Ryan Williams Check him out on Twitter at Ryan Alexander underscore W and Ryan We said last night that hey, you know, it's kind of a interesting game for up at the week And it was anything but so hopefully week number ten can bounce back. How you doing today? Yeah, well nice little a lot into the week nine capper for you Jim Having that three and a half there model telling you that six was a favorable number and we needed to go even higher than that Yeah, fool fool's gold right to think of the jets being Being able to to cover the spread at home Public money coming in on them not able to get breeze hall going But you know shout out to the Chargers defense That was the one kind of thing that we that I talked about mostly Yeah, especially with just being able to kind of keep the game close with Wilson on the other side there But the defense showed out. They're absolutely, you know playing and incredibly especially on the road there in a hostile environment Like you got to give them credit where credit to do so we put that in the books close it and We move on to week 10 here. Well, you did get your under And you said the word fool's gold and like how many times Ryan have we said that about the Chargers? So like if you if we were gonna have like it was a fool's gold magic last night So I think no matter what happened last night. It was gonna be that way I just happen to be the jets or the team that were that for the one night like the Chargers will be it again in the very near future, oh Definitely definitely in the favorable matchup as well. Oh, yeah, we know that we know this This is just how the world works. I accept that and it's okay I feel lucky to have gotten away with being behind that that wretched wretched team for once in my life We're gonna break down the futures market here in just one second I want to see if we can get some value in the Ravens to the Super Bowl potentially plus a 50 right now Fandall sportsbook. We'll talk about whether that's a value We'll talk with the Texans I'll plus 250 now to make the playoffs and then other futures Ryan likes Entering week number 10 the first-day reminder to make sure you're subscribed to covering the spread Wherever you get your podcast you can find us on Apple podcast Spotify, etc. If you like what you hear leave us a five start rating on Apple podcast or over on Spotify as well You can also find this show on the fandall YouTube page and fandall TV plus to get fandall TV plus Go to fandall.com slash watch it log in with a fandall account or go to The fandall TV plus app on Amazon fire Apple TV a Roku device You can watch us you can watch covering the spread the heat check NFL shows You can watch the daily ISO with Tom Vecchio. You can watch run it back You can watch up and Adams all in the same place on fandall TV plus a fantastic place to get all of Your fandall needs covered now Ryan Let's start things off here by talking about those Baltimore Ravens who are currently plus 850 to win the Super Bowl this year And they had another huge win over a quality team in week number nine So is plus a 50 appropriate or does that sell the Raven short right now? It it's appropriate. I mean that you're talking about arguably mmm Team like every week like the chiefs are gonna be chiefs are gonna be up there Regardless of how how they're playing games or what what's happening with Kelsey or anything like that? Just you know the way the public perception is in the way that the books align this like we're always gonna see the Chiefs up there so the absolutely rolling, you know, I even think sand Fran And you know six to one there that seems seems to be a little light like I don't I don't know that they are You know a tenth behind the Eagles there just yet with the way the Eagles competition We're gonna see with the Eagles coming out of there by If they're for real, but yeah 850 It's going to feel Like a wrong number. I feel like to the public because it's just Baltimore like they've kind of Disappointed over the past couple seasons. We talked about the injury history here, but I mean the way the defense is playing It's it's it's nice And if you had them, you know at 12 at 12 to 1 or or higher as we had kind of been talking about the AFC north in the summer And leading into the year like this was one of my favorite divisions Just because of the Bengals and the and the Ravens and then potentially What was going to happen with the Browns and even the Steelers like having a winning record under Tomlin Like this has been a division that has really outside of the Steelers I should maybe the Browns but the Browns defense. I feel like has kept them in the This has been a division that's been fun to watch and it it seems right. I will say I have seen some plus Plus 900 odds on the Ravens in some other spots as well too. Like that that feels like a good number I mean, I think that we when you're talking about the Ravens gym outside of them winning the Super Bowl Like you need to start looking at, you know, although the number is outside of like win totals and playoffs But like, you know, getting getting those futures on Lamar and and things of that nature to win MVP Like this team really controls the on destiny here and you want to make sure that you Take advantage of other of other opportunities in the market just with the Super Bowl It's being under 10 to 1 We got to tell Lamar that he's in the MVP race. He stops giving it to Gus Edwards in the goal line From a DFS perspective. I need that. So Lamar win yourself your second MVP. Stop giving it to Gus. Please save me Please help me here. Now you mentioned the 49ers being potentially been undervalued. I I agree I look at I have a model that runs with no priors And this is not a model I use to bet because you should have priors still at this point in the year but When I look at that one looking at just 2023 data, the top right team in the NFL is the 49ers and number two is the Ravens So both these teams look pretty good relative to where the betting markets have them right now So I find that pretty intriguing personally and that's even with San Francisco's defense like not performing up to snuff as of late They've been underwhelming I would say get a pretty tough test against the Jags coming up here this week so I wouldn't be shocked if that six to one number does look a bit light in retrospect on the 49ers Given they should get debuff Samuel back out of the break. They should get Trent Williams back out there by as well Brock Purdy played poorly But like we also saw a very long stretch of him playing well And again with those guys being healthier the odds he can remain afloat. I do think go up So to me Ryan, I agree that you think the 49ers might be the more intriguing way to bet the Super Bowl right now They're NFC odds plus 270. I think I'd rather go Super Bowl personally at six to one They the NFC a plus 270 But I do think overall your point about them being a bit undervalued is something I'd agree with as well Yeah, and I mean I don't I don't want to bury the lead here, but I mean one of my favorite bets At this point in time right now in the season is around the 49ers as they're coming off of their buy and coming off of three losses So I guess I'll I guess I'll save that for a later as I know you'll be asking me about that So I'll bury the lead bury the lead. I love that little tease let's talk first about the Houston Texans because we saw CJ Stroud go nuts and This is not a huge surprise Ryan. He's been very good this entire year and We talked a bit about the Texans as I like though as a bit as a dark horse to win the ASC south I think that's probably not going to happen because the Jags are playing really good football right now So that that hope is probably gone But they're right in the thick of the ASC playoff rates They're currently plus 250 to make the playoffs of fan will sports book They were plus 260 yesterday So it seems like there's a tiny bit of interest in the Texans right now Any interest for you there in the Texans a plus 250 Ryan or Is it more so just excitement for the future around this team? Yeah, you know, we I always like to look at these odds Jim just especially with the new format where we're getting You know that at that extra team that's in there in the Houston Texans Jim. I mean CJ Stroud like You know carolina's might be kicking themselves To come this they're just so fun and you know, it's so fun to root for rookie quarterbacks So fun to root for rookie quarterbacks who are able to come in and just Make claim, you know to it right away like Joe Burrow was able to do that We've seen that with some other Patrick Mahomes when he first started So, you know, CJ Stroud he goes as this team goes and you know, they do play in a favorable division Was still some great matchups on paper To be able to kind of stake their claim there and and sneak into the playoffs I think that's a fair number of just under three to one Especially if they're going to continue rolling now the the thing about it Jim is that they're going to have to continue rolling They're going to get the Bengals this week, which is on the road. That's not going to be great So there might might be another loss, but then you get a home game against Arizona Jacksonville You know, it's at home at least and we know that Jacksonville can play that Drucklein hide game Denver the Jets Tennessee Cleveland Tennessee and indy to finish out the year Like these are going to be games that they're going to be in and when you're talking about the way that the offense Is playing here, you know, they can keep up with Cincinnati. They can keep up with Jacksonville I think they're they're going to be in position to be able to be in these games not necessarily get blown out So yeah, I'm with you here. Absolutely love getting action on this number. Yeah, you mentioned the schedule I think that's pertinent here. I think that that if you like the Texans It might be a good time to wait and bet them after this Bengals game So I do think that'll probably be a loss. I'm looking at like I've bet The Texans money line every single week this year. This would be the first week I do not because I actually do not show value in them the market need to move a lot Actually just kidding. I do show value on their money line. Okay. Well, I lied So I do show value in the Texans money line. I've got the spread at 5.55. So that's probably I think that's a bit aggressive or I'll just where it should be given how all the Bengals have played recently So I think I'd rather wait kind of like you were saying, you know, take advantage of the schedule The fact they're playing Arizona with Kyler though next week, which is kind of fun, but Maybe hold off until next week Get them there take advantage before they get into the softer portion of that schedule Right if I remember other model has this game Houston, yeah, it's five point or six point. Oh, so like both are a bit under six and a half So maybe some value there, but I think I'd wait You let the Bengals beat them because the Bengals will probably look pretty good It's not going to ruin my enthusiasm around the Texans So get them before that Arizona game take advantage of the undulations of the schedule Like you said, the Jag team is at home. They beat them once already so far this year I think they are a team to monitor and a team to potentially invest in but maybe wait until after week number 10 to do so Now let's open things up Ryan. Talk about other teams that grabbed your attention in week nine Outside of the Ravens and Texans which teams got the biggest bump up or bump down for you based on what they did in week number nine Well bump up is it's the Cincinnati Bengals and how long had we've been talking about this, Jim? You know uncovering the spread, you know the one thing if people if fans and you know constituents have been listening to this podcast It's been banging the drum for the Cincinnati Bengals Since the joe borough injury like we kind of talked to sensor fruition Like there could be a time when the Bengals are just kind of firing on all cylinders and you're going to be looking at odds and thinking Wow, how did I get action on them any earlier like and that that is all gone now like when you're Where is it here our seasonal awards futures on the market like joe borough now nine to one like this guy was 30 In higher odds to win MVP like not just two three weeks ago Um, so that's gone. You know the Bengals even the win the division Which doesn't even feel that favorable now the way that the ravens are rolling But you know three just over three to one there They they are just you know Lou Amaro Lou Amaruno. I'm gonna get his name right but the defense coordinator For the Bengals he's got this team real and joey b I mean You know we bet on we bet on talent. We bet on quarterbacks like That's just every time for me and you know joey b as long as he was healthy And those were what the reports were saying and they kept putting them out there Now they're on a four game winning streak and I think they're they're riding high so absolutely love the Bengals Uh, we have a couple futures on them that i'm excited. Uh to see how those play out later. Um, you know, I think The other team, um, that's just been we've talked about them Oh, you're too is the Buffalo bills and I just don't know what to do With the squad. I mean they have all the pieces there. They have the talent on paper to be able to Still feel like they can put this together. Um, and when we're talking about, you know, their upcoming schedule Before they head into the buy, I think they set themselves up for some success here I mean to make the playoffs they're minus 128 like You're not even looking at that like I think the bills are making the playoffs So I don't think there's any value there, but it's the season futures like outside it I'm not going to take josh allen for mvp the lab bills Futures to win the super bowl like and put themselves in the chance to succeed to win the afc like yeah I want to get some action on that we get denver, uh, and the jets both at home They're gonna have a road match up in philly leading into the buy like Can they keep up? A three game win streak going into the buy and bring back on the the bills bandwagon If other teams start to falter here in the three weeks, so I still want to get action on the buffalo bills I still think that they're favorable in the futures market I mean this offense has still been so good for the bills like the I know the defense has been bad and That's that matters for sure And it's gonna keep being bad because they've lost so many key pieces on the defense So that part is going to stick But josh allen even with the shoulder injury is still playing very good football And I'm with urine. I want to invest in the bills I'm going to invest in the bills in week number 10 specifically, which we'll talk about Later on against the denver broncos. So I agree with you. Um, they're not dead yet And until they are this is the kind of team that can make a playoff run If they make it because of how good josh allen could be in a single game setting stuff like that So bills definitely not dead yet the bangles 14 to 1s win super bowl bills are 15 to 1 I probably lean bangles over bills in in the in that in that market personally, but I agree the both these teams still have the upside to get the job done Even if they don't want to having the best playoff positioning now ryan, which are the futures? Are you targeting entering week number 10? Yeah, uh, I want to talk about some fun ones here We're going into the passing props market and I was going to talk about, you know The the carolina panther's kind of reeling and maybe having a you know There's a second favorite odds on the fandom sportsbook to have the worst record. I think that's pretty viable I am curious to see how arizona handles the kyler situation because I think that could kind of put some spark plugs into Into the arizona, but that defense is so bad. So it's just one that money But brice young um to lead in interceptions. He's nine to one right now Um, and I just I don't know that they'll bench him like I don't know I think frank right it's kind of prideful and I think they'll kind of just let him run and you know, I don't think that he's You know Fortics better or fortics work. However, that Which takes out the mac jones. He's five to one, you know and mac jones I do like we've seen the bailey zappy story, right? Like we've seen them been able to pull it and you know, there's bella check Um, there's just too much uncertainty there for me to go with mac jones like josh allen I think he's going to get an upswing here Actually heading into the buy with some favorable matchups. So, uh, I do like brice young there I think even jordan love is kind of interesting the way that he's Been playing and turned the ball over. I think almost in every game This season. So, uh, that's that's a market that i'm looking at For sure when I talked about the 49ers earlier Jim which I actually clicked on the wrong thing as I was going through it But if we look at their win totals the number there 11 and a half like this is It's plus money. This is something that i'm just going to be hammering now. They have seven games Left in the season. Um, they Are coming off of their buy like I said, they've just lost three games in a row But after the buy this is actually where the 49ers have shined under kyle shanahan So if we just look at, uh, the tenure there for kyle Kyle shanahan Before the buy um, their record the record is actually 16 and 30 30, but after the buy 36 and 16 I mean something about this team just after the buy that they are able to You know get things going on the right path and they just have you know, they're bringing chase young like We know what the christian mccaffrey story is debo. Samuel is going to come back healthy And their division kind of lends itself for them to be able to have some favorable matches So i'm i'm i'm really on this team to be able to you know, pull this off and pull some magic off to get to that 12 number at plus 120 Yeah, looking ahead here for the 49ers Currently as you said they're coming out of their buy The record for them so far is five and three So in order to get to 12 wins they need to win seven games and they have got nine games remains It's seven and two. That's right. Yep. I said yes But nine games left needs seven wins Yes, seven and two and you look at their schedule I think like the one they've got games against philadelphia and um, baltimore both those games are uh, the the baltimore game is at home Philly is on the road. I think they can hang with philadelphia for sure You know, it's already match of the ns2 championship game last year, but rock party. Hopefully healthy this time around I think they can make that kind of run I did uh, lay the three with the 49ers against the jags on sunday So I do like them in week number uh week number 10 as well. So I think that's not a bad number. It's plus 120 to get over 11 and a half So the the sports book is accounting for the fact their schedule is pretty tough So it's not as if you're catching them off guard here So I don't think that's too bad ryan like you said three straight losses But they are again based on my 2023 only numbers the best team in football. So I don't think that's totally out of bounds either No, it's it's one that I I just thought was so interesting I'm always going back into the win totals market just to see adjustments there And absolutely love being able to get in on that number Okay, so the 49ers over 11 and a half wins plus 120 ryan is liking that one Right now over at faddle that is what we have for ryan for today Ryan back with us next week on monday and tuesday check out ryan on twitter at ryan alexander underscore w ryan a pleasure to have You on for today as always. Good luck to you your bets across upcoming weekend and we'll talk to you again on monday Yeah, can't wait jim. Good luck to everybody Alrighty again fine ryan on twitter at ryan alexander underscore w back with us once again Next week on monday to preview the bills and the broncos a team We just discussed we'll dig into that game and more Outline where my model is showing value across week number 10 in just one second at first score early this nfl season with faddle america's number one sportsbook right now new customers get 150 dollars in bonus bets any winning five dollar money line bet That's 150 bucks if your team wins if you've been thinking about joining faddle There is no better time to get in on the action the app is so easy to use There is a wide range of betting options including spreads player props totals and more So visit faddle and kick off the nfl season faddle official partner of the nfl must be 21 plus and president select states Faddle is offering online sports waging in kansas under an agreement with kansas star casino llc first online real money wager only Five dollar pregame money line wage required 10 dollar first deposit required Bonus issued as non-littrable bonus bets that expire seven days after receipt C terms at sportsbook.faddle.com gambling problem call 1 800 gambler or visit faddle.com slash rg in colorado iowa michigan New jersey ohio pennsylvania illinois kentucky tennessee and virginia call 1 800 next step or text next step to 5 3 3 4 2 in arizona 1 888 79 7 7 7 7 over the ccpg.org slash chack netiquette 1 809 with it in indiana 1 805 224 700 visit ks gambling health.com in kansas 1 877 770 stop in louisiana visit md gambling health at organ maryland's 1 800 gambler.net in west virginia 1 805 224 700 in wyoming hope is here for the gambling help line ma.org or call 803 27 50 50 for 24 7 support in massachusetts or call 1 877 8 hope and why or text hope and why in new york Let's dig in now to the week 10 lines over at fan dual sportsbook and Outline where my model is showing value for this week Let's actually start things off with the final game of the week That is the broncos and the bills and right now The bills are seven and a half point favorites of fan dual sportsbook minus 105 on that side and i do show value in the Bills there there now with this number being a seven and a half I think the bills could be a good teaser leg for this week. I think the only partner I saw for them Based on numbers yesterday was the raiders. They were plus two and a half against the jets That is not up again yet with the jets having played last night I would bet that number changes a bit based on how poorly the jets played But if it's two and a half or one and a half on the raiders side plus Plus one and a half or plus two and a half I could see teasing the bills down to one and a half and teasing the raiders to get across Both three and seven with them So based on right now don't have any other teasers to pair them with but I do like the bills straight up And that's part of why I'd be willing to put them in a teaser The reason for liking them is that I think there's good value in seven and a half I've got this number in the double digits as the bills take on the broncos so Enough of a discount to justify Not getting a win if this game lands on seven the bills Have definitely had issues of late, but they still ranked second in my models offensive power rankings this year The defense has been Legitimately bad they rank 27th there, but denver is still dead last in defense despite some recent improvements so Still pretty bad there josh allen's shoulder injury definitely concerning, but even with that the bills have maintained Really good levels of late down success They're converting on third and fourth down at a high rate and the early down numbers are still respectable With the broncos coming off a buy with the bills having some stink on them right now I understand why this number is where it is But I think it's an overreaction. So i'm on the bills here I think uh, they are again a good option for a teaser if you like another team getting across three and seven But regardless, I think that they are A quality straight that as well minus seven and a half is minus 105 at fan dual sportsbook on now Other side I like for this week is going to be in the uh, the germany game It is the the colts taking on the patriots where right now Patriots are one and a half point favorites total in this game is 43 and a half I do like the under here a bit But i'm gonna go with the colts minus one and a half which is minus 110 at fan dual sports We have seen some movements toward the patriots here from where things were yesterday So it's possible you can get a better number on this one later and the colts have also A lot of times this year had the market move against them as week has gone along with the openers have been More optimistic on them than where the numbers have closed. So maybe hold off on betting this one But where it stands right now, I do show value looking at gardener minchew This year he's at 0.01 passing net expected points per drop back. NEP is number fires epa metric And 0.01 is not great. The gavage tends to be around 0.1 So it's below average, but it is a quite a Bit better than mac jones mark of negative point one two and That number is Unadjusted for opponent, but the colts have actually faced a pretty decent level of competition on defense thus far And they've also maintained their early down rushing efficiency even with no anthony richardson Jonathan taylorgan ramped up has helped their zack moss playing well has helped too So they're still running the ball effectively despite not having anthony richardson out there the patriots You know, they they lost this past week to the commanders. I think they played better than what their result was so that is a bit A bit misleading I would say how things played out for them in week nine But there's still just 28th in my models offensive power rankings and that is not accounting for the kendrick borne loss because that's just a straight power ranking before injury adjustments are made so Downgrading them even from there. I again think the under is in play um, if you were to tie those together the colts Minus one and a half with the under at 43 and a half it'd be plus 239 if annual sports book I don't mind that by any means Prefer to go straight with the colts at minus one and a half But do you think there is a potential value if you want to go with the same game parlay there with the colts Minus one and a half and the under at 43 and a half don't mind that but I will go With the colts minus one and a half personally So the two sides I like this week are the bills minus seven and a half and minus 105 and the colts minus one and a half at minus 110 a couple totals stand out to me for this week first one is between the seahawks and the commanders and That total is 45 and a half and I took the under on the commanders last week And I'm going to do it once again here in this matchup with Seattle And obviously the commanders are a pretty over conducive team because they just traded away montez sweat and chase young So lost a couple of key defensive players and they throw at a very high rate throwing keeps the You know stops the clock when you don't gain yards most of the time and that's a good thing for overs So I understand why this number is here But The seattle defense has played pretty well so far outside of the baltimore game Pace in this game is still middling despite the commander's high pass rate And that's the number that would be influenced most by that And they take a lot of sacks sacks kill drive sacks lose points now Sam howl to his credit has done a lot better that the past two weeks. So maybe this is a trend where howl Realizes that he can't take sacks as already has been improves in that metric and suddenly Makes his commander's offense more efficient But again, it's a tough match up here with seattle. They're on the road The offense for seattle doesn't tend to let it rip unless they're pushed by the opposing side so I do think that like It's within the range of outcomes for this game to be very high scoring Like if you told me this was a 30 to 27 game, I wouldn't bad not that's very much in the range of outcomes But when we're betting on things like this, we're betting on medians I think the median outcome is under 45 and a half my model has this one at 41 So actually a good amount below Where the market currently has that there is some rain in the forecast currently I don't care a ton about rain personally but I do have the wind speeds for this game at seven miles per hour So not zero there either and that is influencing the model a bit too. So under 45 and a half Is minus 105 minus one fifth or minus 110 at vandal sportsbook right now I do think there's value in that. I understand why this number is where it is But do you think we should take the under given The rain given the winds given all those factors combined and given how well the seattle defense has played I do think the under is the way to go here Final spot where i'm seeing value for this week is another total that is between the titans and the buccaneers Over 38 and a half is minus 105 right now at vandal sportsbook and I do feel pretty good about this number It's a match of two teams that are very good against the run the titans haven't been as good recently But had some injured up front those guys are now getting healthy. So I'd expect their run defense to bounce back and the buccaneers have been Among the best rush defense teams in football for a very very long time getting healthy up front once again as well So it's two teams that encourage you to throw the ball against them on early downs And again throwing is good for overs despite the fact we want the under on that seattle washington game So I think we should see a decent amount of play volume in this game. It's not the fastest pace game It's actually one of the slower ones for this week But wind speeds here eight miles per hour not great But also not terrible two offenses that can move the ball well enough Will levis has had similar efficiency numbers to ryan tana hill Their pass rate is pretty similar. So honestly i'm keeping them fairly similar to what they were before the tana hill injury Just because that's what we've seen thus far out of levis and the way they've operated For this team and also levis chucks it deep and chucking it deep isn't like a Thing that where you automatically get efficient offense, but it's more likely to keep that clock paused Due to incompletions it can get you chunky it's the gauge turnovers all those things are good for overs As to the pucks they can't run the football like they're very bad against them I don't very bad it and I don't think that's going to change in this matchup here with tennessee So basically what i'm seeing here is we should see a matchup where we see a decent amount of passing volume neither past defense is good And the weather is not bad the pace is not bad enough to cancel this out I've got this one at 41.6 It's where my model my model has this total total right now at vandal sports, but again It's 38 and a half over is minus 105. These two teams have been very under friendly so far this year but I think that's accounted for in the market right now So we'll take the bucks and the titans over 38 and a half minus 105 at vandal sports But yeah the uh bets i'm liking for this week That one plus the commander seahawks under 45 and a half and minus 110 The colts minus one and a half at minus 110 and the bills minus seven and a half at minus 105 and if you can get A teaser chance there likely with the raiders depending on where they reopen against the jets If they reopen it plus one and a half or plus two and a half Could potentially throw the raiders in there as a teaser with the bills as well That's what we got here as far as the first look for week number 10 before we close off shop for today We do got to go back through recommendations From last week here on the show Let's start things off with the breeder's cup. We had dubs anderson on to preview the breeder's cup You can find dubs on twitter at mr. Dubsey find him on fendall tv and tvg as well in the breeder's cup cup classic dubs liked ushba tesoro at four to one in the saudi crown at 12 to one white abir abirio wound up winning that race so No catch there on ushba tesoro or saudi crown and then the other one that dubs liked was caraville five to one in the Turf sprint nobles won that one so didn't get the wins on those but it was good talking to dubs Hopefully getting back here on the show Once the horse races season picks back up as we get to the spring our guests in the college football The nfl side of things was dr. Ed fang as well always you can find him on twitter at the power rank Check him out at the power rank com as well ed's college football benefit this week was kansas state plus four and a half against texas And ed has been on fire throughout this entire college football season Got another win with another win here Kansas state did not win outright but did cover the four and a half as they lost that game 33 to 30 in overtime so a win for ed on the college football side of things In the nfl ed liked the bills money line against the bangles as did i and obviously the bills lost again 24 to 18 so Hoping for a bounce back on the bills this week as they take on the broncos And ed again really good in the college's football side of things Check him out on twitter at the power rank and the power rank com ed is back with the smore college football tomorrow here on the show JJ zackereason was our player prop guests on friday and jay j Five for five in this one find jay j on twitter at late round qb Check him out at late round dot com in the late round a fantasy football podcast the the wins for jay j He had patrick mahomes over 25 and a half rushing yards against the dolphins minus 114 He had tea higgins over 48 and a half receiving yards pretty sure he doubled that number. I think he had like 110 So easy win there He had dalton kinkade over 34 and a half receiving yards. That was well over as well. He I think he was around 81 so Didn't just hit he hit in a big way. We did talk about tea higgins alternate markets as well Potentially getting more upside there which would have paid off you had decided to go With that route two both the touchdown bets for jay j hit within the span of like 30 seconds The first one was chris olave two to one for the sains taking on the bears He finally scored has been a decades since chris olave scored But of course jay j was on him when he did and he also had k. Dotten plus 490 For the buck in years against texans and how otten scored not just once but twice so jay j Had tea higgins double up his yardage number He had dalton kinkade double up his yardage number and had k. Dotten scored twice in addition to the olave one At two to one and then the homes hit so not just five for five but five for five In emphatic fashion awesome week for jay j Check him out on twitter at late round qb finance work at late round dot com and on the late round fantasy football podcast We have ryan williams on last night to talk about monday night football flying ryan on twitter at ryan alexander underscore w Rough night here just because it was such a weird night where the guys we expect to be involved didn't get the job done And austin eckler dropped a bunch of passes that that did impact things quite a bit ryan though did like the jets chargers under 39 and a half which hits Is that total finish at 33 points had the jets plus three and a half which did not hit The props here brice brice hall over 21 and a half receiving yards He had a longer reception that called back via via penalty I thought that was kind of a ticky tech call on the zard But regardless that's accounted for you know we had to account for that stuff always embedding So missed on a brice hall over 21 and a half receiving yards Did hit garret wilson over 68 and a half receiving yards. He had 80 in that game So good hit there The eckler ones were over for 84 and a half rushing plus receiving yards over 33 and a half receiving yards and over four and a half receptions at minus 106 and eckler I I think one of the drops is more on herbert because he kind of under threw him when he was wide open So like it wasn't all eckler's fault, but didn't wind up hitting on any of those Also had eckler plus 380 for the first chargers reception that went to Was it jerald ever got that one? So No eckler there either Had donald parham plus 430 for any time touchdown didn't get that one and herbert throw picket plus 104 Which missed as well, you know, he was really bad in this game. So rough game overall That one for the chargers and the jets will try to bounce back With the bills and broncos on Monday night That's upcoming week and find ryan on twitter at ryan alexander underscore w As for my stuff and the NFL side of things went two and two for this week One of the losses was the bills. I got them at plus 136 in the money line They closed it plus 110 and obviously didn't get the job done So it's been frustrating in that regard getting good closing line value throughout this year not good results That was annoying Got good clv on the chargers at minus three They closed the three and a half and of course did win pretty handily last night I had the patriots and commanders under 40 and a half That one looked toast in the third quarter as I think it was at like 34 or so pretty early on in the third quarter But finished at 37 patriots couldn't get that final drive going Mack jones throw pick off jujus mistrooster's hands. So, you know It a win is a win We'll definitely take that with the under for the patriots and commanders other total was the raiders giants over 37 and a half And the raiders did their half they scored 30 But Daniel joins going down with a a torn acl Unfortunately couldn't get the over at 37 and a half and injuries happen They've happened a lot to me recently because I had three bets where the quarterback got hurt in week number eight One here again. So could have been a better week But you know two and two could have been worse too With that patriots and commanders total so can't complain But frustrating not to get that raiders and giants game despite being on the raiders offense in a game where they did play very well Counter-amp up the nascar cup series as well final race of the year Ryan Blaney wins the championship talked about that in the show was digging if you get him a plus 280 or longer So hopefully you were able to find blaney a plus 280. I was earlier on the week Not sure if that was still around later on once we spoke, but blaney had the best car He deserved to win the championship glad he did Fun to listen to his motion on the radio after he won that race So happy for ryan blaney happy he won that race and happy to have won the blaney championship bet As far as recommendations here on the show iakrister bell doing group one He was four to one and bell. I thought had a good car didn't qualify well but was running with blaney honestly early on that race and They were picking the way through the pack. I thought they had better cars than Byron and larson so i'm not sure what bell would have done But he crashed blew a tire or something broke on the car hit the wall So he did not win that one, but I feel pretty good about the process there Given the number was four to one. I did like that. He's very fast in practice on friday as well Top 10 bets were chase elliot at plus 150 and alex bowman at plus 450 and hendrich Just was not on with those two the entire second half of the year So i'm curious what those two guys will do early on in 2024 my model will probably be pretty low on them We're all just a market, but like they're good drivers. It's a very good team You know kind of curious what they will do, but uh I showed value on them a lot toward down the stretch this year and never really got the job done So i'm curious what things will look like for them next year, but Overall profitable season for me and nascar excited about that excited to Make some tweaks make some improvements as always the model for next year and see where we're at once 2024 rolls around the day 2500 will be here before you know it That is all that we have here for today on covering the spread one final big Thank you to our guest ryan williams check him out on twitter at ryan alexander underscore w I am on twitter at jim saunas j i m s a n n e s You can also follow me on threads at jim dot saunas and find fando research on twitter at fando research tomorrow Dr Ed feng will be with us tucks and college football in week number 11 should be a fun one as always Make sure you're subscribed to covering the spread wherever you get your podcast or on the family youtube page and fandall tv Plus to get that show as it goes live Want to thank you all for tuning in for today as always we'll talk to you once again wednesday This has been covering the spread right here on the fan dual podcast network


Hello, this is Chuck McDowell, President and CEO of Wesley Financial Group here in Nashville, Tennessee. Look forward to seeing each and every one of you at the 8% Nation Insurance Wealth Conference here at Nissan Stadium, home of the Tennessee Titans. Normally when you go to a conference like this, you go home and you've got a lot of information, actually too much information. I'm going to give you one thing and one thing only that will change your life. See you then.


That was just a test. OK. So if you come back the same time tomorrow, you get that one. All right, let's try that again. So today, I'm doing the Libvert KVM driver update. So what that's going to entail. So primarily, we're going to focus on the kilo features, obviously. I'm going to do a little bit of an architecture refresher. So a refresh of how the driver fits into OpenStack, how the driver works, and also how Libvert and KVM work as well. After that, I'll dive into some kilo features, primarily around the performance tuning enhancements for virtual machine guests we've done in this release, and also some Liberty predictions slash speculations. So obviously, alongside the general summit this week, we have the design summit, which is the primary forum in which we define the agenda for the next release. So none of these things are really confirmed, obviously. So obviously, Compute is one of the original OpenStack projects. It forms the basis of the infrastructure of the service offering along with storage and networking. I personally would argue that some of the other services we offer, things like salamander for monitoring, heat for orchestration are really infrastructure of the service plus, which in turn are based on these components. So like most OpenStack projects, Compute has a number of back ends. So not just Libvert back ends, but also things like vCenter, Hyper-V, and so on. In this particular case, we're talking about the Libvert driver, and specifically Libvert KVM. Libvert itself actually supports a number of virtualization technologies. So the Libvert driver itself also supports a number of virtualization technologies through the same piece of code. So alongside KVM, we have support for things like parallels, LXC containers, Zen, and so on. So Nova itself is, I say, relatively technology agnostic. So in terms of we're dealing with virtual machines, bare metal, even containers. But the API, just because of the way it was envisaged originally around virtual machines, is a little bit virtual machine specific. So there are some things that are very specific to virtual machines that don't necessarily apply to, for example, containers. When we look at the support matrix, and I'll talk a lot more about this in the talk tomorrow, the broader compute talk, but there's a list of things that a compute driver must support, and then there's a list of things that are optional. So what I'm referring to there, again, is that there are actions that a compute driver doesn't necessarily have to support, because they may not make sense for the underlying technology. So this particular slide, if we break it down at a high level, we have the Nova API. We have an RPC message bus for communication between the services. We have the conductor for interacting with the database, which means we don't need to have the database creds on every single compute node in the environment. And the scheduler responsible for placing instances. So primarily today, we're going to be focusing on that box to the right, the compute node itself. So that is where our instance is run. In the Libert KVM driver case, the Nova compute service that initiates the build of the instance is co-located on the same machine as the hypervisor, or as the QMU and KVM processors. In some of the other drivers, like the vCenter driver, that's not necessarily the case. So Nova compute may run in another ESX-IVM, or another hardware, and so on, and talk to vCenter separately. So Libert KVM, based on the latest survey results that came out this week, it's used in 85% of production over stack deployments. That is slightly down from the 87% last time we did the survey, so that's primarily if you look at the results based on uptick in the usage of ironic for bare metal management and also some of the container related drivers. So Libert itself, and in fact the entire Libert QMU KVM stack, provides a free and open source hypervisor effectively. So Libert is itself an abstraction layer providing an API to talk to hypervisors and manage virtual life machine life cycles. Supports many hypervisors and architectures, so primarily today, I'm kind of implicitly talking about Libert KVM slash X86, which I'm most familiar with, but we also have things like, in KiloCycle, for example, support for KVM on S390 was landed in the Nova driver as well. There's plenty of other architectures supported too. QMU is effectively the Swiss Army knife of virtualization, so it's a machine emulator. It's able to use dynamic translation, so basically run a virtual machine guest without any hardware assistance at all, but that's quite slow. So we primarily use KVM, the kernel based virtual machine, to provide hypervisor assistance or hardware acceleration to those guests. So I mentioned Libert being an abstraction layer. You might think, why are we using Libert instead of speaking straight to QMU? Who isn't Nova, my abstraction layer? So when we look at this tiny, tiny print, so this entire command is just the QMU KVM command line for booting a guest in OpenStack without any customization whatsoever. So this is the out of the box what you get. And that, as an API, doesn't work so great to talk to. And in the Libert project, there's a lot of experience in dealing with that. So it's been around for about 10 years, and a lot of stuff has been built into it. So in that previous command, when we look at what is all this configuration that we're getting in the default, it's configuring the CPUs, the NIC presentation to the guest, the disks, the bus type for those disks where they're IDE, Virtio, iSCSI even. PCI device pass-through potentially, or even without it when we're not using PCI device pass-through in the default case, we still have to expose things like even a virtual machine needs a virtual keyboard, for example, so we can talk to it. Consoles, the clock parameters, and so on. The Libert project also, and its ecosystem, also provides a number of tools that are very useful for working with these virtual machines. So Verge, a CLI for interacting with Libert. Primarily in an OpenStack environment, you won't use this to modify the guest, because Nova will just clobber those modifications. But it's useful for getting out the XML so you can see exactly what was created when you're troubleshooting, for example. Vert Rescue, for running a rescue shell on a virtual machine. So if on a Saturday when you're preparing for a presentation, you kind of kill your guest in some unfixable way, you can get in there and sort that out. Vert Sys Prep for creating templates, Vert V2V for converting from other environments, Vert Spotify for converting to thin provision. These are all useful tools that have existed for some time, and you can use with OpenStack images intended for use with Libert KBM. So I mentioned on my Nova architectural diagram that we be focusing on the box to the right. So kind of minimizing control plane here and zooming in on that. So on our hypervisor or our compute node, we have the Nova compute service or agent, which is responsible for communicating with Libert. It does that using Libert's exposed APIs. Libert, in turn, launches a QMU process for each guest. I'm being a little bit liberal here because sometimes when you're doing activities like snapshotting or migration or other things, there can be additional QMU processes related to that guest that are involved in doing that. But primarily I would think about it as there's a QMU instance at least for each guest. And then those QMU instances in user space are responsible for talking to KVM in the kernel to execute commands on the actual hardware as needed. We also have around kind of the fringes of the driver or useful tools. There are Vert.io drivers for providing para-virtualized device access to virtual machines. This provides a speed improvement. For example, the vast majority of users would primarily use Vert.io net instead of the default emulated device and similarly Vert.io block instead of IDE for performance reasons. So those drivers are included in the vast majority of Linux-based operating systems, if not all. They're also available for Windows users as well. QMU guest agent optionally runs inside guests, facilitates interaction either by users or management platforms so that they can run something inside the guest effectively. We'll talk a little bit actually in the killer features about an example of how that's used. But just from a basic point of view, it just provides an API for doing things that you need to get into the guest to do. So extracting the IP address, for example, or something like that, or even initiating snapshots. Venom, kind of topical. So people who saw the security advisory last week around QMU as using both KVM and Zen environments, for that matter, with the Venom vulnerability, there was mitigation of that by using S-Virt. So S-Virt is a framework for effectively defining a policy for what the QMU process is allowed to see. And if it tries to access something that isn't on that list, then it gets denied. Because it's named S-Virt, because it was originally a Red Hat project, I think people sometimes assume that this is tied in with SE Linux in a way that you can only use it on rel or Fedora. It is actually, and always was, designed with the idea of multiple security backends in mind. So it is actually something that works with App Armor as well. So most of the time, your distribution should enable this by default. If you're disabling it for some reason, probably don't do that. The VIF drivers, so this is getting more into the Nova specific side of things when we talk about the driver architecture. So there is a concept of a virtual interface driver, which defines how we plug and unplug NIC devices from the guest. What that means in practical terms is that a different interface type in LibVirt has a slightly different XML incantation to attach it. You don't need to think about this too much from a user point of view usually these days, because there's a LibVirt generic VIF driver responsible for plugging all of the most common device types. It is not plug-able easily by out-of-tree implementations anymore, which is a bit of a sticking point, but there's something that's being looked at for LibVirt that might ease some of the pain around that without making it fully plug-able. So just by way of example, when we're looking at the difference between a pass-through device and a V host user device as generated by the VIF driver or the VIF.py file, so we can see that the interface type is different, direct versus V host user. They're both using the same MAC address. In this case, the model type is vertio in both cases, but the source device is different. So in the first example, we're using the physical eth0. In the second example, we're actually using a Unix socket. Volume drivers are conceptually similar, except there's no generic driver. So there is a very, very long list of them. In this particular example, I'll just put in a few. The same idea basically applies. It's telling LibVirt what it needs to put in the XML so that you can attach that type of volume. Moving into the kilo features section, and I mentioned primarily, I'll be focusing on performance features. So some of this stuff actually started off in Juno. So some things you'll see on the list. Numera were scheduling, for example. I think, wasn't that in Juno? Well, yes. But I would position the kilo versions as the first usable baseline, where you can combine all these things together and have them play relatively nice. So we have the ability to pin virtual CPU cores to physical CPU cores, albeit implicitly. And I'll talk about that a little bit in a moment. The ability to back guess memory with huge pages. Numera were scheduling both the extension to cover memory binding, IO device locality awareness, and to be honest, just general cleanup of a number of bugs in that area. So when we talk about CPU pinning, so there's in Juno, there's a pneumatopology filter added to the scheduler to have the ability to take into account the pneumatopology the host was scheduling. This kind of needs to be done in two places, actually. So we need to be aware of the pneumatopology of the hosts when scheduling and what cores and which nodes they're in are available. But also on the agent, we need to have that same information to then build the guest in the correct way on the other side. So the pneumatopology filter was extended to add the concept of a dedicated resource guest. So unlike, perhaps, a typical virtualization environment, say, like VMware or Red Hat Enterprise virtualization, we don't explicitly, from a user perspective, say, this is the exact CPU core I want, pin my VCPU to that because we're not supposed to have awareness in a cloud environment of exactly how the hardware looks from that point of view. So to simplify and abstract that out a little bit, the concept is applied in a way that you say in your guest request that I want this guest to have dedicated resources. Then the scheduler and the compute agent are responsible for finding available cores to pin that guest to effectively. You are trading off when you do this, the ability to overcommit memory and CPU. So the pneumatopology filter and the agent code do that implicitly for you, but you need to be aware of that. So there's a performance tradeoff to be made in the fact that you're getting dedicated cores, dedicated memory, but as a result, your consolidation ratios aren't as good. And just mentioning at the end there, and I'll go through this in an example actually, you also need to combine these configurable options with existing techniques for isolating cores. So for example, if I have four CPU cores in my host and I pin guests to all of those, my host processors and my V-switch are still bouncing around somewhere inside that node. So you're not getting the deterministic performance you're probably after, unless you also pin host processors somewhere. So looking at an example, very basic NUMA hardware layout. So I'm just using NUMA control here to dump what it's seeing. So have on the left you'll see node 0 and node 1, the two NUMA cells on NUMA nodes available. NUMA node 0 has CPUs 0, 1, 2, and 3, so four CPU cores. NUMA node 1 has 4, 5, 6, and 7. In each case, they have around a gig of memory available. In some newer systems, you can also get an IO layout associated with this. So PCI devices or PCI-U lanes can be associated with a specific NUMA node as well. And you can see in the bottom there, it also shows me the node distances. So we see there that access from node 0 to node 0 is obviously closer than accessing node 1 from node 0. And that applies mainly to your memory in this particular case, but also to the IO devices in architectures where that's supported, or on chipsets where that's supported rather. So visualizing that a little bit, this is just a diagrammatic representation of that same thing. And to explain what I mean by access being slower, so if I'm on core 0 in this example, and I need to access memory that's in node 1's memory banks, then I have to go through the interchange bus, and that's going to add a performance penalty versus if I'm accessing memory local to the node I'm on. So I mentioned earlier that verse allows you to dump the XML, not just related to the guest actually, but also related to the host, so it limits representation of what it's seeing. In this particular case, this is just an excerpt. So we see here that I'm looking at cell ID 0. In this particular case, we see my 8 gig of memory exposed as kilobytes here. It also shows in the pages element. So all of my pages in this particular example are 4k. I have no huge pages, which is the next line down there. The 2048 is 2 meg huge pages. I have none of them in this example. And then at the bottom I have my series of CPUs starting with CPU ID 0, 1, and the alignment they have with specific numeros. So I'm going to walk through a little bit of an example of configuring this. So in this example, I'm going to try and set it up with that hardware layout I just showed. I'm going to set up CPU pinning based on that. So first of all, I have to enable the pneumatopology filter. And typically the aggregate instance extra specs filter as well. So pneumatopology filter is obviously taking account for my host topology. The aggregate filter is used because I want to segregate the machines on which I run guests that need dedicated resourcing from the rest of them. So the ones I want dedicated resourcing on, I need to take some additional configuration steps to make sure they're ready for that. So in this particular example, I'm going to reserve for the purposes of running guests CPU cores 2, 3, 6, and 7. So what that means is that I'm reserving two cores out of four on each of my nodes, keeping in mind that this is a fairly contrived example. But stay with me. And what the ISO-LCPUs kernel parameters are doing is telling the host kernel, basically, do not schedule processes to these cores. Now, it still will allow you to schedule processes to those cores if you explicitly pin them, which is, of course, what we're going to do. Using the vCPU pin set variable in nova.conf, we're going to express basically the same thing. So this is telling Libvert and QMU, and specifically the Libvert driver, hey, this is where I want you to run the virtual machines. So it's going to explicitly, even without any further configuration, if we're not doing CPU pinning, it will put pinning ranges into the guest XML to ensure that your virtual machines are running on the cores specified in this variable. And you can specify a range. So for example, if I was giving the entire first numer node to running guests, I would specify the range of 0 to 3, for example. And this is a visual representation of what I'm trying to do. So I'm reserving, it's kind of the reverse, because I specify that I want 2, 3, 6, and 7 to be isolated from the kernel scheduler. Implicitly, that means that the rest of the cores, so 0, 1, 4, and 5, are being used for host processes. And realistically, in an environment that cares about this kind of stuff, like a network for function virtualization or a packet processing use case, I would pin my vSwitch to one of those cores, for example. So in terms of setting up the guest, we have a opportunity to specify whether we want the instance to be dedicated. Either in this case, I'm going to use the flavor extra specifications. You can actually also do it from an image property, if I recall correctly. But in this particular case, I've pre-created a flavor called m1.small.performance. So it's basically just a copy of m1.small, but I'm adding this configuration key. So CPU policy equals dedicated. And then on the nova boot command, I simply specify my image, as usual, and this new flavor I've created to create my instance. So we take a look at the resulting guest lv.xml for the guest. So vCPU placement is static, but it would have been before, actually, as well. But what it does give me in addition is there's a one-to-one relationship between the vCPUs of my guest and the physical CPU cores on the host. So you can see here that vCPU or virtual CPU 0 is explicitly pinned to the second CPU core or CPU core 2 on the host. And similarly, virtual CPU 1 is pinned to number 3. We also, in this example you can see, have pinned what's referred to the emulator thread, so this is an additional QMU process associated with a guest. And the current implementation is pinned to the union of the allocated CPUs. So the emulator thread will still move around between those two CPUs. That's something we may look at tuning further providing other options for in the future, but that's the default implementation for now. When we go further down in the output, we'll also find that the memory is strictly aligned to the Numer node. So this is relatively new ability to do this in not just QMU, but also the kernel. And it only, if I recall correctly, will work when you're in KVM mode. So you can't use this using QMU emulation. You have to have the hardware acceleration. But you can see here that the memory backing for this particular guest is pinned to node 0 as well, or cell 0. So moving on and now combining this with huge pages. So in that previous example, my host didn't have any huge pages to find yet. Huge pages allow us to use larger page sizes for our memory, which improves our cache efficiency. So effectively, instead of requesting over and over again 4K pages, obviously if I can request once a one gig page, I'm going to have a faster lookup time. But there's pros and cons to that as well. So we're primarily dealing with on x86 two meg and one gig huge pages. So allowing these, the other thing I should mention is these can't be over committed. So if I'm using huge pages, then again my memory over commit is gone. And different workloads are going to exhibit different characteristics when using huge pages. There are workloads that benefit from two meg huge pages but may not benefit from one gig huge pages, for example. It really takes some profiling to work out exactly what the right fit is. Bigger is not always better. So in terms of the process for setting this up, an administrator uses the normal Linux tools for reserving huge pages during compute node setup, and then creates some flavors to match. Again, you can also do some of this from image properties. So just taking a look at an example here, so I mentioned I have to allocate the huge pages I want up front on kernel boot in this particular case. So I'm requesting 2048 two megabyte huge pages, which is, of course, enough to back a four gig guest, which is what I'm going to create for this example. Again, this is a relatively contrived example for the purposes of this presentation. There's obviously a lot more involved, but there's also a lot of very exotic hardware configurations once you get into some of the newer stuff as well, depending on what chipsets are in use and so on. So I use Grubby to set that up. I install to the master boot record. I re-bent my machine, and then I take a look and see where my huge pages are at. By default, when you specify the huge pages the way I did, the system will simply split them equally over the number of new nodes you have. So in this particular case, I have two new nodes, so I get 1,024 of those huge pages on each side. Similarly, we can see when I run verse capabilities that the allocation for the new node has changed. I now have 1,024 on each node. So I'm re-using my m1.small.performance flavor. I'm adding the keyword that I want the mem page size of 2048. You can also, obviously, request the one gig huge pages, or there is also shortcuts where you can specify smaller, large. But for the purposes of this architecture, it's basically the same thing, so it doesn't make a lot of difference. And then I obviously boot my guest using that flavor. And when we dump the XML, we can see that the memory backing has been changed to use those huge pages on node zero, or on node zero where possible, sorry, it's more accurate. So moving on to the PCIe example, so we're using the same host here. Most, well, more modern X86 chipsets have the PCIe lanes associated with a given new node. And it's basically the same principle as with the memory stuff. So if I'm on core zero, and I'm using a physically pass through device, and that device is attached to node one, then I'm not going to get the same performance I would if it was attached to node zero. So again, some extensions to the pneumatopology filter allow it to make use of this information where it's available. For chipsets that don't expose it, it will make no difference. So that was kind of the wrap on the performance features. I have also started, and I'm working on a series of blog posts to work on those in a more expanded basis. But now I'm just moving on to some more general features in the driver for this Keeler release. So Libvert 1.25 and higher, or greater than 1.25, sorry, supports the ability to use something that was recently added to the QAMing guest agent. So that's as a reminder the agent that can run inside the guest and perform actions on that side. And it's what's called a freeze-thor API. So what that means is that I can tell the guest I want to freeze the file system. So that can take a snapshot and ensure that snapshot is consistent or queues the file system, sorry. And then when I'm done snapshotting, I can throw it again to allow the guest to start modifying the disk again. So there's a very useful ability for creating consistent snapshots or ensuring consistent snapshots currently, the way to enable that. So when we have the guest agent inside a guest image, we need to set the QMU guest agent image property to yes to show that it's there so that Nova knows it's there. Because we don't really know if at this time have a lot of introspection inside the guest yet other than what we get via these agents. And for the guests where we want to use this capability, we need to set the require FS Freeze Image Property to yes. If these things are set up, the when snapshotting, this will be implicitly taken care of for you. So there's nothing to do after that point. So it's primarily a guest creation and setup thing when you're creating the image. This was actually not a blueprint, but a bug fix or treated as a bug fix. So Hyper-V supports a number of additional para-virtualization features, so particularly for Windows. So it provides an enhanced experience for Windows guests running on top of Hyper-V. And actually Linux guests also support those these days. So there's contributions in the kernel that allow them to take advantage of these features when they're running on Windows hypervisors. On Livert KVM on Linux, we have the ability to emulate a number of these features. And in particular, and the reason this was primarily treated as a bug fix is that the certain Windows versions, when they're running on heavily loaded hosts, you can encounter a blue screen of death if these particular features aren't present or exposed to the guest. So to take advantage of those, we expanded the behavior of the existing OS type equals Windows image property. So there is an image property you can set which says this guest is of type Windows and then some customization of the XML on the virtual hardware presented to that guest will be done based on that. Support for Vhost user. So Vhost user is a new type of network interface implemented in QMU on Livert. It's intended to provide a more efficient path between a guest and user space switches. It becomes particularly interesting, not just in normal OVS use cases, but as we look to things like OVS and DPTK acceleration when they combine together. So the VIF driver is there at the moment. And I'll talk a little bit more about in the Liberty look forward, what more we need to do around that. So Liberty predictions. So I mentioned at the start, and I'll highlight again that this is a fairly critical time in a cycle for determining what we're actually gonna achieve in the next six months. So these are all in varying states of discussion and review. And this is just kind of my read on stuff that looks like, I'll say it's likely to happen. But this is again, just me speculating primarily. So Livert hardware policy from LibOS Info. So we touched on the OS type image property for telling Nova what type of guest is running. Now we said for that particular Hyper-V Enlightenment example that we're saying OS type equals Windows. And the obvious question when you think about that is, does that mean Windows 3.1? Does that mean Windows XP? Windows ME, probably not, and so on. And not just in the Windows world, but there's also some versions of BSD and other guests are also very sensitive to some of the timer information. So we wanna get a little bit more granularity in what we're doing there so that we're more explicit about exactly what guests we're talking about. Because obviously, when we look at something like XP now versus the latest versions of Windows, the workarounds we had to apply for XP are potentially quite different from the ones we need to apply for newer versions. So LibOS Info provides kind of agreed upon form for expressing this information. So the idea is first to expand the use of the OS type variable or image property so that it can at least take this format and use that format. Ideally, what we'd like to get to and probably beyond to Liberty Cycle, to be honest, would be introspection to actually be able to determine the guest without the user having to explicitly tell us. But that's kind of an extrapolation of what's proposed currently. Postplug VIF scripts. So I mentioned that the VIF driver interface is not pluggable because it's not really a stable API to begin with. And this causes some issues because it means if someone, if a networking vendor wants to out of VIF, they have to land it in the nova tree before anyone can really use it at the moment or they have to apply patches to people's distributions and so on. And one of the main reasons they're typically doing this is not because they're not using one of the already defined interfaces, but because they have to do some additional customization or calls to their V-switch or setting up flows or that kind of thing after plugging the interface. So to get around that or to help them find a solution that's more in the middle, what's proposed at the moment and what's been discussed a little bit and still under review is the idea of allowing for a postplug script so that people could use, for example, the generic V-host user VIF driver, but then run some additional logic that they can plug externally to do whatever they need to do on their V-switch. There's a lot of discussion around further work around SRO-V device pass-through. And there's a number of other blueprints related to this, but the primary two that seem to have the most interest at the moment are the ability to attach and detach pass-through interfaces from a running guest. So at the moment, you have to attach the device or the port at the time you're booting the guest. You can't change it afterwards. And also the ability to do live migration of guests with SRO-V devices, but there's a little bit of a catch there in that live migration of those guests is only gonna work where we're using the Mac V-tap pass-through mode. We're effectively creating a virtual device in between. It won't work when we're doing direct pass-through and Mac V-tap is a bit of a performance penalty involved. So it's kind of a trade-off. You can have maximum performance, but you're trading off live migration and that applies to a few other things in NOVA as well. The ability to be more explicit about what CPU model and or features a guest wants. So there is actually a filter, a schedule filter at the moment that can be used to say, this guest needs to run on a host with these CPU features. The problem with that is that it doesn't actually check what host model that particular node is exposing to the guest. So all right, I landed on a host that has AEX or whatever feature it is I wanted, but I may not be getting exposed to that in my guest anyway. So there's a couple of proposals and a discussion around how to resolve that issue in a way that we have what we actually intended, which is the guest not only goes on a CPU that has that feature, but that is exposing that feature to virtual machines. Virtual Machine HA, I put on here because there's a lot of interest in it. It's not actually primarily an inside NOVA thing to implement, but there is some discussion about having the ability for external tools like Pacemaker or KeepoliveDE or other high availability tools that are already well-established as ways to detect failure, the ability to tell NOVA, hey, this failed and what they're doing in reaction to that. So the bulk of the HA work is actually in Pacemaker and KeepoliveDE and other high availability solutions and the way people are deploying those, but there is also this proposal for an API call in NOVA for them to tell it what it's doing. There's a couple of little tweaks around Vertio performance enhancements under discussion. One of the challenges with those is how to abstract those enough that you are giving a good experience to the generic cloud use case and also enough customizability to people really pushing the boundaries and it's very challenging with some of these because they are, for example, Vertio multi-qs is a way to enhance performance in terms of increasing the number of queues associated with a Vertio device for processing traffic that is very specific to the Vertio driver and as a result, in a cloud model, it's difficult to abstract that enough. I should have mentioned that as I go down these, I get to the ones I have less confidence in, just from my own take. So hot resize I put up here, which is kind of like not the first time it's been proposed. So this is the idea of most modern hypervisors, if not all, have the ability these days to add and remove CPUs, RAM on the fly, so at run time. And the idea is to implement an equivalent of the resize function, or cold resize, to do it on the fly as well in Nova. Whether or not that happens or not, we'll see. So that's the end of what I have for today. Again, if people are interested in breaking up, blowing up compute itself I'm taking a look at the wider architecture. I'll be back here the same time tomorrow doing that. I'll also take any questions people have.


Hey, Sifu David. In this video, we're going to show you the five self-defense moves that everyone should know. This is so simple that you can learn these in the next 10 minutes and you'll be able to use it in the fight even if it happened right after this video. This is how simple it is that any Tom, Dick or Harry can use these techniques right away. At the end of this video, you're going to see bonus technique number six and we're going to show it to you. So stay tuned. Here we go.