similar to: Automatic vncviewer startup

Hello, I have a Gentoo Linux guest, which was working very well with the past xm tool stack. Since the migration to xen-4.1.1 and to the new xl tool stack, I have a problem for the IP assignation. Actually, when dhcpcd starts at boot time the IP address is not correctly assigned. This also happens if I perform "dhcpcd eth0" once I''ve accessed to the guest shell. I

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

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

Hi, I build Xen 4.1.1 on a Gentoo base dom0. Everything is working great. I tried one of Joseph Glanville''s PV-HVM image (debian6) and its working as it should. Now l''im trying to build a Gentoo based domU with then same specs as Joseph''s PV-HVM. I used a copy of the .cfg and adapted to my needs to make the gentoo work. when booting the minimal install image using

Hello, I set up a Sabayon Linux domU as hvm guest and I completed the installation successfully. The problem is that when KDE is going to start, I see a blank screen. I use vncviewer but I don''t think this problem is related to vnc. Then I''ve read the minimal system requirements and I have seen this: 1) i686 Processor (starting from AMD K6 and Intel Pentium II) 2) 512 MB of RAM

Changes since v1: - Removed libxl vncviewer related dependencies - The vncviewer function was modified to accept a domid instead of domspec; - main_vncviewer was updated to reflect the new use. - A domain_create structure is now passed to the parse_config_data where required/feasible (NULL otherwise) - xl restore now have long options for vncviewer/vncviewer-autopass; docs updated. - Updated

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

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

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

I have been scouring this list''s archives and have consumed any and all how-to guides I could find but am still unsure. All discussion in this list on this issue is around hvm/vti DomU''s. Has anyone been able to attach a vnc client to a vanilla (non-hvm) DomU using the VNC console setting? On an FC5 (2.6.16-1.2080_FC5xen0) kernel deployed on vanilla (non-hvm) hardware,

What are the outstanding things to do before we think we can start on the 4.2 -rc''s? Does anyone have a timetable in mind? hypervisor: * ??? - Keir, Tim, Jan? tools: * libxl stable API -- we would like 4.2 to define a stable API which downstream''s can start to rely on not changing. Aspects of this are: * event handling (IanJ working

the man page for vncviewer presents the -via gateway option to use ssh through a gateway. I understand if I want a secure vnc connection to server.foo.com I can use the command: vncviewer localhost -via server.foo.com But I have moved my SSHD services from port 22 to port n. So according to the man pages, I need an environment variable of VNC_VIA_CMD and override the default command with:

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:

Hello Community, I encountered an error while running "xm console domU". Here is the running script: # xm console domU xenconsole: Could not read tty from store: No such file or directory I googled and found out that this issue is mostly result from forgetting starting xenconsole service. However, after I started xenconsole, the issue is still there. Please see: #

How do you send special keystrokes in vncviewer? I need to send Shift-F10... Searching the net showed nothing and realvnc's webpage yielded nothing either. Thanks! jlc

We began experiencing failed vnc connections to the console display on servers that have been updated to EL 6.3. No such failures have occurred on similar connections to EL 6.2 servers. On the client machine a normal vncviewer display appears with the expected graphical login until the mouse pointer is moved within the boundaries of the vncviewer window. At this point the window closes and an

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

Hello, I am trying to setup Debian Squeeze as domU, but I get the message below during the setup process: No Ethernet card was detected on Debian Squeeze domU install And it asks to select the driver to me. I followed the instructions at page 27 of the guest.pdf manual, but there is no indication on how to set-up the bridge in order to make the ethernet interface available for the guest. How

Hello everybody, Here again with a Xenbr0 bridge problem I''m a Gentoo user, xen-sources-2.6.34 and I always used the bridge from eth0 to xenbr0. Here''s what I get at boot time: * Bringing up interface eth0 * null [...] * Starting Xen control daemon ... And the bridge doesn''t come up. The normal behaviour should be that the Xenbr0 bridge comes up automatically, but