Problem with Dom0 ( SuSE )

Problem with Dom0 ( SuSE )

[Gonzalo Medina Castro]

I install Xen in a SuSE ES 9. The problem is that if I connect to the server
with ssh, and I try to make a tar, or copy files from another server with
rsync, Dom0 down, I neet to reboot it. If I do the same, but directly on the
server, nothing happends, only happend if I try to do this remotely.
Any ideas?
--
View this message in context: http://www.nabble.com/Problem-with-Dom0-%28-SuSE-%29-t1182898.html#a3114207
Sent from the Xen - Dev forum at Nabble.com.

Re: Problem with Dom0 ( SuSE )

[Keir Fraser]

On 24 Feb 2006, at 19:24, Gonzalo Medina Castro wrote:

> I install Xen in a SuSE ES 9. The problem is that if I connect to the 
> server
> with ssh, and I try to make a tar, or copy files from another server 
> with
> rsync, Dom0 down, I neet to reboot it. If I do the same, but directly 
> on the
> server, nothing happends, only happend if I try to do this remotely.
> Any ideas?

Perhaps a network card problem. Does dom0 print any error messages when 
it fails? What NIC are you using?

  -- Keir

Re: Problem with Dom0 ( SuSE )

[Gonzalo Medina Castro]

When Dom0 freeze, after reboot it, I found this in messages log:

Feb 27 11:36:59 dbaxixen kernel: megaraid: aborting-912059 cmd=28 <c=2 t=1
l=0>
Feb 27 11:36:59 dbaxixen kernel: megaraid abort: scsi cmd:912059, do now own

I search in google, but I can't found a problem with this module for Xen.

The server is a DELL PowerEdge 2850, with an LSI Logic MegaRAID, I don't
know what only fail if I use disk access trough an ssh connection. If
someone have an idea, I appreciate that. Thanks.


--- Original Message ---
> 
> On 24 Feb 2006, at 19:24, Gonzalo Medina Castro wrote:
> 
> > I install Xen in a SuSE ES 9. The problem is that if I connect to the 
> > server
> > with ssh, and I try to make a tar, or copy files from another server 
> > with
> > rsync, Dom0 down, I neet to reboot it. If I do the same, but directly 
> > on the
> > server, nothing happends, only happend if I try to do this remotely.
> > Any ideas?
> 
> Perhaps a network card problem. Does dom0 print any error
> messages when 
> it fails? What NIC are you using?
> 
>   -- Keir
> 

--
View this message in context: http://www.nabble.com/Problem-with-Dom0-%28-SuSE-%29-t1182898.html#a3146449
Sent from the Xen - Dev forum at Nabble.com.

Re: Problem with Dom0 ( SuSE )

[Gonzalo Medina Castro]

I find this, when this module fail, only ssh connection fail, I believe that
the server down, but this not true, only ssh conection down. I'm still
looking a solution for this problem.
--
View this message in context: http://www.nabble.com/Problem-with-Dom0-%28-SuSE-%29-t1182898.html#a3147053
Sent from the Xen - Dev forum at Nabble.com.

Re: Problem with Dom0 ( SuSE )

[Keir Fraser]

On 27 Feb 2006, at 15:34, Gonzalo Medina Castro wrote:

> I find this, when this module fail, only ssh connection fail, I 
> believe that
> the server down, but this not true, only ssh conection down. I'm still
> looking a solution for this problem.

Try booting with 'nousb' as a domain0 kernel parameter.

  -- Keir

Re: Problem with Dom0 ( SuSE )

[Gonzalo Medina Castro]

Thanks Keir, with "nousb", I can resolve my problem.
--
View this message in context: http://www.nabble.com/Problem-with-Dom0-%28-SuSE-%29-t1182898.html#a3164673
Sent from the Xen - Dev forum at Nabble.com.

Re: Problem with Dom0 ( SuSE )

[Keir Fraser]

On 28 Feb 2006, at 14:46, Gonzalo Medina Castro wrote:

> Thanks Keir, with "nousb", I can resolve my problem.

It'd be interesting to know whether 'usb-handoff' (instead of 'nousb') 
also fixes the problem. Using usb-handoff would mean that you could 
still use USB devices.

  -- Keir