[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] pci-passthrough in pvops causing offline raid
- To: Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
- From: Olivier Hanesse <olivier.hanesse@xxxxxxxxx>
- Date: Thu, 11 Nov 2010 12:13:31 +0100
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Thu, 11 Nov 2010 03:14:29 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iPRMVxwoouq7I6GI/VjgluPbRrY6rp72o/JM+8s4xY+tfIWY6bu1GDBPIXxTPz37DR 2tM8g2y5KlR+dm9WWlGOegIixsSw+kb1fqAKi+qbfVvdbu3JWVfFhGdNdUJMoJL3cJoO KUj1QfW1CEttgPQp7UmIA3hQ/juDkOIJ9Ewes=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Hello,
What is the module of your raid card ? If it is "megaraid_sas", please try upgrading the version of that module (see others post in the ML).
Regards
2010/11/11 Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Hi All,
Running xen 4.0.1-rc6, debian squeeze 2.6.32-21.
In a voip setup, where I have forwarded the onboard NIC interfaces
through to domU using the following grub config:
module /vmlinuz-2.6.32-5-xen-amd64 placeholder root=UUID=25c3ac79-6850-498d-afcf-ea42970e94fd ro quiet xen-pciback.permissive xen-pciback.hide=(02:00.0)(03:00.0) pci=resource_alignment=02:00.0;03:00.0
I'm having a serious issue where the raid card goes offline after an
indefinate period of time. Sometimes runs fine for a week, other times 1
day before I get "offline device" errors. Rebooting the machine fixes it
straight away, and everything is back online.
What in the Xen pciback is causing the raid card to go offline? The
only devices hidden are the 2 onboard NIC's.
I know that this issue is with Xen, as I had this running on a different
server (same xen setup) and it had the same issues, which I initially
thought were to do with the raid card.
Is there known issues in this kernel and xen version with pciback? I'm
going to update to the current package versions this evening (4.0.1-1
and 2.6.32-27) however would appreciate if anyone has any other insight
into this issue, or even just a note to say it is a bug that has been
fixed in current versions!
Thanks,
Mark
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|