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


Re: [Xen-users] [SOLVED] vbd segment not found

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] [SOLVED] vbd segment not found
From: "axanet@xxxxxxxxxxxxxx" <axanet@xxxxxxxxxxxxxx>
Date: Thu, 24 Nov 2005 15:01:56 +0800
Delivery-date: Thu, 24 Nov 2005 07:02:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Hello List:

I solved this problem when i fix loop.c in kernel source tree

Doing as following:

1. cd /usr/src/linux-
2. Using your editor to modify loop.c  (Line 74,1146 and 1147) 

max_loop = 8

max_loop = 32

3. changing "kernel" parameter in /boot/grub/grub.conf

kernel  /xen-2.0.gz dom0_mem=1024000 max_loop=32 com1=115200,8n1

4. reboot

5. After rebooting, you can use dmesg|grep loop to verify max loop devices

dmesg output: 
loop: loaded (max 64 devices)

axa@HiNet <axanet@xxxxxxxxxxxxxx>
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-users] [SOLVED] vbd segment not found, axanet@xxxxxxxxxxxxxx <=