All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: xen-devel@lists.sourceforge.net
Subject: trying to get a domU to manage lvm pvs
Date: Fri, 11 Feb 2005 11:33:02 -0800	[thread overview]
Message-ID: <420D086E.6090507@tupshin.com> (raw)

I'm trying to have a domU run lvm and manage one vg, a few pvs, and lots 
of lvs without the dom0 having any role in the situation.

To simplify things as much as possible, I set up a test with one pv, 
that is recognized as such by the dom0, and I'm using the same dom0 
kernel for my domU.

I did the following:
* pvcreate /dev/hda6 from dom0, and verified that pvscan showed it
* I then explicitly excluded it in dom0's lvm filter, and verified that 
pvscan did not see it
* I added an entry ('phy:hda6,hda6,w') to the domU's  disk configuration
* started the domU
* did a "dd if=/dev/hda6 | less" and saw that the device existed and 
contained information indication it was  a pv.
* copied the exact lvm.conf that I was using in dom0 before adding the 
hda6 exclusion
* restarted lvm (and later rebooted the domU just to be certain)
* did a pvscan and pvdisplay /dev/hda6, both of which claimed to not see 
anything
* tried to redo the pvcreate from within the domU and got the message: 
"/dev/hda6: Couldn't find device.  Check your filters?" (triple checked 
the filters)
* noted that /etc/lvm/.cache consistently is getting filled with:
        valid_devices=[
                "/dev/loop0",
                "/dev/loop1",
                "/dev/loop3",
                "/dev/loop4",
                "/dev/loop7",
                "/dev/loop2",
                "/dev/md0",
                "/dev/loop5",
                "/dev/loop6"
        ]
instead of the specific device(s) that I am handing off to the domU. The 
dom0 lvm cache contains none of those entries.

Any suggestions?


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-02-11 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 19:33 Tupshin Harper [this message]
2005-02-11 22:48 ` trying to get a domU to manage lvm pvs Tupshin Harper
2005-02-12  1:48   ` Christian Limpach
2005-02-12  2:44     ` trying to get a domU to manage lvm pvs (SUCCESS) Tupshin Harper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=420D086E.6090507@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.