thr3ads.net - Fedora xen - RE: [Fedora-xen] File operation causes kernel panic [Apr 2006]

If this information is useful, please help other people find it:
Share via:

Alex.Upton@instinet.com

2006-Apr-26 17:25 UTC

RE: [Fedora-xen] File operation causes kernel panic

I recently experienced the same issue and noticed that it was related to
my snmpd flipping out. 

I''m not sure if its just a buggy version of snmpd that ships with FC5
or
if it''s an overall issue with SNMPD and virtualized environments.

Disabling snmpd resolved it for me, however I''m hoping this issue is
resolved some day. 

Hope this helps.
-Alex
-----Original Message-----
From: fedora-xen-bounces@redhat.com [mailto:fedora-xen-bounces@redhat.com]
On Behalf Of EJacobsh@connectknowledge.com
Sent: Wednesday, April 26, 2006 1:17 PM
To: fedora-xen@redhat.com
Subject: [Fedora-xen] File operation causes kernel panic

Hello,
I''m having a problem with a Dell server (PowerEdge 2850) and a recently
installed Fedora Core 5 with Xen kernel (2.6.16-1.2096_FC5xen0).  Whenever
I try to copy a larger file (128MB) to the server over the network, the
server crashes (register dump on the console, remote sessions stop
responding).

This happens consistently with Anaconda, Samba and WinSCP3.  It has
happened with yum twice, although it works most of the time.

When I reboot the server with a kernel that does not include Xen
(2.6.16-1.2096_FC5), the copying works.

I need some help figuring out what my next steps should be.  I don''t
see
anything unusual in the xend.log (see below).  The xend-debug.log is
empty.  Is there some other place I should look?  Are there any other
diagnostic tools to use?

Thanks for you help.

Eric Jacobshagen
CONNECT: The Knowledge Network

xend.log:

[xend] INFO (SrvDaemon:285) Xend Daemon started [xend] INFO
(SrvDaemon:289) Xend changeset: unavailable .
[xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({''paused'': 0,
''cpu_time'': 24271818792L, ''ssidref'':

0, ''handle'': [0, 0, 0, 0, 0, 0, 0, 0, 0, , 0, 0, 0, 0, 0, 0],
''shutdown_reason'': 0, ''dying'': 0,
''dom'': 0, ''mem_kb'': 524288,
''maxmem_kb'':

-4, ''max_vcpu_id'': 1, ''crashed'': 0,
''running'': 1, ''shutdown'': 0,
''online_vcpus'': 2, ''blocked'': 0})
[xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000.
[xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store for
existing domain 0 [xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing
VM details: 
{''ssidref'': ''0'', ''uuid'':
''00000000-0000-0000-0000-000000000000'',
''on_reboot'': ''restart'',
on_poweroff'': ''destroy'', ''name'':
''Domain-0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''memory'': ''512'',
''on_crash'': ''restart'',
''maxmem'': ''512''}
[xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: 
{''cpu/0/availability'': ''online'',
''memory/target'': ''524288'',
''cpu/1/availability'': ''online'',
''name'': ''Domain-0'',
''console/limit'':
''1048576'', ''vm'':
''/vm/00000000-0000-0000-0000-000000000000'',
''domid'':''0''}
[xend] DEBUG (XendDomain:151) number of vcpus to use is 0 [xend] INFO
(SrvServer:114) unix path=/var/lib/xend/xend-socket

--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


*****************************************************************
<<<Disclaimer>>>

In compliance with applicable rules and regulations, Instinet
reviews and archives incoming and outgoing email communications,
copies of which may be produced at the request of regulators.
This message is intended only for the personal and confidential
use of the recipients named above.  If the reader of this email
is not the intended recipient, you have received this email in
error and any review, dissemination, distribution or copying is
strictly prohibited. If you have received this email in error,
please notify the sender immediately by return email and
permanently delete the copy you received.  

Instinet accepts no liability for any content contained in the
email, or any errors or omissions arising as a result of email
transmission. Any opinions contained in this email constitute
the sender''s best judgment at this time and are subject to change
without notice.   Instinet does not make recommendations of a
particular security and the information contained in this email
should not be considered as a recommendation, an offer or a
solicitation of an offer to buy and sell securities.

*****************************************************************

Eric Jacobshagen

2006-Apr-26 17:30 UTC

head link

RE: [Fedora-xen] File operation causes kernel panic

Unfortunately for me, I am not running smnpd...

-Eric

Alex.Upton@instinet.com wrote on 04/26/2006 11:25:18 AM:
> I recently experienced the same issue and noticed that it was related to
> my snmpd flipping out. 
> 
> I''m not sure if its just a buggy version of snmpd that ships with
FC5 or
> if it''s an overall issue with SNMPD and virtualized environments.
> 
> Disabling snmpd resolved it for me, however I''m hoping this issue
is
> resolved some day. 
> 
> Hope this helps.
> -Alex
> -----Original Message-----
> From: fedora-xen-bounces@redhat.com 
[mailto:fedora-xen-bounces@redhat.com]> On Behalf Of EJacobsh@connectknowledge.com
> Sent: Wednesday, April 26, 2006 1:17 PM
> To: fedora-xen@redhat.com
> Subject: [Fedora-xen] File operation causes kernel panic
> 
> Hello,
> I''m having a problem with a Dell server (PowerEdge 2850) and a
recently
> installed Fedora Core 5 with Xen kernel (2.6.16-1.2096_FC5xen0). 
Whenever> I try to copy a larger file (128MB) to the server over the network, the
> server crashes (register dump on the console, remote sessions stop
> responding).
> 
> This happens consistently with Anaconda, Samba and WinSCP3.  It has
> happened with yum twice, although it works most of the time.
> 
> When I reboot the server with a kernel that does not include Xen
> (2.6.16-1.2096_FC5), the copying works.
> 
> I need some help figuring out what my next steps should be.  I
don''t see
> anything unusual in the xend.log (see below).  The xend-debug.log is
> empty.  Is there some other place I should look?  Are there any other
> diagnostic tools to use?
> 
> Thanks for you help.
> 
> Eric Jacobshagen
> CONNECT: The Knowledge Network
> 
> xend.log:
> 
> [xend] INFO (SrvDaemon:285) Xend Daemon started [xend] INFO
> (SrvDaemon:289) Xend changeset: unavailable .
> [xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
> XendDomainInfo.recreate({''paused'': 0,
''cpu_time'': 24271818792L,
''ssidref'':> 
> 0, ''handle'': [0, 0, 0, 0, 0, 0, 0, 0, 0, , 0, 0, 0, 0, 0,
0],
> ''shutdown_reason'': 0, ''dying'': 0,
''dom'': 0, ''mem_kb'': 524288,
''maxmem_kb'':> 
> -4, ''max_vcpu_id'': 1, ''crashed'': 0,
''running'': 1, ''shutdown'': 0,
> ''online_vcpus'': 2, ''blocked'': 0})
> [xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, 
UUID> 00000000-0000-0000-0000-000000000000.
> [xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store 
for> existing domain 0 [xend.XendDomainInfo] DEBUG (XendDomainInfo:667) 
Storing> VM details: 
> {''ssidref'': ''0'',
''uuid'':
''00000000-0000-0000-0000-000000000000'',
> ''on_reboot'': ''restart'',
on_poweroff'': ''destroy'', ''name'':
''Domain-0'',
> ''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''memory'': ''512'',
''on_crash'': ''restart'',
> ''maxmem'': ''512''}
> [xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details: 
> {''cpu/0/availability'': ''online'',
''memory/target'': ''524288'',
> ''cpu/1/availability'': ''online'',
''name'': ''Domain-0'',
''console/limit'':
> ''1048576'', ''vm'':
''/vm/00000000-0000-0000-0000-000000000000'',
''domid'':''0''}> [xend] DEBUG (XendDomain:151) number of vcpus to use is 0 [xend] INFO
> (SrvServer:114) unix path=/var/lib/xend/xend-socket
> 
> --
> Fedora-xen mailing list
> Fedora-xen@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
> 
> 
> *****************************************************************
> <<<Disclaimer>>>
> 
> In compliance with applicable rules and regulations, Instinet
> reviews and archives incoming and outgoing email communications,
> copies of which may be produced at the request of regulators.
> This message is intended only for the personal and confidential
> use of the recipients named above.  If the reader of this email
> is not the intended recipient, you have received this email in
> error and any review, dissemination, distribution or copying is
> strictly prohibited. If you have received this email in error,
> please notify the sender immediately by return email and
> permanently delete the copy you received. 
> 
> Instinet accepts no liability for any content contained in the
> email, or any errors or omissions arising as a result of email
> transmission. Any opinions contained in this email constitute
> the sender''s best judgment at this time and are subject to change
> without notice.   Instinet does not make recommendations of a
> particular security and the information contained in this email
> should not be considered as a recommendation, an offer or a
> solicitation of an offer to buy and sell securities.
> 
> *****************************************************************
>

Fedora xen - Apr 2006 - RE: File operation causes kernel panic

RE: [Fedora-xen] File operation causes kernel panic

RE: [Fedora-xen] File operation causes kernel panic