Hello and welcome to the Grand Line Review Source for everything One Piece, and today we have a review of chapter 1001, and this week sees a direct continuation of the eternally glorious chapter 1000, because we are straight into action here and it's almost surreal really. Reading some of this stuff does genuinely make me wonder if I'm actually awake, because this is the sort of chapter I've been waiting for ever since the beginning of Warner. In fact, no, much longer than that, since the Ninja Pirate Minx Samurai Alliance against Kaira was formed on Zoho, except probably longer I would say ever since Luffy and lore formed an alliance to take down Kaido on Pongkazid, after which point Luffy made lore press the subscribe button for the Grand Line Review, which granted him regular One Piece content uploaded straight into his YouTube feed, and it can do the same for you as well. Say hi below if you're a new member of the Grand Fleet, welcome. Except that in all honesty, it's probably been ever since Garth first revealed the existence of the four emperors way back in the water seven saga. I remember reading that exact chapter weekly in 2006 and just saying to myself, well it's going to be a long time before we take these guys on. Although even I could not have predicted just how long that long time would be, because 14 to 15 years later, here we are finally doing the thing and it is fantastic. This is the sort of chapter I've been waiting for my whole life. But here's the thing, for such a grand scale chapter, 1001 actually felt surprisingly intimate. And that's because it took place all in exactly one location, with a focus on seven characters. Five members of the worst generation and two emperors of the sea. And that might sound like a lot of characters, but this is actually a very small pool for one piece, especially during our climaxes where all of the crazy stuff is happening all of their time. For comparison, just think back to some of the recent chapters featuring the vassals versus Kynar. Those scenes alone had 10 characters to juggle, and they weren't even the only scenes in those chapters. So focusing on a mere seven characters gives the time and opportunity to make sure that they all have something of a moment of resonance here, which they do. And to start with, the character who was most prominent to my mind after having read this chapter was of course Trafalgar Law. In fact, I'd go so far as to say that Chapter 1001 made me a much bigger fan of Law than I previously was, and it's not just because of the face fault either. But I think what this chapter achieved was the same sort of thing that Wano has done really well for Robin, by which I mean that Oda hasn't been afraid to use Robin for jokes and some pretty weird physical humor as well, whereas previously Robin was a more stoic and untouchable figure by comedy, especially this kind of comedy. And Law was in a very similar position. He's the established cool guy who plays the straight man in any jokes that just so happened to be in his general vicinity, but he steps up on a couple of occasions here, the first of which was saving Luffy from Kaito's attack, only to chastise Luffy for ordering him to send Kinemon and the others downstairs. What are you doing, Law? You're acting all, uh, all cindereal all of a sudden. Baka! It's not like I wanted to obey your orders or anything. It's another great example of Oda being greedy as well, because due to these experiences of Law being separated by chapters, you get the full dramatic weight of Luffy's order in Chapter 1000, but then also some great comedy spawning from that moment here as well. And of course it all just seems so natural, but that's a tough thing to do as an author. It's sort of like how Oda used Kikuzan for two different purposes, one being the shock of losing it, and the second being to activate Zora. Oda is just really stupidly efficient with events and actions like these. But in essence, this chapter gave Law a shot of personality that I always crave from him. He's cool and all, but I want a bit more, and that's exactly what I got here, before even moving on to the face fault. And in general, that was amazing just all over. Very classic one piece. You think you're getting into the most serious of battles ever within the series, but instead you get a joke. And it was so good as well, because it pretty much justifies every time Big Mom or Kaidov called the worst generation members brats or kids or whatever, because they kind of are. Our three captains here all have this innate immature nature, as well as fierce competitiveness, even in the face of what looks more like overwhelming defeat than not. And it's times like this where I can just imagine Oda laughing uncontrollably to himself whilst drawing in his studio, and you can tell that after more than 20 years of doing this, he's still having a lot of fun with his work as we are reading it. When it comes to some form of seriousness though, the second character most pronounced here to me would have to be Kaido. It's so subtle, but he makes some crazy expressions during 1001 that we've just never seen before. The first of which is that smirk he makes right before initiating Thunder Bagua. It's just so cheeky. And what's more amazing is that it emerges from what looks like a state of complete anger, like between these two panels Kaido flips an emotional switch, and in his own way he's being incredibly playful. And then after Luffy sort of dodges the attack, there's this panel where he has the look of a proud father about him. You know, I wish that my father looked at me the way that Kaido looks at Luffy after dodging an attack. Granted, Kaido would be a very abusive father, with all of the clubbing and such, but still. It's so wholesome though, or about as wholesome as Kaido can get, which still would probably involve child abuse. One thing it does bring up though again is the sheer speed of Thunder Bagua. Something that I actually ranted about at great length, when the first one was adapted in the anime during Act 1. The anime did not portray Kaido's sheer speed or the surprised nature of the attack. It was very, very slow and like Luffy didn't want to dodge it, in fact he actively attacked into it. Whatever the case, there was no element of speed at play. It was all power. And having dug that hole, it makes me wonder what they'll do when they reach this episode in about a year from now. Probably some sort of clash where Luffy removes himself for the last second. But in regards to the manga, this was a great moment, because it's a tangible cue of Luffy's progression. He will not be taken in by a blitz attack like that again, and so we have a much more serious fight on our hands, which is very much thanks to Future Sight by the way, so Whole Cake Island is still paying off a lot in the section. Although something I did skip over is my favourite panel of the chapter, where Kaido is having a sort of inner monologue, regarding the fact there have only ever been a small selection of people capable of fighting him. And then these beautiful Oda-style silhouettes appear behind Luffy. Roger, Whitebeard, Odin, and… is that Rocks? Yeah, it's gotta be. There's so much more definition on him, I think we've ever seen before. And the shockier to me was the appearance of Rocks. I mean, it shouldn't be a shock appearance, it should be a given, since Rocks was the one who wrangled Kaido in the first place, but the whole panel itself was so unexpected for me, so it was a nice surprise appearance. And it makes me salivate just a tiny bit more for some information on Rocks in the future. Ah, ah, Shanks is there as well. He's hiding behind Luffy, sneaky one-arms ninja. And it took me a while to digest this, but Shanks is also in this image strategically placed right behind Luffy as if he was some sort of role model figure. But I legitimately did not even register that he was here at first, because when you're surrounded by Roger, Whitebeard, Rocks, as well as partially blocked by Luffy, it's just not the first place my eyes are going to go. But it is some very nice confirmation that Shanks and Kaido have indeed fought in the past. In fact, it would now seem like Kaido has fought against every other Emperor, with the exception of perhaps a Blackbeard. The Shanks stuff is important though, particularly to nit-picky people like me, because it's generally accepted that Shanks and Kaido fought offscreen during the Paramount War or just prior to it. However, that has always been very vague and unconfirmed. I have a whole video outlining why if you are interested to find out, but this pretty blatantly says to us that even if they didn't fight at that exact point of time, they have indeed battled before. And this is one of the rare tangible cues that we have of Shanks' strength. But in the end, none of that matters, not one bit, because all of this goes to serve exactly one man and that man is Luffy. This panel is like an injection of inherited will straight into the veins of the manga paper. Because with the exception of Rocks, these are all very fundamental figures in Luffy's journey, and he embodies the hopes and dreams of the large majority of them. And right now we are seeing his rise to prominence. Yes, so one who is there, it's a very make or break moment. Either this is where the legend of Monkey D. Luffy is born, or this is where the will of D goes to die. And given that Luffy is the protagonist thing, it's probably going to be the former. Continuing with Luffy, though, he is immediately thrust into serious mode, having activated Gear 4th, which is kind of worrying to be honest, because we still don't seem to be anywhere near the serious culmination of this fight. Especially since, at least traditionally, we'll need to travel back to everyone else and watch them defeat their respective members of the Beast Pirates before we really dive into the main meat here, um-nom-nom. There's also the very real problem that it seems like Luffy is the only one that can deal any real damage to Kaeda at the moment. Kid did the best his could with his brilliant Mecha creation. I'm really enjoying seeing more of his powers. Even if it does bring up how sort of limited he is in terms of strength, I mean being constrained to whatever happens to be around you can't be an easy way to fight. He's a bit like Douglas Bullard from One Piece Stampede, just lacking any sort of physical force behind him. And in terms of lore, he's even more underwhelming in the action because his big plan is to drop lots and lots of rocks on Kaeda, which he surely knew would have next to no effect. Unless he's going to chop Kaeda into pieces or swap his heart with someone else, unfortunately I think lore is much better used to support in this fight, mainly to remove other worst-generation members from tight spots or for surprise attacks. I mean, lore's fruit is so deadly and versatile and generally amazing, and right now it is being used to start a rock collection. Very admittedly impressive rock collection, but still. I also find it interesting that by the end of the chapter, Kaeda went into his dragon form, which made for an amazing spread along with Big Mom, really showing the scale of their power versus the worst generation. But, and I said this with the vassals, I can't help but feel like his dragon form is more of a hindrance than a benefit. It makes him a very, very big target, and the vassals didn't start seriously losing until Kaeda turned into his more humanic incarnation. Then again, to say that Kaeda was actually taking this fight seriously, that would be a lie, it would just be a blatant lie. He's still very much in worst-generation beta testing mode, where he's still seeing if these goofy chumps are worthy of a serious fight, or even better, worthy of a serious death. In other news, Zorro, just Zorro. That man is always big news, but especially here when he's taking a lot of initiative, and actually he's the only one who got a hit in on both of the emperors during this chapter. One more meaningful than the other, which is when he sliced up Prometheus, which I actually thought was pretty funny because now two of Big Mom's homies have been cut in half like that because Brooke sliced up Zeus and Hawkeyeke Island, so I'm just waiting for the trifecta now. Someone needs to cut Napoleon in half, and this pattern will be complete. Also, Zorro in true pirate style quite literally stole an attack in order to perform this, which is great because I think people have been speculating on Zorro learning something along these lines ever since we first saw Foxfire style back on Punk Hazard. So whilst it's not quite advanced arm and tarky, it is still a legit upgrade, and there's room for improvement as well, because this chapter seeds some future in my action. We are just warming up here. Although the crowning moment of Zorro to me of course was when he put on the bandana. Wait a minute, he put on the bandana. I'd say, you know, things are getting serious. Bandana's a pretty serious stuff in one piece, and we haven't seen Zorro done here since Dressrosa, and I have just missed this look a lot. Happy to have it back. Also, Zorro had this fun little interaction with Killer as well, who is not to be left behind as he joins Zorro for an attack on Kaido. He's still very much kind of the odd one out here to me.  However, he does have just as much reason to be here as anyone. Even if he wasn't just happy to follow Kid blindly into battle, he has business to settle for the whole being force fed a smile, fruit, or deal. And all in all, Chapter 1001 was a fantastic continuation of the hype from 1000, which is probably very well expressed in the final pages as well, with Kaido stating the stakes of this fight, which is basically that whoever wins is going to be disgustingly close to becoming the king of the pirates. And I suppose we shall see which Monkey D. Luffy comes out on top throughout the rest of this year. But that pretty much does it for Chapter 1001, and what do you guys think? Please leave your thoughts in the comments below, or even join my Discord server. And if you'd like to see more videos like this, then please do go and check out some of my other content, or even subscribe to the channel for more glorious One Piece Business uploaded straight into your YouTube feeds. But for now, this has been the Grand Line Review, and I'll see you next time.


So our next talk is actually from a colleague of mine and he will talk on his broker as he made on his virtualization interface for multiple VMMs. So here's Alexander Petruf. Thank you. Welcome to my presentation about microconvitalization on the one roof. The outline of my talk looks like this. I will give short introduction and the motivation. Then I will go through several kernel interfaces looking at the common features and the differences. And based on that I will try to discuss or to show how such virtual machine interface of all the kernels can be harmonized in a way so that we can on top run virtual machine monitors which are portable across kernels. If you today look at off the shelf virtualization solutions, then you will see that they are written of complexity. For example, if you look at Linux KVM, there you have a monolithic operating system running with virtualization extensions. There's no isolation between your drivers or the sub-sub-sub-sub-sub system in the kernel. Or if you think on DOM0 on Xen, it's a huge Linux kernel running there and all your virtual machine monitors. So your QMU instances have to trust that it's working perfectly fine. That's million lines of code you have to rely on. But actually application for virtualization call for trust-worthy solutions but this somehow complexity defeats trust. There are of course alternative approaches around. One way to go, not the only one, but one way to go is to use a microkernel with virtualization extension for hardware-assisted virtualization and build from the architecture point of view with something trust-worthy as a system. How does that architecture look like in principle? I took Nova here for example so you can replace it in theory with other kernels. What you need first is of course a microkernel which is quite tiny which also has features to run as a hypervisor. Then on top you need some user-level environments. Your drivers are running well protected from each other in own protection domains. And of course you have native applications on top and some resource management stuff. For this talk relevant is that you have some virtual machine monitor. Together with a hypervisor you can drive your guest operating system, your unmodified guest operating system. The nice thing in such architecture is that as a virtual machine monitor you can have multiples of some. So not the same implementation. They can be specific to your guest operating system if you want to optimize for low code or for security reasons. So you have some, you can play a bit. Taking from this picture you see that we need a microkernel, we need a user-level environment and we need virtual machine monitors. And the Genant Operating System framework is such a user-level environment. It consists of more than 100 ready-to-use components. So you have native drivers. It's a button on the bottom left. You have low complex resource multiplexers for network disk, graphical user interface. So I'm talking about something like 1000 lines of code, not about million lines of code. Then we have support for several kinds of libraries. You can even use your GNU software. And the main interesting thing is that this user-level environment which is specifically designed for microkernels supports already more than, we support eight kernels. In the middle you see some of them. The nice thing about it, I think like two years ago we even got to the point that we have a unified API for all the kernels. For some specific hardware platform you are talking on, you develop your GNU component once. You compile it once and link it once and then it will run on all the kernels immediately. You don't have any recompilation step or adjustment you have to do. It just works. Why is this interesting? If you want to build some general purpose OS, when you mentioned that you have to package all the components, all the software for each specific kernel, again and again it takes some effort. And with this step we actually have, for example, for x86 we have just to build it once, to package once, and it will run on all the kernels. Regarding virtualization, we support already several virtual machine monitors and virtual box and so on, but I will come to this point later. When looking at the kernel, so that's a current one, so eight we support in principle. Actually, five of them are capable to run unmodified, so have hardware as its virtualization features. On the one hand, it's a Nova micro-advisor where my machine currently running is on. Then we have a kernel called base hardware, so HW, typically called, developed by Genotlabs. Then we have SL4 as you have heard beforehand. We have Fiasco OC support, and even we support Linux to some degree. When we look at the inventory of the virtual machine monitors, we have often on Genotlabs currently. You will see that for our own kernel, so for HW, we have some custom implementation, mainly used on ARM machines. Thanks to the Muen separation kernel project, we have even x86 support for our kernel. Originally, it was just designed for ARM. Together with that, we can run Bindo 7 on Muen with our own kernel. Here we use a port of virtual box 4. On the other hand, we have the Nova micro-advisor, which is running on everything, which is x86. There's a nice thing about it, that it supports already multiple vzpus, 64-bit guests. The actual point here is that we have already support for three different virtual machine monitors. You can run them all in parallel, so you don't have to decide on one. Depending on what you want to run, you can choose. The question now was, the unified API, what I was talking about, is working for Genotlabs components, which are not virtual machine monitors. The virtual machine monitors currently are directly built against the kernel API, so that means although you cannot move it easily to SL4 or Fiasco OC, it's not possible at the moment. The question was, can we do it? What does it take to get to this point? That's what I want to talk about now. In the beginning, we said, okay, let's focus on micro kernels first, and then on x86, because the grass cut is the biggest. Let out Linux for the moment, so Linux KVM would be also a nice thing to look into, but for the moment we want to have the micro kernels running. The virtual machine monitors are all of the micro kernels for a specific platform. The approach is simply that we take the interface we have from our own kernel, where we have a good experience on ARM and also on this together with a more in-separation kernel, and extend it to this degree that we can run over SL4 and Fiasco OC with this interface. Now I would like to go a bit through the kernel interfaces to see the differences. Beforehand, I just want to make a short describe how such a virtualization event looks like in principle. So when you have once you have your guest operating system running, you will at one point get some exit, because the guest is doing something which is maybe privileged or it touches a virtual device. So the hardware will cause a VM exit. The hardware will then transfer some of this data to some specific region called VMCS on Intel. The task of the kernel is to look up whom to deliver this event or who takes care about it. The microhyper will not do it. So with each guest operating system and virtual machine monitors associated, when the kernel finds a specific thread which the message will be delivered, it will also find some shared memory region between the handling thread and the kernel called user thread control block. Via this user thread control block, you would transfer some of the state from the VMCS, give it to the virtual machine monitor. The virtual machine monitor looks into it, decides what to do and to emulate things or whatever. So this is the principle flow in general. Now I would like to go a bit through the differences. For the NOVA hypervisor, it looks like this, that the state is transferred via the so-called UTCB, which is attached to each thread. The layout of the UTCB is agnostic regarding whether you're running on Intel or AMD, so you don't see the differences in the layout. And the other thing is if your virtual machine monitor is clever enough, it even can specify which state should be transferred to the virtual machine monitor, so you don't have to get ever the whole state. When looking on Fiasco OC, your handling thread has also a UTCB, but actually there you set up another shared memory page between kernel and virtual machine monitor where the state from the VMCS or VMCB if you're running on AMD is copied. On Fiasco OC, the full state is copied ever, and the layout of the VCPU state actually is not agnostic regarding Intel and AMD. So this is the difference. On SLL4, they decided to go in the third direction. They have also some shared memory per thread. It's called IPC buffer, not UTCB, but it's semantically the same. When you create a VCPU, you set up some VCPU state also in the kernel, but they decided that it's not shared with the virtual machine monitor directly, but instead when you get NVM exit, you get a fixed set of registers via the IPC buffer transferred, so 17 registers. And if you want to have more, you have to make synchronize this code per item in the VMCS to ask for the rest. And then you want to enter, want to resume, you transfer three registers, which is fixed, and when you want to transfer more, you have to make synchronize this code beforehand and fill each item one by one. I have looked up something like 60 registers in the VMCS are relevant at most, so it means it's quite an overhead you can produce. So now we have seen how the state is copied for us back, and now the question is how the control flow works. So when you get an exit on the Nova Hypervisor, the kernel sets up for your IPC, an IPC call, that means your handling thread gets a synchronous call, and as soon as it, when it applies, the VCPU gets running again. On Fiasco OC, it's the way around. You have a thread in the virtual machine monitor, you assign some VCPU object to it, and if you have done this, then you can make a blocking source call called VM resume, and then the blue thread in the virtual machine monitor is blocking until the point when the VCPU exits again. And for SL4, it's the same as for Fiasco OC, they have a thread, you attach some VCPU object to it, and afterwards you are allowed to call it as blocking source call. So it's semantically the same as for Fiasco OC. When we're looking on the kernel developed by Genotes, there it's done more non-blocking and asynchronously, so when your VCPU exits, the VCPU is stopped, the kernel sets up some asynchronous notification, the next time the virtual machine monitor thread will be scheduled, the signal will be delivered, and when you want to resume the VCPU, you make a call to the kernel, which is however non-blocking, and that means the virtual machine thread is ever ready to do something else in the meantime. It's not blocking at all. So now we have seen the common features and differences. Now the question is how harmonized interface can look like, how we can support it on Genote in general, or is it possible? And the main idea here is that the virtual machine monitor should just be a normal Genote component. Then the question is what is a normal Genote component? A Genote component is designed in a way that it should be driven by events, so it's in order to implement easily state machines. So that means when you start a Genote component, you have a thread which is called entry point, and so the only job of this thread is to register for any kinds of events he is interested in, and afterwards you leave the scope, so you're not blocking or not spinning or something like this, you leave just the scope of your initialization, and then you wait to have that something happens. And then when an event comes in, you get ready, only during this event or this state transition, you do actually something useful, and as soon as you leave the handler, you are ready again to handle something else. And such events can either be synchronous incoming remote procedures calls or asynchronous notification. From the handler point of view, you don't see the difference actually. For a virtual machine monitor now, such VM access, such a VM event should just be another event source, so if you don't want to do any special about it. Also, if you want, if some IO is ready and must be, for example, a network arrived for your guest, this IO event should also just be another event source. You don't want to do any special. Of course, we want to have a kernel-agnostic API, and the vCPU state on this interface should also be agnostic regarding whether you're running on Intel or AMD. It should not matter. So we don't want to expose it to the normal developer of a G-Node component, so of the virtual machine component. What I have told you now in a picture maybe, so when you start a virtual machine monitor, you have your entry points, which registers, for example, for you want to have timeouts or you want to get networks packets delivered to your VM, and when you create vCPUs, you get just a notification that something happens. This picture was mainly so that you can build single-readed virtual machine monitors, which is nice in order to have to don't to care about locks and stuff, but of course you can also go multi-readed if you have multiple vCPUs, if you have multiple physical CPUs, you want to put the vCPUs on the physical CPUs, then you can have, of course, spawn several entry points. That's also possible. Now regarding the kernel-agnostic API. So what we do on G-Node is that G-Node-based library is part of the dynamic linker. The API for this shared library is, as I said, kernel-agnostic, so it's fixed. The actual implementation of the library, of course, can be kernel-specific. So that means for, depending on which kernel you're running, you get another LD, but the interface is the same for this. So that means all our components are typically dynamically linked. So, and yes, we put this interface just in the base library and then we have some freedom to implement it kernel-specific. How this interface looks in general from an abstract point of view. So on G-Node, when you want to have a service, you set up a connection. If you get this connection, you have a get-back capability. So you have a session. This implicitly sets up your address space for the guest, which is empty in the beginning. Then you can populate it with creating new CPUs, getting access to the state of the guest, attaching memory, so, packing the virtual machine monitor with some memory. And then you have a specific handler class where you actually register for this event for an exit. And then you can let run or pause vCPU. And the calls are actually unblocking. So in a picture it looks like this. So when you start up your kernel, the first task is core. Then you have some management component in it which spawns a new instance, virtual machine monitor in that case. When the endpoint starts, it sets up a connection. So it asks the parent, I want to have the service. Please give it me. So then you have policy attached, which can be enforced. Then you get this connection to the service, get-back a capability, and then you can directly talk to the service. So that means on genotes when you have a VM session, it means you have a connection to some service. And via the service you can create CPUs, attach memory, also operation you have seen beforehand. And whenever an exit happens to some of the vCPUs, the exit will be delivered directly to the virtual machine monitor. What you see from this picture here is we have some freedom to decide where to implement stuff, which depends heavily on the kernel and the kernel interface and how nicely we can hide the special things of the kernel. So in this picture, this task is kernel-specific, it must be. And in the library here is, so the implementation is specific. And for Nova, Fiasco, the delivery of the exits are, for example, goes directly to the virtual machine monitor. In theory, we also can divert here and then get a notification over there, but couldn't it look like this? Just to give you an idea, so on the service side, just to get your virtual machine running, we need something like 200 to 500 lines of code. On the client side, for Nova and SFO, we need something like 500, which is mainly copying the state, forth and back of the VCPU. For Fiasco, see it's a double amount, mainly because of the fact that you have to do for Intel and AMD twice, and you cannot nicely abstract away. For our own kernel, you see that's actually just a Corsus wrapper, so there we don't implement anything currently. Now I would like a bit go through the control flow stuff. It's the pictures you have seen beforehand for our own kernel and Nova. So the direction, how is it called, when on an exit, how it looks similar. And a more detail is, so when you get an exit from your VCPU, your kernel gets running, and on our own kernel, we set up a signal, an asynchronous notification on Nova as a call, then the handler becomes running. The fact that it's a synchronous or an asynchronous notification is not relevant for the handler. It just becomes running, it got its event. When you then decide to resume the execution on our own kernel, it's just a non-blocking asynchronous notification or a source call to the kernel, which is non-blocking. On Nova, when you actually say, I want to run, the implementation just will remember its effect, and as soon as you leave the handler, this handler class, the IPC reply will be done. And if you said run, then the kernel will take care to resume the VCPU, and if you said not run, we have some kernel extension where the VCPU will not be resumed. So the next topic is, for example, you have a virtual device model which programs some timeout and the timeout fired. So you get some event, your entry point is non-blocking is running. So the first thing what it does, it calls pause to get the VCPU hold it. On Nova, it's a recall source call, and the nice thing is it's both non-blocking. Then at one point, the VM gets stopped, and as soon as this happens, again, you get your IPC call on Nova or a signal on our own kernel. And then you look at the states, write to the right registers that you want to inject and interrupt so that the timeout happens, and yes, you can just resume it. So both kernels are quite similar, and the Nova-specific parts we could nicely hide. When looking at SF4 and fiasco C, so they have the same control flow direction, so you have a blocking thread, a thread which makes a blocking source call to resume the VCPU. This makes for us life complicated because on GNOT we don't want to have blocking source calls. The kernels actually provide mechanisms that you can cancel this ongoing blocking source call, but we decided in the first take not to look in detail into it. So because it caused some headaches, how to get it nicely hidden on API level. And so the current workaround is that we spawn per VCPU you set up in the kernel also add extra handler thread in the virtual machine monitor. What does it mean?  While we are doing this, so that the entry point just can run the non-blocking call, the handler does actually the blocking call and that means immediately after this run this entry point is still ready to do something else, so it's non-blocking. For example, it can't just run another VCPU while it's the same thread. Regarding an IO event you want to inject, for example you have again a timeout, instead of the entry point on the API level you will make a port. Actually what now that's happening is that we go to the kernel and we have set up this asynchronous notification object on SL4, on Fiasco, it's an interrupt object and what actually happens is that this blocking call will be canceled. So that means here we pause, we immediately return the entry point is ready to do something else, it's non-blocking, which is good.  So with this look around we can nicely abstract this blocking call away. So now we have seen how we in principle get this harmonized, this interface. Now the question is how is the virtual machine monitors better we can actually run with a virtual machine on top. Of course you start first with just simple unit tests so you start with some simple instructions where you know that they will exit when you're instructed then you just check the control flow when this was working you add several vCPUs then you put several entry points on several CPUs and have multiple vCPUs running and getting this unit test running. After some while the Nova and Fiasco OC it was running quite nicely it was no big deal but as before we hit some issues. The first thing was more or less by accident we called this VM end of source call on a thread which has no vCPU attached and what happened the kernel folded just away there was a null pointer dereference in the kernel and the kernel died. So we patched this array notified the SO4 developers and they acknowledged it's a bug so it's not just that we did something wrong it's just a bug. The next issue was the test began running and we got our inwardly guest states of SO4 on Fiasco OC and Nova it was running fine but on SO4 it was not running fine. After some time we recognized we are running in 16-bit mode and we have no unrestricted guest support so the hardware has the support but the kernel does not enable it. So we looked through the input specification and enabled it in the SO4 kernel because we don't want to change the test just because SO4 can't do it. The next thing was when we had some specific case where a vCPU was just spinning and was not exiting and as soon as the thread becomes running the whole system starved blocked nothing happens anymore. So we added we have some top utilities where you see the utilization and afterwards that the top utility put to a high priority level and the vCPU below we saw that it's running on 100% the vCPU and all the vCPUs next to it on the same priority level was not scheduled anymore. So we looked through the kernel it must be a bug, we found the place so we reported this to the SO4 developer and they acknowledged it, yes, it's a bug. They missed some state checking in the scheduler. Finally, we were done. The tests were running, we were happy. Now we just wanted to wrap up and run our mobile tests on SLF4 and the kernel will just not boot on some machines and then we noted as soon as you enable this feature this kernel cannot be used on CPUs which has not VTX available. This is if you think about a general purpose OS where you want to use this kernel is it's quite not going to work because you don't know it's a target machine actually. So we patch this out because we don't want to provide several kernel compilations. So at the end of the day the Toyo virtual machine monitor was running on all three kernels. It also works on AMD on my private home machine but SLF4 has no support for this. So the next thing was actually we would like to run real virtual machine monitors, not the toy stuff. We have Zool and VirtualBox 5 as port. I decided for Zool first because it's much, much, much smaller than VirtualBox. If you run in trouble you can easily out the bucket of course. Mainly I ripped off all the Nova specific parts replace it with a new interface, got it running after some days on Nova and then the idea was now it must just run on SLF4 and Fiasco OC. It turned out no. It took me several days, which some ups to weeks to get it running on the one hand because I did things wrong. On the other hand there were difficult differences where I have some back ups life but I cannot go into detail now. The final conclusion was that we need a further patch for SLF4 and one tiny patch for Fiasco OC to get it running. At the end of the day all three kernels were running with the Zool virtual machine monitor. That means we have a Linux VM running with network even with SMP, but not for SLF4. As soon as we enabled SMP for the Linux guest the kernel just dies again with some fault in the kernel. This time I did not investigate it. The next step was actually we want to have the VirtualBox 5 virtual machine monitor running because with that you get support for Windows 7, Windows 10 Ubuntu, whatever you like to and this is currently working progress still. So VirtualBox binary is already kernel agnostic so it puts up the same compilation. It starts running on Lova quite fine for some simple genote VMs. I used genotes as VM because it is easier to debug for me if something goes wrong. For SLF4 it comes up to some point but something is still not correct but we will find out. Besides unknown remaining challenges are still that VirtualBox 5 port requires access to its FPU state. Lova has this access in principle which is currently missing in the virtual machine interface so we have still to edit. But for SLF4 and Fiasco OC I am quite not sure whether it is supported. For a quick look it does not look like this but maybe I am wrong. And on SLF4 actually there is no 64 bit guest support that means you will not get your Windows 10 running at all. So the final conclusion so in the beginning of my tour when I prepared the start of this work I was quite skeptical that's why my subtitle now it looks more like it could be possible of course there are some restrictions depending on the kernel you are using you should be aware of it and the roadmap now is that we will finish the VirtualBox 5 adaptation so getting all our VMs we are currently running on Lova back again so the same functionality and if we done then depending on the time you want to invest in SLF4 and in Fiasco OC we will also do this. When this then gets upstream the next idea is that our own kernel then it is the time to add to our own kernel also visualization extension for x86. And the same approach you in principle can apply to ARM or RISC 5 or this is quite optional. So the benefits of this work are that you get portable virtual machine monitors across the kernels and at the end of the day actually the genome user has the ultimate choice regarding the kernel so depending on the stability of the features of the kernel you can choose within some minutes you can choose another kernel and run the same compilation the same virtual machine monitor and the same VM on Gnode. That's all from my side. Thank you. Any questions? Yeah. Yeah. Yeah. For the Nova case it's not possible so your question is in principle, yeah I don't know the overhead but for example for the Nova kernel you cannot do this cross-core so it means that if you have a vCPU running on some physical scores you have to get a point on the same physical core. Yeah. Yeah. No questions? So the question was how did we find the box in SF4 and what was the post? And why it was not formalized by SF4. The actual point is that typically they don't verify everything or every configuration especially this virtualization extension for x86 they did not verify it but probably they will do and should do. Okay. Sounds good. Nice to hear. The question regarding the address spaces of the various components in particular in light of things like secure and complete virtualization from AMD and things that are coming like this where one is


Welcome to Access to Trader, the number one community for those who are committed to taking control of their trading in order to achieve success, profitability, and longevity. Thank you for joining us. Here's Dan Shapiro to help you find your edge, master your process, and own your future. Hey guys, good morning everybody. Welcome to another edition of theactionsandtraded.com weekend update show. Hope everybody is doing well. Hope everybody had a really good week of trading, a lot of great action. If you are brand new to the channel, like, subscribe, share, come aboard. Come aboard, spend some time with us Monday through Wednesday and on the weekend video. 15 minutes trying to give you an unbiased take of the equities markets on the day to day basis. No guessing, no opinions, just based on data collection and the relevance for the next trading day. That's it, not further than that, not beyond that, just for the next trading day. And if you look at the equity tape this week, a lot of things have changed from our last update on Wednesday. If you guys remember on Wednesday's session, you had Tesla come out with earnings as I was recording the video. This was before the Q&A session, the conference call, the stock was pretty much flat. And after the conference call, Elon Musk just didn't really give the shareholders a lot, or at least didn't give the traders and investors a lot of really big optimistic boom of this quarter. And the market sold off Tesla, right? Netflix came out with earnings. Subscribers rose by 8% because of the crackdown of password sharing, but they sold the stock off. Meta that had a huge run in the last several months, several weeks. News came out on Friday that their threads engagement since the launch is down nearly 70% on like 13 million viewers, 13 million subscribers, so that took a big dent. And the most important part is what we haven't seen in the NASDAQ 100 or the QQQs is we finally saw a week that was not only red, but we saw a week that not only did we lose the five-day moving average, which is the short-term sentiment, we lost the 10-day moving average. And if you are an avid subscriber to this YouTube channel or in the live webinar, or even follow me on social media, you kind of know the PS60 theory stems around the 10-day moving average, which is the birth of the trade, right? Five days, the short-term sentiment, but the 10-day is the birth of the trade, and it could spill out for multiple, multiple sessions. But we'll get to that in a second.  I don't think anybody is denying that even the biggest perma-bears, you know, have pretty much lost for words. And even if we do have a backtest this week into this, you know, 271 level, 371 level on the QQs, ultimately the bull market is still way intact for us to have a problem. Okay, for the bulls to have a problem for a longer-term timeframe, we would have to lose the 50-day moving average, which is 355. So we're still 20 points away from that. This week, you have earnings, the big numbers this week are from on Tuesday from Microsoft and Google. And on Wednesday, you have Meta, all the other ones traditionally been usually on the following Thursday. They're got pushed back. Apple got pushed back. AMD got pushed back. Amazon pushed back. And the video is like two weeks prior to that. So the big ones this week is going to be in the tech space. Tuesday, Microsoft and Google. And Wednesday, you have Meta, right?  But from our point of view, you know, my niche is the Nasdaq 100, the Beta names, the Megatap technology names. And this is kind of where we want to focus our attention. Last time we spoke, and this is kind of where we talk about, you know, speculation, right? Speculation. They were coming for three weeks. They were coming from the $300 calls. So you guys probably heard me talk about that in Nausium going into the earnings, the 300 calls, the 300 calls, the 300 calls. Well, the 300 call buyers got paid, right? They definitely got paid because the runner from the 300 call buyers was from like the 270s. And it went on, you know, went on what, on Thursday on, excuse me, on Wednesday to $299 and change. So I'm assuming they got paid out. The ones who didn't get paid out, I'm assuming what the rest of them did was, you know, sell their 300 calls and roll them over into the 330s, 340s, 350s, 360s that we started seeing towards the end of the week. Those guys obviously, you know, lost money.  Any time you're rolling up your contracts for the next series, you're taking the majority of the risk off the table because you're trading smaller and allocating a smaller quote, quote unquote, AKA House Money. So they'll be okay. But the market did sell Tesla, okay? And that's the most important part. You have to understand they did sell Tesla. You know, we had some great pivots the last couple of days of this week. We'll talk about the pivots in a second. We had some really great moves. Tesla closed below the 20-day moving average. You could see the last time it held the 20-day moving average was on June the 27th. We lost the 20-day moving average. We followed through yesterday on Friday. And you could see how much room you have left here. You have a lot of room left here to the possible 150-day moving average and the 50-day moving average. And when the stock has such a big run as we all know, a phenomenal one. Absolutely exceptional run. We traded to the long side. We traded to the short side. But now that we're below the 20-day moving average, we're going to watch this thing this week. It attempted a dead cab bounce on Friday. It actually went green and they sold it off into the close. I want to watch, obviously, Tesla this week. Is there a possibility you could have a dead cab bounce? Absolutely. If you were to get back to be long biased on Tesla, Tesla would need to reclaim at least 270 on the close, which would be the 20-day moving average. And to have overnight risk on, these are the numbers here, the 5- and 10-day moving average, you would need Tesla to reclaim 277 on the close. So those are my numbers going to this week.  What I'm looking for this week to the downside is a confirmation of this week's lows, right? That's what we're looking for. If the bulls start building below this week's lows, then look at which room we have. Again, the whole point of the PS60 theory is understanding that stocks trade from supply to supply on the upside and they trade from demand to demand to the downside. Well, here's your 20-day demand. It's below that. And the next demand is roughly around 243, 244. So there's a lot of room. Guys, stock closed at 260. There's still a lot of room for a good amount of value to the downside. But again, we have to see if the bulls can reclaim the 20-day or start losing back. Again, we're prepared on both sides of the market. Look at the queues. Here's kind of where we start the day. We start the week. The queues close below the 10-day moving average. And that is going to be a problem if the queues, if the bulls can't reclaim back to, let me see what the 10-day is, if the bulls can't reclaim back 377 on the close, well, the next demand is 371. And again, it's not a big deal. If you're an investor, if the queues go down another four points this week, they could just gap down four points. You're not even going to even feel it. But for traders, for the avid experienced trader or even inexperienced traders, just the trading and the intraday cycles that are active, you still have about four points of room to the next measure potential to 371. Where it gets very, very sticky for the bulls is if we lose 371 on the close. The way we lost the 20-day moving average on Tesla, that brown line, the way we lost the 20-day moving average on Tesla and continued lower, that's kind of where the bigger picture on the queue is going to be. If we start losing any close below 371 on the queues, that's where we have some pretty good measure potential all the way down to the 50-day moving average. But again, I don't want to put the cart in front of the horse just yet. Again, we're trying to play it day-by-day, trying to take advantage on both sides of the market. But going into Monday's session, if the bulls lose this 375, yeah, expect more downside on Monday. And that's exactly what we're planning for. I would say, you know, majority of my focus list is to the downside just to see because majority stocks close at the bottom of the range. Is it possible something wakes up this week? Absolutely. Again, that's the whole point of not trying to be right. You're trying to be prepared. That's the whole thing is why we try to be prepared on both sides of the market. But this was the first close below the 10-day moving average. If we start losing the 10-day moving average on Monday, yeah, we're going to have some more downside and that's not going to be good if you are a bullish trader. But again, if you're an investor, I think you will be okay. Just a matter of intervals that could be lost, whether it's right off the word go, whether it's right off the word go is worth throughout the day. But it's just super-duper important to kind of understand the dynamics of where we are in the retrospective of things. And we'll get to the pivots in a few seconds. Let's look at some individual names going into this trading week. You have Microsoft, again, held the 20-day. They are reporting on Tuesday. Watch the 20-day guys, right? I understand they had a great run on Microsoft and great AI news, all that stuff. But keep an eye on this thing below the 20-day moving average. Again, we just described, we just kind of showed the importance of the 20-day for the cues, what happened with the 20-day lost for Tesla. Watch Microsoft this week. If this thing starts losing the 20-day and the market bakes in its recent run-up on earnings, so who knows, maybe it could pull a Tesla, maybe it could pull a Netflix. Again, keep this in mind. This is what we talked about the whole time before Tesla's and Netflix earnings. The question was, was there moves, was there really bigger moves that they had in the last couple of months were going to be sold off into earnings, right? Were they baked into earnings so far, Tesla with their, even though they had their all-time highest quarterly revenues, it was due to price cuts, right? So it's, again, it's like winning the Tolle's Dwarf competition. No offense to any Tolle's Dwarf in the crowd. But the point is, we want to keep an eye on, is this going to be a theme, this earnings season for the really big run-up for the mega cab group, or is this going to be case by case? Let's see exactly what happens with Microsoft on Google when they report on Tuesday. But the 20-day from Microsoft is going to be a problem. Look at AMD, right? AMD lost its 100-day moving average, put it in an inside day on Friday. Now watch AMD this week, right? Keep an eye on this bottom channel. If this thing starts confirming and cues start confirming that 10-day, you're going to have more downside. You know, keep an eye on that as well. Look at a name like Metta, right? Look at a name like Metta. Metta, you know, had a great run. It lost its 20-day. The only thing that saved this was this linear regression line. If Metta starts losing this linear regression line this week, again, you have more downside ahead. So, you know, there's a lot of names that close below their channels. A lot of names close right above their channels. But the key is definitely the cues. Since most of these stocks mirror the NASDAQ 100, if the NASDAQ goes and your leaders go, you're going to have a lot more aggressive selling come in just because of the nature of gravity. Again, every single stock eventually gets pulled and no matter how wonderful. And again, I can't reiterate how wonderful this run has been on Metta and how wonderful this run has been on Nvidia and Microsoft and Apple that gave us the greatest gift in the world on Thursday and Tesla and everything else. Eventually, the gravity bug does pull in and you have to be naive to think that it's not going to affect you. So it's going to be very interesting to see Monday how the bulls handle what started out as an inside day. Primarily they were just kind of dead cat bouncing that we closed below. It actually didn't turn into an inside day. It turned into a resumption day from the 2% sell-off on Thursday's session. So it's going to be very, very interesting to see what happens this week. Again, I'm prepared for more downside. If it comes on Monday, if not, there's always going to be something that is lit up in the options market that is going to probably give us an idea of which way the market's going to go. So let's talk about some pivots from Friday. Really, really strong session. Congratulations, guys, especially Tesla. Tesla, we had a great pivot on this thing. Here is the pivot on... Let me just get rid of this. I opened up the wrong browser back in it. This was the pivot from Thursday. Remember, guys, Thursday there's no video. So here is the pivot from Thursday. 276 daily held and also held 714 lows for experienced traders. If it builds below, it can flush. Well, it flushed, right? It took down to 276 level. Traded all the way down to 261. Traded down to 261. Great, great trade. And then we took it overnight. 261 and 261 after our lows needs to confirm for more downside. And here is Tesla, right? Tesla took down every level. Took down to 76. Took down to 61. Traded all the way down to 255. I'm definitely watching the bottom of this range here from the June 30th bug, because if this thing loses that again, there's a lot of room to the downside. But Tesla's been awesome. Both sides, long, short. This has been a really, really great trader. Here is Metta, right? So I saw this news. Really early, right? Metta reported threads. User engagement fell 13 million, nearly 70% from the July 7 peak. Watch for selling. And I said, I don't think many people saw this. And the stock actually gapped up. And just like a lot of names. But 302, if it builds below, can flush. Here was Metta, right? Took down the 302, which has basically confirmed the 10-day. That's why we're watching the queue so intensely. It lost the 302, got all the way down to 91. Just a really, really big move. Again, congratulations for what you guys caught that as well. And that was kind of the theme for the day. AMAD didn't confirm. AMD didn't confirm. Queues confirmed on the close. 375, 72 is the 10-day. In case this gap gets pulled, which it did, it gets sold, it could bring in more sellers. And the queues put in its lowest close in this whole formation, guys, closing below the 10-day. Again, something to watch going into Friday. NVIDIA got hit as well. 450 held twice if it builds below, can flush. Here was NVIDIA, right? Here's the whole 450 area. 450 was the low on July the 14th. It was the low from Thursday. It took out to 450 and went all the way down to 441. They were coming for this week, this up-and-coming week for the 440 puts and the 430 puts. Just something to keep an eye on as well. UPSC number got down to 5340. Ruby, and again, this is where we talk about second entry, got above 2690. It only went up like 25 cents, and then it really aggressively went down. Netflix, another example of continuation from its earnings lows. 432, if it builds below, can flush more. And yeah, here is the flush. Here is the flush. It took down 432 as the previous day's low. It took down this whole channel and went all the way down to 423. Again, more downside ahead if the market doesn't rally. And that's it, right? And that's it. So going into this week, guys, very, very important levels. Watch that 375 area on the queues, because if the queues get pulled, so will everything else. If you are on the fence or want to try the PS60 theory, guys, click the link below. I think it's in the comments. Kyler has it pinned. Try it out for 30 days. Again, nobody trades these pivots on the whole planet. The way we do, it's a very, very specific niche that I kind of created in 2012. Everybody has their own kind of way of trading pivots. We trade it very, very differently than everybody else. So if you are kind of stuck in the mud or are looking for a little bit of an identity, there's kind of a break away from the quote, unquote, normal that you're used to. And if you are interested, come check out the webinar for 30 days. If nothing at all, it's going to give you a different approach how I view at the market that somebody's been doing nearly a quarter of a century. So maybe it'll give you a little bit more of a clue of what to look for in the market that you kind of haven't been exposed to yet. But anyway, guys, have a great, great weekend. God bless. Stay healthy. Stay happy. And God's help. I'll see you all on Monday. Take care.


Hi, my name is Steve Rosted, and this is my work desk. You can see I have two monitors. The one on my right is mostly for Red Hat work. The one on the left is for upstream work. The keyboards are, you have two keyboards for various computers that's all hooked to the computers behind me. On top of my desk, you can see a bunch of junk, books, my Red Hat, a penguin that my daughter made for me.  She passed away. Her name's Angel. That's why I have target dogs up here. They're bull terriers as well.  Computer books, personal books, books that are in German. Yes, that's Harry Potter down there. Right now I'm all in German. That's not English. Here's my cabinet filled with more junk. It's a mess. Yes, my office is pretty much a mess. So I try to clean it up three times a year and it's almost due for a new cleanup.  As I mentioned, my dog Angel, I gotta come up here and say she's here with me. I never had her buried. I had her cremated and put in a box. So she stays in my office with me, keeps me company. As I come back around here, here's my workstations with penguins on top of it. My main workstations, my fax printer, more old computers that I use to salvage. There's a test computer down there.  I buy a new one on Black Friday for really cheap and just kinda swap them around for backups. Power strips on the wall underneath. I have a daisy chained KVM switches. Below that, a power strip. And if you can see in the back there, that's a digital loggers web power switch that I could automatically turn on and off my machines. Remote control or actually through the network. Here's some more test boxes and some other boxes that are just used for spare parts. And more test boxes I have down there. It's actually my workstation for my red hat box over here. Junk on top of a cabinet. If you remember the old IBM slogan, you know, peace, love, Linux. I have, I got one of those a long time ago when they're about, they threw them out and I grabbed one from the garbage. Here's my embedded boards I have over there that I have attached to this little cheap, another Black Friday laptop that I use for the serial console that I connect through. There's another web power switch over there. Over here is my other desk. There's my Chromebook over there on top of it. And if I zoom outside my window and so that a focus, you can see my backyard. There's my dog. One of my dogs is out there. I don't know what she's getting into. Below here, hummingbird feeder. Haven't seen any hummingbirds lately, but they do come by. And I come all outside my office after I get frustrated, you know, doing email on the Linux kernel mailing list. I have ways to get rid of my frustrations, a treadmill with a TV in front of it, punching bags, a couple of them, more workout equipment. And here's my little dojo I have that I also come out here workout when I'm all frustrated with everything that's going on inside my office.  My little pull up bar that might come in. I do pull ups as I walk inside my office. And basically that's about it.


Alright, after you've made adjustments, you can fire next year round. Alright. It's a bit hard. You get it, man. You're gonna have a tight grip. Should we get it? Yeah, because it... Sorry, my bad.


Hey friends, today I am being sponsored by Boxlunch Gifts to show you a new Mickey and Minnie's Runaway Railway Pinset that's being sold through the Shop Disney app and also through Boxlunch Gifts.  So, let's go do this. I traveled out to the Florida Mall to visit the Disney Store and the Boxlunch retail location to purchase the pinset right here in Orlando, Florida. There are a lot of different Boxlunch retail locations but if you don't wanna visit a store like I said, you can buy them on the Shop Disney app. I've always been into pin trading but I've never actually traded the pins before. I always just get pins to keep. So I decided I wanted to come out here and just take a look at all the other Mickey and Minnie's Runaway Railway stuff that they have including this t-shirt. Look at this, they actually sent this to me to wear and I love it. This is really awesome. If you pull up the Shop Disney app, you're gonna be able to find the other set of this whole entire collection. This one has Donald on it, Minnie, and then also Pete. I love Pete, he's one of my favorite characters. You don't see a lot of merchandise with him on it and this is the other set. So if you buy the one through Boxlunch and the one through Shop Disney, it makes a full train ride and it's just so cool. I love Mickey and Minnie's Runaway Railway. It's definitely one of my favorite rides. I love the storyline and I love all the different characters that are in it. Once I get the pins, I'll let you guys know how you can enter the giveaway so that you can win them. They are super rare and they're only being sold through Shop Disney and Boxlunch. So hopefully I can get enough because I'd like to give out more than one. I've never been to a Boxlunch store before but I see all the amazing clothing and cool things that they have and I've always wanted to visit one so that's why I'm at the Florida Mall and I've never even been to the Florida Mall before so this is a day full of new things for me. I know I'm here specifically to buy the Mickey and Minnie's Runaway Railway pin set but they do have a lot of other amazing things and I can't wait to do a little shopping. Take a look at the window display here. Look at it, I love it. And then down here that's the shirt that I'm wearing right now. I really do like it. It's a very fancy shirt and it fits perfect. They have a ladies version there too. Wow, do they have like a Mickey cologne? I might need to be getting that as well. Lots of fun stuff. Hair ties, necklaces, I'm gonna like this. They have a lot of really cool things here and one thing I appreciate is the different licensing for Disney parks like merchandise. A lot of places can't really sell that stuff but here they can because they partner with them and they have exclusive rights to use like the name of attractions or even the parks themselves, you'll see. But you won't find that other locations where they can't say Disney World or Disneyland or they can't say like Tower of Terror or Mickey and Minnie's Runaway Railway and that's why I like this shop a little bit more. And the merchandise is just really cool. Look at Tiana's palace shirt right here. That one's very fancy. They even have lounge flies. Ooh, flowers got a bloom. That would be awesome for Flower and Garden Festival. And this is what I was talking about right here. Like a lot of places other than Disneyland or Disney World is where you can buy things that say Disneyland Resort. So look at that. I really like this. I wonder how much this is. Oh, it's only $44. In the parks that would probably be $65. Ooh, a lot of really good stuff. Here is the Mickey and Minnie's Runaway Railway merchandise line and they have a lot of good stuff. Look at this, oh boy. Look at that. I like this a lot. And they have my shirt that I'm wearing. They also have a lady's shirt that, oh, I really can't show you. Oh, they have a mannequin with it on. So I'll show you afterwards. But what we really wanna see are the pins. Look at this. We got Goofy in the train. We've got Mickey, Pluto, Daisy, and these all connect. And these are actual Disney pins. And they're $12.90 a piece. So you can buy the whole set of them. This is gonna be really fancy. Mickey and Minnie's Runaway Railway is one of my favorite rides because it's the first ride that's solely or surrounded around Mickey and it's such an adventure. I love watching Pluto trying to catch up to them because they leave Pluto behind so he's constantly on the run to catch up to Mickey and Minnie on their little adventure. And I think it's such a cool storyline. I also like the Pixar things they have here. Adventure is out there. A lot of up-merchandise. Up is really one of those movies that, it's kinda like a classic and it's probably the saddest Disney movie I've ever seen. I mean, I don't know of any other sadder movies. Maybe Bambi. Ooh, but I do love this pizza planet truck. Like, not truck, the pizza planet jacket. It's like the delivery driver's jacket. Wow, that is awesome. How much is this? Oh, this is $59.99. That's the price of a spirit jersey. You can get a whole jacket. They also have a nice Alice in Wonderland section and these flannels are actually really popular and it says, do you suppose she's a wildflower? That is so nice, isn't it? Also, they have like a spirit jersey type with the Queen of Hearts. I like it. They also have a really nice Nightmare Before Christmas section. I love Jack and this is really cool stuff. It doesn't like look like the normal Nightmare Before Christmas stuff either. It's fancy. It's very fancy. Like I live, how they have like, just the way that it's designed. Halloween Towns National Park. Halloween Town National Park, simply meant to be. But now I think we're just gonna buy our pens and actually move along. I'm very excited. I wanna hook them all together and see what they look like. That'd be really fun. You can buy the pens individually if you want. So if you're just a Mickey Mouse fan, you can just get the Mickey one or you can buy them and they have them all like pre-packaged for the set. Look at that, it's fancy.  I really like it. And it's almost just under 50 bucks for all four of them. So it's a very cool deal. Limited release. Look at Daisy. She's peeking at me. Look how fancy that is. I love it.  The total for the set of four pens came to $41.22, which is really good deal. I ended up getting three sets and I'm gonna give them away to you guys.  If I select you as a winner, I'm just gonna mail the pens out to you. And if you wanna enter, you just have to like this video, comment on this video saying my favorite pen is and just let me know what pen you would trade for this. And like I said, you don't actually need to send me those pens. And I will use a random comment selector to pull out the three winners and then I will get your information. I can message you on Instagram or on Facebook or if you reply back to my comment, then that's how I'll get your information and we'll send them out and you'll be the proud owner of a nice set of Mickey and Minnie's Runaway Railway Pinsets. And they are really, really fancy and I like how they all connect. So like they connect with these little hooks right here. And I think I know exactly where this train is going. Nothing can stop us now. I'll tell you how we're gonna make it happen. Let's take a ride and spend a day in the countryside. I can't think of a better way to celebrate the new pen set than taking them on a ride on Mickey and Minnie's Runaway Railway. Sounds like a really good idea. Bum, bum, bum, bum, bum, bum, bum. Thank you. Welcome over folks. We're already worried we're actually flying around the course. Everyone to your positions. One, two, three. One, two, three. Oh, excellent.  Now, let's... Nothing was gonna go wrong. That's gonna do it for me. Thank you so much to Boxlunch Kiss for actually giving me the pens and sponsoring this video. And I hope you guys win them. And I'm gonna be so happy to make sure they go to a good home. I really like them. I think they're really cool. I have a set for myself that I'm gonna keep and probably never trade. But I wanna give those three sets to you. Like I said, just like this video. Leave a comment letting me know what your favorite pen is. And good luck. So I hope you enjoyed the video. I enjoyed making it. We will see you next time. Nothing can stop us now.


All right, I just got to do that three more times. I think it's three more times Those definitely take a while 50 V bucks It's kind of funny a lot of battle royale players play this for the V bucks That you can spend in battle royale birthday stuff ends tomorrow at 3 a.m. Eastern so in about In about ten hours probably nine hours now You got about now. Yeah, you should get on that try to get at least a couple of birthday llamas before they go away Yeah, Fortnight celebrating their first birthday and They're having a special event and this birthday llama has some good stuff in it like the guy my main guy I'm using I got from a birthday llama He's arguably the best class in the game urban assault I Got him from a birthday llama. So I should be able to Get these squares now. No, that's Require a storm shield defense seven. Oh, no Well, I didn't know that I should have looked at that first Because I could get these guys But I don't ever do close assault. That's why I don't really bother with this bottom half of the tree Like I don't do ninja Maybe the slow field. I don't know How do you get birthday llamas? You get tickets they're called road trip tickets and And Several missions So you can find some Offer them as rewards a lot of daily quests. I think offer them as rewards. Let me see No, not the dailies Oh Yeah, okay. So on the maps, there'll be a bunch of cakes this one if you find five you get a hundred road trip tickets So that's one way and I've been randomly getting road trip tickets just by doing stuff So once you get enough road trip tickets you go up to the loot tab and It's kind of hard to find it's an event tab right here It's not obvious like people go to story like where is it? Where is it? If you go to loot and then click event Then you'll see Not here, I'm sorry if you go to I was thinking about something else birthday llamas what you're talking about I'm confusing him birthday llamas what you're talking about. It's right here. So once you get enough tickets You can buy one of these I have 335 and I'm trying to get another one. I may not But essentially the best way you can do it. I think it's just when you go and maps look for those cakes big giant cakes And press E on them All right, so I have to do this What? That didn't count why didn't that count I did play now from this I'm still three out of six on it. That's weird. I didn't get credit for that. Yeah, my wife likes it She was the reason why I was so upset with the epic because they really They banned her account her first account because she had got pretty far in the other count During a band wave. It was like a false positive on a lot of cheats and she was doing pve and they banned her for cheating and Basically ignored all tickets and everything and that was a founder's account We pay for that account a founder's account, right and They banned the account and I was mad with them For a long time because they just ignored all tickets. They didn't they didn't even do anything about it They just said she was cheating. I'm like in pve No So and her account didn't get hacked we verified that it didn't get hacked So they just left the loan and eventually she forgave them. I Didn't it took me a long time to forgive them, but she eventually forgave them Because it made her upset and when my wife gets upset I go Hulk So the She forgave them and Ty zoom Hooked her up with another account He had a key for another count and she started playing that he had a One of those keys that you get with the founders. He had managed to get one And I gave it to her and that's the account she's using now Yeah, I DM them as I posted on Twitter and I was talking with them to DM I gave them the ticket number and everything Defining silence So it wasn't a pleasant experience and they have done more than one false bandwave. It was just like You're logging one day your band like what in the world is going on and I told her to just forget the game put it down. It's like don't even work like there's there's so many other games out there That's what I kept saying to her. I was like, there's so many other games You don't have to play this and she really likes the game as you can tell so She eventually talked me into giving them more money, which I didn't want to do I Really here's a birthday cake. So you find these they're blue exclamation points on the map You find five of these And you get a hundred tickets Why's this guy down? I guess I should get over there and help him, huh? Yeah, so we upgraded her free account to another to Standard Founders and then we eventually gave more money. I gotta just stand in there Man, I join this really late, but all this forgiven You probably you haven't heard me say anything bad about epic in a long time. So I Think that was handled really badly though This is a nice wood structure, sir They claim they did fess up. They said they were fixing the accounts and they went and unbanned a lot of people But they didn't unbanned her account. Yeah, she was uh, she wasn't unbanned in the unbanned wave But they did fess up that it was a false positive wave Okay, that's interesting. I don't know if I want to stay here. This one guy is just AFK I I don't think it's gonna kick him He's going to get credit for this Hopefully it's just Jimmy taking out the trash. Let's put the wood to use I guess Can't get to the inside walls yet. I'm down for a wood challenge. All right. Let's get a gun that I crapped it. Yep. They guys AFK. I'm gonna try to finish anyway. I mean do my best Plus there's a cake on the way over the Seabot Hey Two birds get it two birds chat two birds one stone. Are we under attack? That was going to Seabot. All right cakes past Seabot. You walk. Oh him goodness Seabots dead chat He's gone. I'm going for the cake. I'm going for the cake cut the cake Bye Bye miss my precious I What's up Zephyr welcome. Do I have any more ceiling traps? One do it heal No Leave him alone Not the eye Ah You can't touch him What? Tarnation that's going on here. Hello. It's you. Do you play battle royale too? I Do not Do you have the pumpkin launcher? I probably don't Soon as if I've been away from the game for my long for a long time. I Don't have a lot of the event items. I got this thing from the From the birthday llama. Why is that a health going dude?  Just fix it. That's right. I'm upgrading things Wait Seabot Go for Seabot What's up kids love ninja? Mmm? Watch that step Wait, do I want to revive here? Probably do I want to get out. I want to get away. I Want to fly Away. No, that was it Why it please Help Seabot was neon a quest reward. What is neon what I have on?  Oh, okay. Yeah, I don't have those Is this my first game as in the first time I've ever played No, I'm level 24, dude. It's I'm in Plankerton If you could do that your first time playing that be very impressive Yeah Wait, what's this icon? That a module Right What up? I probably should have waited on that lot the dot dot dot. This is a long mission. I Remember when I first did this I hated it That's a while ago. Oh These dudes. Hello Yeah, dude, I'm only in Plankerton. I haven't gotten past Plankerton yet I got this hero from a birthday llama People see this hero and they probably think I'm advanced because he's like one of the best in the game Urban assault, but I got it. I got it from a birthday llama like four days ago So I'm very very very new dish and my wife gave me a bunch of guns for those moments She gave me a bunch of nocturnals and some typewriters. I have a desk stalker Wait, that's my desktop And I'm using a dragon's roar. She gave me that last night So she's giving me some guns to help me out look at this Monstrosity thanks brief of the lutes Some do for your party should get a new mic You can hear him. I don't hear anybody in my party What are you hearing? That's the wind blowing from the storm man. Oh Like what are you talking about? Oh, don't ask that question. No, no, that's just inviting all kinds of just fire Just like my mouth will open and all these flames will come out Are you always this stupid? Oh, yeah, you know, I just oh my gosh. That's too easy, man You can't make it that easy. You can't make it. You gotta you gotta you gotta let us at least try All right, what are we gonna do? Okay, it's installing the last module. I think we're almost done Holy crap, what a mission I Think I'm just gonna pick mine from now on I've been clicking that play now button and just letting it choose I Still feel burned after not finding the download button and dollars I Forgot all about that.  It was like download new. I missed all those guys. You didn't see that It was so huge.  I'm like, are you kidding? Is this a joke? I was like, is this a joke? No Find it.  Everybody Thank you, sir. Nope. It's a bad throw.  That was supposed to be X I'm gonna win MVP for the best nades ever. Why thank you. That's so nice My chat is so nice nice people's Victory Then break two million XP Not that I don't even know what that means The timing though. All right guys, we're gonna take a break be back in three minutes Thanks for watching feel free to follow less stream if you enjoyed the love self Twitter comm slash one click the follow button at the top make sure click the notify button when I go live Otherwise, you won't know when I go live. I'll be back in like three. I Don't have anything to refill.