| tres said: another thing about the hyper v is that if a game developer wants to use up to 7.5 gigs if the os is under 512gb they can. in most cases those apps will be very small so anyway. |
No. MS fixed the amount of memory that the devs can use... it won't be dynamic.
| Adinnieken said: I'm waiting to hear official numbers on the OS before I suggest any memory usage. The implication that the OS uses 3GB (1GB per each OS) is ridiculous, imho. I think the OS actually uses very little, but probably close to 2 GB is reserved for the display (GPU). But yes, the HyperVisor OS is capable of allocating resources based on need between the two VMs. The system is even designed to throttle up or down cores and memory as needed. So if you're just watching a movie, the system can throttle down to next to no processing power, but if you receive a Skype call during that movie, it could throttle up the resources needed. |
HyperVisor yeah... can do that.
But MS is locking resources for each VM because the App VM can't take recourse from Game VM or vice-versa.
A lil off-topic but can you use your kinect as a facecam for twitch? That'll be useful
ethomaz said:
No. MS fixed the amount of memory that the devs can use... it won't be dynamic. |
where did they say that. hell where did they even say 3 gb were going to be used for the os. that defeats the purpose of hyper v. that makes it just v
| papamudd said: Hmm this sounds like the os would definitely use more ram than less ram. Another thing is that it sounds potentially harder to capitalize on the hardware as well, and potentially more secure/ harder to hack |
The HyperVisor OS would require some overhead, to run the service but not 2GB of memory worth. HyperV (the HyperVisor service) requires 512MB of memory to provide all of its services. The general rule of thumb is 32MB for the first 1GB of RAM for the virtual machines, and 8MB for each GB thereafter. That's on top of what the base OS would require, which shouldn't be that much considering the limited focus of the console (versus a PC).
The Xbox OS likely is small. Very small. The Apps OS is probably no more than 512MB, when running. The HyperVisor OS would likely consume something in the neighborhood of 1GB. Memory is handled dynamically between the OS and VMs, so based on need the HyperVisor OS would throttle back one to give resources to another. So if you were playing a game and decided to take that Skype call in a Snapped window, the HyperVisor OS will reduce the available memory for the game to provide what the Apps OS needs.
This isn't even a postulated feature, this already exists with the HyperV service on Windows Server.
Virtualization of the hardware shouldn't have any impact on capitalizing on the features of the hardware. Well, unless a particular feature isn't virtualized. Virtualization has proven extremely successful in the corporate IT world. So much so that you can emulate systems via virtualization.
However, you are absolutely correct that it would make it harder to hack. The user has no direct access to the hardware via the HyperVisor OS. They have access to the virtualized hardware through both the Games OS and Apps OS, but not the HyperVisor. When you insert a game disc, it's the virtualized Blu-Ray drive in the Games VM that's accessing it. Or if it's a Blu-Ray/DVD movie, the Apps VM that is. At best, a hacker might get access to the Games or Apps VM, but the HyperVisor OS has a couple more tricks up its sleave.
The HyperVisor OS shadow copies the VMs. If at any point unauthorized software is stored and run on the VM, the HyperVisor will restore from the shadow copy. Your profile isn't a part of the VM, so the shadow copies of the VMs is actually pretty small. Bottomline is, if you could get on the hardware, you wouldn't be able to last very long.
| Netyaroze said: Snapping this is the same feature as on Win 8 tablets I guess. |
Similar.
In simple terms, snapping is putting an app on the edge in a fixed amount of space. 1/3rd of a screen on the Xbox One, 1/4 of the screen on Windows 8. On Windows 8.1 snapping is no longer fixed. You can make the app any size you want with up to four apps on one scree (for large resolution monitors).
Behind the scenes though, Windows 8 is simply running two apps concurrently. On Xbox One, it's running two virtual machines (virtual computers) concurrently. The latter would be akin to running HyperV on your Windows 8 computer with an application running in it, snapped to the desktop.
Mistershine said:
|
That is a great point.
ethomaz said:
HyperVisor yeah... can do that. But MS is locking resources for each VM because the App VM can't take recourse from Game VM or vice-versa. |
There is no indication that Microsoft is locking resources. In fact Marc Whitten, in a post Xbox One launch discussion, mentioned the fact that the Xbox One will be able to dynamically allocate resources.
ethomaz said:
HyperVisor yeah... can do that. But MS is locking resources for each VM because the App VM can't take recourse from Game VM or vice-versa. |
Where did you see that? I must admit that I did not read a lot on the internet lately (was busy); if Microsoft released this information , I missed it :(
I was believeing the opposite actually, so this is really surprising to me.
|
Imaginedvl said: Where did you see that? I must admit that I did not read a lot on the internet lately (was busy); if Microsoft released this information , I missed it :( I was believeing the opposite actually, so this is really surprising to me. |
Why? Game resource have to be same, all the same, to all developers... can be dynamic in any console... what happen if the OS VM consume part of resources of the Game OS... you can't do that.
MS already confirmed the Game VM will have 5GB available... no more, no less... always 5GB.
Xbox One uses 6-Cores of CPU, 5GB RAM and 90% of GPU for games
About Us |
Terms of Use |
Privacy Policy |
Advertise |
Staff |
Contact
Display As Desktop
Display As Mobile
© 2006-2025 VGChartz Ltd. All rights reserved.
