On Sat, Mar 14, 2009 at 9:40 PM, Florian Manschwetus <[email protected]> wrote: >> I'm using pygrub with no problems at all. I use zvols directly as >> domU's storage (without partition). > would be like: > /dev/dsk/c0t600A0B800049E902000007FD49B54652d0p1 > (what works well for the domU if I map it as xvda1) > > normally I map > /dev/dsk/c0t600A0B800049E902000007FD49B54652d0p0 directly as xvda to > domU so the domU has a full disk to partition on its own.
It depends more on your preferences, actually. You could map a file (.img, .vmdk, whatever), a zvol, a disk, or a partition as domU's disk or partition. So mapping /dev/dsk/c0t600A0B800049E902000007FD49B54652d0p0 as xvda1 should work as well. But that would somewhat limit scalability since xvda1 will be limited to that size (i.e. you can't grow it), which is why I prefer to use zvol (on opensolaris) or LVM (on Linux). pygrub can work with block devices mapped as disk (xvda) or partition (xvda1), so I'm curious why you're experiencing problem. > >> Does your domU has /boot/grub/menu.lst? AFAIK as long as that file is > I have a /boot/grub/grub.conf Try symlink it to menu.lst. Should work. > I have no initrd (isn't needed normally) So I take it you're not using RHEL/Centos or Debian/Ubuntu domU, or you're building your own kernel? By default those systems need initrd to boot correctly. >From pygrub's perspective it doesn't really matter though, it can work with or without initrd. Regards, Fajar _______________________________________________ xen-discuss mailing list [email protected]
