Yes, it is a dup. Sorry for the noise.
On Tue, Jul 18, 2017 at 9:03 PM, Eric Blake wrote:
> On 07/18/2017 07:58 PM, Nathaniel McCallum wrote:
>> Glibc used to have:
>>
>>typedef struct ucontext { ... } ucontext_t;
>>
>> Glibc now has:
>>
>>
ly use the standardized type name.
Signed-off-by: Nathaniel McCallum
---
linux-user/host/aarch64/hostdep.h | 2 +-
linux-user/host/arm/hostdep.h | 2 +-
linux-user/host/i386/hostdep.h| 2 +-
linux-user/host/ppc64/hostdep.h | 2 +-
linux-user/host/s390x/hostdep.h | 2 +-
linux-user/h
"-boot d" == "Boot off of drive 'd', aka the cdrom"
Nathaniel
On Wed, 2006-07-05 at 22:19 +0100, Daniel Carrera wrote:
> On Wed, 2006-05-07 at 17:12 -0400, Nathaniel McCallum wrote:
> > A person who is in your position (frustrated for lack of documentation)
A person who is in your position (frustrated for lack of documentation)
is actually the most qualified person to write documentation. Feel free
to ask any questions you have on this list.
Nathaniel
On Wed, 2006-07-05 at 21:57 +0100, Daniel Carrera wrote:
> Hello,
>
> I write here because there
On Tue, 2006-07-04 at 11:23 +0200, Fabrice Bellard wrote:
> Hi,
>
> I am not sure it is interesting to store the configuration of the VM in
> the disk image (there can be several disk images for a given VM).
> Moreover, extensions to the qcow header must be added at its end.
Storing the config
Mark's notes on the qcow format got me to thinking how useful it would
be to be able to store other information in the qcow image itself. For
instance you could store the configuration for the virtual machine in
the image which could be extracted and then start the virtual machine.
So... I'm prop
