Sure enough the netboot/xen directory is not there, although it is
present in the i386 directory. I modified the config file to pull my
local kernel (/boot/vmlinuz-2.6.26-2-xen-amd64), but that hung when I
tried to install. So I changed the cfg file to pull the ramfs and the
kernel from the following path:
ftp://ftp.us.debian.org/debian/dists/lenny/main/installer-amd64/current/images/cdrom/
Also with no success (invalid kernel).
Why is there no xen directory under netboot?I had read that the same
kernel was needed on both Dom0 and a DomU for pci pass through to work,
and that's how I set it up successfully on my x86 machine. Is this
correct for the amd64 kernel or can I pass a device through with the 686
kernel in the DomU?
I looked into using xen-tools, but it seems you cannot create a DomU in
a physical partition. I suppose I could create an image and dd it over,
but I would hope there is a better way.
Thanks for any feedback,
Dan
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
According to the 'xen-create-image' manpage, "--image-dev" is
"Specify a physical/logical volume for the disk image.". I havent tried it
myself (because I love lvm), but it sounds like you can use a physical disk
for the root image with xen-tools.
Cheers,
Tyler
--