mcr's questions

I'm looking for a tool, very much like rdisc6, that will, having received the RA, will configure the v6 address(es) on an interface using a static IID. This is a server that needs to be at a known address within a ULA. (No, I can't use mDNS and SLAAC, as there are certificates bound to names involved, and mDNS may not even work until this interface is configured).
If I have to, I'll extend rdisc6, but I'm hoping not to replicate something someone already did. This will be running on Linux (armv7) inside an LXC container.

Output from: sudo lvs --all -o +devices

root                        hp03 mwa-ao  18.62g                    root_mlog        100.00         root_mimage_0(0),root_mimage_1(0)                        
[root_mimage_0]             hp03 iwi-ao  18.62g                                                    /dev/sda3(0)                                             
[root_mimage_1]             hp03 iwi-ao  18.62g                                                    /dev/sdc3(0)                                             
[root_mlog]                 hp03 mwi-ao   4.00m                                     100.00         root_mlog_mimage_0(0),root_mlog_mimage_1(0)              
[root_mlog_mimage_0]        hp03 iwi-ao   4.00m                                                    /dev/sdd3(0)                                             
[root_mlog_mimage_1]        hp03 iwi-ao   4.00m                                                    /dev/sdb3(0)                                             

/dev/sdb3 and /dev/sdd3 are surplus to my needs, and I want to remove them. As my mirrorlog is mirrored, I feel happy having it on /dev/sda3 and /dev/sdc3. I try to move the mirror log elsewhere:

# pvmove --name /dev/hp03/root_mlog_mimage_1 /dev/sdb3
Skipping mirror image LV root_mlog_mimage_1
All data on source PV skipped. It contains locked, hidden or non-top level LVs only.
No data to move for hp03

No dice. How can I unlock/unhide these volumes so that they can be moved? I hope the answer is not, remove the mirror and add it back, as there is several TB of data that I need to do this for.

As Chris Benninger says over at: http://www.benninger.ca/?p=58 lots and lots of people have the problem with Squeeze and xen4.0 telling them:

launch_vm: SETVCPUCONTEXT failed (rc=-1)

but nobody seems to know what the solution is. I don't know either, but at least here, a solution might get recorded.

In my case, I can start one guest machine. An identical configuration for a second machine fails. Whichever one I start first, is the one that runs, the other gets the error.

I've got at least a dozen other systems (at my work) running great with Squeeze and 64-bit XEN, but not this new machine at home.