similar to: [Patch] Fix blktap to work with a bootloader

Guys, I''ve successfully ran dom0/domU (both Debian) in my local laptop using 2.6.32.15 dom0 with xen-4.0.1-rc3-pre. Great. Now I want to install it into couple of test-machines without compiling from source. So I did following.. a. make dist-xen b. make dist-tools PYTHON_PREFIX_ARG="--install-layout=deb" c. make dist-stubdom This

Folks, The tag 4.0.1-rc3 has been added to http://xenbits.xensource.com/xen-4.0-testing.hg Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am trying to start a large number of SMP domains (> 50). However, I am unable to create more than 7 domains. When I try creating the 8th domain, I get this error: Using config file "myconf7". VIRTUAL MEMORY ARRANGEMENT: Loaded kernel: 0xc0100000->0xc0344c24 Init. ramdisk: 0xc0345000->0xc0345000 Phys-Mach map: 0xc0345000->0xc0347800 Page tables:

Hello everybody, Could someone please explain to me what is the difference between kjournald and jbd (precisely, what does each of them do?) Thank you, Alina _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

Hi all, I've pushed my current set of ext3 diffs (against Marcelo's current tree) to http://people.redhat.com/sct/patches/ext3-2.4/dev-20030314/ This includes: 00-merged/ diffs recently merged into 2.4 10-core-fixes-other/ misc fixes/tweaks from akpm, adilger 11-core-fixes-sct/ misc fixes/tweaks from sct 20-tytso-updates/ Ted's recent updates 21-updates-sct/ recent sct diffs

Hi I have two box xen 3.2.1 and 3.3. On the 3.3 box I can''t use drbd as a device in the domu cfg. xm create -c test.cfg Using config file "/etc/xen/test.cfg". Error: Block device must have "phy", "file" or "tap" specified to type cat /etc/xen/test.cfg # Configuration file for the Xen instance test, created # by xen-tools 3.8 on Tue Sep 16

Hi all (and developers in particular) I just got bitten by this Assertion. The one that starts as in the subject, and ends with: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" Google reminds me that it was mentioned a few times earlier this year, but I couldn't find any statement saying that it has been fixed. I got this in a 2.4.16 kernel, though the

Hi, ext3-0.0.6a has been uploaded to ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ext3-0.0.6a.tar.gz and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ext3-0.0.6a.tar.gz This version changes the way dirty buffers are marked to protect against device drivers which might block in the ll_rw_block() function. (Loop and lvm are examples.) It should also fix a rare but persistent report of

Hi, On paravirt x86 (both 32- and 64-bit), since cset 13998: http://xenbits.xensource.com/xen-unstable.hg?rev/13998 we translate all ptes from being mfn-based to pfn-based when the hardware _PAGE_PRESENT bit is cleared. We do this for PROT_NONE pages, which appear to the HV to be non-present, but which are special-cased in the kernel to appear present (a different bit in the

Hi, ext3-0.0.5d.tar.gz is now up on ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ as patches against 2.2.18. This only contains the kernel bits: we're in the process of syncing up on some e2fsprogs so I'll do another release shortly once we've got all of the pending changes for the user-mode tools assembled. This release is mostly

> AW> This should be fixable though. I''m also not sure how carefully > AW> dm-u watches block completion responses to ensure safety of > AW> metadata updates relative to data writes. This too should be > AW> fixable -- i just don''t know if the user-level tools can currently > AW> request completion notifications on requests that they''ve

I've been thinking recently that we should re-enable DIR_INDEX in mke2fs by default. When it first came out, we had done this and were bitten by a few bugs in the code. However, this code has been in heavy use for several thousand filesystem years in Lustre, if not elsewhere, and I'm inclined to think it is pretty safe these days. Likewise, RHEL/FC have had RESIZE_INODE as a standard

Hello! I'm using a CompactFlash as storage device. Since those CF cards only have limited write cycles (CF does wear-levelling by itself, but you don't want to write too many timet so the card) i was wondering by what a factor the journaling of ext3 increases the write accesses to the CompactFlash compared to ext2. Thanks a lot already for your help! Sincerely Chris Braun

Hi, Can anyone tell me the ext3/ext2/vfs FS specifications: max number of files: ? max number files a dir can have: ? max number sub-dirs in a dir: ? max file size: ? max filesystem size: ? Dongsheng Song

Hello All! I've asked this question on others lists but didn't found any answer - full distro upgrade was only reasonable option. I understand why ext3 patches require up-to-date e2fsprogs - ext2 in heavy development. Q1: Why ext3 requires 'very' up-to-date util-linux? I've tryed to upgrade from tarball - but realized that I can run into problems with my distro. SuSE

Just looking through the 2.4.20pre changelogs, I see there's been a bunch of Ext3 patches since 2.4.19. I'm keen to take advantage of any bug fixes and performance improvements, but am nervous about using 2.4.20 until it's completed its release cycle. Is there any way to get a patch just containing the Ext3 changes? Are there any changes since 2.4.20 that are very important, either

In the spirit of improving communication of Fedora Xen plans to the world, below is a mail I recently circulated in the Fedora community about the direction for Xen-ified kernels from Fedora 9 and onwards. The short story, is that we intend to ship hypervisor & userspace based on Xen 3.2.0 tree, and a kernel based on latest LKML pv_ops tree and patches ontop of that to support Dom0 and

Hi all, ext3-0.0.6b is now available at the usual places: ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ and ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ The only significant change in this release is the fix to the orphan list recovery, and that fix also affects e2fsprogs, so please pick up the new e2fsprogs from the same directory when you grab the ext3 release. I've put tarballs,

Hello Folks, We have 2 (identical hardware) busy public 2U rack servers, both have several hundred users & peak email (for example) deliveries at 300/5min during the daytime. Both servers run RAID1 over 2 EIDE disk drives. One server is fine - it never has problems - it is running RH7.3 and CPU loads are normal. The other server has constant disk activity & kjournald at CPU load of

Hi Andrew, The patch below addresses the problem we were talking about earlier where ext3_writepage ends up accessing the inode after the page lock has been dropped (and hence at a point where it is possible for the inode to have been reclaimed.) Tested minimally (it builds and boots.) It makes ext3_journal_stop take an sb, not an inode, as its final parameter. It also sets