I'm just wondering if anyone has done this and gotten a guest OS up and running, and if so, could you direct me to a good how-to on this?

I tried earlier today, and I just could not get the guest OS to boot up after it had completed its installation. It got to the anaconda part that says "okay to reboot," then just shut down my VNC window and that was the last that I heard of it. So I tried to reboot my own system, and suddenly the partition on which I had installed the guest OS (/free , a standard ext3 partition that I had free) was not responding to a shutdown (it was busy), and apparently it was mislabeled somehow, because I could not boot up. It would send me to the useless "repair filesystem" command prompt. I was so desperate that I had to load up a Knoppix LiveCD and reformat that /free partition, which helped me to be able to boot into my regular Linux install.

So anyway, upon booting into my FC5 after this process, I was informed that my / (root) partition was low on space. I'm going to post some other threads on this, because it looks like two seperate problems. Anyway, I have a symlink called "core" in the /dev directory that says it's 856MB large. It says it's a link to a bug report, but I can't start it up with bug-buddy (the program that it wants to start it up). I researched this, and it looks like this is a symlink to /proc/kcore, which is my system memory....neat. So I don't know if this is a new problem....that I have an 856MB link in /dev. I don't know know if it was there before, but SOMETHING new is taking up my disk.

Also, my /var/cache/yum file is full of 908MB of junk. I've run "yum clean all," and it doesn't want to detect much of anything. It looks like the files there were created during the time that I was running the Xen install, but I don't know why they're on my / root partition. Also, I thought I downloaded about 1.7GB of stuff, not about 908MB. Anyway, I'm posting a different thread on this, but is it alright to just delete these files? I don't see any real use for them, and I need that space back.

Finally, third is there a way to tell how much of my disk was used up before I started messing around with Xen? Thank you!

Okay, good news. I'm doing another Xen install, and it looks like it IS in fact Xen that loaded up my yum/cache the way that it did. It's now going to that cache instead of trying to download a bunch of files. That's very good news to me, because I thought I had a problem.

I'm going to post a link to the site that I'm following for the Xen instructions. I can't do it now, because I need 3 posts until I can post a link.... =)

I still want to know about the /dev/core file that says it's a link to crash information. Apparently it's a symlink to /proc/kcore, which is my main system memory, but I've never seen it before, and it says it's 843MB (/proc/kcore is 940MB, my system has 1024MB, so there's some lame descrepency there...)

Anyway, one more post until I can give the Xen instructions.

Now, I've done these several times, but things kept cropping up. Actually, the first time, I used a very, VERY slow place to download the OS, and it seemed like it locked up. I've since used a different one (http://mirror.linux.duke.edu/pub/fed...re/5/i386/os/), and it's made a world of difference. It's actually running so fast right now that I might be wrong about saying it's using those cached files....arg. I hope it cleans up after itself this time.

Xen install instructions: http://fedoraproject.org/wiki/FedoraXenQuickstartFC5

Alright, and update on my situation...apparently the Xen guest install did not fill up my yum cache. I have no idea how it happened, now. I also have no idea why "yum clean all" does not find them. I'll probably post a new thread on this on this later, but not right now (I'm actually napping)

Also, the darn repository must have slowed down, because it's now taking a while to download the files. Oh well. Done in 110 minutes, I guess.