Description: QtEmu is a graphical user interface for QEMU written in Qt4. It has the ability to run virtual operating systems on native systems. This way you can easily test a new operating system or try a Live CD on your system without any troubles and dangers.
For more information see the included README file (e.g. install instructions).
Qt 4.1 is required.
I have planned a version which integrates in a KDE4 desktop (build on kdelibs 4).
Please report any problems or feature wishes! Thank you.Last changelog:
Features: * Option for custom network settings. Patch by Dawit Alemayehu. Thanks! * Possibility to set additional options which are not covered by QtEmu (e.g. "--kernel-kqemu"). Patch by Dawit Alemayehu . Thanks! * Sound configuration. * Poslish translation by Milosz Galazka and Grzegorz Gibas. Thanks! * Brazilian Portuguese translation by Jackson Miliszewski. Thanks! Fixes: * Code optimization (Mosty detected by KDE Krazy check). * Initialize all variables in machineprocess.*. Patch by Dawit Alemayehu. Thanks!
very friendly and intuitiv front end.
encontred problem: I was not able to connect my real CD (amovable CD like in laptops) probably because of the new address management in kubuntu jaundy.
possible amélioration
indicate where the setup files created by QtEmu contain the selections
thank you
Hi,
qtemu is really nice, but there are still a lot of features missing.
Disable kvm
Network card selection
VLAN support
Sound support
SMB dir support
It would be great to see these features soon.
Thanks
What about the old Kqemu/KRDesktop project at http://kqemu.sourceforge.net/ ? That tool, even though it was marked as "0.3alpha", works fine since 2005... a joint effort might achieve more than 2 separate projects... (but, alas, maybe not).
What about the old Kqemu/KRDesktop project at http://kqemu.sourceforge.net/ ? That tool, even though it was marked as "0.3alpha", works fine since 2005... a joint effort might achieve more than 2 separate projects... (but, alas, maybe not).
It is not possible to add any options to this command line (i.e. to work around some things as of yet not implemented such and -soundhs, etc.
So the program is not simply concatenating its command line options to the text here. Seems it should or could.
Yes, one might have a text edit field for additional command line parameters.
(Indeed, one might do this for each VM (unless most things like -kernel-kqemu, special networking options and such are implemented in the GUI)
This is nice looking, trying to be more like virtualbox and other such interfaces than the usual qemu GUIs.
A few quirks:
1. Selecting device from /dev is wierd. OK, most likely recognizing the not-so-nice qemu-fact that if a floppy or CD is not in the drive selected, qemu will not run.
2. Sound. Qemu will emulate a sound-blaster or en1370. Need pane for this.
3. Networking has options, to be implemented I suppose. Simply worked as-is.
4. SHM (insist on it?)
5. kqemu,ko. Yes (if modprobed), no, enhanced (only for linux guest but makes a big difference).
6. Important question: If I am using an image or iso already created, what is the function of the MyMachine/OS/Os.img? Initial snapshot? Possible "nest" for Knoppix or Dynebolic? Option to use mine instead?? Qemu will allow multiple hd "drives" so you might implement as well.
7. USB Tablet? I do not have one. I have a Roland UM1 Midi interface plugged in, no others. Are you running the mouse using this tablet to get it seemless? Would explain all the mouse results (see below). Option not to use this?
Results:
At first, Win98 did not run. Starting adding new hardware already on my image, found driver (USB Tablet) on non-existant D: drive!!! Soon simply stopped. At this point, seemless mouse worked!! Reran, cancelling that driver. Now win98 worked but not seemless mouse.
Dynebolic boots up much slower than in virtualbox so kqemu may not be (fully) utilized. I had successful runs with Dyne 1.4 previously in qemu but 2.* would not run. Knoppix's KDE would not come up either. Both of these work beautifully in VirtualBox.
ReactOS ran and so did Haiku (BeOS). Choosing seemless mouse rendered the mouse inoperative in both of these!
Thanks for your points. I'm going to comment some:
4) Cannot understand.
6) The created image is the default first harddisk. You can change it of course to an already created image.
4. One of the other GUIs had a check for share memory. In fact, I made my shared memory larger to enable larger qemu sessions. There is no qemu command line parameter for this so I guess it is default.
Hi,
perhaps you should write somewhere that Qt 4.2 is needed.
I tried to compile it with Qt 4.1 and got this error:
wizard.cpp:58: error: ‘class QLabel’ has no member named ‘setStyleSheet’
setStyleSheet() is included in Qt since version 4.2
HI,
Your work looks great. But I think to make it more usable some more important features need to be implemented first.
a) Network - The network part in the current UI is very bad. Probably you could try something similar to what VMWare has.
b) There's no add-on image option. Qemu can support multiple images. -fda, -hdb and many more. To test legacy and alpha OSes, there workaround are really needed.
I think this would be the right time for you to push qtemu more. At this moment qemu has all core features:
a) kvm
b) kqemu
c) qemu itself.
What it badly lacks is:
a) A good GUI
Thanks for your comment.
Most of these features should be quite easy to implement. I'll to them on my TODO list, but my time is at the moment a bit limited to work on this project.
Fell free to do it by your own (it's mostly only copy-past-edit work). You can send me the patches and I'll include them in the next release.
edo@darkstar:~/dataku/Linuxapp/qtemu$export QTDIR=/opt/qt4/
edo@darkstar:~/dataku/Linuxapp/qtemu$qmake
qt_config.prf:8: Unknown test function: debug
qt_functions.prf:1: Unknown test function: defineTest
Error processing project file:
QFile::open: No file name specified
QFile::open: No file name specified
qt_config.prf:8: Unknown test function: debug
qt_functions.prf:1: Unknown test function: defineTest
Error processing project file:
QFile::open: No file name specified
QFile::open: No file name specified
qt_config.prf:8: Unknown test function: debug
qt_functions.prf:1: Unknown test function: defineTest
Error processing project file:
QFile::open: No file name specified
QFile::open: No file name specified
qt_config.prf:8: Unknown test function: debug
qt_functions.prf:1: Unknown test function: defineTest
Error processing project file:
QFile::open: No file name specified
QFile::open: No file name specified
qt_config.prf:8: Unknown test function: debug
qt_functions.prf:1: Unknown test function: defineTest
using slackware 11
Ratings & Comments
36 Comments
good property and try to use
very friendly and intuitiv front end. encontred problem: I was not able to connect my real CD (amovable CD like in laptops) probably because of the new address management in kubuntu jaundy. possible amélioration indicate where the setup files created by QtEmu contain the selections thank you
$ qmake fails ? then try: $ qmake-qt4
qemu internal network setup http://blog.cynapses.org/2007/07/12/qemu-kvm-internal-network-setup/ Support for such things would be really nice!
Hi, qtemu is really nice, but there are still a lot of features missing. Disable kvm Network card selection VLAN support Sound support SMB dir support It would be great to see these features soon. Thanks
Thanks for your comment. In the next days I will release a new version of QtEmu. Some of your requestest will probably be in the next release.
What about the old Kqemu/KRDesktop project at http://kqemu.sourceforge.net/ ? That tool, even though it was marked as "0.3alpha", works fine since 2005... a joint effort might achieve more than 2 separate projects... (but, alas, maybe not).
The problem is that nobody is working anymore on kqemu for more than one year. Also it is written in a different language (Kommander; QtEmu in Qt4).
This tool is really nice, however, I miss a feature for configuring bridged network-connections. Would be perfect with it. Good work!
What about the old Kqemu/KRDesktop project at http://kqemu.sourceforge.net/ ? That tool, even though it was marked as "0.3alpha", works fine since 2005... a joint effort might achieve more than 2 separate projects... (but, alas, maybe not).
I created a Gentoo ebuild and posted it at their Bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=184112
It is not possible to add any options to this command line (i.e. to work around some things as of yet not implemented such and -soundhs, etc. So the program is not simply concatenating its command line options to the text here. Seems it should or could.
I'm not sure if I have understood your comment right. Would you like to have a text edit field to enter some additional qtemu commands?
Yes, one might have a text edit field for additional command line parameters. (Indeed, one might do this for each VM (unless most things like -kernel-kqemu, special networking options and such are implemented in the GUI)
Ok. It will probably be point of one of the next releases. ;)
Are you thinking in add Qtemu-ppc features yo your amazing application?
Not yet. I have only an Intel based MacBook.
This is nice looking, trying to be more like virtualbox and other such interfaces than the usual qemu GUIs. A few quirks: 1. Selecting device from /dev is wierd. OK, most likely recognizing the not-so-nice qemu-fact that if a floppy or CD is not in the drive selected, qemu will not run. 2. Sound. Qemu will emulate a sound-blaster or en1370. Need pane for this. 3. Networking has options, to be implemented I suppose. Simply worked as-is. 4. SHM (insist on it?) 5. kqemu,ko. Yes (if modprobed), no, enhanced (only for linux guest but makes a big difference). 6. Important question: If I am using an image or iso already created, what is the function of the MyMachine/OS/Os.img? Initial snapshot? Possible "nest" for Knoppix or Dynebolic? Option to use mine instead?? Qemu will allow multiple hd "drives" so you might implement as well. 7. USB Tablet? I do not have one. I have a Roland UM1 Midi interface plugged in, no others. Are you running the mouse using this tablet to get it seemless? Would explain all the mouse results (see below). Option not to use this? Results: At first, Win98 did not run. Starting adding new hardware already on my image, found driver (USB Tablet) on non-existant D: drive!!! Soon simply stopped. At this point, seemless mouse worked!! Reran, cancelling that driver. Now win98 worked but not seemless mouse. Dynebolic boots up much slower than in virtualbox so kqemu may not be (fully) utilized. I had successful runs with Dyne 1.4 previously in qemu but 2.* would not run. Knoppix's KDE would not come up either. Both of these work beautifully in VirtualBox. ReactOS ran and so did Haiku (BeOS). Choosing seemless mouse rendered the mouse inoperative in both of these!
Thanks for your points. I'm going to comment some: 4) Cannot understand. 6) The created image is the default first harddisk. You can change it of course to an already created image.
4. One of the other GUIs had a check for share memory. In fact, I made my shared memory larger to enable larger qemu sessions. There is no qemu command line parameter for this so I guess it is default.
Hi, perhaps you should write somewhere that Qt 4.2 is needed. I tried to compile it with Qt 4.1 and got this error: wizard.cpp:58: error: ‘class QLabel’ has no member named ‘setStyleSheet’ setStyleSheet() is included in Qt since version 4.2
You are right. I'll add a notice for the next release. Thanks.
HI, Your work looks great. But I think to make it more usable some more important features need to be implemented first. a) Network - The network part in the current UI is very bad. Probably you could try something similar to what VMWare has. b) There's no add-on image option. Qemu can support multiple images. -fda, -hdb and many more. To test legacy and alpha OSes, there workaround are really needed. I think this would be the right time for you to push qtemu more. At this moment qemu has all core features: a) kvm b) kqemu c) qemu itself. What it badly lacks is: a) A good GUI
Thanks for your comment. Most of these features should be quite easy to implement. I'll to them on my TODO list, but my time is at the moment a bit limited to work on this project. Fell free to do it by your own (it's mostly only copy-past-edit work). You can send me the patches and I'll include them in the next release.
edo@darkstar:~/dataku/Linuxapp/qtemu$export QTDIR=/opt/qt4/ edo@darkstar:~/dataku/Linuxapp/qtemu$qmake qt_config.prf:8: Unknown test function: debug qt_functions.prf:1: Unknown test function: defineTest Error processing project file: QFile::open: No file name specified QFile::open: No file name specified qt_config.prf:8: Unknown test function: debug qt_functions.prf:1: Unknown test function: defineTest Error processing project file: QFile::open: No file name specified QFile::open: No file name specified qt_config.prf:8: Unknown test function: debug qt_functions.prf:1: Unknown test function: defineTest Error processing project file: QFile::open: No file name specified QFile::open: No file name specified qt_config.prf:8: Unknown test function: debug qt_functions.prf:1: Unknown test function: defineTest Error processing project file: QFile::open: No file name specified QFile::open: No file name specified qt_config.prf:8: Unknown test function: debug qt_functions.prf:1: Unknown test function: defineTest using slackware 11