GNOME Bugzilla – Bug 754436
ReactOS do not work in boxes
Last modified: 2018-01-11 10:26:46 UTC
fedora 22 64 bit gnome 3.16.2 I used the latest "ReactOS download images" (install, live and qemu version). In the images live and install, it seems that boxes do not recognize the keyboard and mouse, so the system can not function. Moreover, using the qemu disk, after booting, crashes and is unusable. I tried the same images on kvm/qemu (CLI) or using virt-manager and operating properly. thanks
Created attachment 311024 [details] ReactOS isoinfo and kvm/qemu hardware profile Attachment disk ID information for ReactOS and operating hardware profile for kvm/qemu (virt-manager/gnome-boxes tested). ReactoOS is a system compatible with Windows binaries based in the design NT 5.2 (Windows Server 2003). There are known problems with the driver kvm/qemu usb tablet option among other hardware devices (one of them must cause the system crash). I could create a functional MV with ReactOS using virt-manager, using supported hardware parameters, and the disk image works perfectly in gnome-boxes. I hope this information to be useful. Cheers Related links: kvm/qemu usb tablet problem http://svn.reactos.org/svn/reactos?revision=59118&view=revision ReactOS hardware compatibility https://www.reactos.org/wiki/Supported_Hardware/IO
(In reply to Bastián Díaz from comment #1) > Created attachment 311024 [details] > ReactOS isoinfo and kvm/qemu hardware profile > > Attachment disk ID information for ReactOS Thanks. If you'd like to be even more helpful, could you please send this information to libosinfo list instead? A patch like this would be even more helpful: https://git.fedorahosted.org/cgit/libosinfo.git/commit/?id=34995abfd2444303c4a39d78c6381753fb0e2f5f > and operating hardware profile > for kvm/qemu (virt-manager/gnome-boxes tested). Thanks but for future ref, this info isn't relevant since it just shows one of the many possible configurations that would work for the guest OS.
(In reply to Zeeshan Ali (Khattak) from comment #2) > > Thanks. If you'd like to be even more helpful, could you please send this > information to libosinfo list instead? A patch like this would be even more > helpful: > I have already sent the information to the libosinfo mailing list . It would be very useful to find in the boxes wiki to do in these cases. Thank you.
(In reply to Bastián Díaz from comment #3) > (In reply to Zeeshan Ali (Khattak) from comment #2) > > > > Thanks. If you'd like to be even more helpful, could you please send this > > information to libosinfo list instead? A patch like this would be even more > > helpful: > > > > I have already sent the information to the libosinfo mailing list . Awesome! Thanks so much. > It would be very useful to find in the boxes wiki to do in these cases. Indeed! Please keep in mind it's a wiki so if you could spare some more time, feel free to add it on a new page under http://wiki.gnome.org/Apps/Boxes/.
(In reply to Zeeshan Ali (Khattak) from comment #2) > (In reply to Bastián Díaz from comment #1) > ?id=34995abfd2444303c4a39d78c6381753fb0e2f5f > > > and operating hardware profile > > for kvm/qemu (virt-manager/gnome-boxes tested). > > Thanks but for future ref, this info isn't relevant since it just shows one > of the many possible configurations that would work for the guest OS. Never mind this coment, I forgot the fact that problem isn't just that Boxes doesn't recognise the OS but also that things fail quite badly.
(In reply to Zeeshan Ali (Khattak) from comment #5) > > Never mind this coment, I forgot the fact that problem isn't just that Boxes > doesn't recognise the OS but also that things fail quite badly. In that you are right, but surprisingly ReactOS could run with most of the functions running decently (including USB redirection of supported devices). Remember that ReactOS is in alpha state and many things can crash. (itself, so it is very useful to run it in a VM). Cheers
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/69.