My dom0 is Gentoo and I''m trying to boot an HVM off of a Ubuntu Feisty
ISO image.
I apparently have X already listening on 5900... for the "shared
desktop" feature of the modern X servers.
So I have:
vnc=1
vncdisplay=6
vncconsole=1
I''ve left out the vncdisplay and vncconsole in trials. Still (netstat
says) nothing is listening on 5901 or 5906 for my vncviewer to connect
to. In /etc/xen/xend-config I have vnc-listen ''127.0.0.1'' and
a
vncpasswd set.
I ran across xenstore-ls. I see this:
backend = ""
vfb = ""
1= ""
0 = ""
vncunused = "1"
....
2 = ""
0 = ""
vncunused = "1"
....
Does the vncunused shown here indicate a problem?
Could it be the build of Xen on Gentoo?
Thanks,
Scott Serr
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2007/9/18, Scott Serr <serrs@theserrs.net>:> My dom0 is Gentoo and I''m trying to boot an HVM off of a Ubuntu Feisty > ISO image. > > I apparently have X already listening on 5900... for the "shared > desktop" feature of the modern X servers. > > So I have: > > vnc=1 > vncdisplay=6 > vncconsole=1Can you paste all config file?> Could it be the build of Xen on Gentoo?Which package are you using? I have the last 3.1 from portage tree and it works perfectly. Regards. -- Alessandro R. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
two things : - in the xend-config, if you have a listen 127.0.0.1 you can use vncviewer only on the local server. try 0.0.0.0 - perhaps you have an iptables running regards yves Scott Serr a écrit :> My dom0 is Gentoo and I''m trying to boot an HVM off of a Ubuntu Feisty > ISO image. > > I apparently have X already listening on 5900... for the "shared > desktop" feature of the modern X servers. > > So I have: > > vnc=1 > vncdisplay=6 > vncconsole=1 > > I''ve left out the vncdisplay and vncconsole in trials. Still (netstat > says) nothing is listening on 5901 or 5906 for my vncviewer to connect > to. In /etc/xen/xend-config I have vnc-listen ''127.0.0.1'' and a > vncpasswd set. > > I ran across xenstore-ls. I see this: > backend = "" > vfb = "" > 1= "" > 0 = "" > vncunused = "1" > .... > 2 = "" > 0 = "" > vncunused = "1" > .... > > Does the vncunused shown here indicate a problem? > > Could it be the build of Xen on Gentoo? > > Thanks, > Scott Serr > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Yves-Gaël Chény Directeur technique 44 Boulevard des Pas Enchantés 44230 St Sébastien sur Loire Tel : 02 40 97 62 67 - 08 73 77 24 91 GSM : 06 98 58 41 55 http://www.tranquilitsystems.com/ yves-gael.cheny@tranquil-it-systems.fr Tranquil IT Systems . SAS 37 000 ¤ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Alessandro R. wrote:> 2007/9/18, Scott Serr <serrs@theserrs.net>: > >> My dom0 is Gentoo and I''m trying to boot an HVM off of a Ubuntu Feisty >> ISO image. >> >> I apparently have X already listening on 5900... for the "shared >> desktop" feature of the modern X servers. >> >> So I have: >> >> vnc=1 >> vncdisplay=6 >> vncconsole=1 >> > > Can you paste all config file? > >kernel="/usr/lib64/xen/boot/hvmloader" builder=''hvm'' #device_model=''/usr/lib64/xen/bin/qemu-dm'' memory=384 name=''feisty'' vif=[ ''type=ioemu,bridge=xenbr0'' ] disk=[''file:/data/xen/feisty/hda.img,ioemu:hda,w'',''file:/data/ubuntu-7.04-desktop-i386.iso,hdc:cdrom,r''] boot=''d'' vnc=1 vncdisplay=6 #vncviewer=1 #sdl=1 Note: "xm list" shows the VM name "feisty" is running... I just can''t see it. Ideas of what to try are welcome.>> Could it be the build of Xen on Gentoo? >> > > Which package are you using? I have the last 3.1 from portage tree and > it works perfectly. >I''m using the portage overlay... yes 3.1. (I thought this was the only way to get 3.1) Also, my dom0/Gentoo is "amd64". SLES10SP1 works so well as a dom0, but everything is a bit old. Thanks for your help. -Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Scott Serr wrote:> Alessandro R. wrote: >> 2007/9/18, Scott Serr <serrs@theserrs.net>: >> >>> My dom0 is Gentoo and I''m trying to boot an HVM off of a Ubuntu Feisty >>> ISO image. >>> >>> I apparently have X already listening on 5900... for the "shared >>> desktop" feature of the modern X servers. >>> >>> So I have: >>> >>> vnc=1 >>> vncdisplay=6 >>> vncconsole=1 >>> >> >> Can you paste all config file? >> >> > kernel="/usr/lib64/xen/boot/hvmloader" > builder=''hvm'' > #device_model=''/usr/lib64/xen/bin/qemu-dm'' > memory=384 > name=''feisty'' > vif=[ ''type=ioemu,bridge=xenbr0'' ] > disk=[''file:/data/xen/feisty/hda.img,ioemu:hda,w'',''file:/data/ubuntu-7.04-desktop-i386.iso,hdc:cdrom,r''] > > boot=''d'' > vnc=1 > vncdisplay=6 > #vncviewer=1 > #sdl=1 > > Note: "xm list" shows the VM name "feisty" is running... I just can''t > see it. Ideas of what to try are welcome.I mis-spoke.. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3620 4 r----- 30.8 feisty 1 384 1 ------ 0.0 feisty is not running... not accruing time and not in a run state. Alessandro, did you use a guide? Oh no... I think I found my problem. http://gentoo-wiki.com/HOWTO_Xen_and_Gentoo> *Note:* For HVM guests to be able to start, it is important that you > create the appropriate tap device(s). Thus, the > *sys-apps/usermode-utilities* package is required (tunctl), and > *support for TUN/TAP devices* must be activated in the kernel > configuration.I''ll report if this fixes it. Thanks, -Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Sep-19 13:38 UTC
RE: [Xen-users] VNC to HVM not starting
Hello, I''m not very skilled on the vnc options, but what does it mean if You have vncdisplay=6 ? I gues it should mean the domain should be accessible through VNC on the port 5906, isn''t it? Is there nothing running on this port? Maybe the domain cannot start because the port 5906 is already in use... can You try to run netstat -a -n if the domain not started and if it is started? Are there any differences? What can You find in the corresponding /var/log/xen/qemu-dm*.log file? Are there any errors? With best regards, Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Scott Serr Sent: Tuesday, September 18, 2007 6:30 PM To: Alessandro R. Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] VNC to HVM not starting Scott Serr wrote:> Alessandro R. wrote: >> 2007/9/18, Scott Serr <serrs@theserrs.net>: >> >>> My dom0 is Gentoo and I''m trying to boot an HVM off of a Ubuntu Feisty >>> ISO image. >>> >>> I apparently have X already listening on 5900... for the "shared >>> desktop" feature of the modern X servers. >>> >>> So I have: >>> >>> vnc=1 >>> vncdisplay=6 >>> vncconsole=1 >>> >> >> Can you paste all config file? >> >> > kernel="/usr/lib64/xen/boot/hvmloader" > builder=''hvm'' > #device_model=''/usr/lib64/xen/bin/qemu-dm'' > memory=384 > name=''feisty'' > vif=[ ''type=ioemu,bridge=xenbr0'' ] >disk=[''file:/data/xen/feisty/hda.img,ioemu:hda,w'',''file:/data/ubuntu-7.04-de sktop-i386.iso,hdc:cdrom,r'']> > boot=''d'' > vnc=1 > vncdisplay=6 > #vncviewer=1 > #sdl=1 > > Note: "xm list" shows the VM name "feisty" is running... I just can''t > see it. Ideas of what to try are welcome.I mis-spoke.. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3620 4 r----- 30.8 feisty 1 384 1 ------ 0.0 feisty is not running... not accruing time and not in a run state. Alessandro, did you use a guide? Oh no... I think I found my problem. http://gentoo-wiki.com/HOWTO_Xen_and_Gentoo> *Note:* For HVM guests to be able to start, it is important that you > create the appropriate tap device(s). Thus, the > *sys-apps/usermode-utilities* package is required (tunctl), and > *support for TUN/TAP devices* must be activated in the kernel > configuration.I''ll report if this fixes it. Thanks, -Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2540 (20070919) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Does "/usr/lib64/xen/boot/hvmloader" actually exist?
On my 64-bit gentoo machine, the hvmloader is under
"/usr/lib/xen/boot/hvmloader".
Also, I believe you need the device model uncommented. Here is my
config for a working ubuntu HVM on gentoo. Xen 3.1 was released into
portage a few weeks back (it may be masked, but it works fine) and I''m
running that.
***Note, that this is already installed and I''ve detached the cdrom,
your config options for the cdrom and boot device look correct if you
are still trying to install.
# -*- mode: python; -*-
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 1024
name = "ubuntu"
vif = [ ''mac=00:16:3e:0c:5a:00, type=ioemu, bridge=xenbr0'' ]
disk = [ ''file:/xen/linux/ubuntu/ubuntu-7.04.img,ioemu:hda,w''
]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="c"
sdl=0
vnc=1
vncdisplay=9
vncunused=0
vncconsole=1
> kernel="/usr/lib64/xen/boot/hvmloader"
> builder=''hvm''
> #device_model=''/usr/lib64/xen/bin/qemu-dm''
> memory=384
> name=''feisty''
> vif=[ ''type=ioemu,bridge=xenbr0'' ]
>
disk=[''file:/data/xen/feisty/hda.img,ioemu:hda,w'',''file:/data/ubuntu-7.04-desktop-i386.iso,hdc:cdrom,r'']
> boot=''d''
> vnc=1
> vncdisplay=6
> #vncviewer=1
> #sdl=1
>
> Note: "xm list" shows the VM name "feisty" is
running... I just can''t
> see it. Ideas of what to try are welcome.
>
> >> Could it be the build of Xen on Gentoo?
> >>
> >
> > Which package are you using? I have the last 3.1 from portage tree and
> > it works perfectly.
> >
> I''m using the portage overlay... yes 3.1. (I thought this was the
only
> way to get 3.1) Also, my dom0/Gentoo is "amd64".
>
> SLES10SP1 works so well as a dom0, but everything is a bit old.
>
> Thanks for your help.
> -Scott
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Sep-19 17:18 UTC
RE: [Xen-users] VNC to HVM not starting
Hello, I''ve tested it and this is not true what I said and thought, it seems to be the fact the display is not influencing the port... What does it influence, dies anybody know it? Is it a "bug or a feature"? What is then the purpose of the vncdisplay option in the configuration? With best regards Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Artur Linhart - Linux communication Sent: Wednesday, September 19, 2007 3:38 PM To: ''Scott Serr''; ''Alessandro R.'' Cc: xen-users@lists.xensource.com Subject: RE: [Xen-users] VNC to HVM not starting Hello, I''m not very skilled on the vnc options, but what does it mean if You have vncdisplay=6 ? I gues it should mean the domain should be accessible through VNC on the port 5906, isn''t it? Is there nothing running on this port? Maybe the domain cannot start because the port 5906 is already in use... can You try to run netstat -a -n if the domain not started and if it is started? Are there any differences? What can You find in the corresponding /var/log/xen/qemu-dm*.log file? Are there any errors? With best regards, Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Scott Serr Sent: Tuesday, September 18, 2007 6:30 PM To: Alessandro R. Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] VNC to HVM not starting Scott Serr wrote:> Alessandro R. wrote: >> 2007/9/18, Scott Serr <serrs@theserrs.net>: >> >>> My dom0 is Gentoo and I''m trying to boot an HVM off of a Ubuntu Feisty >>> ISO image. >>> >>> I apparently have X already listening on 5900... for the "shared >>> desktop" feature of the modern X servers. >>> >>> So I have: >>> >>> vnc=1 >>> vncdisplay=6 >>> vncconsole=1 >>> >> >> Can you paste all config file? >> >> > kernel="/usr/lib64/xen/boot/hvmloader" > builder=''hvm'' > #device_model=''/usr/lib64/xen/bin/qemu-dm'' > memory=384 > name=''feisty'' > vif=[ ''type=ioemu,bridge=xenbr0'' ] >disk=[''file:/data/xen/feisty/hda.img,ioemu:hda,w'',''file:/data/ubuntu-7.04-de sktop-i386.iso,hdc:cdrom,r'']> > boot=''d'' > vnc=1 > vncdisplay=6 > #vncviewer=1 > #sdl=1 > > Note: "xm list" shows the VM name "feisty" is running... I just can''t > see it. Ideas of what to try are welcome.I mis-spoke.. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3620 4 r----- 30.8 feisty 1 384 1 ------ 0.0 feisty is not running... not accruing time and not in a run state. Alessandro, did you use a guide? Oh no... I think I found my problem. http://gentoo-wiki.com/HOWTO_Xen_and_Gentoo> *Note:* For HVM guests to be able to start, it is important that you > create the appropriate tap device(s). Thus, the > *sys-apps/usermode-utilities* package is required (tunctl), and > *support for TUN/TAP devices* must be activated in the kernel > configuration.I''ll report if this fixes it. Thanks, -Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2540 (20070919) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2540 (20070919) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
It does influence the port, your original assumption was correct. However the parameter could be broken on your version of xen. What version of xen are you running? Are you running a packaged from a distribution or compiled from source? The vncdisplay parameter did/does _NOT_ work in RHEL 5, or Fedora Core 6 if I recall correctly (xen 3.0.3). It is working correctly in Fedora 7 and the beta of RHEL 5.1 (essentially xen 3.1). It worked correctly for me in xen 3.0.4 in gentoo as well as xen 3.1 on gentoo. I have not tried any other distributions so I cannot comment. On Wed, 2007-09-19 at 19:18 +0200, Artur Linhart - Linux communication wrote:> Hello, > > I''ve tested it and this is not true what I said and thought, it > seems to be the fact the display is not influencing the port... > > What does it influence, dies anybody know it? Is it a "bug or a > feature"? What is then the purpose of the vncdisplay option in the > configuration? > > With best regards > > Archie_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Be aware that tere seems to be some precedence in the parameters. If my memory serves well, you must set vncunused to 0 if you want vncdisplay to be considered. /P. Artur Linhart - Linux communication wrote:> Hello, > > I''ve tested it and this is not true what I said and thought, it > seems to be the fact the display is not influencing the port... > > What does it influence, dies anybody know it? Is it a "bug or a > feature"? What is then the purpose of the vncdisplay option in the > configuration? >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Oh no... I think I found my problem. > > http://gentoo-wiki.com/HOWTO_Xen_and_Gentoo >> *Note:* For HVM guests to be able to start, it is important that you >> create the appropriate tap device(s). Thus, the >> *sys-apps/usermode-utilities* package is required (tunctl), and >> *support for TUN/TAP devices* must be activated in the kernel >> configuration. > I''ll report if this fixes it.After much confusion, this solved the problem. Not only do you have to compile it in... you have to remember to copy the vmlinuz over for your reboot.. which I swore I did last night when I was half asleep. Thanks all for your help, wasn''t a VNC issue after all. I''m very happy now, except for Intel VT not doing VBE and real mode right that many of the splash boots (ISOLINUX) use in Linux distros. Bah, knew I should have bought AMD. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Sep-20 09:32 UTC
RE: [Xen-users] VNC to HVM not starting
Hello, Yes, thank You very much, it is it :-) So, for me the following configuration vnc=1 vnclisten=''IP_of_my_xen_server'' # Here place IP of the Xen server vncdisplay=4 vncunused=0 causes the Xen server listens on the given IP on the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 And I can vonnect to it through the VNC viewer! :-) The "display" value seems to be valid at least also for the number 21 and port 5921 (I do not know if there is some max display number) Dylan, I propose to place such an example into the FAQ You are creating, sure, if it is not already there ;-) With best regards Artur -----Original Message----- From: Philippe Vanhaesendonck [mailto:xen@e-bulles.be] Sent: Wednesday, September 19, 2007 11:21 PM To: Artur Linhart - Linux communication Cc: ''Scott Serr''; ''Alessandro R.''; xen-users@lists.xensource.com Subject: Re: [Xen-users] VNC to HVM not starting Be aware that tere seems to be some precedence in the parameters. If my memory serves well, you must set vncunused to 0 if you want vncdisplay to be considered. /P. Artur Linhart - Linux communication wrote:> Hello, > > I''ve tested it and this is not true what I said and thought, it > seems to be the fact the display is not influencing the port... > > What does it influence, dies anybody know it? Is it a "bug or a > feature"? What is then the purpose of the vncdisplay option in the > configuration? >__________ Informace od NOD32 2541 (20070920) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>From my experience :when vnc=1 vnclisten=''IP_of_my_xen_server vncdisplay=4 vncunused=0 Always allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the display. If it is used by soem other application this will just hang. vnc=1 vnclisten=''IP_of_my_xen_server vncdisplay=4 vncunused=1 allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the display if it is free else allocate other free port. vnc=1 vnclisten=''IP_of_my_xen_server vncunused=1/0 allocate free port. Please correct me if my understanding is wrong. Thanks, Trilok On 9/20/07, Artur Linhart - Linux communication <AL.LINUX@bcpraha.com> wrote:> > Hello, > > Yes, thank You very much, it is it :-) > > So, for me the following configuration > > vnc=1 > vnclisten=''IP_of_my_xen_server'' # Here place IP of the Xen server > vncdisplay=4 > vncunused=0 > > causes the Xen server listens on the given IP on the port > 5900 (standard VNC) + 4 (vncdisplay) = 5904 > And I can vonnect to it through the VNC viewer! > > :-) > > The "display" value seems to be valid at least also for the number 21 and > port 5921 (I do not know if there is some max display number) > > Dylan, I propose to place such an example into the FAQ You are creating, > sure, if it is not already there ;-) > > With best regards > > Artur > > -----Original Message----- > From: Philippe Vanhaesendonck [mailto:xen@e-bulles.be] > Sent: Wednesday, September 19, 2007 11:21 PM > To: Artur Linhart - Linux communication > Cc: ''Scott Serr''; ''Alessandro R.''; xen-users@lists.xensource.com > Subject: Re: [Xen-users] VNC to HVM not starting > > Be aware that tere seems to be some precedence in the parameters. > If my memory serves well, you must set vncunused to 0 if you want > vncdisplay to be considered. > > /P. > > Artur Linhart - Linux communication wrote: > > Hello, > > > > I''ve tested it and this is not true what I said and thought, it > > seems to be the fact the display is not influencing the port... > > > > What does it influence, dies anybody know it? Is it a "bug or a > > feature"? What is then the purpose of the vncdisplay option in the > > configuration? > > > > > __________ Informace od NOD32 2541 (20070920) __________ > > Tato zprava byla proverena antivirovym systemem NOD32. > http://www.nod32.cz > > > > _______________________________________________ > 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
Artur Linhart - Linux communication
2007-Sep-20 11:15 UTC
RE: [Xen-users] VNC to HVM not starting
Hello,
I could not test all the combinations, but I think You are
right. And if the vncunused parameter is omitted, then also vncdisplay
parameter is ignored even if specified - like already wrote Philippe...
With regards, Archie
_____
From: trilok nuwal [mailto:tc.nuwal@gmail.com]
Sent: Thursday, September 20, 2007 12:34 PM
To: Artur Linhart - Linux communication
Cc: Philippe Vanhaesendonck; Dylan Martin; Scott Serr; Alessandro R.;
xen-users@lists.xensource.com
Subject: Re: [Xen-users] VNC to HVM not starting
>From my experience :
when
vnc=1
vnclisten=''IP_of_my_xen_server
vncdisplay=4
vncunused=0
Always allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the
display. If it is used by soem other application this will just hang.
vnc=1
vnclisten=''IP_of_my_xen_server
vncdisplay=4
vncunused=1
allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the
display if it is free else allocate other free port.
vnc=1
vnclisten=''IP_of_my_xen_server
vncunused=1/0
allocate free port.
Please correct me if my understanding is wrong.
Thanks,
Trilok
On 9/20/07, Artur Linhart - Linux communication <AL.LINUX@bcpraha.com>
wrote:
Hello,
Yes, thank You very much, it is it :-)
So, for me the following configuration
vnc=1
vnclisten=''IP_of_my_xen_server'' # Here place IP of the Xen
server
vncdisplay=4
vncunused=0
causes the Xen server listens on the given IP on the port
5900 (standard VNC) + 4 (vncdisplay) = 5904
And I can vonnect to it through the VNC viewer!
:-)
The "display" value seems to be valid at least also for the number 21
and
port 5921 (I do not know if there is some max display number)
Dylan, I propose to place such an example into the FAQ You are creating,
sure, if it is not already there ;-)
With best regards
Artur
-----Original Message-----
From: Philippe Vanhaesendonck [mailto:xen@e-bulles.be]
Sent: Wednesday, September 19, 2007 11:21 PM
To: Artur Linhart - Linux communication
Cc: ''Scott Serr''; ''Alessandro R.'';
xen-users@lists.xensource.com
Subject: Re: [Xen-users] VNC to HVM not starting
Be aware that tere seems to be some precedence in the parameters.
If my memory serves well, you must set vncunused to 0 if you want
vncdisplay to be considered.
/P.
Artur Linhart - Linux communication wrote:> Hello,
>
> I''ve tested it and this is not true what I said and thought,
it
> seems to be the fact the display is not influencing the port...
>
> What does it influence, dies anybody know it? Is it a "bug or a
> feature"? What is then the purpose of the vncdisplay option in the
> configuration?
>
__________ Informace od NOD32 2541 (20070920) __________
Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz
_______________________________________________
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
You can do a :
xm list -ll name_of_the_virtual_machine | grep vnc
you will get something like this :
(vnc 1)
(vnc 1)
(device (console (vnc-port 5902)))
Artur Linhart - Linux communication a écrit :>
> Hello,
>
>
>
> I could not test all the combinations, but I think You are
> right. And if the vncunused parameter is omitted, then also vncdisplay
> parameter is ignored even if specified - like already wrote Philippe...
>
>
>
> With regards, Archie
>
>
>
> ------------------------------------------------------------------------
>
> *From:* trilok nuwal [mailto:tc.nuwal@gmail.com]
> *Sent:* Thursday, September 20, 2007 12:34 PM
> *To:* Artur Linhart - Linux communication
> *Cc:* Philippe Vanhaesendonck; Dylan Martin; Scott Serr; Alessandro
> R.; xen-users@lists.xensource.com
> *Subject:* Re: [Xen-users] VNC to HVM not starting
>
>
>
> From my experience :
>
> when
>
> vnc=1
> vnclisten=''IP_of_my_xen_server
>
> vncdisplay=4
> vncunused=0
>
> Always allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904
> for the display. If it is used by soem other application this will
> just hang.
>
> vnc=1
> vnclisten=''IP_of_my_xen_server
>
> vncdisplay=4
> vncunused=1
>
> allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the
> display if it is free else allocate other free port.
>
> vnc=1
> vnclisten=''IP_of_my_xen_server
>
> vncunused=1/0
>
> allocate free port.
>
>
>
> Please correct me if my understanding is wrong.
>
> Thanks,
> Trilok
>
>
>
> On 9/20/07, *Artur Linhart - Linux communication*
> <AL.LINUX@bcpraha.com <mailto:AL.LINUX@bcpraha.com>> wrote:
>
> Hello,
>
> Yes, thank You very much, it is it :-)
>
> So, for me the following configuration
>
> vnc=1
> vnclisten=''IP_of_my_xen_server'' # Here place IP of the
Xen server
> vncdisplay=4
> vncunused=0
>
> causes the Xen server listens on the given IP on the port
> 5900 (standard VNC) + 4 (vncdisplay) = 5904
> And I can vonnect to it through the VNC viewer!
>
> :-)
>
> The "display" value seems to be valid at least also for the
number 21 and
> port 5921 (I do not know if there is some max display number)
>
> Dylan, I propose to place such an example into the FAQ You are creating,
> sure, if it is not already there ;-)
>
> With best regards
>
> Artur
>
> -----Original Message-----
> From: Philippe Vanhaesendonck [mailto:xen@e-bulles.be
> <mailto:xen@e-bulles.be>]
> Sent: Wednesday, September 19, 2007 11:21 PM
> To: Artur Linhart - Linux communication
> Cc: ''Scott Serr''; ''Alessandro R.'';
xen-users@lists.xensource.com
> <mailto:xen-users@lists.xensource.com>
> Subject: Re: [Xen-users] VNC to HVM not starting
>
> Be aware that tere seems to be some precedence in the parameters.
> If my memory serves well, you must set vncunused to 0 if you want
> vncdisplay to be considered.
>
> /P.
>
> Artur Linhart - Linux communication wrote:
> > Hello,
> >
> > I''ve tested it and this is not true what I said and
thought, it
> > seems to be the fact the display is not influencing the port...
> >
> > What does it influence, dies anybody know it? Is it a "bug
or a
> > feature"? What is then the purpose of the vncdisplay option in
the
> > configuration?
> >
>
>
> __________ Informace od NOD32 2541 (20070920) __________
>
> Tato zprava byla proverena antivirovym systemem NOD32.
> http://www.nod32.cz
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com>
> http://lists.xensource.com/xen-users
> <http://lists.xensource.com/xen-users>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
--
Yves-Gaël Chény
Directeur technique
44 Boulevard des Pas Enchantés
44230 St Sébastien sur Loire
Tel : 02 40 97 62 67 - 08 73 77 24 91
GSM : 06 98 58 41 55
http://www.tranquilitsystems.com/
yves-gael.cheny@tranquil-it-systems.fr
Tranquil IT Systems . SAS 37 000 ¤
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I cannot open VNC yet from xm command I can see the HVM domain is
running. But when I run xm console xp, the command doesn''t return to
the
console terminal unless I shutdown the HVM domain(winxp) in virt
manager.
Please note the HVM domain winxp is created in virt manager. Uuid is got
from its data.
The following are my config file and the xm list -ll result.
====================================================== The following is winxp
xm config file
======================================================# -*- mode: python; -*-
#==========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#==========================================================================
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 512
# shadow_memory = 8
name = "winxp"
uuid = "9bf83d7c13e1848615a36094fcc3ed22"
vcpus=2
#pae=1
#acpi=1
#apic=1
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
vif = [ ''type=ioemu, mac=00:16:3e:79:5c:8b, bridge=eth0,
model=ne2k_pci''
]
disk=[''phy:/dev/sda3, ioemu:hda, w'']
#on_poweroff = ''destroy''
#on_reboot = ''restart''
#on_crash = ''restart''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="cda"
#snapshot=1
#sdl=0
vnc=1
#I get the IP by ifconfig in dom0 eth0
vnclisten="10.8.114.40"
vncdisplay=1
vncunused=0
vncconsole=1
vncpasswd=''123456''
#nographic=0
stdvga=0
serial=''pty''
#monitor=1
#soundhw=''sb16''
#localtime=1
#rtc_timeoffset=3600
#full-screen=1
usb=1
usbdevice=''tablet''
#keymap=''ja''
====================================================== The following is xm list
-ll result
======================================================(domain
(on_crash restart)
(uuid 9bf83d7c-13e1-8486-15a3-6094fcc3ed22)
(bootloader_args )
(vcpus 2)
(name winxp)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 500)
(memory 500)
(shadow_memory 6)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1190340014.17)
(cpu_time 27.190939825)
(online_vcpus 1)
(image
(hvm
(kernel /usr/lib/xen/boot/hvmloader)
(acpi 1)
(apic 1)
(boot c)
(device_model /usr/lib/xen/bin/qemu-dm)
(pae 1)
(rtc_timeoffset None)
(serial pty)
(notes (SUSPEND_CANCEL 1))
)
)
(status 0)
(store_mfn 127998)
(device
(vif
(bridge eth0)
(uuid 29fb6bd9-e8c9-ccf7-bbb4-3cda2f562664)
(script vif-bridge)
(devid 0)
(mac 00:16:3e:79:5c:8b)
(type ioemu)
(backend 0)
)
)
(device
(vbd
(uuid 5d2c7b71-d749-400f-1825-c8f72203a576)
(bootable 1)
(devid 768)
(driver paravirtualised)
(dev hda:disk)
(uname phy:/dev/sda3)
(mode w)
(backend 0)
)
)
(device
(vbd
(uuid 96fc9867-8f43-4a7d-7b99-9c720c612a4a)
(bootable 0)
(devid 5632)
(driver paravirtualised)
(dev hdc:cdrom)
(uname phy:/dev/cdrom)
(mode r)
(backend 0)
)
)
(device
(vkbd (devid 0) (uuid 543accf0-302b-5cb7-f216-379ad31a293d)
(backend 0))
)
(device
(vfb
(uuid c87bde23-3ed3-e7b3-cd03-c8ada1f788b8)
(devid ''None'')
(vncdisplay 0)
(keymap en-us)
(type vnc)
)
)
)
Best regards,
Hu Jia Yi
Ext: 20430
Tel: 65-67510430
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of
xen-users-request@lists.xensource.com
Sent: Thursday, September 20, 2007 8:41 PM
To: xen-users@lists.xensource.com
Subject: Xen-users Digest, Vol 31, Issue 73
Send Xen-users mailing list submissions to
xen-users@lists.xensource.com
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users
or, via email, send a message with subject or body ''help'' to
xen-users-request@lists.xensource.com
You can reach the person managing the list at
xen-users-owner@lists.xensource.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xen-users digest..."
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I cannot open VNC yet. But I can see the HVM domain "winxp" is running
in virt-manager.
I create this domain winxp in virt-manager and put its uuid in xm config
file.
The following are xm config file and xm list -ll result
========================================== xm config file
==========================================kernel =
"/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 512
# shadow_memory = 8
name = "winxp"
uuid = "9bf83d7c13e1848615a36094fcc3ed22"
vcpus=2
#pae=1
#acpi=1
#apic=1
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
vif = [ ''type=ioemu, mac=00:16:3e:79:5c:8b, bridge=eth0,
model=ne2k_pci''
]
disk=[''phy:/dev/sda3, ioemu:hda, w'']
#on_poweroff = ''destroy''
#on_reboot = ''restart''
#on_crash = ''restart''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="cda"
#snapshot=1
#sdl=0
vnc=1
#the IP is get from dom0, eth0
vnclisten="10.8.114.40"
vncdisplay=1
vncunused=0
vncconsole=1
vncpasswd=''123456''
#nographic=0
stdvga=0
serial=''pty''
#monitor=1
#soundhw=''sb16''
#localtime=1
#rtc_timeoffset=3600
#full-screen=1
usb=1
usbdevice=''tablet''
#keymap=''ja''
========================================== xm list -ll result
==========================================(domain
(on_crash restart)
(uuid 9bf83d7c-13e1-8486-15a3-6094fcc3ed22)
(bootloader_args )
(vcpus 2)
(name winxp)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 500)
(memory 500)
(shadow_memory 6)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1190340014.17)
(cpu_time 27.190939825)
(online_vcpus 1)
(image
(hvm
(kernel /usr/lib/xen/boot/hvmloader)
(acpi 1)
(apic 1)
(boot c)
(device_model /usr/lib/xen/bin/qemu-dm)
(pae 1)
(rtc_timeoffset None)
(serial pty)
(notes (SUSPEND_CANCEL 1))
)
)
(status 0)
(store_mfn 127998)
(device
(vif
(bridge eth0)
(uuid 29fb6bd9-e8c9-ccf7-bbb4-3cda2f562664)
(script vif-bridge)
(devid 0)
(mac 00:16:3e:79:5c:8b)
(type ioemu)
(backend 0)
)
)
(device
(vbd
(uuid 5d2c7b71-d749-400f-1825-c8f72203a576)
(bootable 1)
(devid 768)
(driver paravirtualised)
(dev hda:disk)
(uname phy:/dev/sda3)
(mode w)
(backend 0)
)
)
(device
(vbd
(uuid 96fc9867-8f43-4a7d-7b99-9c720c612a4a)
(bootable 0)
(devid 5632)
(driver paravirtualised)
(dev hdc:cdrom)
(uname phy:/dev/cdrom)
(mode r)
(backend 0)
)
)
(device
(vkbd (devid 0) (uuid 543accf0-302b-5cb7-f216-379ad31a293d)
(backend 0))
)
(device
(vfb
(uuid c87bde23-3ed3-e7b3-cd03-c8ada1f788b8)
(devid ''None'')
(vncdisplay 0)
(keymap en-us)
(type vnc)
)
)
)
Best regards,
Hu Jia Yi
Ext: 20430
Tel: 65-67510430
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Sep-21 05:46 UTC
RE: [Xen-users] VNC to HVM not starting
Hello,
I tested also Your second possibility
vnc=1
vnclisten=''IP_of_my_xen_server
vncdisplay=4
vncunused=1
and in my case on Xen 3.1.0 the vncdisplay parameter was
ignored. So, from my point of view if You want to specify the port
explicitely by setting vncdisplay, it works only with
vncunused=0
è exactly like Philippe below wrote...
with regards Artur
_____
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Artur Linhart -
Linux communication
Sent: Thursday, September 20, 2007 1:16 PM
To: ''trilok nuwal''
Cc: ''Philippe Vanhaesendonck''; ''Dylan
Martin''; ''Scott Serr''; ''Alessandro
R.''; xen-users@lists.xensource.com
Subject: RE: [Xen-users] VNC to HVM not starting
Hello,
I could not test all the combinations, but I think You are
right. And if the vncunused parameter is omitted, then also vncdisplay
parameter is ignored even if specified - like already wrote Philippe...
With regards, Archie
_____
From: trilok nuwal [mailto:tc.nuwal@gmail.com]
Sent: Thursday, September 20, 2007 12:34 PM
To: Artur Linhart - Linux communication
Cc: Philippe Vanhaesendonck; Dylan Martin; Scott Serr; Alessandro R.;
xen-users@lists.xensource.com
Subject: Re: [Xen-users] VNC to HVM not starting
>From my experience :
when
vnc=1
vnclisten=''IP_of_my_xen_server
vncdisplay=4
vncunused=0
Always allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the
display. If it is used by soem other application this will just hang.
vnc=1
vnclisten=''IP_of_my_xen_server
vncdisplay=4
vncunused=1
allocate the port 5900 (standard VNC) + 4 (vncdisplay) = 5904 for the
display if it is free else allocate other free port.
vnc=1
vnclisten=''IP_of_my_xen_server
vncunused=1/0
allocate free port.
Please correct me if my understanding is wrong.
Thanks,
Trilok
On 9/20/07, Artur Linhart - Linux communication <AL.LINUX@bcpraha.com>
wrote:
Hello,
Yes, thank You very much, it is it :-)
So, for me the following configuration
vnc=1
vnclisten=''IP_of_my_xen_server'' # Here place IP of the Xen
server
vncdisplay=4
vncunused=0
causes the Xen server listens on the given IP on the port
5900 (standard VNC) + 4 (vncdisplay) = 5904
And I can vonnect to it through the VNC viewer!
:-)
The "display" value seems to be valid at least also for the number 21
and
port 5921 (I do not know if there is some max display number)
Dylan, I propose to place such an example into the FAQ You are creating,
sure, if it is not already there ;-)
With best regards
Artur
-----Original Message-----
From: Philippe Vanhaesendonck [mailto:xen@e-bulles.be]
Sent: Wednesday, September 19, 2007 11:21 PM
To: Artur Linhart - Linux communication
Cc: ''Scott Serr''; ''Alessandro R.'';
xen-users@lists.xensource.com
Subject: Re: [Xen-users] VNC to HVM not starting
Be aware that tere seems to be some precedence in the parameters.
If my memory serves well, you must set vncunused to 0 if you want
vncdisplay to be considered.
/P.
Artur Linhart - Linux communication wrote:> Hello,
>
> I''ve tested it and this is not true what I said and thought,
it
> seems to be the fact the display is not influencing the port...
>
> What does it influence, dies anybody know it? Is it a "bug or a
> feature"? What is then the purpose of the vncdisplay option in the
> configuration?
>
__________ Informace od NOD32 2541 (20070920) __________
Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
__________ Informace od NOD32 2541 (20070920) __________
Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Sep-21 05:51 UTC
RE: [Xen-users] RE: VNC to HVM not starting
Hello, Jia Yi,
I think the problem is the xm command is intended ttach to text
based console ient - in Your configuration You have to start an independent
vnc client to access Your running DomU - You must connect to the specified
IP address and port. This can be done from the same computer if You have
installed the vnc client there, or from a different machine if not. If You
start Your DomU from X-windows, specify
sdl=1
to get new window with the graphical console immediatelly after the start of
the instance - at least so worked it for me under Ubuntu...
with best regards
Archie
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Hu Jia Yi
Sent: Friday, September 21, 2007 4:21 AM
To: xen-users@lists.xensource.com
Subject: [Xen-users] RE: VNC to HVM not starting
I cannot open VNC yet from xm command I can see the HVM domain is
running. But when I run xm console xp, the command doesn''t return to
the
console terminal unless I shutdown the HVM domain(winxp) in virt
manager.
Please note the HVM domain winxp is created in virt manager. Uuid is got
from its data.
The following are my config file and the xm list -ll result.
====================================================== The following is winxp
xm config file
======================================================# -*- mode: python; -*-
#==========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#==========================================================================
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 512
# shadow_memory = 8
name = "winxp"
uuid = "9bf83d7c13e1848615a36094fcc3ed22"
vcpus=2
#pae=1
#acpi=1
#apic=1
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
vif = [ ''type=ioemu, mac=00:16:3e:79:5c:8b, bridge=eth0,
model=ne2k_pci''
]
disk=[''phy:/dev/sda3, ioemu:hda, w'']
#on_poweroff = ''destroy''
#on_reboot = ''restart''
#on_crash = ''restart''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="cda"
#snapshot=1
#sdl=0
vnc=1
#I get the IP by ifconfig in dom0 eth0
vnclisten="10.8.114.40"
vncdisplay=1
vncunused=0
vncconsole=1
vncpasswd=''123456''
#nographic=0
stdvga=0
serial=''pty''
#monitor=1
#soundhw=''sb16''
#localtime=1
#rtc_timeoffset=3600
#full-screen=1
usb=1
usbdevice=''tablet''
#keymap=''ja''
====================================================== The following is xm list
-ll result
======================================================(domain
(on_crash restart)
(uuid 9bf83d7c-13e1-8486-15a3-6094fcc3ed22)
(bootloader_args )
(vcpus 2)
(name winxp)
(on_poweroff destroy)
(on_reboot restart)
(bootloader )
(maxmem 500)
(memory 500)
(shadow_memory 6)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1190340014.17)
(cpu_time 27.190939825)
(online_vcpus 1)
(image
(hvm
(kernel /usr/lib/xen/boot/hvmloader)
(acpi 1)
(apic 1)
(boot c)
(device_model /usr/lib/xen/bin/qemu-dm)
(pae 1)
(rtc_timeoffset None)
(serial pty)
(notes (SUSPEND_CANCEL 1))
)
)
(status 0)
(store_mfn 127998)
(device
(vif
(bridge eth0)
(uuid 29fb6bd9-e8c9-ccf7-bbb4-3cda2f562664)
(script vif-bridge)
(devid 0)
(mac 00:16:3e:79:5c:8b)
(type ioemu)
(backend 0)
)
)
(device
(vbd
(uuid 5d2c7b71-d749-400f-1825-c8f72203a576)
(bootable 1)
(devid 768)
(driver paravirtualised)
(dev hda:disk)
(uname phy:/dev/sda3)
(mode w)
(backend 0)
)
)
(device
(vbd
(uuid 96fc9867-8f43-4a7d-7b99-9c720c612a4a)
(bootable 0)
(devid 5632)
(driver paravirtualised)
(dev hdc:cdrom)
(uname phy:/dev/cdrom)
(mode r)
(backend 0)
)
)
(device
(vkbd (devid 0) (uuid 543accf0-302b-5cb7-f216-379ad31a293d)
(backend 0))
)
(device
(vfb
(uuid c87bde23-3ed3-e7b3-cd03-c8ada1f788b8)
(devid ''None'')
(vncdisplay 0)
(keymap en-us)
(type vnc)
)
)
)
Best regards,
Hu Jia Yi
Ext: 20430
Tel: 65-67510430
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of
xen-users-request@lists.xensource.com
Sent: Thursday, September 20, 2007 8:41 PM
To: xen-users@lists.xensource.com
Subject: Xen-users Digest, Vol 31, Issue 73
Send Xen-users mailing list submissions to
xen-users@lists.xensource.com
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users
or, via email, send a message with subject or body ''help'' to
xen-users-request@lists.xensource.com
You can reach the person managing the list at
xen-users-owner@lists.xensource.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xen-users digest..."
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
__________ Informace od NOD32 2542 (20070921) __________
Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users