4gb seg fixup, process on FC6 domU
by Asrai khn
Hi,
We are running xen on fc6 host and all domU are also fc6, the only issue we
are currently facing is getting lot of error messages in logs
Dec 20 13:06:37 kernel: 4gb seg fixup, process syslogd (pid 873), cs:ip
73:00259ea0
Dec 20 13:06:37 kernel: 4gb seg fixup, process klogd (pid 876), cs:ip
73:001e63a0
Dec 20 13:06:37 kernel: 4gb seg fixup, process klogd (pid 876), cs:ip
73:00268e50
Dec 20 13:06:37 kernel: 4gb seg fixup, process klogd (pid 876), cs:ip
73:001e63a0
Dec 20 13:06:42 kernel: printk: 21 messages suppressed.
Dec 20 13:06:42 kernel: 4gb seg fixup, process master (pid 997), cs:ip
73:003b3cfc
Dec 20 13:06:48 kernel: printk: 30 messages suppressed.
Dec 20 13:06:48 kernel: 4gb seg fixup, process sshd (pid 1121), cs:ip
73:003a4cfc
Dec 20 13:06:50 kernel: printk: 57 messages suppressed.
Dec 20 13:06:50 kernel: 4gb seg fixup, process sshd (pid 1121), cs:ip
73:003a4cfc
getting these error eventually for all processes and on all fc6 domU, I have
tried the fix mention in one of thread ie ..
I've done all of that without success. Any other ideas?
I've renamed /lib/tls to /lib/tls.disabled and echo 'hwcap 0 nosegneg' >
/etc/ld.so.conf.d/libc6-xen.conf
But still getting these error message in domU log file and also on
console when access it via console which makes domU console unusable.
Any help in this regards, will be greatly appreciated.
Thanks. Askar
17 years, 4 months
Strange Disk Goings On and No Console (Long)
by Thomas J. Baker
I did a virt-manager install of FC6 on an FC6 host. I used a real disk
(/dev/sdw) for the disk. The install went fine. Upon reboot, I get a
pygrub error and the following xend-debug log entries:
[root@wintermute xen]# more xend-debug.log
Traceback (most recent call last):
File "/usr/bin/pygrub", line 489, in ?
g = Grub(file, isconfig)
File "/usr/bin/pygrub", line 147, in __init__
self.read_config(file, isconfig)
File "/usr/bin/pygrub", line 345, in read_config
raise RuntimeError, "Unable to read filesystem"
RuntimeError: Unable to read filesystem
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomainDir.py",
line 77, in op_create
dominfo = self.xd.domain_create(config)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line
228, in domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 195, in create
vm.initDomain()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1290, in initDomain
self.configure_bootloader()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1756, in configure_bootloader
self.info['image'])
File "/usr/lib64/python2.4/site-packages/xen/xend/XendBootloader.py",
line 85, in bootloader
raise VmError, msg
VmError: Boot loader didn't return any data!
Traceback (most recent call last):
File "/usr/bin/pygrub", line 489, in ?
g = Grub(file, isconfig)
File "/usr/bin/pygrub", line 147, in __init__
self.read_config(file, isconfig)
File "/usr/bin/pygrub", line 345, in read_config
raise RuntimeError, "Unable to read filesystem"
RuntimeError: Unable to read filesystem
When I do an fdisk -l of the disk I just did the install on, it returns
an empty disk:
fdisk -l /dev/sdw
Disk /dev/sdw: 9105 MB, 9105018880 bytes
255 heads, 63 sectors/track, 1106 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
I go home for the night. I come back the next morning and try to start
the domain and it starts fine (except for a lack of console, more on
that later.) Then for grins, I look at the disk again:
fdisk -l /dev/sdw
Disk /dev/sdw: 9105 MB, 9105018880 bytes
255 heads, 63 sectors/track, 1106 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdw1 * 1 13 104391 83 Linux
/dev/sdw2 14 1106 8779522+ 8e Linux LVM
It shows the correct layout that the domain would have written to the
disk. Maybe I made a mistake. I don't know. So then I explode an RHEL5B2
tree to see if I can do a virt-manager install with it and it works
fine. I point it to a blank disk (/dev/sdx) and do a complete install.
Reboot and get the same pybrub errors. Look at the disk and it's showing
this disk as empty too.
fdisk -l /dev/sdx
Disk /dev/sdx: 50.0 GB, 50019202560 bytes
255 heads, 63 sectors/track, 6081 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
I remember the apparent lack of sync so I run sync a couple of times,
restart xend, all trying to get whatever has the disk data in memory
sync'd back out to disk. No luck. I go home and come back in this
morning and
fdisk -l /dev/sdx
Disk /dev/sdx: 50.0 GB, 50019202560 bytes
255 heads, 63 sectors/track, 6081 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdx1 * 1 13 104391 83 Linux
/dev/sdx2 14 6081 48741210 8e Linux LVM
Domain starts up fine again (except for the console.)
Any clue what's going on here?
As for the console, when I start either domain (FC6 or RHEL5B2), I don't
get a graphics console. Here is the dumpxml of the fc6 domain:
# virsh dumpxml doolittle.fc6
<domain type='xen' id='10'>
<name>doolittle.fc6</name>
<uuid>8a187e862a14669361a482be4df7135f</uuid>
<bootloader>/usr/bin/pygrub</bootloader>
<os>
<type>linux</type>
<kernel>/var/lib/xen/vmlinuz.h_sGDJ</kernel>
<initrd>/var/lib/xen/initrd.oSeDqz</initrd>
<cmdline>ro root=/dev/vgx0/root rhgb quiet</cmdline>
</os>
<memory>512000</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<interface type='bridge'>
<mac address='00:16:3e:5f:03:fd'/>
<script path='vif-bridge'/>
</interface>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/sdw'/>
<target dev='xvda'/>
</disk>
<console tty='/dev/pts/1'/>
</devices>
</domain>
#
It seems to be define correctly:
# cat /etc/xen/doolittle.fc6
# Automatically generated xen config file
name = "doolittle.fc6"
memory = "500"
disk = [ 'phy:/dev/sdw,xvda,w', ]
vif = [ 'mac=00:16:3e:5f:03:fd, bridge=xenbr0', ]
vnc=1
vncunused=1
uuid = "8a187e86-2a14-6693-61a4-82be4df7135f"
bootloader="/usr/bin/pygrub"
vcpus=1
on_reboot = 'restart'
on_crash = 'restart'
#
Any clues on how to get a graphics console after an install?
Thanks,
tjb
--
=======================================================================
| Thomas Baker email: tjb(a)unh.edu |
| Systems Programmer |
| Research Computing Center voice: (603) 862-4490 |
| University of New Hampshire fax: (603) 862-1761 |
| 332 Morse Hall |
| Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb |
=======================================================================
17 years, 4 months
Getting Fedora yum-installed domU running on fedora with fedora-xen packages
by Henning Sprang
Hi
I wrote a very similar question some hours ago for Debian, which maybe
got no replies becuase nobody is interested in running Debian on
fedora.
The sad thing is, with the same problems and effects, I also don't get
a Fedory system running that I instelled with yum. So, just replace
debian with fedora 6 and debootstrap with yum in the mail below.
Again, This same system runs fine with Xen from xensource, but I'd
like to use the Fedora Xen packages, for the security updates and
stuff.
There must be something special in the Fedory Kernel that does make
systems from "normal" partitions not work somehow, or something like
that.
---------- Forwarded message ----------
From: Henning Sprang <henning_sprang(a)gmx.de>
Date: Dec 18, 2006 1:27 AM
Subject: Getting Debian domU running on fedora with fedora-native
packages (works with xensource binaries)
To: fedora-xen(a)redhat.com
Hi,
I built a Debian domU on Fedora using debootstrap (which is really
easy, when using alien to create a debootstrap rpm).
This VM runs very fine on fedora fc 6 with xen and the xen-linux
kernel provides by xensource, and when built from sources.
When trying to use it with the fedora xen packages and kernels, I have
absolutely no luck.
First, I was hanging on error message like "could not mount root
device on /dev/root" (sorry, I don't have it at hand, becaue I just
removed the fedora packages and used the xensource packages again, to
be sure it really still works there).
I got past that by creating an initrd with --with=xennet
--preload=xenblk options, and boot the domU with this instead ofthe
initrd that comes with the fedora xen kernel package.
But then, the domU hangs on "starting crond..." I have no idea what
is missing there, I already installed udev additionally, but that
doesn't help.
As said, this same system runs with no problem on FC6 with the
xensource binaries.
BTW: I run the system without pygrub and not with the kernel from
disk, but with the kernel= options...
Henning
17 years, 4 months
how do I start the xen network
by Laszlo Sturmann
Hi all,
I installed the xen kernel (2.6.18-1.2849.fc6xen) and it works except I
no longer have network connection.
When I boot kernel 2.6.18-1.2849.fc6, the DHCP server provides an IP
address and everything works just fine.
I use the default bridged network and the default config-xen.sxp
I haven't created any domU, yet.
The question is, how do I start the network? xend is running.
Here are the outputs of ifconfig and brctl show xenbr0:
eth0 Link encap:Ethernet HWaddr 00:15:C5:BB:43:ED
UP BROADCAST RUNNING MULTICAST MTU:0 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2944 (2.8 KiB) TX bytes:828 (828.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1274 (1.2 KiB) TX bytes:1274 (1.2 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2996 (2.9 KiB) TX bytes:786 (786.0 b)
Interrupt:18
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:828 (828.0 b) TX bytes:2944 (2.8 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3534 (3.4 KiB) TX bytes:0 (0.0 b)
---------------------------------------------------------------------------------
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
---------------------------------------------------------------------------------
Any comment is appreciated!
Laszlo
17 years, 4 months
Re: [Fedora-xen] Problem installing full virtualized Vista guest
by Ian Patton
Anything with an Intel Core 2 Duo should work fine. I built mine from parts
from tigerdirect.com, so I can't give you a specific model #
New AMD procs have the full virt capability too, but I am not sure which
line of products it is available in.
Hope that helps some,
Ian Patton
On 12/17/06, Henry Zhang <Hua.Zhang(a)sun.com> wrote:
>
>
> Hi Ian,
>
> I am planing to play with HVM too, but I know they need some special
> processor, for example Intel VT, I wonder what machine you are using for
> HVM? could you recommend some machine? ( hope give me the detailed
> model, type, machine name, etc, so that I can tell others what I want
> when I borrow or buy.. )
>
> Thanks for your any help,
>
> Regards,
> Henry
>
> Ian Patton 写道:
> > Bill,
> >
> > Good luck getting Vista to install. You may want to look at my threads
> > for Nov & Dec for a good working file and stuff, but even after I got it
> > installed I had problems with networking and sound not working... also
> > kernel problems with the latest FC6 kernel xen
> >
> > I posted my findings here: http://virtualdreamscapes.blogspot.com/
> >
> > Also, after a few domU reboots it seems that the domU system became
> > unstable and would not boot.
> >
> > Later I tried parallels and did get Vista working with sound and
> > networking, but again after a few Vista reboots the system became
> > unstable and would not boot.
> >
> > I was using RC1 though...
> >
> > If you can get it to run and get networking up and get it stable, PLEASE
> > post to share your success story.
> >
> > Thanks,
> >
> > Ian Patton
> >
> >
> > On 12/13/06, *Bill Davidsen* <davidsen(a)tmr.com
> > <mailto:davidsen@tmr.com>> wrote:
> >
> > Jimison, Ed wrote:
> > >
> > > Now that I finally got W2K installed as a guest, I'm moving on to
> > > Vista. The initial setup and config worked and the Vista install
> > > booted from CDROM and transferred files to the harddrive. After
> > reboot
> > > there is just a blank black screen, which is very similar to the
> W2K
> > > install. With W2K I worked around it by hitting F5 and selecting
> > > Standard PC. With Vista there is no such option.
> > >
> > > I transferred the ISO to disk and added it to my config file.
> When I
> > > create the guest and it tries to boot I get this error:
> > >
> > > Boot from Hard Disk 0 failed
> > >
> > > FATAL: not a bootable disk
> > >
> > You might try running xm with boot from CD.
> > xm create vistavirt1 boot=d
> >
> > I've been trying to install Win98SE, and the startup claims it can't
> > find a driver for the CD. My file looks just about like your, I get
> > asked to boot from disk or CD, then after a few screens it says it
> can't
> > find a CD driver. I'm about to switch to vmware, even if I have to
> run
> > Windows. Also tried:
> > phy:/dev/dvd,hdc:c,r
> > with no more luck.
> >
> > The install used to run slowly under qemu, and the operative word
> there
> > is "run," I spent a bunch on a big new hvm capable server, and I
> can't
> > install the things I need to test.
> > >
> > > My config file:
> > >
> > > # Automatically generated xen config file
> > >
> > > name = "vistavirt1"
> > >
> > > builder = "hvm"
> > >
> > > memory = "500"
> > >
> > > disk = [ '_file:/xen/vistavirt1,hda,w_',
> > > '_file:/home/evjimiso/vista.iso,hdc:c,r_']
> > >
> > > vif = [ 'type=ioemu, mac=00:16:3e:3f:17:66, bridge=xenbr0', ]
> > >
> > > uuid = "2dc04ca6-4de7-0b22-8cc4-4bdb0ff273d9"
> > >
> > > device_model = "/usr/lib/xen/bin/qemu-dm"
> > >
> > > kernel = "/usr/lib/xen/boot/hvmloader"
> > >
> > > vnc=1
> > >
> > > vncunused=1
> > >
> > > apic=1
> > >
> > > acpi=1
> > >
> > > pae=1
> > >
> > > vcpus=1
> > >
> > > serial = "pty" # enable serial console
> > >
> > > on_reboot = 'restart'
> > >
> > > on_crash = 'restart'
> > >
> > >
> >
> ------------------------------------------------------------------------
> > >
> > > --
> > > Fedora-xen mailing list
> > > Fedora-xen(a)redhat.com <mailto:Fedora-xen@redhat.com>
> > > https://www.redhat.com/mailman/listinfo/fedora-xen
> > >
> >
> >
> > --
> > bill davidsen < davidsen(a)tmr.com <mailto:davidsen@tmr.com>>
> > CTO TMR Associates, Inc
> > Doing interesting things with small computers since 1979
> >
> >
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen(a)redhat.com <mailto:Fedora-xen@redhat.com>
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
> >
> >
> >
> > --
> > Ian Patton
> >
> >
> > ------------------------------------------------------------------------
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
>
--
Ian Patton
17 years, 4 months
Getting Debian domU running on fedora with fedora-native packages (works with xensource binaries)
by Henning Sprang
Hi,
I built a Debian domU on Fedora using debootstrap (which is really
easy, when using alien to create a debootstrap rpm).
This VM runs very fine on fedora fc 6 with xen and the xen-linux
kernel provides by xensource, and when built from sources.
When trying to use it with the fedora xen packages and kernels, I have
absolutely no luck.
First, I was hanging on error message like "could not mount root
device on /dev/root" (sorry, I don't have it at hand, becaue I just
removed the fedora packages and used the xensource packages again, to
be sure it really still works there).
I got past that by creating an initrd with --with=xennet
--preload=xenblk options, and boot the domU with this instead ofthe
initrd that comes with the fedora xen kernel package.
But then, the domU hangs on "starting crond..." I have no idea what
is missing there, I already installed udev additionally, but that
doesn't help.
As said, this same system runs with no problem on FC6 with the
xensource binaries.
BTW: I run the system without pygrub and not with the kernel from
disk, but with the kernel= options...
Henning
17 years, 4 months
No keyboard in HVM guest during early startup
by Felix Schwarz
Hi,
I'm using XEN on FC6 and installed Windows XP as a HVM guest. My problem is that my
keyboard does not work early in the startup process (it works after the Windows GUI is
started[1]). I tried to use Windows hibernation and this failed so Windows always asks me
to confirm "Delete restoration data and proceed to system boot menu". Unfortunately, my
keyboard does not work at this stage in XEN. I tried using qemu but had the same problem.
Any hints how to enable my keyboard at the early stages in XEN/qemu so I can start my HVM
guest again?
fs
[1] Only with an US keyboard layout despite using a QWERTZ keyboard.
17 years, 4 months
RE: [Fedora-xen] Problem installing full virtualized Vista guest
by Jimison, Ed
Ian,
Thanks for the tip on the kernel version. Once I changed from kernel
version 2849 to 2798 I was able to install the Vista s/w. I guess I'm at
the same networking problem roadblock you hit. The default Vista network
adapter on both of my machines is Realtek RTL8139C+ Fast Ethernet NIC
and so far I haven't been able to get a network connection on either
Vista guest.
EdJ
________________________________
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Ian Patton
Sent: Thursday, December 14, 2006 12:22 PM
To: Bill Davidsen; fedora-xen
Subject: Re: [Fedora-xen] Problem installing full virtualized Vista
guest
Bill,
Good luck getting Vista to install. You may want to look at my threads
for Nov & Dec for a good working file and stuff, but even after I got it
installed I had problems with networking and sound not working... also
kernel problems with the latest FC6 kernel xen
I posted my findings here: http://virtualdreamscapes.blogspot.com/
Also, after a few domU reboots it seems that the domU system became
unstable and would not boot.
Later I tried parallels and did get Vista working with sound and
networking, but again after a few Vista reboots the system became
unstable and would not boot.
I was using RC1 though...
If you can get it to run and get networking up and get it stable, PLEASE
post to share your success story.
Thanks,
Ian Patton
On 12/13/06, Bill Davidsen <davidsen(a)tmr.com> wrote:
Jimison, Ed wrote:
>
> Now that I finally got W2K installed as a guest, I'm moving on to
> Vista. The initial setup and config worked and the Vista install
> booted from CDROM and transferred files to the harddrive. After reboot
> there is just a blank black screen, which is very similar to the W2K
> install. With W2K I worked around it by hitting F5 and selecting
> Standard PC. With Vista there is no such option.
>
> I transferred the ISO to disk and added it to my config file. When I
> create the guest and it tries to boot I get this error:
>
> Boot from Hard Disk 0 failed
>
> FATAL: not a bootable disk
>
You might try running xm with boot from CD.
xm create vistavirt1 boot=d
I've been trying to install Win98SE, and the startup claims it can't
find a driver for the CD. My file looks just about like your, I get
asked to boot from disk or CD, then after a few screens it says it can't
find a CD driver. I'm about to switch to vmware, even if I have to run
Windows. Also tried:
phy:/dev/dvd,hdc:c,r
with no more luck.
The install used to run slowly under qemu, and the operative word there
is "run," I spent a bunch on a big new hvm capable server, and I can't
install the things I need to test.
>
> My config file:
>
> # Automatically generated xen config file
>
> name = "vistavirt1"
>
> builder = "hvm"
>
> memory = "500"
>
> disk = [ '_file:/xen/vistavirt1,hda,w_',
> '_file:/home/evjimiso/vista.iso,hdc:c,r_']
>
> vif = [ 'type=ioemu, mac=00:16:3e:3f:17:66, bridge=xenbr0', ]
>
> uuid = "2dc04ca6-4de7-0b22-8cc4-4bdb0ff273d9"
>
> device_model = "/usr/lib/xen/bin/qemu-dm"
>
> kernel = "/usr/lib/xen/boot/hvmloader"
>
> vnc=1
>
> vncunused=1
>
> apic=1
>
> acpi=1
>
> pae=1
>
> vcpus=1
>
> serial = "pty" # enable serial console
>
> on_reboot = 'restart'
>
> on_crash = 'restart'
>
>
------------------------------------------------------------------------
>
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
--
bill davidsen < davidsen(a)tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
--
Ian Patton
17 years, 4 months
Could not enable shadow paging for domain?
by Tom Horsley
Playing with Xen, Fedora Core 6, and 8-way Opteron system at work
with 8 gig of memory:
Xen seems to stop being able to create domains after it has been
up for a while (doing things like testing lots of guest installs
or even just dom0 for non-xen related testing).
Any attempt at this point to create a new domain winds up
with error (12, 'Cannot allocate memory'), and the
xend-debug.log shows ERROR: Could not enable shadow paging for domain.
Rebooting the machine (the real one :-) fixes the problem until
it has been up for a while again...
This sound familiar to anyone? Should I file a bug (what would
be a good component to use? kernel-xen?).
17 years, 4 months
Xen and apic
by George Hill
My system uses an Athlon 64 X2 4000+ Socket AM2 (Windsor) chip.
To boot FC6 w/o Xen it requires the noapic option on the kernel line in grub.conf.
When I install the Xen kernel the noapic option moves to the module line.
In this configuration the system gives me
Panic on CPU 0
IO+APIC timer doesn't work...boot with noapic option.
When I move the noapic option from the module line to the kernel line in
grub.conf (for the Xen kernel), the system hangs with
...
(XEN) Xen trace buffers: disabled
IOAPIC[0]: Invalid reference to IRQ 0
(repeats 4 times)
Red Hat nash version 5.1.19 starting
and I get nothing more.
Does anyone have a suggestion as to how I can boot the Xen kernel? Thanks in advance.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
17 years, 4 months
