All good now, and I definitely see a big performance improvement with partitions vs. tap:|
Timing cached reads: 7856 MB in 2.00 seconds = 3936.95 MB/sec
Timing buffered disk reads: 306 MB in 3.00 seconds = 101.95 MB/sec
Previously I was getting ~10MB/s with tap.
On Sat, Jan 24, 2009 at 3:48 PM, Peter Hoose <phoose@xxxxxxxxx>
Never mind, it may have been the mirror, just tried a different one and the install is chugging along smoothly thus far.
Thanks for all of your help!
On Sat, Jan 24, 2009 at 3:35 PM, Peter Hoose <phoose@xxxxxxxxx>
> Yes. For this purpose, you create one LV on dom0, map it to domU asSweet!
> xvda, and install domU like what you'd do with file-based disk image.
Got much closer this time around my new config:
ramdisk = "/var/lib/xen/boot/CentOS/CentOS_5_x64_initrd.img"
kernel = "/var/lib/xen/boot/CentOS/CentOS_5_x64_vmlinuz"
extra = "text"
name = "guest01"
memory = "1024"
disk = [ 'phy:/dev/VolGroup00/guest01,xvda,w', ]
vif = [ 'bridge=xenbr0', ]
The disk shows up properly now, and in theory, it lets me create
partitions on it, format them, etc... But it bombs out as soon as it
starts to install with:
The file system-config-securitylevel-tui-188.8.131.52-2.1.el5.x86_64.rpm
cannot be opened. This is due to a missing file, a corrupt package
or corrupt media. Please verify your installation source.
If you exit, your system will be left in an inconsistent state that
will likely require reinstallation.
This happens regardless of packages selected, it seems to be the first file each time, this is install from the same mirror that I used with no problems with file based, so it seems to still be something wrong with my disk setup?
Anyways, it's much closer now and past the first big question/issue I had.
If you have any ideas what caused the above error, I'd appreciate it, if not I'll just hack away at it until it works.
On Sat, Jan 24, 2009 at 3:29 PM, Fajar A. Nugraha <fajar@xxxxxxxxx>
> I just created a LVM based vbd in my dom0, I want to useYes. For this purpose, you create one LV on dom0, map it to domU as
> this as my 'disk' for my domU, which I would create my partitions on. Is
> this possible,
xvda, and install domU like what you'd do with file-based disk image.
I'm not quite sure what you mean, but you can do this :
> or do I need to create a /boot, / and /swap on my domU and
> share those with dom0 for it to access natively? IE: Does the dom0 see this
> partition as a disk that it can create partitions on, or does it see it just
> like a normal partition?
- create two LVs on dom0, map it to domU as xvda1 (for / ) and xvda2
(for swap). You don't need a separate /boot.
- do mkfs.ext3 and mkswap on dom0 directly on that LV (not creating
partition on top of it)
- populate domU's filesystem (for example, by extracting "templates"
like the one from jailtime.org, or by copying from a working domU.)
- create a suitable initrd
Xen-users mailing list