Since your xdi file is mounted loop and formatted ext3, it isn't partitioned, so hda1 is probably the way to go. It won't hurt to try it as hda instead of hda1, but I don't expect that to help. Good luck determining your new problem. Downloading a xen-ready fedora image from someone might be what it takes to fix it, though, something from your real / filesystm might not be compatible with the paravirtualized environment and might be trying to access things that don't exist in said environment. I am not sure on that, but if documentation suggested it, I would think it would work. Dustin -----Original Message----- From: fedora-xen-bounces@xxxxxxxxxx [mailto:fedora-xen-bounces@xxxxxxxxxx] On Behalf Of Guillaume Sent: Friday, October 26, 2007 12:31 To: fedora-xen@xxxxxxxxxx Subject: Re: Re: problem creating my 1st VM > In the e-mail I just sent, I showed an example for using initrd. > Try that. Sorry, but I just get your message after I mine :) I try your tips, and it seems to work... The initrd image is loaded and... I have a new error message. I'll investigate on it asap, but for this week its over :) >However, the virtual hda should not be detected as a generic scsi > device, it should be detected as a generic ide device. A virtual sda might > be detected as a scsi device, but I don't know if you can even do that in a > paravirtualized environment (I think you can in an HVM, but the virtual BIOS > won't boot to a scsi device in that situation). I'll try the "hda option" next time. For information about my xdi file, i create it with dd, mount it as a loop device, format it with ext3 FS and after copy my "/" on it. I choose use xdi extension on my own, but its stand for "Xen Disk Image". Its not related with any other ext. Bye :) -- Guillaume -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
