Re: [9fans] Vmware playground but in qemu.

["Lluís Batlle i Rossell" <viriketo@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2850 bytes --]

Gabriel Diaz wrote:
> Hello
>
> I made that page, but i think i deleted it. It isn't complete and someone
> told me is not useful at all as it describes what i have done to play
> and not
> something of "general interest".
Aha, I understand. Well, I didn't plan to make something of "general
interest", but having a quite-ready handful of plan9 machines, although
virtual, has been quite good for a new 'user' like me.

>     Among my many unsuccesful tries to get everything done as described in
>     the wiki, it was dark for me the "Set up the nvram", because I thought I
>     should write the lines suggested into the nvram partition. And I also
>     expected that to work, so the rebooting's "error in nvram key" made
>     me mad.
> i created an nvram partition on each virtual machine that booted from
> network.
> On the first  boot, nvram will not be found, so, i created an nvram
> partition
> and boot again, this time, nvram was found, but with no valid contents, so
> plan9 asked again about auth domain and authid. But this time, it saved the
> information, so the next boot, the third, worked fine.
I couldn't boot the machine, if I didn't have any nvram partition. It
hanged. And I could not create the plan9 nvram partition, if I could not
boot. That's why I needed the floppy file - a nvram (yes, with incorrect
content at first) for at least booting and creating the partition in the hd.

>     There are other details that I didn't understood at first from the wiki
>     page, but it would be too a matter of opinion. As an example: what's
>     "First boot"? Should I reboot? As 'bootes'?
> When installing a cpu standalone server you should reboot to use the new
> kernel,
> that is the "first boot" thing. Pointers to setting up standalone cpu
> server should be
> included in the page.
Aha. Well, I coped with it, but it wasn't fairly simply for someone who
has never set up a cpu server. :)
> If you found that page useful please consider putting your comments and
> experiences
> with qemu to make the page complete. And fix the erroneous bits.
I'd like to write about 'qemu', but I feel I should have at least tried
the vmware-way for writting something clear to understand. Even more...
what should I say there about the ether2000.c part? "Please update your
ether2000.c with [link to the new ether2000.c in some way] this one to
get 9pxeload working in qemu"? I feel that would be strange. I'll keep
waiting for some comments on the new ether2000.c - maybe someone can put
that into sources (given someone takes a revision), and then it would be
easier to write the wiki page.
>
> email me if you can't update it and i will try to fix the page.
I've tried with acme, and I think I can write to the wiki. Whether I can
fix or not the page, that's another topic. :)

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3311 bytes --]