> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Thorolf Godawa > Sent: 04 February 2006 08:49 > To: Nakajima, Jun > Cc: xen-devel@lists.xensource.com; xen-users@lists.xensource.com > Subject: Re: [Xen-devel] RE: [Xen-users] Intel/VT > > Hi Jun, > > >Do you happen to use x86_32 PAE Xen? > sure, the computer should be equiped with more than 4GB RAM later! > > >It should work for both plain32-bit and 64-bit. > >It will be available for x86_32 PAE soon. > So I have to deselect the kernel-bigsmp and select the kernel-smp?No, you need to set CONFIG_HIGHMEM4G instead off CONFIG_HIGHMEM64G. That will limit the machines'' kernel space to 4GB, and thus eliminate the need for PAE. Of course, CONFIG_NOHIGHMEM will also turn off PAE, but may not work out quite as well. In menuconfig, this can be found under X86 Processor Configuration, High Memory support. Other configuration tools may use different paths... ;-) -- Mats> > Thanks a lot for your answer, > -- > > Chau y hasta luego, > > Thorolf > > _______________________________________________ > 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
Hi, finaly I had success getting running VMX-guest on Intel/HT. Thanks to everybody who helped me and answered my questions! One thing was getting SLES 10.0 Beta3 with working XEN-support, then using only the i386 without PAE (PAE is not yet supported in XEN 3.0, and the x86-64-Version of SLES is not yet there) and finaly the understanding that you have to free memory of the xen0-domain before starting the VMX-xenU-domains - the paravirt. Linux-xenU-domains seems to take there memory from the xen0-domain by themselves and it was working like that. Beside the the stability not is perfectly and the sometimes the Linux-xenU-domains are hanging while booting I still have some problems: If I connect via VNC to a W2k3-guest everything is working, but the mouse-cursor in the guest is always far away from the cursor in the host and the reaction-time is very bad. I tried this with VNC-viewers for Linux, OS/2 and even Windows, but always the same result! With every boot I get the "TLS-warnig", but in the installation there is no /lib/tls-directory. How can I avoid this warnig and are there still some performance-problems? I''m not able to migrate domains using the "xm migrate", I can save and restore domains even if I restore the on a different host, but mirgrate doesn''t work. Any ideas? Thanks a lot for your help! -- Chau y hasta luego, Thorolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,
finaly I had success getting running VMX-guest on Intel/HT.
Thanks to everybody who helped me and answered my questions!
One thing was getting SLES 10.0 Beta3 with working XEN-support, then
using only the i386 without PAE (PAE is not yet supported in XEN 3.0,
and the x86-64-Version of SLES is not yet there) and finaly the
understanding that you have to free memory of the xen0-domain before
starting the VMX-xenU-domains - the paravirt. Linux-xenU-domains seems
to take there memory from the xen0-domain by themselves and it was
working like that.
Beside the the stability not is perfectly and the sometimes the
Linux-xenU-domains are hanging while booting I still have some problems:
If I connect via VNC to a W2k3-guest everything is working, but the
mouse-cursor in the guest is always far away from the cursor in the host
and the reaction-time is very bad. I tried this with VNC-viewers for
Linux, OS/2 and even Windows, but always the same result!
With every boot I get the "TLS-warnig", but in the installation there
is
no /lib/tls-directory. How can I avoid this warnig and are there still
some performance-problems?
I''m not able to migrate domains using the "xm migrate", I can
save and
restore domains even if I restore the on a different host, but mirgrate
doesn''t work.
Any ideas? Thanks a lot for your help!
--
Chau y hasta luego,
Thorolf
------------------------------------------------------------------
e-Mail: mailto:Thorolf@Godawa.de \|/
/''~''\
Homepage: http://www.godawa.de ( o o )
--------------------------------------------------oOOO--(_)--OOOo-
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Feb 08, 2006 at 02:22:27PM +0100, Thorolf Godawa wrote:> With every boot I get the "TLS-warnig", but in the installation there is > no /lib/tls-directory. How can I avoid this warnig and are there still > some performance-problems?Perhaps you have the tls libs in your initrd bootimage? Ãystei _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Mittwoch, 8. Februar 2006 14:22 schrieb Thorolf Godawa:> Hi, > > finaly I had success getting running VMX-guest on Intel/HT. > > Thanks to everybody who helped me and answered my questions! > > One thing was getting SLES 10.0 Beta3 with working XEN-support, then > using only the i386 without PAE (PAE is not yet supported in XEN 3.0, > and the x86-64-Version of SLES is not yet there) and finaly the > understanding that you have to free memory of the xen0-domain before > starting the VMX-xenU-domains - the paravirt. Linux-xenU-domains seems > to take there memory from the xen0-domain by themselves and it was > working like that. > > Beside the the stability not is perfectly and the sometimes the > Linux-xenU-domains are hanging while booting I still have some problems: > > If I connect via VNC to a W2k3-guest everything is working, but the > mouse-cursor in the guest is always far away from the cursor in the host > and the reaction-time is very bad. I tried this with VNC-viewers for > Linux, OS/2 and even Windows, but always the same result! > > With every boot I get the "TLS-warnig", but in the installation there is > no /lib/tls-directory. How can I avoid this warnig and are there still > some performance-problems?most likely you have created the initrd image for your dom0 or domU kernel at a time where /lib/tls was present... recreate the initrd image now (without the /lib/tls directory existing) and the warning will go away. --Ralph> I''m not able to migrate domains using the "xm migrate", I can save and > restore domains even if I restore the on a different host, but mirgrate > doesn''t work. > > Any ideas? Thanks a lot for your help!_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wednesday 08 February 2006 15:17, Oystein Nerhus wrote:> On Wed, Feb 08, 2006 at 02:22:27PM +0100, Thorolf Godawa wrote: > > With every boot I get the "TLS-warnig", but in the installation there is > > no /lib/tls-directory. How can I avoid this warnig and are there still > > some performance-problems? > > Perhaps you have the tls libs in your initrd bootimage? >Most likely some apps are statically linked against tls glibc ("init" being a prime candidate here), also recent gcc versions can generate code triggering the tls warning on its own, in that case recompiling with less fanatic optimization settings or -mno-tls-direct-seg-refs might help. /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have a possible suggestion for your mouse cursor problem. Not sure if it''ll work, since I haven''t tried it myself, but I''ve seen it cause problems in other scenarios. In your Windows domU disable mouse acceleration. (This can be done under Control Panel->Mouse.) Jared On 2/8/06, Thorolf Godawa <nospam@godawa.de> wrote:> > Hi, > > finaly I had success getting running VMX-guest on Intel/HT. > > Thanks to everybody who helped me and answered my questions! > > One thing was getting SLES 10.0 Beta3 with working XEN-support, then > using only the i386 without PAE (PAE is not yet supported in XEN 3.0, > and the x86-64-Version of SLES is not yet there) and finaly the > understanding that you have to free memory of the xen0-domain before > starting the VMX-xenU-domains - the paravirt. Linux-xenU-domains seems > to take there memory from the xen0-domain by themselves and it was > working like that. > > Beside the the stability not is perfectly and the sometimes the > Linux-xenU-domains are hanging while booting I still have some problems: > > If I connect via VNC to a W2k3-guest everything is working, but the > mouse-cursor in the guest is always far away from the cursor in the host > and the reaction-time is very bad. I tried this with VNC-viewers for > Linux, OS/2 and even Windows, but always the same result! > > With every boot I get the "TLS-warnig", but in the installation there is > no /lib/tls-directory. How can I avoid this warnig and are there still > some performance-problems? > > I''m not able to migrate domains using the "xm migrate", I can save and > restore domains even if I restore the on a different host, but mirgrate > doesn''t work. > > Any ideas? Thanks a lot for your help! > -- > > Chau y hasta luego, > > Thorolf > > ------------------------------------------------------------------ > e-Mail: mailto:Thorolf@Godawa.de \|/ > /''~''\ > Homepage: http://www.godawa.de ( o o ) > --------------------------------------------------oOOO--(_)--OOOo- > > _______________________________________________ > 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
Hi, thank everybody for the answers! >the tls warning on its own, in that case recompiling with less fanatic >optimization settings or -mno-tls-direct-seg-refs might help. so probably I should send this to SuSE, because this are the original RPM-packages from SUSE SLES 10.0 Beta3-i386 I used for installation :-) At the moment I have two more problems: A fresh installed PC (SLES 10.0b3) has lost the eth0-connection (Intel PRO/100) if I boot the xen-kernel. In the standard-kernel network is working always, but in the xen-kernel only sometimes, mostly I loose the connection if the host crashes :-( During boot I get: ---------------------- Setting up network interface ... eth0 is down failed eth0 interface could not be set up until now failed Starting up service network failed ---------------------- I mostly have no success with deleting the nic and reinstall it, setting static IP and setting STARTMODE=''onboot'' an other things :-( An other PC with little diffrent hardware (but also Intel PRO/100), installed exactly the same is working! In the domU-host (SLES 10.0b3) I installed the Apache2, php5 and phpSysInfo (2.5.1), I can connect to the webserver - he''s telling me that he works :-) - but if I try to connect from a client (FF 1.5) to phpSysInfo (http://192.168.0.51/phpsysinfo) the dom0-host crashes and reboots :-((( If I do this localy from Gnome/FF on the dom0-host it works. I have this problem on both machines, tomorrow I''ll check with this domU-images if it also crashes on the Intel/VT-machines! -- Chau y hasta luego, Thorolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi again :-) where can I find informations how to realize an automatic failover with XEN? Are there any "ready" solution or does it need own scripting for recognizing if the guest is still running and if not switching to an other? Thanks for your answers in advance, -- Chau y hasta luego, Thorolf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thorolf Godawa wrote:> Hi again :-) > > where can I find informations how to realize an automatic failover with > XEN? Are there any "ready" solution or does it need own scripting for > recognizing if the guest is still running and if not switching to an other? > > Thanks for your answers in advance,I am using XEN failover cluster with heartbeat(www.linux-ha.org) and drbd.If you have SAN you don''t need drbd only heartbeat. Cheers - -- Adam Hamsik tel.c 0904 937 495 ICQ 249727910 jabber haad@jabber.org - -------------------------------------------------------------- There are 10 kinds of people in the world. Those who understand binary numbers, and those who don''t. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (NetBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD6mpQ9Wt2FT7y228RAs9YAKCUR0yRb18AuhL56vBbUJ4amLLZoQCdH4ca Kdgn2YZV/GUgaeeTg1vRkKk=9wtc -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wednesday 08 February 2006 22:27, Thorolf Godawa wrote:> Hi again :-) > > where can I find informations how to realize an automatic failover with > XEN? Are there any "ready" solution or does it need own scripting for > recognizing if the guest is still running and if not switching to an other? > > Thanks for your answers in advance,First off, please don''t reply to some random thread if you indend to open a new one. Then, for failover, I don''t see a reason why you shouldn''t be able to apply the normal linux failover solutions to xen domUs, like heartbeat etc... The main problem with failover solutions always is to make sure the failing host releases its MAC or IP. Solutions include disabling the port on the switch or forcefully cutting power to the host (serially/network controllable power switch, configurable UPS, etc...) With xen you can archive similar results by "xm destroy" or using brctl to disconnect the failing domU. However if your entire host/dom0 fails, you''ll still need external hardware support to be entirely sure an complete switchover works. failover solutions usually provide means to execute a script whenever action is needed, so issuing the right commands to your dom0 should be quite easy. HTH, /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thorolf Godawa wrote:> where can I find informations how to realize an automatic failover with > XEN? Are there any "ready" solution or does it need own scripting for > recognizing if the guest is still running and if not switching to an other?There are a number of preexisting non-Xen-specific failover solutions that allow you to have arbitrary hooks called when a host goes down or comes up -- the one I''m familiar with is UCARP, but failoverd and others should have similar functionality. Having those arbitrary hooks run xm commands should be straightforward. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, >Did you try to install a Windows operating system on the domain U? I started to do so, and I tried a repair-install of WinXP but because of lack of time finally I stopped my tries and I used the W2k3-image I already had to make my tests! I made an installation of WinXP in QEMU what I wanted to use for XEN, unfortunatey it traps while booting, same as for the Warp Server-installation I made! -- Chau y hasta luego, Thorolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users