[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] disk images & driver geometry

From: Daniel P. Berrange
Subject: Re: [Qemu-devel] disk images & driver geometry
Date: Fri, 31 Aug 2007 20:07:04 +0100
User-agent: Mutt/1.4.1i

On Fri, Aug 31, 2007 at 03:09:19PM -0400, Christopher Friedt wrote:
> Anthony Liguori wrote:
> >I have no idea what you're talking about.  QEMU doesn't care whether you 
> >use a physical disk or a file.  It handles geometry the same way.
> >
> >Is there a concrete example that doesn't work that you think should?
> Yes, a simple example is running CentOS after a typical install from a 
> hard disk image.
> If Qemu is started with the installation cdrom (-cdrom CentOS-1of4*.iso) 
> the installation creates several partitions on the virtual disk, 
> including /boot, and a logical disk containing /. The first 512 Bytes of 
> the disk image are assumed to be the MBR of the disk, which is where the 
> installation will write the boot loader.
> After installation, qemu is started with
> qemu -hda centos.img -boot c

That scenario works just fine for me when I try it with either  RHEL-5
or Fedora Core 6 / 7. QEMU reads the MBR from the disk I pass with -hda, 
whether that's backed by a physical device, or a file backed disk & will
succesfully boot the OS.  I just followed the recommended partitioning
scheme that RHEL-5 installer suggests making no changes.

|=- 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  -=| 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]