Details

    • Type: Improvement
    • Status: Closed (View workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.1.0, 3.2.0, 3.4.2
    • Fix Version/s: 4.0.0
    • Component/s: Node Controller
    • Labels:
      None
    • Environment:

      RHEL6 KVM

    • Benefit:
      High
    • Security:
      No
    • Hypervisor:
      KVM
    • Operating System:
      RHEL 6
    • Sprint:
      4.0 Sprint 7, 4.0 Sprint 8, 4.1.0 Sprint 1
    • Epic/Theme:
    • Rank:
      0|i00ddz:
    • Feature Category:
      Resource Management: Virtual Machine

      Description

      Creating ticket on behalf of Seth Vidal ( email send on community list ).

      Pls find email below:

      I was setting up an instance of euca this week/weekend on rhel6. I ran into a problem and a vnc connection to my instance would have been a big help. I worked out the problem but then I started to investigate vnc support.

      I asked and was told to uncomment the vnc display line in the libvirt.xsl on my NCs. I did this but when I used virt-manager to try to look at the console - I was told it could not connect.

      So I dug and dug - and eventually discovered that in the libvirt.xsl the line I was told to uncomment was:

      <graphics type='vnc' port='-1' autoport='yes' keymap='en-us' listen='0.0.0.0'/>

      that line is fine - except for listen='0.0.0.0'

      If you set that then virt-manager won't try to setup any ssh tunneling to get to the nc itself.

      if you just leave listen='0.0.0.0' off entirely it all works just fine.

      So why not leave it off and change the example libvirt.xsl to reflect that?

        Gliffy Diagrams

          Attachments

            Issue links

              Activity

                People

                • Votes:
                  0 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: