On Mon, Apr 15, 2013 at 9:29 AM, Ian Campbell <i...@hellion.org.uk> wrote:
> On Mon, 2013-04-15 at 09:21 -0400, Anthony Sheetz wrote: > > > > > How did you do this? IIRC getting mount options to the root > > filesystem > > to take effect involves more than just editing fstab > > (rootflags= on > > command line I think? No idea how one inserts a space there) > > Ah, ok. Did use fstab options. Will look in to other methods of > > specifying this. I'd imagine editing the boot option in pygrub might > > be a good avenue? > > I think so. Or you can (probably) uses extra = "foo" in your domain > configuration file. You can tell if you've edited the right place > from /proc/cmdline. > > I'd expect there would be some indication in dmesg that barriers were or > were not in use , but I didn't look > > > > > For experimentation it might be useful to attach an xvdb to > > the domain > > and use that as the write target, it'll allow easier > > experimentation > > with mount options, and as a bonus you won't keep hosing your > > root > > filesystem (which I imagine is getting pretty tedious...) > > To be sure I understand: create a new lv, mount it, and use it as the > > write target. That's an excellent idea. Next time I experiment I'll be > > using that. > > Are you using LVM in the domU as well as the dom0? I had thought you > were using it only in dom0 but the ambiguity here made me wonder. > Sorry, domU's volumes are also logical volumes created initially in dom0. So, xvda is backed by a logical volume. > What I meant was to create a new LV in the dom0, edit the domain > configuration to attach it as an extra disk (i.e. xvdb or whatever) and > then to format/mount it from within the guest. > That's what I thought you meant, and what I will try. > > [...] > > Ok, will try that. If you've got instructions close to hand on > > installing and using a different kernel in domU, that'd save me the > > trouble of looking it up. No worries if not - my google foo is decent. > > I expect backports.org has a reasonably recent Wheezy kernel which you > could install or else I think the kernel is independent enough that a > partial upgrade (i.e. add Wheezy to sources.list and "apt-get install > <linux-image-foo>") would not pull in too much of Wheezy. > Thanks, will check in to that. > > Ian. > >
