qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] International Virtualization Conference
Date: Tue, 10 Oct 2006 13:18:10 -0400	[thread overview]
Message-ID: <20061010171809.GA27303@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200610101148.34187.rob@landley.net>

On Tue, Oct 10, 2006 at 11:48:33AM -0400, Rob Landley wrote:
> > Here you are using the terms "virtual" and "emulated" interchangably. That's
> > ok as long as the difference between virtualization and virtual/emulated is
> > understood. 
> 
> Well, the hardware people see a huge difference.  To them one is "doing it in 
> hardware" and the other is "doing it in software".
> 

That is not how he uses the terms. He uses them interchangably.

I was just trying to make clear the difference between emulation and virtualization.

> 
> > If I follow your logic, then bochs is also a good canidate for the workshop.
> 
> If you mean the way Hurd is a candidate for a workshop anywhere Linux is, 
> sure.

I was trying to say that qemu (sans kqemu) is a bad candidate. Someone else explains the virtualization-vs-emulation thing much better than I could (short answer: VMware, kqemu, and other virtualizers do it in the hardware whie emulators like qemu and bochs do fully it in the software).

>  If it's a purely academic conference where being useful doesn't enter 
> into it.  (I followed Bochs and Plex86 5 years ago, but could never actually 
> get them to do anything useful despite repeated attempts.  Still haven't, 
> although I see Bochs is back from the dead...)

Someone else pointed it out was more a corporate marketing gig. *shrug*.

> 
> > -- 
> 
> And I'm sorry, but I find your tagline actively wrong:
> 
> > Infinite complexity begets infinite beauty.
> 
> It begets "unmaintainable" after about 5 minutes.
> 

Natural complexity not human-made complexity :)

Think fractals here. Or those pretty pictures we get when looking at subatomic particles.

> > Infinite precision begets infinite perfection.
> 
> You've never been micro-managed, have you?
> 

Really not what I was referring to. :P

> "Perfection is reached, not when there is no longer anything to add, but when 
> there is no longer anything to take away."
>  - Antoine de Saint-Exupery

I agree.

> 
> Rob
> -- 
> "Perfection is reached, not when there is no longer anything to add, but when 
> there is no longer anything to take away." - Antoine de Saint-Exupery
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2006-10-10 17:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-08 12:30 [Qemu-devel] International Virtualization Conference Ottavio Caruso
2006-10-08 14:36 ` Jim C. Brown
2006-10-08 15:35   ` Joshua Root
2006-10-08 16:58   ` Jamie Lokier
2006-10-08 23:35     ` Jim C. Brown
2006-10-09  4:05   ` Rob Landley
2006-10-09 12:08     ` Jim C. Brown
2006-10-10 15:48       ` Rob Landley
2006-10-10 17:18         ` Jim C. Brown [this message]
2006-10-11  2:03           ` Rob Landley
2006-10-11  2:54             ` Jim C. Brown
2006-10-10  9:26     ` Joshua Root
2006-10-10 15:54       ` Rob Landley
2006-10-10 17:23         ` Jim C. Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061010171809.GA27303@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).