On Wed, Feb 28, 2007 at 01:06:24PM -0500, taoj2@xxxxxxxxxx wrote: > Hi, > > Thank you guys a lot. > > This time I didn't create the file manually. Just Let the virt-manager to > do this. First, I try to use /home/jane/xen/box1, but it failed. > > So according to Dan's suggestion, I use /var/lib/xen/images/box1 as the > storage location of guest OS. > > But why this file has to be under /var/lib/xen/images rather than /home? I > didn't realize this problem when I was intalling the guesting OS before. > Only /var/lib/xen/images is a valid directoy? Is there any other valid > directory? Yes, it has to be in that directoy to comply with the SELinux security policy - we don't want to let XenD write all over the disk. > And I found another problem even if I use /var/lib/xen/images/box1 : > > "The partition table on device xvda was unreachable. To create new > partitions it must be initialized, causing the loss of All Data on this > drive. This opeartion will override any previous installation choices > about which drives to ignore. Would you like to initialize this drive, > erasing ALL DATA? > " > > So this means each time I want to install an guest OS, I have to create > new partition? It seems not good. :( This is completely expected & normal behaviour. The '/var/lib/xen/image/box1' file in the host, is exposed to the guest as a *disk*. So anaconda sees this disk and wants to partition it - this is same thing you'd see if running anaconda on a bare-metal machine with a brandnew harddisk which hadn't been partitioned before. Simply say 'yes', and it'll create the neccessary bits. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
