WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Any xen kernel configs to ensure that this doesnt happen?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Any xen kernel configs to ensure that this doesnt happen?
From: "Christopher Isip" <cmisip@xxxxxxxxx>
Date: Sun, 25 May 2008 10:19:40 -0400
Delivery-date: Sun, 25 May 2008 07:20:11 -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:mime-version:content-type; bh=4K1BRlome0RuLPxQaZDsc8k5wI1yR+hKVtRlqi907l0=; b=YvtaBlPlXpV19F8Rf5diE5K/UaqgA2gL/g7l/XncGD2BhE6JfqkXUe7NKr16PeSARNiM1uAfPGMeAkD7aoH4xdrIutudTgfh2Bh3utWd8SMNu1Hgbq4ie6FnGyzpOu55Pn1g6+jQLQDXF7isjv9XGJCI/7tuZo7gORSGCoFXewQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=vmIV7lJiBKiFRBZiquzbY/QEcW2F8cbn6sSoYpyTPqnYCG6VmzPV+u11h0STadUuUbUYkNt5H5F3Yzrj4b2RKIitUq1W8TJfJWKougMMD7+SWN5BMRA+OfreRA+G6iTeza2JIACA+oylVLFqSWEOAqlSsOyOxqlEJBgsd2tOq3o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Whenever I boot the mythtv domU after booting another domU, I get this:

[    0.000000] Linux version 2.6.24-16-xen (hiranotaka@noto) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #2 SMP Sun Apr 20 05:49:43 JST 2008 (Ubuntu 2.6.24-4.6-generic)
[    0.000000] Reserving virtual address space above 0xf5800000
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 0000000028800000 (usable)
[    0.000000] 0MB HIGHMEM available.
[    0.000000] 648MB LOWMEM available.
[    0.000000] NX (Execute Disable) protection: active
[  749.268764] Zone PFN ranges:
[  749.268766]   DMA             0 ->     4096
[  749.268768]   Normal       4096 ->   165888
[  749.268770]   HighMem    165888 ->   165888
[  749.268771] Movable zone start PFN for each node
[  749.268774] early_node_map[1] active PFN ranges
[  749.268776]     0:        0 ->   165888
[  749.286124] ACPI in unprivileged domain disabled
[  749.286135] Allocating PCI resources starting at 30000000 (gap: 28800000:d7800000)
[  749.286189] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 164592
[  749.286195] Kernel command line: root=/dev/hda1 ro console=xvc0 swiotlb=force
[  749.286409] Enabling fast FPU save and restore... done.
[  749.286417] Enabling unmasked SIMD FPU exception support... done.
[  749.286422] Initializing CPU#0
[  749.286589] PID hash table entries: 4096 (order: 12, 16384 bytes)
[  749.286629] Xen reported: 3391.510 MHz processor.
[    0.374407] console [xvc0] enabled
[    0.374477] Console: colour dummy device 80x25
[    0.374652] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.375186] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.424706] Kernel panic - not syncing: No suitable physical memory available for SWIOTLB buffer!
[    0.424710] Use dom0_mem Xen boot parameter to reserve
[    0.424711] some DMA memory (e.g., dom0_mem=-128M).
[    0.424711]


I want to be able to boot the domU's in any order and was wondering if there is anything I can add to the configs to allow that.  I want to boot the Firewall, Mysql and then Mythtv domUs in that order as mythtv depends on those two domains.

I treid adding dom0_mem=-128 in the kernel line but that didn't do anything.

Here is my grub.conf in the mythtv domU
title           Ubuntu 8.04, kernel 2.6.24-16-xen
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.24-16-xen root=/dev/hda1 ro console=xvc0 swiotlb=force
initrd          /boot/initrd.img-2.6.24-16-xen

in the dom0
title CentOS (2.6.18-xen_3.2.0)
        root (hd0,5)
        kernel /boot/xen.gz-3.2 dom0_mem=-128M
        module /boot/vmlinuz-2.6-xen ro root=LABEL=/ rhgb quiet
        module /boot/initrd-2.6-xen.img

And my mythtv xen config file:

bootloader = '/usr/bin/pygrub'
memory = 640
name = "Ubuntu-Mythtv"
disk = ['file:/mnt/VM/Ubuntu-Hardy-Mythtv.img,hda1,w','file:/mnt/VM/Ubuntu-Hardy-Mythtv-swap.img,hda2,w']
vif = [ '' ]
pci = [ "0000:03:02.0","0000:04:08.0","0000:04:09.0" ]
extra = "swiotlb=force"
sdl = 1

If I cant  accomplish this, I may just have to write a script to start the mythtv backend after the mysql service is up and running.

Thanks
Chris

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Any xen kernel configs to ensure that this doesnt happen?, Christopher Isip <=