[image: image.png] Hello Samu, Thank you for the kind words and for your questions. First, I want to be transparent about how this was done: the implementation was carried out with Claude Code, Anthropic's AI coding agent. My role was direction and supervision — deciding what to build, reviewing the results, and testing everything against real oVirt environments. This is also why community review matters so much to me: I would genuinely appreciate feedback on wrong implementations, questionable design decisions, and security issues. On the VNC issue (broken virt-viewer on Windows): I solved it by re-implementing the console as a browser-based noVNC web console. The native client path (.vv / remote-viewer) is removed entirely — the console opens as a popup connecting over a same-origin websocket through the engine's Apache, so Windows users need nothing but a web browser: no virt-viewer install, no separate certificate acceptance. It is working today against real VMs in my environment. To be clear, this does not fix virt-viewer itself, but with this UI you no longer need it. On sharing: I have pushed everything here: https://github.com/tkqltm/ovirt-engine-react — a fork of ovirt-engine with full upstream history. It contains the complete backend changes (GWT-RPC layer and GWT servlets removed, all client-server communication moved to the REST API, the whole codebase migrated from javax to jakarta / Jakarta EE, running on WildFly 40, Java 21, PostgreSQL 13+) and the new React 19 / PatternFly 6 frontend under frontend/webadmin-react/. The changes go far beyond the UI, so I believe the backend needs to be reviewed as a whole, not just the frontend. One honest caveat: the base product was customized before this conversion, so it deviates from stock oVirt in places — Gluster was removed from the UI, and we use a custom "Ceph RBD" storage domain type (we originally used the ceph-iscsi gateway but hit sanlock problems, so kernel-mapped RBD devices are treated like FC LUNs instead). I would love as much feedback and as many corrections as the community can give. And I sincerely hope this contribution brings a new atmosphere and many changes to ovirt-engine. If there is a preferred way to take this toward upstream (devel list RFC, patches, anything), please point me in the right direction. Best regards, Jeong Haneul 2026년 7월 10일 (금) 오후 9:37, Marcos Sungaila <marcos.sungaila@oracle.com>님이 작성:
Hi Samu,
virt-viewer is part of the virt-manager project. Any way, searching the oVirt users list I didn’t find any virt-viewer issues or broken report. You can report virt-viewer issues by accessing the upstream Gitlab virt-viewer repository at https://gitlab.com/virt-viewer/virt-viewer. Remember to include your virt-viewer version, OS type and version, guest VM type you are trying to access, and step-by-step instructions on how to reproduce the issue.
Marcos
*From: *Samu Paaso via Users <users@ovirt.org> *Date: *Thursday, 9 July 2026 at 05:14 *To: *users@ovirt.org <users@ovirt.org> *Cc: *정하늘 <ahanaoal@gmail.com> *Subject: *[External] : [ovirt-users]Re: Fwd: React-based WebAdmin modernization for oVirt Engine
Hello 정하늘
This work looks amazing. I have a couple of questions:
Are you planning to address the VNC issue that we have going on? What I mean by that is the broken virt-viewer on Windows
Are you planning on sharing the work you have done with the developers of the upstream projects? If yes, are you also planning on sharing some of your builds with the public?
Br, Samu
On Wed 8. Jul 2026 at 8.04 AM, 정하늘 <ahanaoal@gmail.com> wrote:
Hello oVirt maintainers,
My name is Jeong Haneul, and I'm an infrastructure engineer from South Korea.
First, I'd like to thank everyone who has contributed to oVirt over the years. I still provides virtualization solutions based on oVirt Engine, and we've relied on the project for a long time.
As upstream development has slowed, I started a personal modernization project to address some of the platform's technical debt.
So far, I've completed the following work:
- Replaced the legacy GWT WebAdmin with a React-based frontend. - Completely removed the GWT frontend and the GWT-RPC communication layer. - Migrated client-server communication to REST APIs. - Upgraded the platform to Jakarta EE 11, WildFly 40, Java 21, and PostgreSQL 16. - Applied numerous security and dependency updates.
The project is still being validated, but most of the functionality is already working.
I would like to know whether there is still active interest in modernizing oVirt Engine. If so, I'd be happy to discuss the project, share my experience, and explore whether any part of this work could be useful for the community.
Please note that I'm not a professional software developer—I'm an infrastructure engineer—and I'm communicating in English using a translator. I appreciate your understanding.
Thank you for your time, and I look forward to hearing from you.
Best regards,
Jeong Haneul [image: image.png][image: image.png][image: image.png][image: image.png]
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy <https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy__;!!ACWV5N9M2RV99hQ!J2X-2ogNFzABr1TRRTFVrcKPHMEfdQrOSVwr_cR4gMEfTvBqq-N2qmporI2zZ2-Oc2VyA1bLDBAwmOqzjw$> .html oVirt Code of Conduct: https://www.ovirt.org/community/ <https://urldefense.com/v3/__https://www.ovirt.org/community/__;!!ACWV5N9M2RV99hQ!J2X-2ogNFzABr1TRRTFVrcKPHMEfdQrOSVwr_cR4gMEfTvBqq-N2qmporI2zZ2-Oc2VyA1bLDBARnK3_2w$> about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/ <https://urldefense.com/v3/__https://lists.ovirt.org/archives/__;!!ACWV5N9M2RV99hQ!J2X-2ogNFzABr1TRRTFVrcKPHMEfdQrOSVwr_cR4gMEfTvBqq-N2qmporI2zZ2-Oc2VyA1bLDBC27nPVMA$> list/users@ovirt.org/message/6VDTZFPNSMPCEIBK6AOWPR7VOGCGUQZG/
