This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: Need mega basic Xen help

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: Need mega basic Xen help
From: "Rob Greene" <robgreene@xxxxxxxxx>
Date: Sat, 26 Apr 2008 11:24:50 -0500
Delivery-date: Sat, 26 Apr 2008 09:25:21 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=etwUp3TwUjHyjAZau+w9qNJ0PIKbYHnx1qP0DeI6idE=; b=Q5AoV0VkNMHOfnXGh0G7bvR7WeX3srbm/p63tIGCCHvGY37KYoLHEoCUjEt0bp5H7zqdYFEMADk4fdGvW/Pn1iBkPU+k4iGfRaifPali7S2NIusF4jIov1WpFdhnbHkbMPVeUoGBKpMKphIsyjuEvdjkm1saO3Mh9yOaPCSRiqg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=tLYhwndSafOTbweTAP/m2RzZOvkVMlfXqtlhK6OGfLKSGgkV2f8TDkCXxCojw65+Lkq6udiPQvr0/FDx1TQOTDPEyJody57ScJIoVmN7wQM2gnyCxy9URfzPAWrCxuB87FxkoM/ImlU592X3NBhb01L8n8GiXPwhQHAzYWg5aZY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <738584f80804241859y4642c7c2jc6ca3fafaa29dae6@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <738584f80804241859y4642c7c2jc6ca3fafaa29dae6@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Quick status update and need more direction...

Per the discussion, I am trying to stick with CentOS as the domU since it apparently does have ivtv drivers.  So, I did hook them in without too much of an issue but the kernel crashes.  I've got both 32 and 64 bit configurations right now, and both appear to have the same problem.  The pertinent part of the dump (to me) is:

Fatal DMA error! Please use 'swiotlb=force'
------------[ cut here ]------------
kernel BUG at arch/i386/kernel/pci-dma-xen.c:364!
invalid opcode: 0000 [#1]
last sysfs file: /class/video4linux/video0/dev
Modules linked in: msp3400 saa7115 tuner ivtv(U) i2c_algo_bit cx2341x tveeprom i2c_core videodev v4l1_compat v4l2_common pcspkr dm_snapshot dm_zero dm_mirror dm_mod xenblk ext3 jbd ehci_hcd ohci_hcd uhci_hcd
CPU:    0

So, after googling, I did add the swiotlb=force line to both my extras line in the Xen config file as well as to the grub.conf file within the domU itself (I left the dom0 alone).  Unfortunately, this message tells me nothing:

------------[ cut here ]------------
kernel BUG at lib/../arch/i386/kernel/swiotlb.c:160!
invalid opcode: 0000 [#1]
last sysfs file:
Modules linked in:
CPU:    0
EIP:    e019:[<c04e1370>]    Not tainted VLI
EFLAGS: 00010282   (2.6.18-53.1.14.el5xen #1)
EIP is at swiotlb_init_with_default_size+0x88/0x14e
eax: fffffff4   ebx: 00000180   ecx: 00000000   edx: f5416000
esi: c0702b64   edi: 08000000   ebp: c06d4fc0   esp: c06d4fb4
ds: e021   es: e021   ss: e021
Process swapper (pid: 0, ti=c06d4000 task=c065e2c0 task.ti=c06d4000)
Stack: c1825000 c0702b64 c0271b07 00000020 c06e3bae 0000000e 00000002 c1825000
       c0702b64 c181fa64 00000020 c06d9873 00008000 c0748800 03040800 c0ef7000
       00000000 00000000 c040006f
Call Trace:
 [<c06e3bae>] mem_init+0x58/0x390
 [<c06d9873>] start_kernel+0x1fb/0x388
Code: c2 b6 f3 ff 83 c8 ff 40 83 f8 06 75 fa 89 d8 b9 1e 00 00 00 c1 e0 0b ba 06 00 00 00 03 05 14 c7 78 c0 e8 00 41 f3 ff 85 c0 74 08 <0f> 0b a0 00 c1 4e 62 c0 83 eb 80 a1 18 c7 78 c0 39 c3 72 c5 b9
EIP: [<c04e1370>] swiotlb_init_with_default_size+0x88/0x14e SS:ESP e021:c06d4fb4
 <0>Kernel panic - not syncing: Fatal exception

I did try a number of "swiotlb=(64|128|256),force" lines and then upped the VM image to 1GB ram also since one post suggested it could simply be not enough memory (I have 8GB physical). 

I remember something about a Xen permissive mode for PCI cards... do I need that?  Some of the messages I've been seeing looked to actually have that test in the logs somewhere and I don't see it, so I'm guessing no.

I'm not sure where to proceed from here.  I guess worst case, I put these cards back into the original machine and dedicate it to Myth or Sage (which it ran ok for a couple of years).  I'd really like to consolidate all of this, and the virtual world would really rock.  :-/

Any suggestions?
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>