RE: [Xen-devel] RE: Intel/VT

RE: [Xen-devel] RE: Intel/VT

[Petersson, Mats]

> -----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
> 
> 

Intel/VT success :-)

[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?

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

Intel/VT success :-)

[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?

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-\x1a

Re: Intel/VT success :-)

[Oystein Nerhus]

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

Re: Intel/VT success :-)

[Ralph Passgang]

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 and failover

[Thorolf Godawa]

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

Re: XEN and failover

[Thorolf Godawa]

Hi,

 >First off, please don't reply to some random thread if you indend
 >to open a new one.
sorry for this, I just was to lasy, I take care not to do it again.

OK, I have the following:

Two servers connected via NFS to a storage-solution.

Both servers have the same hardware and same software (SLES 10.0b3) on 
it, both are running XEN 3.0.0 and some Linux-guests for testing.

I'm able to do "xm save/restore", "xm migrate --live ..." etc.

 >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
OK, but heartbeat just checks if the other machine is still there and 
then it can do s.th., f.ex. starting the domU that just crashed on the 
master machine on the backup machine!

But it would be better to make in an fixed (and short as possible) 
interval snapshots of the running VM including processor and memory 
(like "xm save" does, but without interrupting or even disturbing the VM 
too much), putting it on the shared storage and if the domU crashes 
restoring it from the backup host quite fast and in a most actual state!

I've read several times the XEN 3 should support failover with the 
live-migration, but how can I use it for the BEFORE the master crashes?

 >The main problem with failover solutions always is to make sure the
 >failing host releases its MAC or IP. Solutions include disabling the
With XEN 3 and the live-migration this should not be a big problem, or?

 >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.
Yes, it should be, but only if you know the right commands and there 
parameters :-)


Thanks for your answers,
-- 

Chau y hasta luego,

Thorolf