similar to: [PATCH][VT]Don''t leave vncviewer processes running if xm create fails

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''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

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

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 everyone! I have a problem with start correctly HVM Suse from iso under DEBIAN Dom0 64bit. I installed xen from debian packages and then I create this config file: gamma.hvm kernel="/usr/lib/xen-3.0.3-1/boot/hvmloader" builder=''hvm'' device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' memory=512 name=''gamma'' vif=[

VT is enabled in BIOS and ''xm info'' shows that hvm can be created like below: xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm -3.0-x86_64 Several Windows VMs have been created on this server and running perfectly. However, I wonder that it does not show anything when commands show VT-x availability such as ''xm dmesg | grep VMX(or

Hi, When a domain shuts down it seems to stay visible in the output of xm list (see below) even if I do an ''xm destroy''. Has something changed (they used to disappear just fine for me)? I am running Xen 2.0 (fairly up-to-date). Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 395 0 r---- 2377.2 cagnode91-clone 10 199 2

If I have vnc=1 and try to start a domain, if the domain creation fails for some reason, the vncviewer process is not cleaned up. I''ll try to send a patch next week if no one gets there before I do. -Arun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Unable to connect to my HVM # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3869 2 r----- 368.6 vm00 45 128 1 -b---- 62.3 The vm00 changes state from "r" to "b" after about a minute. (I have a fedora dvd in the drive.) #cat

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

When start a domU through xl create. The domU associated ip in the configuration file is not recorded in the xenstore. For this reason vif-common.sh antispoof scripts fails. *xl create * /usr/bin/xenstore-ls /local/domain/0/backend/vif/5/0 frontend = "/local/domain/5/device/vif/0" frontend-id = "5" online = "1" state = "4" script =

Hi all, Anybody know what it means for a DomU to show up in the "xm list" as follows: Name ID Mem VCPUs State Time(s) Domain-0 0 256 2 r----- 43929.3 Clonezilla 16 512 1 ------ 6.2 The domU "Clonezilla" does not have an "r" state

The patch attached is to set effective memory type for EPT according to the VT-d snoop control capability, and also includes some cleansup for EPT & VT-d both enabled. Signed-off-by: Zhai, Edwin Edwin.Zhai@intel.com<mailto:Edwin.Zhai@intel.com> Signed-off-by: Xin, Xiaohui xiaohui.xin@intel.com<mailto:xiaohui.xin@intel.com> _______________________________________________

Dear List, I need to make an Aladdin eToken Pro visible in a Linux guest HVM, but I cannot assign the device to any domU, while it''s being blocked by the dom0. To avoid this trouble I would like to pass the whole USB bus to the domU directly, via PCI passthrough. Now I use xen 3.3.0 from xensource and xen kernel from Ubuntu 8.04 2.6.24-19-xen, because the xensource xen kernel

Hello everybody, i have a problem setting up a DomU with Windows XP. I get the following error: xen:/etc/xen# xm create windows.hvm Using config file "./windows.hvm". VNC= 1 Unexpected error: exceptions.OSError Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-3.1-1/bin/xm", line 7, in ? main.main(sys.argv) File

I have xkeybindings running just fine on centos 5. I have vncviewer running in full screen mode showing another PC. When vncviewer is running is running it seems to override my xkeybindings. Is there a way to tell vncviewer to not bind to any keys?? The only keys I am binding is on the Keypad 3,4,6, 9 and Enter. Nothing that vncviewer uses anyway. How can I still have my xkeybindings active

I have a host that I have been accessing with vncviewer via its fqdn that had only an IPv4 A record. I just added a AAAA IPv6 record, and vncviewer via fqdn stopped working. But worked when I provided the IPv4 address instead. It LOOKS like vncviewer is trying the IPv6 address, eventhough all documentation indicates that it does not support IPv6. Definitely my server is only listening on

Hi, all I was trying to install Xen on CentOS5.4. The OS has a "virtualization" option, and I choose to install, so I get the 3.0 version of Xen. When I trying to install a higher version 3.4.1, the make world and make install process went ok, and the "xm list" command could show the domain 0. So I created a guest OS in virtual machine manager and wanted to install a guest

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug