From xen-users-bounces@lists.xen.org Sat Mar 01 08:48:42 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 01 Mar 2014 08:48:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WJfa0-000340-3H; Sat, 01 Mar 2014 08:47:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WJfZy-00033o-MV for xen-users@lists.xen.org; Sat, 01 Mar 2014 08:47:30 +0000 Received: from [85.158.143.35:58600] by server-3.bemta-4.messagelabs.com id 5E/A6-11539-2AE91135; Sat, 01 Mar 2014 08:47:30 +0000 X-Env-Sender: sonjs91@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1393663648!9172486!1 X-Originating-IP: [209.85.192.42] X-SpamReason: No, hits=2.0 required=7.0 tests=BODY_RANDOM_LONG,HOT_NASTY, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15159 invoked from network); 1 Mar 2014 08:47:29 -0000 Received: from mail-qg0-f42.google.com (HELO mail-qg0-f42.google.com) (209.85.192.42) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2014 08:47:29 -0000 Received: by mail-qg0-f42.google.com with SMTP id q107so5150789qgd.1 for ; Sat, 01 Mar 2014 00:47:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=sWrzcceoO73LHRDjDXZOa6xy+ECW0wiWE8GS96vsY70=; b=oyG1E9kxYmSYOdxUbuwVDa8ojSZn52chiSKDIg0l+xUF8mbcFuHA90zgKXfs3Gdu0J J7XbkoTiCPjCXZlANF0HKoYeD1RWi8zIaMUhPIzhUQt/7dD06YK0L2KsQ8yAshtMLhdY XOA25xt6qrp3Fv7lYaCUAvZuhvIMRSyL8ArRTjlNhbVnCx9qoZWLCqIPRZw6Bv79eF7g PMEPYIQh8nXceZmKx25pIdL4t4JyD5c8+XZflXfFWq7v5+K0gFc9aPIEkfMHraFVwNyJ bzO92HTT+w8gLEn3BN9Yb4zwO/UympiDJhQ0bcQ9AHVUvQz2xEcxkby3SlLtQ11djyUz Okjg== MIME-Version: 1.0 X-Received: by 10.140.83.99 with SMTP id i90mr931886qgd.100.1393663647962; Sat, 01 Mar 2014 00:47:27 -0800 (PST) Received: by 10.224.88.194 with HTTP; Sat, 1 Mar 2014 00:47:27 -0800 (PST) In-Reply-To: <20140227144444.GF16241@zion.uk.xensource.com> References: <20140227144444.GF16241@zion.uk.xensource.com> Date: Sat, 1 Mar 2014 17:47:27 +0900 X-Google-Sender-Auth: Ti6drcmwkYeA1xhEcZB8xFk5P_I Message-ID: From: Jeongseok Son To: Wei Liu Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Cannot access to PV domU via VNC X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thank you so much. I did a stupid mistake. Now I set the vnclisten option as 0.0.0.0 then I can connect to it. However, I could only see a black screen on VNC client so I tried to install x window system. apt-get install x-window-system And then I ran "startx" command but I got this error message. (EE) open /dev/fb0: No such file or directory (EE) No devices detected. Fatal server error: no screens found Why frame buffer device is not enabled in PV domU? Ho can solve this issue? On Thu, Feb 27, 2014 at 11:44 PM, Wei Liu wrote: > On Wed, Feb 26, 2014 at 11:47:39PM +0900, Jeongseok Son wrote: >> Hello, I have to use graphical interface in PV domU so I tried to >> connect to domU via VNC. >> >> I'm currently using Xen Hypervisor 4.3.1. I installed Ubuntu Lucid >> (10.04) PV domU with xen-create-image. I can use hvc0 console of domU >> (with xl console command) but cannot connect to VNC console. >> >> The following is my xen configuration for PV domU. >> >> # Kernel + memory size >> kernel = '/boot/vmlinuz-3.9.4+' >> ramdisk = '/boot/initrd.img-3.9.4+' >> >> vcpus = '2' >> memory = '2048' >> >> # Disk device(s) >> root = '/dev/xvda2 ro' >> disk = [ >> 'file:/path/to/disk.img,xvda2,w', >> 'file:/path/to/swap.img,xvda1,w', >> ] >> >> # Hostname >> name = 'pv-ubuntu' >> >> # vfb >> vfb = [ "vnc=1, vncpasswd='', vncdisplay=1" ] >> >> # Behaviour >> on_poweroff = 'destroy' >> on_reboot = 'restart' >> on_crash = 'restart' >> >> With netstat -a command, the following line is printed so I think Xen >> listens the connections. >> >> Proto Recv-Q Send-Q Local Address Foreign Address State >> tcp 0 0 localhost:5901 *:* >> LISTEN >> > > That's because your vnc is listening on 127.0.0.1 only. > > Please have a look at xl manpage for the "vnclisten" option. > > Wei. > >> But when I attempt to connect to it using VNC client, I got >> "Connection to host xxx.xxx.xxx.xxx::5901 was closed." message. >> >> I successfully worked with GUI Interface via VNC in HVM domU (Both >> Ubuntu 12.04 Desktop and Server). >> Why it doesn't work in PV domU? Are there anything to set up in PV >> domU to make it work? >> I really appreciate any help you can provide. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Mar 01 08:48:42 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 01 Mar 2014 08:48:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WJfa0-000340-3H; Sat, 01 Mar 2014 08:47:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WJfZy-00033o-MV for xen-users@lists.xen.org; Sat, 01 Mar 2014 08:47:30 +0000 Received: from [85.158.143.35:58600] by server-3.bemta-4.messagelabs.com id 5E/A6-11539-2AE91135; Sat, 01 Mar 2014 08:47:30 +0000 X-Env-Sender: sonjs91@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1393663648!9172486!1 X-Originating-IP: [209.85.192.42] X-SpamReason: No, hits=2.0 required=7.0 tests=BODY_RANDOM_LONG,HOT_NASTY, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15159 invoked from network); 1 Mar 2014 08:47:29 -0000 Received: from mail-qg0-f42.google.com (HELO mail-qg0-f42.google.com) (209.85.192.42) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2014 08:47:29 -0000 Received: by mail-qg0-f42.google.com with SMTP id q107so5150789qgd.1 for ; Sat, 01 Mar 2014 00:47:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=sWrzcceoO73LHRDjDXZOa6xy+ECW0wiWE8GS96vsY70=; b=oyG1E9kxYmSYOdxUbuwVDa8ojSZn52chiSKDIg0l+xUF8mbcFuHA90zgKXfs3Gdu0J J7XbkoTiCPjCXZlANF0HKoYeD1RWi8zIaMUhPIzhUQt/7dD06YK0L2KsQ8yAshtMLhdY XOA25xt6qrp3Fv7lYaCUAvZuhvIMRSyL8ArRTjlNhbVnCx9qoZWLCqIPRZw6Bv79eF7g PMEPYIQh8nXceZmKx25pIdL4t4JyD5c8+XZflXfFWq7v5+K0gFc9aPIEkfMHraFVwNyJ bzO92HTT+w8gLEn3BN9Yb4zwO/UympiDJhQ0bcQ9AHVUvQz2xEcxkby3SlLtQ11djyUz Okjg== MIME-Version: 1.0 X-Received: by 10.140.83.99 with SMTP id i90mr931886qgd.100.1393663647962; Sat, 01 Mar 2014 00:47:27 -0800 (PST) Received: by 10.224.88.194 with HTTP; Sat, 1 Mar 2014 00:47:27 -0800 (PST) In-Reply-To: <20140227144444.GF16241@zion.uk.xensource.com> References: <20140227144444.GF16241@zion.uk.xensource.com> Date: Sat, 1 Mar 2014 17:47:27 +0900 X-Google-Sender-Auth: Ti6drcmwkYeA1xhEcZB8xFk5P_I Message-ID: From: Jeongseok Son To: Wei Liu Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Cannot access to PV domU via VNC X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thank you so much. I did a stupid mistake. Now I set the vnclisten option as 0.0.0.0 then I can connect to it. However, I could only see a black screen on VNC client so I tried to install x window system. apt-get install x-window-system And then I ran "startx" command but I got this error message. (EE) open /dev/fb0: No such file or directory (EE) No devices detected. Fatal server error: no screens found Why frame buffer device is not enabled in PV domU? Ho can solve this issue? On Thu, Feb 27, 2014 at 11:44 PM, Wei Liu wrote: > On Wed, Feb 26, 2014 at 11:47:39PM +0900, Jeongseok Son wrote: >> Hello, I have to use graphical interface in PV domU so I tried to >> connect to domU via VNC. >> >> I'm currently using Xen Hypervisor 4.3.1. I installed Ubuntu Lucid >> (10.04) PV domU with xen-create-image. I can use hvc0 console of domU >> (with xl console command) but cannot connect to VNC console. >> >> The following is my xen configuration for PV domU. >> >> # Kernel + memory size >> kernel = '/boot/vmlinuz-3.9.4+' >> ramdisk = '/boot/initrd.img-3.9.4+' >> >> vcpus = '2' >> memory = '2048' >> >> # Disk device(s) >> root = '/dev/xvda2 ro' >> disk = [ >> 'file:/path/to/disk.img,xvda2,w', >> 'file:/path/to/swap.img,xvda1,w', >> ] >> >> # Hostname >> name = 'pv-ubuntu' >> >> # vfb >> vfb = [ "vnc=1, vncpasswd='', vncdisplay=1" ] >> >> # Behaviour >> on_poweroff = 'destroy' >> on_reboot = 'restart' >> on_crash = 'restart' >> >> With netstat -a command, the following line is printed so I think Xen >> listens the connections. >> >> Proto Recv-Q Send-Q Local Address Foreign Address State >> tcp 0 0 localhost:5901 *:* >> LISTEN >> > > That's because your vnc is listening on 127.0.0.1 only. > > Please have a look at xl manpage for the "vnclisten" option. > > Wei. > >> But when I attempt to connect to it using VNC client, I got >> "Connection to host xxx.xxx.xxx.xxx::5901 was closed." message. >> >> I successfully worked with GUI Interface via VNC in HVM domU (Both >> Ubuntu 12.04 Desktop and Server). >> Why it doesn't work in PV domU? Are there anything to set up in PV >> domU to make it work? >> I really appreciate any help you can provide. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Mar 01 11:43:22 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 01 Mar 2014 11:43:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WJiIe-0006Bg-KY; Sat, 01 Mar 2014 11:41:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WJiId-0006Bb-CV for xen-users@lists.xensource.com; Sat, 01 Mar 2014 11:41:47 +0000 Received: from [193.109.254.147:49438] by server-12.bemta-14.messagelabs.com id 2B/DB-17220-A77C1135; Sat, 01 Mar 2014 11:41:46 +0000 X-Env-Sender: guy20034u@yahoo.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1393674104!7701654!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.6 required=7.0 tests=FORGED_YAHOO_RCVD, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22193 invoked from network); 1 Mar 2014 11:41:45 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-10.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 1 Mar 2014 11:41:45 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WJiIZ-0003CP-GH for xen-users@lists.xensource.com; Sat, 01 Mar 2014 03:41:43 -0800 Date: Sat, 1 Mar 2014 03:41:43 -0800 (PST) From: sbdcunha To: xen-users@lists.xensource.com Message-ID: <1393674103498-5721437.post@n5.nabble.com> In-Reply-To: <1393584710.27819.19.camel@hastur.hellion.org.uk> References: <1393581460837-5721433.post@n5.nabble.com> <1393584710.27819.19.camel@hastur.hellion.org.uk> MIME-Version: 1.0 Subject: Re: [Xen-users] static Ip to DomU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear Ian, really appreciate your wise reply .. am really grateful to all u guys and sorry for lots of postings. As I mentioned before I have centos 6.5 X64 xen server 6.5 and has installed xen as per http://wiki.centos.org/HowTos/Xen/Xen4QuickStart & http://www.howtoforge.com/virtualization-with-xen-on-centos-6.3-x86_64-paravirtualization-and-hardware-virtualization my xen version is --- virsh # version Compiled against library: libvirt 0.10.2 Using library: libvirt 0.10.2 Using API: Xen 0.10.2 Running hypervisor: Xen 4.2.0 --- as i said before my xen Guest cannot reach outside DOM0. Now I deleted all the vm and created 2 new Centos 6.5 Guests through graphical utility virt-manager For the first guest I choose the option for network as host device eth1 ( bridge 'br1') and assigned ip from the same range as DOM0's br1 the second guest I choose the option Virtual Network 'default':NAT and then during the installation I let DHCP assign the ip for my Guest centos OS i found that my guest vm has a ip setting from virbr0 that is 192.168.122.x . Now I found that from my first VM can only ping DOM0 br1 ip and nothing else but from the second VM i can not only ping Dom0 but also any other pc in our network and also the internet in virsh command mode i see for my first VM under network interafce ---