QEMU: Virtual Machine Manager (Part III)
After proceed the last 2 previous articles, now I have a Windows XP emulated over QEMU. In my situation, - I explained again that - it was running with Acer Travelmate 6291 on Linux Fedora Core 7. After last step process, it now should be restart automatically. If it is not, get started manually by pressing Run button on main panel of QEMU.
Now, let's take look at inside of the system emulated hardware. What it displayed on system properties window? For somehow, QEMU interpretive that the system is currently running on Intel Pentium II processor with 39.05Ghz of speed. What a confused display. This is the reason why that the installation process was established (a very) slowly. I couldn’t figured out why it happened.
Anyway, the dual virtual processor logic was displayed correctly. Also the system RAM 256MB was dedicated as so as well.
From Device Manager window, some hardware was detected improperly. The real Mobile Intel 945GM/GU Express chipset family detected as Cirrus Logic 5446 compatible graphic adapter. While the Matshita DVD-RAM UJ-850S are known as QEMU CD-ROM. The laptop are not equipped with floppy drive, but it was emulated not in that way. Broadcom NetLink Gigabit Ethernet detected as Realtek RTL8029(AS) based Ethernet Adapter (Generic).
Summary
After using Windows XP emulated over QEMU for some couple hours I found that the system was running somehow not too stable than it emulated over VirtualBox. For several times it displayed the blue screen errors containing of different unknown problems & sometimes, the system got locked up. The built-in touchpad also act weird. I could not tested further by implementing networking device or installing applications since it has not enough space & the systems runs too slow. This last part articles finished, I suggested to considering using VirtualBox than using QEMU built-in from Fedora Core 7. Hope that soon QEMU will developed more reliable than other VM to support the future of virtual machine.
Labels: My Share
| PS: If you've benefit from this blog, you can support it by making a small contribution. |
Saturday, February 16, 2008 8:06:00 AM
It looks like you don't understand what emulation or virtualization is. It detected the correct hardware, and you need to make sure KQEMU is running or else it's just emulating and not virtualizing. Emulating is more than an order of magnitude slower.