ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Kimchi VM Guest Console Timeout Issue

    IT Discussion
    linux fedora fedora 25 kimchi
    7
    21
    4.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ObsolesceO
      Obsolesce
      last edited by

      I just tried with selinux disabled, same result after rebooting, turning it back on.

      So, it doesn't seem to be firewall/selinux related (as far as I can tell).

      dafyreD 1 Reply Last reply Reply Quote 0
      • dafyreD
        dafyre @Obsolesce
        last edited by

        @tim_g said in Kimchi VM Guest Console Timeout Issue:

        I just tried with selinux disabled, same result after rebooting, turning it back on.

        So, it doesn't seem to be firewall/selinux related (as far as I can tell).

        The VNC ports are in the 5900 range. I don't see those in your firewall-cmd statements.

        stacksofplatesS 1 Reply Last reply Reply Quote 0
        • stacksofplatesS
          stacksofplates @dafyre
          last edited by

          @dafyre said in Kimchi VM Guest Console Timeout Issue:

          @tim_g said in Kimchi VM Guest Console Timeout Issue:

          I just tried with selinux disabled, same result after rebooting, turning it back on.

          So, it doesn't seem to be firewall/selinux related (as far as I can tell).

          The VNC ports are in the 5900 range. I don't see those in your firewall-cmd statements.

          Same with SPICE. If you look with virt manager it should tell you what port each VM is on. No idea if this interface will tell you.

          To test you can create an SSH tunnel with whatever port the console is on and see if it shows up locally.

          1 Reply Last reply Reply Quote 0
          • ObsolesceO
            Obsolesce
            last edited by Obsolesce

            Do all of those ranges need to be opened if im connecting via SSL on the web browser via port 64667? That's what shows in the browser, ip:64667, when attempting to connect to VM console. Its browser based. Im not actually connecting via spice/vnc. That's internally.

            matteo nunziatiM 1 Reply Last reply Reply Quote 0
            • matteo nunziatiM
              matteo nunziati @Obsolesce
              last edited by

              @tim_g did you try the same thing with virtmanager? Install it where kimchi is and try. Just to sort out issues: system, setup, bug...

              1 Reply Last reply Reply Quote 1
              • ObsolesceO
                Obsolesce
                last edited by

                I opened an issue on git, and it turns out that I was using version 1.5.1-0 and current release is 2.5.

                Why installing it from the repo (dnf install kimchi) installs such an old version, I shall never know... so I never thought to check that.

                I'm finally able to access it remotely, and get a web-based console view of my VMs... mostly anyways.

                Only a few issues remain that I'm trying to work out... it doesn't display the full screen and the keyboard/mouse stops functioning in the console.

                A 1 Reply Last reply Reply Quote 0
                • A
                  Alex Sage @Obsolesce
                  last edited by

                  @tim_g Screenshots would be nice to see 🙂

                  1 Reply Last reply Reply Quote 0
                  • ObsolesceO
                    Obsolesce
                    last edited by Obsolesce

                    So far it seems to be okay:
                    (edit: oh, Test1 doesn't seem to work... I guess because I either don't have novnc installed, or I didn't do anything to it... but Test2 works with webconsole as pictured below using spice)

                    • I can remotely access it
                    • Web console is showing the whole screen (but I have scroll bars to deal with... still rather have that than nothing)
                    • Keyboard and mouse seem to be working okay now (in Edge, haven't yet tried in FF/Ch)

                    0_1500579458173_Untitled.jpg

                    0_1500579470884_Untitled2.jpg
                    and the bottom
                    0_1500579481094_Untitled3.jpg

                    1 Reply Last reply Reply Quote 0
                    • ObsolesceO
                      Obsolesce
                      last edited by

                      Went to install novnc. It's already installed. So I have no clue why I can't use webconsole on Test1 that uses vnc... test2 works just fine as pictured above using spice via web console.

                      1 Reply Last reply Reply Quote 0
                      • ObsolesceO
                        Obsolesce
                        last edited by

                        Okay, so looks like:

                        • https://IP:9090 (for server admin via Cockpit)
                        • https://IP:8001 (for KVM VM management via WOK/Kimchi & web VM console)

                        Potential to remotely manage your Linux servers, hypervisors, and VMs via HTML5 from anywhere in the world.

                        Works great! Just don't create a template that uses VNC. Use Spice instead and you'll have no issues. At least that's my fix until they get around to helping me clear it up.

                        1 Reply Last reply Reply Quote 0
                        • FATeknollogeeF
                          FATeknollogee
                          last edited by

                          How did you re-install since dnf install kimchi was an old version?

                          ObsolesceO 1 Reply Last reply Reply Quote 0
                          • ObsolesceO
                            Obsolesce @FATeknollogee
                            last edited by

                            @fateknollogee said in Kimchi VM Guest Console Timeout Issue:

                            How did you re-install since dnf install kimchi was an old version?

                            First I did a wget <theKimchiFile>.rpm and then tried "dnf upgrade <kimchi-file>.rpm" but that failed saying it was missing new version of WOK.

                            So I did a wget <theWOKfile>.rpm and then installed that, then I could do the upgrade command above.

                            At that point, I did a bunch of stuff and it wasn't working, so I did a "dnf remove kimchi wok" and removed everything.

                            Then I installed the prerequisites for wok, installed that, then kimchi... this was after installing a GUI and all the crap that comes with it because I couldn't get on remotely, I twas only working via localhost.

                            I need to recreate my steps completely from fresh Fedora install to working Kimchi doing it this other way.

                            Once I do that, I'll post the steps in a very easy to read and accurate step by step from fresh Fedora 26 install to completely working Kimchi.

                            1 Reply Last reply Reply Quote 1
                            • FATeknollogeeF
                              FATeknollogee
                              last edited by

                              Are you connecting to kimchi via localhost or remotely from another pc?

                              ObsolesceO 1 Reply Last reply Reply Quote 0
                              • ObsolesceO
                                Obsolesce @FATeknollogee
                                last edited by

                                @fateknollogee said in Kimchi VM Guest Console Timeout Issue:

                                Are you connecting to kimchi via localhost or remotely from another pc?

                                Remotely from another PC.

                                1 Reply Last reply Reply Quote 0
                                • 1
                                • 2
                                • 1 / 2
                                • First post
                                  Last post