New
#31
yes, QEMU can run your vm completely from user space, no installation required. However, it's very very slow in this mode. To get it faster, you will need QEMU Accelerator, which is a kernel driver and again requires installation.
Another thing about QEMU is that it lacks guest addition support, so the vm and host integration is not smooth, for example,you will have to capture/release mouse. There is no folder sharing, etc.
Even with the XP mode or SUN's Portable VBox you still see the mouse captured while the exit method changes for each one. With the XP mode the alt-Tab key combo and for the PVBox you simply press the ctrl key to exit there.
no, you don't. When the guest tools are installed, you can move mouse smoothly across vm Window and host Windows. The vm is like another native application. Perhaps, you haven't installed the guest additions if you need to press Ctrl key to release. QEMU does not have any of guest additions to install.
interesting i see this this being somewhat difficult to achieve while at the same time have the same speed as some of the vm software such as vbox (with additions installed of course) and vmware (with its tools installed)
that is great news...
my question though is what image are implying as your standard image
meaning is the standard image is vdi (the standard image for VBox) or would it something different with a new feature set?
so are going to implement some sort of acceleration driver/toolset so you can get the same speed as VBox and others?
It depands on what you are running on the MS Virtual PC there. Besides the XP mode I already have 7 running following an replacement upgrade from the previous Vista installation on the same vhd.
The XP mode so far is the only one where you can simply slide the cursor across the screen. The rest simply capture that as part of the process.
oh, I see. You are absolutely right. I only played with XP mode. Seems XP mode is using RDP trick for the smooth mouse movement. There is no guest tool inside virtual PC doing mouse integration.
Thanks for your points.
Back a few years ago, we started to implement an OS container for Windows apps. So a group of apps can run on windows within a separate context with their own registry and file system. In this model, the same OS instance is used, and thus achieve native performance. The downside of OS container is that it does not fully isolated from host OS. For example, a kernel driver crash will bring down the whole system. This drawback made us to look at system virtualization. We then started to integrate our OS container with a system virtual machine. Yes, it's very difficult. However, this integration will bring many benefits, we will gradually release the features.
With our converter, you can select an image format, we support vmdk, vdi, vhd and parallels format, these are the major vendors out there. With these formats, our converter does its best to make the disk bootable.
We use VBox OSE for the system virtualization layer, plus our own guest tools.
VBox could use a little access to physical drives as well as the particular it goes on. The same could be said for a custom install on a vhd run on the Virtual PC simply being limited to the dvd drive there. The XP mode provides full accesss even for usb drives/devices with the latest RCs.
We are implementing a powerful physical to virtual machine (P2V) converter, called "MyOldPCs", that can generate all popular formats (.vmdk, .vdi, .vhd, .hdd) and bootable in major vm vendors.
I'd like to get some inputs on whether need to support Windows 95/98/NT. Anyone here still have old computers with thos OSes and worth converting them to a vm?
Thanks,