Ross S. W. Walker wrote:
> After seeing this same issue on my Xen 3.2 install, but with NO
> migration or iSCSI happening I decided it is probably NOT iSCSI's
> fault, so I decided to research it a little more and this is what
> I found:
>
> http://docs.xensource.com/XenServer/4.0.1/guest/ch04s08.h
Ross S. W. Walker wrote:
>
> Brett Worth wrote:
> >
> > Hello All.
> >
> > I've just started looking into Xen and have a test
> > environment in place. I'm seeing an
> > annoying problem that I thought worthy of a post.
> >
> > Config:
> >
> > I have 2 x HP DL585 servers each with 4 Dual cor
Brett Worth wrote:
>
> Hello All.
>
> I've just started looking into Xen and have a test
> environment in place. I'm seeing an
> annoying problem that I thought worthy of a post.
>
> Config:
>
> I have 2 x HP DL585 servers each with 4 Dual core Opterons
> (non-vmx) and 16GB RAM
> configured
My un-authoritative answer: I've been tracking this bug (or several with the
same symptoms) for going on a couple years. It's ridiculously common,
apparently well known to the Xen/Xensource guys judging by the number of
reports/bugs posted, but I haven't seen mention of it actually being add
Hello All.
I've just started looking into Xen and have a test environment in place. I'm
seeing an
annoying problem that I thought worthy of a post.
Config:
I have 2 x HP DL585 servers each with 4 Dual core Opterons (non-vmx) and 16GB
RAM
configured as Xen servers. These run CentOS 5.1 with t
