similar to: Libvert live migration problem!

Hi all, In live migration using shared memory, there would be a following step to input the password after typing: migrate --live vm_name qemu+ssh://Destination_IP/system. . I wonder if it is possible to include the password in the URI so that the password procedure can be avoided? Thanks, Yi -------------- next part -------------- An HTML attachment was scrubbed... URL:

I''ve recently installed Debian Lenny witch Xen (xen-utils, xen.tools and xen-linux-system-2.6.26-2-xen-amd64). I want to virtualize some windows servers, but I''m unable to connect to localhost VNC when I start the vm (xm create) to proceed with windows instalation. The VM config is: import os, re arch = os.uname()[4] if re.search(''64'', arch):

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:

I have an FC6 dom0 running on a headless server. I want to install a CentOS 4.4 domU with a console accessed using vnc from a remote machine. I *think* I should be able to do this from my understanding of the documentation. I''ve configured a domU to boot from an ISO image to do the CentOS install and run xm create. netstat on dom0 shows there''s a listener on 0.0.0.0:5900, but

Hello, I was getting the following error in syslog: libvirtd: 21:19:12.116: 10955: error : qemudDispatchServer:1355 : Too many active clients (20), dropping connection from 127.0.0.1;0 I investigated a bit and tried the following in a python console: import libvirt ~~~~ conn=libvirt.openReadOnly("qemu+ssh://HOST_IP/system<http://10.16.71.1/system> ") //now check the no. of

On Thursday 07 February 2008 05:19:26 pm Hamid Majidy wrote: > When I start guest with "xm create clientdom", I get: > xm create clientdom > Using config file "./clientdom". > VNC= 3 > Started domain clientdom >   > But when I try to connect to it with "vncviewer 192.168.122.1:5900" I get: > VNC Viewer Free Edition 4.1.2 for X - built Mar 14

Hi. How I can see what happend in my domU??? dom0 Debian Lenny domU FreeBSD6.4 xen 3.2-1 -------- Xen 3.2-1 :/etc/xen# xm create tttt.cfg Using config file "./tttt.cfg". Started domain freebsd -------- /etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2969 4 r----- 48.0 freebsd

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

Hello, I''ve launched my first guest installation on XCP and I would like to know how to see the installation process through VNC. On the XCP: # netstat -lnatp |grep vnc tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 7867/vncterm tcp 0 0 127.0.0.1:5901 0.0.0.0:* LISTEN 8928/vncterm So, there is something listening for

Hi. I found this issue with IA64 box while looking at the c/s of 18204:21dd1fdb73d8, but I believe the things is same with x86 box. I''m not sure whether this patch coexist with the old ioemu which is to be removed soon. So it might be desirable to apply this patch after deleting the internal ioemu tree. thanks, xm: Don''t spawn vncviewer twice. Without this patch, vncviewer

On Mon, May 08, 2017 at 03:35:19PM +0100, Daniel P. Berrange wrote: >On Sat, May 06, 2017 at 08:09:49PM -0400, Dan wrote: >> On Fri, May 5, 2017 at 4:29 PM, Nicolas Bock <nicolasbock@gmail.com> wrote: >> >> > Hi, >> > >> > I am running a webserver on the libvirt host and would like to add a >> > nwfilter such that a VM can access that

Well, not that remote. I'm trying to get it working from my laptop to an ancient workstation behind me I use for testing. I appear to get the connection okay. virt-manager --connect qemu+ssh://root@<host_ip>/system I can click on the entry on the panel that comes up and see facts about the remote machine. I then tried the "Create a new virtual machine" item on the tool

I''ve attached the preliminary patch to add vncviewer options to the ''xl create''. It applies cleanly against c/s 4e1d091d10d8. All feedback is welcome. Goncalo # HG changeset patch # User Goncalo Gomes <goncalo.gomes@eu.citrix.com> # Date 1332257809 0 # Node ID 46f8afe643dee8de2c592c65204567fbad657616 # Parent 4e1d091d10d83130842170cd61f1194e5459f2aa Add

Hello, is there a way to start automatically the vncviewer when a domU starts? When I was using the xm toolstack I could use "xm create domain.cfg -vncviewer" or something similar (if I''m not wrong), but I don''t know how to do it with the xl toolstack. At the moment, I have to create the domain using xl create domU.cfg, then xl list to see the domU id and then xl

Hi list, I''m using Dom0 gentoo with xen 3.0.4 and xenman. I have several DomU working and it is really nice :) so all my DomUs are installed with disk images. Now i want to use an ISO to boot and install a linux system (or win). When i try to boot the DomU i dont have nothing, nothing relevant (for me) in logs and i can connect to the console. The state of the DomU is unknow. Any help

I am working on the Centos wiki instructions for doing an install via vnc: http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall CD is all burned and ready to go. I then thought about the viewer settings particularly the port number and firewall rules. When I connect vncviewer to a vncserver it uses port(s) 590n where n is the display number. OK, is that what happens when a server connects

Hi all, the patch "qemu-vnc-wmvi.patch" adds support for the WMVi pseudoencoding in qemu vnc server. If the client implements it, it is supposed to be able to change colour depth when receiving a WMVi message. Since I didn''t know any client that supports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The

I have the vncserver running on CentOS 4, but when I log in using vncviewer from another box, I don't see my gnome desktop, just a fancy terminal. I suspect I need to edit the ~/.vnc "xstartup file, but what do I add to fix this. On all other distros I have tried, the vncserver serves up my gnome desktop by default. -- Lee Parmeter Emperor, linXos - The Flying Penguin

Hi My original message and problem is in http://lists.xenproject.org/archives/html/xen-users/2013-06/msg00422.html, but I couldn''t reply to that, so I''m sending an update in the form of a new message. I have changed the memory parameter in /etc/xen/win.cfg, from 1024 to 4096 and now the domU stays active, or at least on the list before: memory=1024

Hello I am trying to boot/install VM on XenClient. I would like to learn the way to install VM. Please teach the example of the operation and config file. (Especially, configuration file of method of displaying screen.) thanks. ========================================= [My Executed History] (1) I made a config file for VM(Windows XP:below). (2) I executed the following commands. # xenvm