similar to: hiding the xm console window

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]

Hi all, the guest is really running but issue xm list command, the states is -b---- . when I want to connect to the guest using #xm console dom1 Now waiting a long time and get no response. But I can "xm console" into it only during boot and shutdown like this: #xm reboot dom1 #xm console dom1 Now it can be connected. what is the problem?

Hello all, I am new to Xen; I followed a few techtips/technotes from How2forge and other linux sites to walk me through configuring the following: - proper installation of xen kernel on a CentOS 5.1 server - booting into the xen kernel and checking the Dom0 (all is fine): [root at dataserv3 /]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0

Hello, I''m using Red Hat AS 5 with Xen 3.0, and sometimes ''xm console'' does not work, the most of times when I''m trying to connect one full-virt machine with different arch from server, for example: [root@xen-5 ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1933 8

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

Hello, I''m running XEN 3.0.3 on RHEL5 2.6.18-53.1.4.el5xen. I used to start the vm with "xm create myvm -c". I see the boot during a couple of second, then, it freeze. The console is freezed, not the vm, a couple of second later, I can ssh the vm without any problem. "xm console myvm" also display a freezed state. This is an extrat of the console : # xm create

While installing DomU via debootstrap method I got the following error in my /var/log/xen-tools/mydomU logs Can not write log, openpty() failed (/dev/pts not mounted?) and when I tried to run xm console mydomU I got /usr/lib/xen-tools/jaunty.d# xm console mydomU Error: Domain ''mydomU'' does not exist. now what is the meaning of above error I want to resolve it and proceed

Hi guys, On my CentOS 5.5, I installed xen by yum, and create ‘vm1’, and ‘vm1’ work well. Then I find I install a very old version of xen by yum as default. So I download xen4.0.1 source code, and installed successfully. Then I just create vm1 by the old configuration file, ‘xm create vm1’. The vm1 running well, and I can ssh onto it, but while I login it by ‘xm console vm1’, it hangs, no other

If I type "xm console 6", say (when I have a virtual machine 6 running), what should I get? The documentation seems to indicate that I should get something that behaves like a telnet to a serial console. What I actually get is a connection that might show me a couple of lines of output that do look like they belonged on the console, but doesn't seem to accept any input (except that

Hi all I''m running CentOS 5.1 x64 + Xen 3.0 & I have setup a CentOS 5.1 x64 domU as a HMV. For the setup I used VNC, but I would prefer to be able to access it via "xm console cPanel" via SSH directly. Here''s the output cPanel HVM: [root@pc-00059 ~]# more /etc/xen/cPanel name = "cPanel" uuid = "ff940501-507d-04ca-e590-831e79ba0397" maxmem =

Previously, I used to run 2.6.18 kernel built from Xen sources. I just tried to run a 2.6.25.1 domU kernel on top of Xen 3.2 - after changing domU''s config file here and there, I successfully booted the guest, but I''m still unable to use xm console. When I start the domain, it displays all kernel and bootup messages, but I don''t get any prompt after the bootup is

Hi Fellas, When I connect to a domain''s console via xm console vmid I have to press an enter to get the console prompt. I am wondering if anyone else has seen this and if there is a remedy for this? Thanks, -Himanshu -- ------------------------------------------------------------------------- Himanshu Raj PhD Student, GaTech (www.cc.gatech.edu/~rhim) I prefer to receive

Hi folks, my problem: i am using putty and german layout. if i login from dom0 with "xm console xen1" i can login into the xen1 (domU) but how can i quit this console ? i have tested several commands: ctrl+5 ctrl+altgr+9 ctrl+c ctrl+x nothin happend. any hints ? -- Have an nice day, Viele Grüße Dominique H Schramm _______________________________________________ Xen-users

Hi, What''s best way to connect to a Redhat 7.3 HVM console by using "xm console <domU>"? Set up serial console in some way? Simon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I notice that since upgrading to the CentOS Xen 3.2 package the command "xm console" appears to hang. Only when I hit enter it shows me the login prompt. If I don''t do that it hangs indefinitely. Also, it prints a dmesg-like output before showing the login prompt now. If I hit enter too fast it may still be in the middle of this output and I have even seen it then hang

Currently console class''s "other_config" parameters (such as "vnclisten" and "vncpasswd") are not passed to xend when creating a domain by xm command through xen-api. The attached patch fixes this problem. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list

Hi list, I am running a virtualized server. Dom0 uses Xen 3.2.1 with Debian Etch and a custom kernel 2.6.21 created by my webhosting company. I install my domU using debootstrap for a Debian Etch with 2.6.18-6-xen-amd64 kernel. Everything works well except the fact that once the VM is started I cannot "xm console" into it. It only works while it is booting and while it is shutting

Hi all. I am comming back to the virtualization... Days ago I installed Centos 5.5 and I want to tray xen Full virtualization.. so I create and installed my Full virtual machine. I use virt-manager... the VM run pretty well... But... If I connect remotly using ssh to domain0 and then use "xm console ID" I get nothing.... and I have to ctrl + ].... (this happen too if I am locally in

Package: xen-utils-common Version: 3.4.2-2 Severity: important On a fresh Debian Sid system, I get this: # xm new Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-3.4/bin/xm", line 8, in <module> main.main(sys.argv) File