[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] [xen4.4] DomU Windows server HVM with xen-tools xl create
I do not understand your example for forwarding X.
As I replied to David, I managed to access my Windows DomU with VNC and
RDP too. And that works perfectly.
But I discovered a little problem : How to know the id value to adding
from 5900 base port ?
I read that "xl list" gives the domain_id which is not necessarilythe
good value to add (I had just discovered thisjoyousness).
Also I read that "ps -ef | grep vnc" gives the value behind the -vnc
parameter, but for me this does not work.
The vnclisten parameter : limit remote clients and security ?
I will dig it further but it seems that vncdisplay parameter does not
work as expected to define the static port !
So how to know with certaintywhat is the real value to add ?
Le 13/10/2015 10:53, Ian Campbell a Ãcrit :
On Mon, 2015-10-12 at 19:39 +0200, estebann@xxxxxxxxx wrote:
It's also my fault. I read the man pages and have not seen the non-sense
between vnc and console :)
root@lnj-ubu64:/home/lnj# xl -vvv vncviewer xen-domu-ubuntu
No protocol specified
Error: Can't open display: :0.0
I just realized that for using VNC tool, the X server must be up, but to
be frank, I do not have sufficient skill in this domain. In fact, my Xen
host is an headless workstation (my new PC :) ), so no direct display. I
tried also the xserver-xorg-video-dummy, but with no success and that is
not the aim of this thread.
If you are logging into the headless workstation via ssh from a system
running X windows then you can use "ssh -Y user@host" to enable X11
forwarding, then a vncclient running in dom0 should be able to display on
your main machine.
Otherwise you can run a vnc client directly on whichever machine you like
and point it at the Xen dom0. If doing this then you would likely want to:
* use the vnclisten option to bind to either 0.0.0.0 (everything) or the
public IP of your dom0
* use the vncdisplay option to pick a static display number for the VM
(otherwise if you have multiple VMs then they will get assigned display
numbers based on what was available when they booted).
* Check that the dom0 firewall is not blocking the VNC port, which is 5900
+ display number.
You can actually combine the vnclist and vncdisplay into a single vnclisten
with the <address>:<display> syntax (according to the man page, I've not
tried this).
HTH,
Ian.
That is why, first I want ensure, that I can connect to my HVM DomU from
console or SSH.
Le 12/10/2015 14:06, Ian Campbell a Ãcrit :
On Mon, 2015-10-12 at 13:57 +0200, estebann@xxxxxxxxx wrote:
Ok, it is confusing... I will try to clarify.
When following tutorials I managed to run PV DomU guest (successfull
tests with Ubuntu, Debian), but for this moment I did not managed to
run
HVM DomU guest (no Windows and no Ubuntu). So in the first time, I
suspected a CPU incompatibility but this is not the case.
So, I can create an Ubuntu HVM DomU, but a simple terminal access,
shows
me that is does not work completely.
root@lnj-ubu64:/home/lnj# xl -vvv vncconsole xen-domu-ubuntu
command not implemented
xc: debug: hypercall buffer: total allocations:6 total releases:6
xc: debug: hypercall buffer: current allocations:0 maximum
allocations:1
xc: debug: hypercall buffer: cache current size:1
xc: debug: hypercall buffer: cache hits:5 misses:1 toobig:0
I have no 'vncconsole' parameter in xl tool. Wrong version ?
Sorry, I should have said "xl vncviewer", my mistake.
BTW, you can find the list of commands in the xl manpage, or in the
output
of "xl help".
Ian.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
