Hi,
where does you root-device reside on?
Do you use sda or hda?
Can you post your DomU-config (without comments) here?
What messages do you get before LVM complains?
It might be that you don't have the rigth drivers in your DomU-initrd
(any more)...
Kind regards,
Nils
-Original
Hi,
my local RH-salesman told me that rh6 will be based on a mix of Fedora 11/12 -
so I hope for the best.
At the moment I am stuck with SLES (currently 10) on our Dom0-servers, since it
has the newer XEN-version.
I would love to move to RH or CentOS with my Dom0s...
Kind regards
Nils
- Christopher Hunt dharmach...@gmail.com wrote:
This brings me back to suspecting the problem is in the different file
structures. I'm still trying to wrap my head around the other replies
in this thread.
mkinitrd in dom0 with xenblk and xennet and use that new initrd for the guests.
Pasi,
Thanks very much for the tip. That did give me some additional
information:
Scanning and configuring dmraid supported devices
Scanning logical volumes
Reading all physical volumes. This may take a while...
Activating logical volumes
Volume group virt01vg00 not found
Creating root
Well that was more helpful than I could reasonable hope for but alas, the
error didn't change much:
device-mapper: dm-raid45: initialized v0.2594l
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Scanning logical volumes
Reading all physical volumes. This may
- Christopher Hunt dharmach...@gmail.com wrote:
Found volume group vg00 using metadata type lvm2 ## this is the VG
on the KVM host
Volume group virt01vg00 not found ## this is the VG on the XEN host
mkinitrd is getting this from your dom0's /etc/fstab.
sed 's/virt01vg00/vg00/g'
- Christopher Hunt dharmach...@gmail.com wrote:
I've updated accordingly, and now am getting a brand new file system
issue:
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Creating root device.
Mounting root filesystem.
mount: could not find
ugh after doing inglorious battle, I return. It's definitely situation
(1). The error messages haven't changed. Inside the init file, should the
paths references be from the point of view of Dom0?
lvm vgchange -ay --ignorelockingfailure vg00
resume /dev/vg00/swap00
echo Creating root
- Christopher Hunt dharmach...@gmail.com wrote:
ugh after doing inglorious battle, I return. It's definitely
situation (1). The error messages haven't changed. Inside the init
file, should the paths references be from the point of view of Dom0?
This is the initrd, running in the
James B. Byrne wrote on Mon, 9 Nov 2009 16:23:55 -0500 (EST):
Lastly, why is qemu 4.5M but kvm-qemu-img is only 125K?
I would assume it's just the module that works on image files. AFAIK, you
don't need qemu if you have KVM. The same way you don't need KVM if you
use Xen ...
Kai
--
Kai
On Mon, November 9, 2009 20:31, Kai Schaetzl wrote:
James B. Byrne wrote on Mon, 9 Nov 2009 16:23:55 -0500 (EST):
Lastly, why is qemu 4.5M but kvm-qemu-img is only 125K?
I would assume it's just the module that works on image files.
AFAIK, you don't need qemu if you have KVM. The same way
On Mon, November 9, 2009 20:31, Kai Schaetzl wrote:
I would assume it's just the module that works on image files.
AFAIK, you don't need qemu if you have KVM. The same way you
don't need KVM if you use Xen ...
The rpm package note for kvm-qemu-img says this:
Summary : Qemu disk image
12 matches
Mail list logo
