From: Zachary Amsden <zach@vmware.com>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [para-list] Paravirt-ops success
Date: Fri, 25 Aug 2006 13:40:11 -0700 [thread overview]
Message-ID: <44EF602B.2010708@vmware.com> (raw)
In-Reply-To: <44EE751D.506@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Zachary Amsden wrote:
> Zachary Amsden wrote:
>> I booted into X11 and have networking working and a kernel compile
>> running. SMP and PAE should be less than a day away. This completes
>> the proof of concept, I believe ;)
>>
>> I didn't cc LKML since I didn't want to spam them with graphics.
>> Very controversial graphics. Hopefully you appreciate the humor.
>>
>
> Now to outdo my last graphics shot. Paravirt-ops with SMP working.
> And some very controversial artwork for a group of three different
> hypervisors. Since the blue pill thing is popular recently, I thought
> I'd leave a subtle reference to it on the desktop.
>
> Zach
And even further. Now paravirt-ops works with SMP + PAE mode. My
machine has reached enlightenment.
Zach
[-- Attachment #2: paravirt-ops-pae-smp.jpg --]
[-- Type: image/jpeg, Size: 151437 bytes --]
[-- Attachment #3: Type: text/plain, Size: 165 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2006-08-25 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 23:53 Paravirt-ops success Zachary Amsden
2006-08-25 0:06 ` Nivedita Singhvi
2006-08-25 3:57 ` [para-list] " Zachary Amsden
2006-08-25 20:40 ` Zachary Amsden [this message]
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=44EF602B.2010708@vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.