RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 561975 [details]
package list

Description of problem:
No protocol specified
Cannot open display:

Version-Release number of selected component (if applicable):
virt-viewer          0.4.1   7.el6

Steps to Reproduce:
0.  install rhel-server-6.2-x86_64-dvd.iso
1.  login (as g)
2.  vncserver <args>
3.  sudo xterm #run subsequent commands in the root xterm in Xvnc
4.  rhn_register
5.  alias vinst='virt-install -wbridge:br1 --accelerate'
6.  lvcreate -L 5G VGpecan6 -n6a
7.  vinst -r500 --disk path=/dev/VGpecan6/6a -n 6a -c/var/local/nfs/r6/rhel-server-6.2-x86_64-dvd.iso --os-variant=rhel6
8.  virsh list #6a running
9.  virt-viewer 6a
10. yum update
11. reboot
12. repeat steps 1-3
13. virsh list #6a running
14. virt-viewer 6a
  
Actual results: virt-install and virt-viewer both complain
No protocol specified
Cannot open display:

Expected results:
a virt-viewer window

Additional info:
am i missing a needed package?

umm, so, is virt-viewer simply DOA in rhel6.2?  is there anything i'm doing here that's out of the ordinary?

> Cannot open display:

That means there is no DISPLAY environment variable set and thus virt-viewer cannot connect to the X server.

ok got it.  bizarre.  i can "su", and from there i can launch xterms, and those root xterms can launch other xterms ad infinitum, but as soon as the "su" process exits, none of the root xterms can launch anything anymore.  well clearly that's not a virt-install bug, sorry.  i've no idea which module, but clearly not well thought out behaviour.

When you run 'su' it'll add an entry to your $HOME/.Xauthority file which gives the root applications the permission to connect the X server. When you exit 'su', I presume it is removeing the .Xauthority entry, which will prevent further apps from starting.