| To: | xen-users@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: [Xen-users] [SOLVED] vbd segment not found |
| From: | "axanet@xxxxxxxxxxxxxx" <axanet@xxxxxxxxxxxxxx> |
| Date: | 2005年11月24日 15:01:56 +0800 |
| Delivery-date: | 2005年11月24日 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.6.11.12-xen/drivers/block 2. Using your editor to modify loop.c (Line 74,1146 and 1147) ‧Before: max_loop = 8 ‧After: 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 Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-users] Minimum Ram requirement to run Xen , Mustafa Abbasi |
|---|---|
| Next by Date: | Re: [Xen-users] Debian, Xen and CLUSTER / GFS Support , Dirk H. Schulz |
| Previous by Thread: | [Xen-users] Minimum Ram requirement to run Xen , Mustafa Abbasi |
| Next by Thread: | [Xen-users] New Xenoppix with Install2win and PXE-terminal-server , Kuniyasu Suzaki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |