Hi folks, I set up Xen on a freshly-installed FC5 system, configured the guest using xenguest-install.py and then began an installation via VNC. However, as soon as I got to the partitioning phase I received an error that the partition table for my disk couldn''t be read. I opted to ignore this as I''ve seen that error even on real systems and have proceeded without incident. However, the installer continued to produce errors about not being able to find the disk, being unable to read the partition table, etc and eventually just died. Looking at the disk file I told Xen to create (I gave it 4096 as the size) it appears to have a size of 0. Is that the way it should be? Any further advice for troubleshooting? Thanks, --Brad
Hi, On Thu, 2006-03-30 at 07:14 -0500, Brad Smith wrote:> I set up Xen on a freshly-installed FC5 system, configured the guest using xenguest-install.py and > then began an installation via VNC. However, as soon as I got to the partitioning phase I received > an error that the partition table for my disk couldn''t be read. I opted to ignore this as I''ve seen > that error even on real systems and have proceeded without incident. However, the installer > continued to produce errors about not being able to find the disk, being unable to read the > partition table, etc and eventually just died. Looking at the disk file I told Xen to create (I gave > it 4096 as the size) it appears to have a size of 0. Is that the way it should be?No! The disk size is specified in GB, though, so you just asked for a 4TB file, which is beyond ext3''s tiny little brains. Try something a little smaller. :-) Yes, we should deal with this error better. --Stephen
"Stephen C. Tweedie" <sct@redhat.com> wrote: ...> No! The disk size is specified in GB, though, so you just asked for a > 4TB file, which is beyond ext3''s tiny little brains. Try something a > little smaller. :-) > > Yes, we should deal with this error better.One way to avoid the problem is to require a suffix on the size arguments, e.g. 2.6GB, 3200MiB, etc. Then there''s no possibility for confusion.