I try to install Windows XP on an AM2-box with Debian unstable and Xen 3.0.3. I can get the XP-install to start but cannot find any way to see the domU-display with vnc. If I have a domU.cfg of: sdl = 1 vnc = 0 vncviewer = 0 stdvga = 1 then I get a sdl-window on the dom0-window. If I have a domU.cfg of: sdl = 0 vnc = 1 vncviewer = 0 stdvga = 1 nothing happens when I try to connect with a vncviewer. I have tried all combinations I can image, mostly "ip.of.my.dom0:domU_id" . From dom0, nothing happens. From a windows-box I an told, that vnc cannot connect io server. From the windows-box I can vnc to dom0 with "ip.of.my.dom0" , and from dom0 I can vnc to the windows-box. I have googled without luck. Where can I find some background-material or FAQ about Xen and VNC ? -- Morten Christensen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Morten Christensen wrote:> I try to install Windows XP on an AM2-box with Debian unstable and Xen > 3.0.3. > > I can get the XP-install to start but cannot find any way to see the > domU-display with vnc. > > If I have a domU.cfg of: > > sdl = 1 > vnc = 0 > vncviewer = 0 > stdvga = 1 > > then I get a sdl-window on the dom0-window. > > > If I have a domU.cfg of: > > sdl = 0 > vnc = 1 > vncviewer = 0 > stdvga = 1 > > nothing happens when I try to connect with a vncviewer. I have tried all > combinations I can image, mostly "ip.of.my.dom0:domU_id" . From dom0, > nothing happens. From a windows-box I an told, that vnc cannot connect > io server. > > From the windows-box I can vnc to dom0 with "ip.of.my.dom0" , and from > dom0 I can vnc to the windows-box. > > I have googled without luck. Where can I find some background-material > or FAQ about Xen and VNC ?Hi, maybe missing "vncviewer = 1"? Maybe it is a help for you to see a working config from my domU on Debian/unstable: ... device_model = ''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' sdl=0 # enable VNC library for graphics, default = 1 vnc=1 # enable spawning vncviewer(only valid when vnc=1), default = 1 vncviewer=1 # no graphics, use serial port #nographic=0 # enable stdvga, default = 0 (use cirrus logic device model) stdvga=0 # start in full screen #full-screen=1 ... When I start the domU with #xm create mydomU.cfg from a xterm, I see a listening vnc-port afterwards: # netstat -nlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 4244/qemu-dm ... To this I can connect with vncviewer by ... $ vncviewer localhost VNC Viewer Free Edition 4.1.1 for X - built Oct 23 2006 05:52:17 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Mon Nov 20 20:17:27 2006 CConn: connected to host localhost port 5900 CConnection: Server supports RFB protocol version 3.3 CConnection: Using RFB protocol version 3.3 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding CConn: Throughput 20000 kbit/s - changing to hextile encoding CConn: Throughput 20000 kbit/s - changing to full colour CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding Mon Nov 20 20:18:33 2006 CConn: Throughput 20000 kbit/s - changing to raw encoding CConn: Using raw encoding ... and a xwindow with XP pops up. Gruss, Oliver _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
oz skrev den 20-11-2006 20:46:> Morten Christensen wrote: >> I try to install Windows XP on an AM2-box with Debian unstable and >> Xen 3.0.3. >> >> I can get the XP-install to start but cannot find any way to see the >> domU-display with vnc. >> >> If I have a domU.cfg of: >> >> sdl = 1 >> vnc = 0 >> vncviewer = 0 >> stdvga = 1 >> >> then I get a sdl-window on the dom0-window. >> >> >> If I have a domU.cfg of: >> >> sdl = 0 >> vnc = 1 >> vncviewer = 0 >> stdvga = 1 >> >> nothing happens when I try to connect with a vncviewer. I have tried >> all combinations I can image, mostly "ip.of.my.dom0:domU_id" . From >> dom0, nothing happens. From a windows-box I an told, that vnc cannot >> connect io server. >> >> From the windows-box I can vnc to dom0 with "ip.of.my.dom0" , and >> from dom0 I can vnc to the windows-box. >> >> I have googled without luck. Where can I find some >> background-material or FAQ about Xen and VNC ? > > Hi, > maybe missing "vncviewer = 1"? > > Maybe it is a help for you to see a working config from my domU on > Debian/unstable: > > ... > device_model = ''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > sdl=0 > # enable VNC library for graphics, default = 1 > vnc=1 > # enable spawning vncviewer(only valid when vnc=1), default = 1 > vncviewer=1 > # no graphics, use serial port > #nographic=0 > # enable stdvga, default = 0 (use cirrus logic device model) > stdvga=0 > # start in full screen > #full-screen=1 >When I changed my config to vncviewer = 1 stdvga = 0 I got one step further. Now I can make a vnc-session from dom0 with 0.0.0.0:1. It has to be :1 though the ID in xm list is 6 (probably because I only have one domU running). I have not had any success in connecting from the windows-box after trying all combinations I can imagine. On the other hand, the install of XP is just at the beginning, and the dom0 does not have any networking. -- Morten Christensen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Frank Pikelner skrev den 20-11-2006 21:42:> Morten, > > I''m planning to try Xen, AMD, and Windows XP/2003 shortly. Which AMD AM2 > motherboard are you using? Also do the AM2 motherboards have a BIOS > setting for enabling hardware virtualization like Intel CPU based > motherboards? Please let me know if you get your installation working. >ASRock am2nf6g-vsta. No special settings found anywhere. I am only at the beginning, but hvm seems to work. -- Morten Christensen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Frank Pikelner wrote:> Wanted to ask you offline, are you using an AMD AM2 socket motherboard > for Xen? If yes, which motherboard make/model?No sorry, it''s a Mac-mini-like Senyo 600X from transtec, based on Core 2 Duo T7200 and Intel chipset, board manufacturer unknown to me: http://www.transtec.de/D/D/products/PCworkstations/transtecsenyo600pc.html Gruss, Oliver _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Morten Christensen wrote:> oz skrev den 20-11-2006 20:46: >> Morten Christensen wrote: >>> I try to install Windows XP on an AM2-box with Debian unstable and >>> Xen 3.0.3. >>> >>> I can get the XP-install to start but cannot find any way to see the >>> domU-display with vnc. >>> >>> If I have a domU.cfg of: >>> >>> sdl = 1 >>> vnc = 0 >>> vncviewer = 0 >>> stdvga = 1 >>> >>> then I get a sdl-window on the dom0-window. >>> >>> >>> If I have a domU.cfg of: >>> >>> sdl = 0 >>> vnc = 1 >>> vncviewer = 0 >>> stdvga = 1 >>> >>> nothing happens when I try to connect with a vncviewer. I have tried >>> all combinations I can image, mostly "ip.of.my.dom0:domU_id" . From >>> dom0, nothing happens. From a windows-box I an told, that vnc cannot >>> connect io server. >>> >>> From the windows-box I can vnc to dom0 with "ip.of.my.dom0" , and >>> from dom0 I can vnc to the windows-box. >>> >>> I have googled without luck. Where can I find some >>> background-material or FAQ about Xen and VNC ? >> >> Hi, >> maybe missing "vncviewer = 1"? >> >> Maybe it is a help for you to see a working config from my domU on >> Debian/unstable: >> >> ... >> device_model = ''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' >> sdl=0 >> # enable VNC library for graphics, default = 1 >> vnc=1 >> # enable spawning vncviewer(only valid when vnc=1), default = 1 >> vncviewer=1 >> # no graphics, use serial port >> #nographic=0 >> # enable stdvga, default = 0 (use cirrus logic device model) >> stdvga=0 >> # start in full screen >> #full-screen=1 >> > When I changed my config to > vncviewer = 1 > stdvga = 0 > > I got one step further. Now I can make a vnc-session from dom0 with > 0.0.0.0:1. It has to be :1 though the ID in xm list is 6 (probably > because I only have one domU running). > > I have not had any success in connecting from the windows-box after > trying all combinations I can imagine. On the other hand, the install of > XP is just at the beginning, and the dom0 does not have any networking.It''s not clear, what you''re doing exactly; are you running "vncviewer 0.0.0.0:1"? Then :1 is the display number and not your vm-id. Look at the output of "$ env" and a line like DISPLAY=:0.0 (then :0 is the display number of your desktop-owner). What do you mean with "windows-box"? When you open a x-terminal like xterm, konsole or gterm as a normal user, entering "vncviewer 127.0.0.1:0" should do it (assuming ifconfig shows a loopback interface lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0). Gruss, Oliver _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
oz skrev den 20-11-2006 22:48:> Morten Christensen wrote: >> oz skrev den 20-11-2006 20:46: >>> Morten Christensen wrote: >>>> I try to install Windows XP on an AM2-box with Debian unstable and >>>> Xen 3.0.3. >>>> >>>> I can get the XP-install to start but cannot find any way to see >>>> the domU-display with vnc. >>>> >>>> If I have a domU.cfg of: >>>> >>>> sdl = 1 >>>> vnc = 0 >>>> vncviewer = 0 >>>> stdvga = 1 >>>> >>>> then I get a sdl-window on the dom0-window. >>>> >>>> >>>> If I have a domU.cfg of: >>>> >>>> sdl = 0 >>>> vnc = 1 >>>> vncviewer = 0 >>>> stdvga = 1 >>>> >>>> nothing happens when I try to connect with a vncviewer. I have >>>> tried all combinations I can image, mostly "ip.of.my.dom0:domU_id" >>>> . From dom0, nothing happens. From a windows-box I an told, that >>>> vnc cannot connect io server. >>>> >>>> From the windows-box I can vnc to dom0 with "ip.of.my.dom0" , and >>>> from dom0 I can vnc to the windows-box. >>>> >>>> I have googled without luck. Where can I find some >>>> background-material or FAQ about Xen and VNC ? >>> >>> Hi, >>> maybe missing "vncviewer = 1"? >>> >>> Maybe it is a help for you to see a working config from my domU on >>> Debian/unstable: >>> >>> ... >>> device_model = ''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' >>> sdl=0 >>> # enable VNC library for graphics, default = 1 >>> vnc=1 >>> # enable spawning vncviewer(only valid when vnc=1), default = 1 >>> vncviewer=1 >>> # no graphics, use serial port >>> #nographic=0 >>> # enable stdvga, default = 0 (use cirrus logic device model) >>> stdvga=0 >>> # start in full screen >>> #full-screen=1 >>> >> When I changed my config to >> vncviewer = 1 >> stdvga = 0 >> >> I got one step further. Now I can make a vnc-session from dom0 with >> 0.0.0.0:1. It has to be :1 though the ID in xm list is 6 (probably >> because I only have one domU running). >> >> I have not had any success in connecting from the windows-box after >> trying all combinations I can imagine. On the other hand, the install >> of XP is just at the beginning, and the dom0 does not have any >> networking. > > It''s not clear, what you''re doing exactly; are you running "vncviewer > 0.0.0.0:1"? Then :1 is the display number and not your vm-id. Look at > the output of "$ env" and a line like DISPLAY=:0.0 (then :0 is the > display number of your desktop-owner).Does VNC always connect to the display-number and not to the vm-id ? -- Morten Christensen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/22/06, Morten Christensen <mc-xen@mc.cx> wrote:> Does VNC always connect to the display-number and not to the vm-id ?Yes - it is VNC, after all... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello I had same problem with xen 3.0.3 ebuild on gentoo x86. The previous version 3.0.2 worked without problem. The problem is that vnc setting little bit changed. Here is qoute from /etc/xen/xmexample.hvm #---------------------------------------------------------------------------- # address that should be listened on for the VNC server if vnc is set. # default is to use ''vnc-listen'' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" And that is the reason why you are not able to connect via VNC to DOMu because VNC server is bindend to 127.0.0.1. After I have changed my windows domain config file adding: vnclisten="ip.of.my.dom0" I can connect to hvm domain via VNC. Further investigation is probably still needed because vncviewer ip.of.my.dom0:domID is not working now. Maybe editing xend-config.sxp will help. BR Peter 2006/11/24, Jerry Amundson <jamundso@gmail.com>:> On 11/22/06, Morten Christensen <mc-xen@mc.cx> wrote: > > Does VNC always connect to the display-number and not to the vm-id ? > > Yes - it is VNC, after all... > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users