Results 1 to 8 of 8

Thread: virt-manager (only) will not X forward

  1. #1

    Default virt-manager (only) will not X forward

    I have this odd issue where when I ssh into a remote box with X forwarding enabled, and try to run virt-manager on the remote box, it does not display on my local machine.

    Any other X app will forward fine - xeyes, xterm, etc. all display fine, so it is not a general X forwarding issue, or display not being set, etc. - the only time I see it is with virt-manager.

    I've tried connecting with but -X and -Y options. If I turn on verbose info for the session, it looks like it thinks the window has been created locally, but in fact nothing is displayed:
    Code:
    [root@blah ~]# virt-manager 
    debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
    debug1: client_request_x11: request from 127.0.0.1 34923
    debug2: fd 7 setting O_NONBLOCK
    debug1: channel 1: new [x11]
    debug1: confirm x11
    [root@blah ~]# debug2: channel 1: rcvd adjust 45776
    debug2: channel 1: rcvd adjust 49152
    debug2: channel 1: window 2039508 sent adjust 57644
    debug2: channel 1: window 2035120 sent adjust 62032
    debug2: channel 1: rcvd adjust 34856
    debug2: channel 1: window 2045784 sent adjust 51368
    debug2: channel 1: window 2044100 sent adjust 53052
    debug2: channel 1: rcvd adjust 33968
    More weirdness: If I try to run it as an unprivileged user, I do actually get the initial dialog asking for root password, but if I continue the actual virtmanger window never appears.

    This is on:
    2.6.34-12-desktop, 64 bit, Suse 11.3, xorg-x11-7.5-11.3.x86_64

    Thanks for any suggestions, I really kind of need this to work.

  2. #2

    Default Re: virt-manager (only) will not X forward

    Some additional info. The box I am ssh'ing into is a RHEL 5.5. I've tried both -X and -Y options, connected with ssh -v and even started virt-manager with strace to see if there was anything odd showing up. Nope - everything appears to work perfectly with no error or odd messages - but no window ever shows up.

    Every other X app I have tried forwards fine, no problem. I can run virt-manager with X forwarding if I use another system, works fine. But if I try from my Suse 11.3 box it does not forward.

  3. #3
    Join Date
    Jun 2008
    Location
    Frisco, TX
    Posts
    1,233

    Default Re: virt-manager (only) will not X forward

    LewsTherinTelemon wrote:

    >
    > Some additional info. The box I am ssh'ing into is a RHEL 5.5. I've
    > tried both -X and -Y options, connected with ssh -v and even started
    > virt-manager with strace to see if there was anything odd showing up.
    > Nope - everything appears to work perfectly with no error or odd
    > messages - but no window ever shows up.
    >
    > Every other X app I have tried forwards fine, no problem. I can run
    > virt-manager with X forwarding if I use another system, works fine. But
    > if I try from my Suse 11.3 box it does not forward.


    Well... I normally start virt-manager on my Dom0 itself (SLES 11 SP1), but
    for fun, I just ssh -X into a RHEL 5.5 box and started virt-manager.... and
    in my case, it came right up. So I think something else is happening... not
    sure what.






  4. #4

    Default Re: virt-manager (only) will not X forward

    Yea, it is odd. Made even more so by the fact this is a brand new install of Suse 11.3 64 bit, and exactly the same thing just happened with Ubuntu 10.04 64 bit. Only virt-manager does not forward, everything else does.

  5. #5

    Default Re: virt-manager (only) will not X forward

    Perhaps there is a way to collect some info by using xmon to attach to and monitor the Xwindow messages, but I've not done that before, and I'm not entirely certain that is the right route. (Plus, since there is no window displayed, it is a bit hard to do anything with it to get info, as the issue occurs on window creation.)

  6. #6

    Default Re: virt-manager (only) will not X forward

    I was having the same issue on ubuntu server. Nothing would appear just running virt-manager. However using the full path eg /usr/bin/virt-manager works

    Cheers

  7. #7

    Default Re: virt-manager (only) will not X forward

    Thanks for the suggestion Insanemachine on using the full path. In fact, I tried that as well but got the same result. I am about convinced this is due to a the Xorg on a newer distro (Suse, Ubuntu) when connecting to, and X forwarding from, an RHEL 5 system. I've experienced exactly the same thing with Suse 11.3 and Kubuntu 10.04.

    It's a bit hard to diagnose though as there are zero error messages, either on the app that is launched remotely on on the local Xorg system displaying.

    If anyone has any other suggestion, perhaps what to look for in an strace, or other X debug tools I could run that would be great.

    Thank you,
    LewsTherin

  8. #8

    Red face Re: virt-manager (only) will not X forward

    At last - I figured this out.

    Looking at the output from ssh -v showed:
    debug1: confirm x11
    X11 connection rejected because of wrong authentication.
    debug1: channel 2: free: x11, nchannels 3
    The application 'virt-manager.py' lost its connection to the display localhost:12.0;
    most likely the X server was shut down or you killed/destroyed
    the application.
    That lead me to this post which had a solution, and a good explanation as well:

    https://bugzilla.redhat.com/show_bug...iple&id=239395

    So what worked was directing to my own .Xauthority when sudoing, like:

    $XAUTHORITY=~/.Xauthority sudo virt-manager
    I'll quote the explanation here as I found it useful:
    Miloslav Trmač 2007-05-16 07:23:35 EDT

    This happens because ssh uses the default Xauthority file, and does not set
    XAUTHORITY, so libXau uses $HOME/.Xauthority. sudo changes the uid, but not
    $HOME, so the original $HOME/.Xauthority is still used. Then, userhelper (or su
    -) use the pam_xauth module.

    pam_xauth does not use $HOME/.Xauthority, but "invoking user's home
    directory"/.Xauthority, i.e. /root/.Xauthority, which does not exist.

    So, pam_xauth should be using $HOME/.Xauthority if XAUTHORITY is not set and
    $HOME/.Xauthority is readable by the invoking user.

    You can use (XAUTHORITY=~/.Xauthority sudo virt-manager) as a work-around.
    Note this does not explain really why this is necessary when connecting from a Suse 11.3 box, but the same does not occur when connecting from a RHEL 5 or Fedora box. Since this issue is apparently related to which .Xauthority is being used (on the server side), you would think it would apply to all clients connecting, however in practice that is not the case.

    Lews Therin

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •