similar to: Boot delay

I am needing to explicitly assign VNC ports to my virtual guests so that I can connect to them externally via a VNC client, and not virt-viewer. Since I will have multiple KVM Hosts with access to the same shared storage (to facilitate migrations) I need to ensure I have unique VNC ports assigned to each guest so that I don't overlap somehow. I had planned to use a range of ports starting at

Yes, I also think that iptables module should be loaded before libvirt-bin and I have seen a post which regarded loading conntrack modules and these modules also seem to be necessary... I know a little about Upstart in Ubuntu. However, I still don't know how to properly solve this problem. ip_tables module depend on other modules being loaded and since I don't know the full list of modules

On Tue, Dec 30, 2014 at 9:58 AM, Marcelo Roccasalva < marcelo-centos at irrigacion.gov.ar> wrote: > On Tue, Dec 30, 2014 at 11:46 AM, Bill Gee <bgee at campercaver.net> wrote: > > > Hello everyone - > > > > I am trying to use virt-viewer to connect to KVM virtual machines running > > on a > > CentOS7 host. It works great when running directly on

On Tue, Dec 30, 2014 at 4:08 PM, Bill Gee <bgee at campercaver.net> wrote: > > Thanks! I changed the qemu.conf file to listen on 0.0.0.0. That works - > I can > connect to the virtual machines using a VNC client. > Listening on 0.0.0.0 listens on all network interfaces. Mark's comment is not a major concern unless your KVM host is directly connected to the Internet (no

Need some pointers here. I've got CentOS 4.4, and I want to control my OSX 10.4.9 box via VNC. It connects, and I get a little dot for the mouse cursor, but just a black screen. I can see the mouse controlling the OSX desktop... Here's the output when I start in a terminal: [d at f ~]$ vncviewer VNC server supports protocol version 3.889 (viewer 3.3) VNC authentication succeeded

I''m running snv93. I''m trying to install a windows hvm domU using the virt-install command: /usr/bin/virt-install -n windowsts -r 2048 -s 20 -f /data/domU/windowsts --hvm --vnc -c /dev/dsk/c0t0d0s2 The vncviewer is unable to open a connection to the xend VNC server and is failing with the Connection refused (146) error message. xend is set up with the following properties:

Hi, I''ve run into a problem, and no amount of Googling seems to help. I''m running Xen 3.4 and have the consoles of my DOMUs setup to be VNC. I can connect to them just fine from Chicken of the VNC etc etc. I cannot, however, connect using the built in vnc client using vnc://machine_name:59XX. I''m running os X 10.6.3 BTW Has anyone found a way around this? My end game

Hi everybody, i've been using ultravnc viewer from long time without any problem. Starting from wine-1.2-rc2 when i'm connected to a vnc server i cannot close anymore the viewer window and when I try to close the window it sends an ALT+F4 to the application running in the vnc server !! With wine until version 1.2-rc1 the viewer windows close as expected. In console there are no messages

The new merged qemu no longer has the ability to spawn a vnc viewer process in the bowels of the xend/qemu stack. In this patch we provide support for this use case in a different manner - one more akin to the mechanism used for `xm console'' and `xm create -c''. We introduce new xm options: xm create --vncviewer [--vncviewer-autopass] xm vncviewer [--vncviewer-autopass]

Hello, I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and dom0 3.18.17 rpms, and noticed these new problems: 1) virt-manager fails to start with an error: "D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory" And indeed.. there was no such file. Running

os x comes with openssh, and some other nixy goodness. the rest you can get at brew.sh. when i ssh -Y into the host, ill just virt-manager or virt-viewer, but the x server on os x comes with some baggage and silly annoyances like "helpfully" trapping the mouse with a release combo thats hard to deal with from os x. running a vnc client over os x would still come with baggage and

Hi List, Is it possible to prevent other clients from stealing my libvirtd hosted spice session? This is a problem for me where multiple co-workers access the same guest over a qemu+ssh:// connection. Instead of simply disconnecting clients, I'd like libvirtd to deny the new client. I've been looking at polkit acl rules and the vnc sharePolicy attribute but so far no luck.

Hi, I am pretty new to libvirt, but have succeeded in setting up two VM's, Windows 10 and ClearOS (a Centos derivative) and they both have the same issue. I have installed both of them with a UK English keyboard, but the host machine is remote and in the US with a US locale. When I access either through VNC (I've tried TightVNC and VNC-Viewer), a number of my keys don't map

- perform dns lookup on hostname, - randomize local tunnel port - bump rpm spec version updated to include danpb's feedback regarding getaddrinfo --- main.c | 36 ++++++++++++++++++------------------ ovirt-viewer.spec | 9 ++++++++- tunnel.c | 29 ++++++++++++++++++++--------- 3 files changed, 46 insertions(+), 28 deletions(-) diff --git a/main.c b/main.c index

Hello Xen-Users, I am currently provisioning old Linux guests as HVM on a server, and giving clients access through VNC. The current setup uses the default Xen framebuffer as a VNC server (all configuration files have vnc=1 and a few other settings), and my clients are using vinagre (a.k.a. Remote Desktop Viewer) on Arch as their VNC client. Problem: Keyboard input is not consistently handled

Hello all: I am trying to install CentOS 5.4 as a KVM guest. The host is running CentOS 5.4 and does not have X installed. I used ssh to connect to the host and ran this command (I formatted it for readability, it is all on one line): virt-install -n jamm12e -r 1024 --vcpus=1 --check-cpu --os-type=linux --os-variant=rhel5 --hvm --accelerate --cdrom=/tmp/CentOS-5.4-x86_64-netinstall.iso

Hi, I have a virtualization host running KVM and libvirt 0.9.12 (on Debian unstable). I would like to connect with virt-viewer 0.5.4 from a different host to a domain that has Display Spice configured as graphics interface. I can connect to the KVM host using virsh --connect=qemu+ssh://mh at fan.local/system and start m KVM domain from there, so I guess that authentication is just fine.

Hello! I'm investigating a case where x11vnc (or RealVNC server or vino) on a _real_ X11 server seems to be broken with any VNC viewer. By broken I mean: it seems to keep old frames in memory, in such a way that in every three frames, two are from the past and one is the current one. This is easily spotted when using gnome-shell and looking at the clock at the top. Besides being

run on startup by default like the other ovirt services --- conf/ovirt-vnc-proxy | 49 ++++++++ installer/modules/ovirt/manifests/ovirt.pp | 1 + ovirt-server.spec.in | 5 + src/vnc-proxy/vnc-proxy.rb | 167 ++++++++++++++++++++++++++++ 4 files changed, 222 insertions(+), 0 deletions(-) create mode 100755 conf/ovirt-vnc-proxy

- perform dns lookup on hostname, - randomize local tunnel port - simple autobuild script - bump rpm spec version --- autobuild.sh | 41 +++++++++++++++++++++++++++++++++++++++++ main.c | 14 +++++--------- ovirt-viewer.spec | 9 ++++++++- tunnel.c | 29 ++++++++++++++++++++--------- 4 files changed, 74 insertions(+), 19 deletions(-) create mode 100755