similar to: Open virt-viewer with virsh start

Hello, here is my problem : i migrated an old debian server, with kvm host and guests vm, on a new one (wheezy to jessie). Everything worked fine on this old server. On the new server, i created a storage pool, copy the qcow2 guests files (from the old server) inside this storage pool, copy the xml guests files (from the old server) to /etc/libvirt/qemu , then virsh define guests and virsh

On Thu, Sep 05, 2013 at 03:30:12PM -0300, Fernando Lozano wrote: > >>I've pushed test builds of mingw-virt-viewer packaging libvirt 1.1.2 if you want > >>to give them a try to see if they work better (disclaimer: I haven't tested > >>these installers at all). > >Pushed to http://teuf.fedorapeople.org/virt-viewer-msi/ ;) > > Thanks for providing those

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

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.

On Thu, Sep 05, 2013 at 06:50:43PM +0200, Christophe Fergeau wrote: > On Wed, Sep 04, 2013 at 04:41:40PM -0300, Fernando Lozano wrote: > > >What version of virsh is included in that msi? Maybe it's just a case > > >of a stale build, for something that has been fixed upstream? > > C:>virsh -V > > Virsh command line tool of libvirt 0.10.2 > > I've

Hi, >>>> I'm trying to use virsh and virt-viewer on Windows. I'm running the >>>> latest binaries from http://spice-space.org/download.html, that is, >>>> virt-viewer-x64-0.5.7.msi on a Windows 7 64-bits computer. >> I am willing to help all I can to test, but I'm not a Gnome developer. I >> have not coded a single line in C for more

Hi, >> I'm trying to use virsh and virt-viewer on Windows. I'm running the >> latest binaries from http://spice-space.org/download.html, that is, >> virt-viewer-x64-0.5.7.msi on a Windows 7 64-bits computer. >> >> So far I got remote-viewer.exe to work, after some pain. But have no >> sucess using virt-viewer.exe and virsh.exe. Are they supposed to

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

On Fri, Sep 06, 2013 at 04:00:25PM -0300, Fernando Lozano wrote: > On the other side, there should be an official place for people like > me, who are interested in testing virsh and virt-viewer (and who > knows, some day virt-manager) on Windows, to get test binaries. > There should be some effort on continuing the porting, not stopping > on remote-viewer. I fully agree with that,

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 the host, but I have not been able to figure out the magic connection string to make it work from another computer. On the host, I set selinux to "permissive" and stopped the firewalld service. No change, so it is not related to

Ever since I upgraded my laptop from FC15 to FC17, I've been getting this message when I ssh to some RHEL6 hosts inside Red Hat. In particular, I'm trying to do this: virt-viewer --connect \ qemu+ssh://kvm11.devlab.phx1.redhat.com/system \ bork-s01.candlepin.dev.devlab.phx1.redhat.com This is the message I get: X11 forwarding request failed on channel 0 A viewer window pops

Hi there, Sorry for the cross-post, but I seeked help on this issue before on those lists, but nobody answered. :-( I'm trying to use virsh and virt-viewer on Windows. I'm running the latest binaries from http://spice-space.org/download.html, that is, virt-viewer-x64-0.5.7.msi on a Windows 7 64-bits computer. So far I got remote-viewer.exe to work, after some pain. But have no

Helle and thanks for your answer You should never modify/update/create files under the /etc/libvirt/qemu directory. The correct way to do this is virsh dumpxml $domain > $domain.xml and virsh define $domain.xml. I didnt modify or create anything i just copied xml file from the old server to the new server Debug log from virt-manager (virt-manager --debug) would be helpful. Cf

Hi, I''m asking my question here, because I could not find any answer to my problem, but I''m affraid shorewall is not the one to blame. First of all I''m using shorewall version 2.0.15 on two linux box. I set up an ipsec tunnel beetween those 2 boxes to be ables to connect 2 not routable subnetworks. Here is my network topology: 10.66.17.0/24 - 10.66.17.1 = eth0

On 08/12/2010 10:29 AM, Lars Kellogg-Stedman wrote: > Hello all, > > I'm trying to get virsh (and virt-manager) to talk to a remote libvirt > instance. I cannot for the life of me figure out how to tell either > tool where to find client or CA certificates. Do they *really* need > to access the ones in /etc/pki? In particular, the client seems to > want to read the

Hi all, I''m currently using ipsec with Shorewall 3.0.7 on a patched 2.6.10 kernel. Having heard that ipsec support was in the standard kernel starting from 2.6.16, I tried to upgrade to the last kernel. My problem is that shorewall won''t start anymore. I get this output in /var/log/shorewall-init.log: Starting Shorewall... Initializing... Shorewall has detected the

I'm attempting to use speex preprocess for automatic gain control in an application I'm working on and could use some help. I'm using Opus as my codec. In order to keep the number of packets down, I'm using 60msec frames. I'm sampling at 48KHz as is recommended for Opus. So, the frame length is 2880 samples and the sampling rate is 48000. The source of the data is a

virt-viewer-plugin is deprecated and will be replaced w/ ovirt-viewer-plugin, vm details pane uri indicates ovirt-viewer should be used with the specified hostname --- src/app/views/vm/show.rhtml | 18 ++++-------------- 1 files changed, 4 insertions(+), 14 deletions(-) diff --git a/src/app/views/vm/show.rhtml b/src/app/views/vm/show.rhtml index ffe5055..30b17cb 100644 ---

On Fri, Jan 29, 2016 at 02:20:50PM +0100, Pascal Legrand wrote: > Hello, Hi, > here is my problem : > i migrated an old debian server, with kvm host and guests vm, on a new > one (wheezy to jessie). > Everything worked fine on this old server. > > On the new server, i created a storage pool, copy the qcow2 guests files > (from the old server) inside this storage pool,

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