diff options
Diffstat (limited to 'hurd/running/qemu')
| -rw-r--r-- | hurd/running/qemu/babhurd_image.mdwn | 67 | ||||
| -rw-r--r-- | hurd/running/qemu/discussion.mdwn | 144 | ||||
| -rw-r--r-- | hurd/running/qemu/image_for_l4.mdwn | 376 | ||||
| -rw-r--r-- | hurd/running/qemu/microsoft_windows.mdwn | 52 | ||||
| -rw-r--r-- | hurd/running/qemu/networking.mdwn | 43 | ||||
| -rw-r--r-- | hurd/running/qemu/networking/sharing_files.mdwn | 38 |
6 files changed, 0 insertions, 720 deletions
diff --git a/hurd/running/qemu/babhurd_image.mdwn b/hurd/running/qemu/babhurd_image.mdwn deleted file mode 100644 index c0952fcf..00000000 --- a/hurd/running/qemu/babhurd_image.mdwn +++ /dev/null @@ -1,67 +0,0 @@ -What this little Hurd image can do ----------------------------------- - -### About this text - -This is the README file accompanying a -[disk\_image](http://draketo.de/dateien/hurd/bab-hurd-qemu-2008-10-29.img.tar.bz2) for -[[running_the_GNU/Hurd_via_qemu|hurd/running/qemu]]. To run the disk image, just use *'qemu -disk_image.img'*. - -You can find the custom *.bashrc* used to tell the user about it as well as this text itself -in the Mercurial repository [hurd_intro](http://bitbucket.org/ArneBab/hurd_intro). - -### Intro - -The Hurd has some unique capabilities, and we created this simple image -to enable you to easily try two of them: - -* The simplest of translators: Hello World! -* Transparent FTP - -### Hello World - -To try out the simplest of translators, you can go the following simple steps: - - $ cat hello - $ setrans hello /hurd/hello - $ cat hello - "Hello World!" - $ settrans -g hello - $ cat hello - -What you do with these steps is first verifying that the file "hello" is empty. - -Then you setup the translator /hurd/hello in the file/node hello. - -After that you check the contents of the file, and the translator returns "Hello World!". - -To finish it, you tell the translator to go away from the file "hello" via "settrans -g hello" and verify that now the file is empty again. - -### Transparent FTP - -We already setup a a transparent FTP translator for you at /ftp: - -With it you can easily access public FTP via the file system, for example the one from the GNU project: - - $ ls /ftp://ftp.gnu.org/ - -But you can also do this very easily yourself: - - $ # Setup the translator on the node ftp: - $ settrans -c ftp: /hurd/hostmux /hurd/ftpfs / - -and you can access FTP sites via the pseudo-directory ftp:, for example with - - $ ls ftp://ftp.gnu.org/ - -What you do here is setting up the translator /hurd/hostmux on ftp: and passing it the translator /hurd/ftpfs to use for resolving accesses as well as / as additional path component. - - -These were only two basic usages of translators on the Hurd. We're sure you'll quickly see many other ways to use this. - -As a last comment: You can setup a translator on any node you have access to, so you can for example mount any filesystems as normal user. - -You might currently be logged in as root, but you could just as well do the same as normal user. - -Why don't you try it out? diff --git a/hurd/running/qemu/discussion.mdwn b/hurd/running/qemu/discussion.mdwn deleted file mode 100644 index 1ce14b01..00000000 --- a/hurd/running/qemu/discussion.mdwn +++ /dev/null @@ -1,144 +0,0 @@ -[[!meta copyright="Copyright © 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free -Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!tag open_issue_documentation]] - -# Using Partitions - -[[IRC]], #hurd, 2007-07-04. - - <azeem-uni> so, is there a way to use a Debian GNU/Hurd partition - (/dev/hda6) with qemu directly? - <tschwinge> Don't dare to do that, please. - <tschwinge> It will lead to inconsistencies. - <tschwinge> Because the Linux kernel thinks that it has complete control - over the disk, or something. - <tschwinge> In theory you could run something like ``-hda /dev/hda'', - having GRUB installed on there to offer you to boot your Hurd system from - hda6 and that will even work, but then don't get the idea to stop qemu, - mount that partition on your Linux system and restart qemu. That's where - I got lots of inconsistencies then, afterwards. - <azeem-uni> it's probably the same problem as having that partition - mounted, suspending to disk, booting into it in the Hurd, and resume - Linux - <neal> right - <tschwinge> That's a different problem. - <tschwinge> Then the partitoon is still mounted. - <neal> no, I think it is basically the same problem - <tschwinge> The file system stuff is cached in the kernel. - <neal> you have data that has not been written to disk yet - <tschwinge> Right. - <neal> and neither is prepared for the resource to be shared - <tschwinge> In the azeem-uni scenarion the data is on the file system layer - and in my scenarion it's some disk block caching inside the Linux kernel, - I guess. - <azeem-uni> anyway, do you guys think if I use -hda /dev/hda and tell Grub - to boot off /dev/hda6, that the rest of hda should be fine, right? - <azeem-uni> maybe adding -snapshot makes it totally safe - <neal> azeem: Should be fine. - <tschwinge> Yes. - -The problem is actually that the linux block cache doesn't make any consistency -between /dev/hda and /dev/hda6, so if you give /dev/hda to qemu, qemu writings -won't be consistent with mounting /dev/hda6 in linux. You can give /dev/hda6 -directly to qemu and it will be fine. - - -# Host-side Writeback Caching - -IRC, freenode, #hurd, 2011-06-07 - - <braunr> hm, i guess i should have used cache=writeback with kvm before - starting the debian installer :/ - <braunr> ah yes, much better - <braunr> this shows how poor the state of our I/O drivers and subsystem is - :/ - <antrik> indeed... still no clustered pageout :-( - <braunr> and no I/O scheduler either - <braunr> although an I/O scheduler has limited value without clustered - pageouts - <braunr> since one of its goals is to pack related I/O requests together eh - <braunr> i wonder if the wiki mentions using cache=writeback to speed up - qemu performances - <braunr> it would help those unable to use kvm a lot - <braunr> and even those running kvm too - <braunr> kvm -m $RAM \ -monitor stdio \ -drive - cache=writeback,index=0,media=disk,file=hd0.img \ - <braunr> etc.. - <braunr> the idea is that qemu doesn't open its disk file synchronously - <braunr> changes are queued in the host page cache before being flushed to - the disk image - <braunr> but if you brutally close your qemu instance, you're likely to - loose file system consistency - <braunr> ext2fs will think it has committed its metadata to the disk, but - the disk image won't be updated synchronously - <braunr> on my machine (which is quite fast), my kvm has installed debian - like 10 times faster than without the option - <antrik> braunr: I don't think killing qemu should hurt in this - case... probably only matters when the host machine dies - <braunr> antrik: ah yes, right - <braunr> it really makes everything faster, even downloading, since I/O - requests aren't interleaved between networking RPCs - <antrik> regarding I/O sheduler... this discussion came up before, but I - don't remember the outcome -- doesn't the glued Linux driver actually - come with one? - <braunr> i don't remember either - <antrik> braunr: err... I don't think interleaving has anything to do with - it... I guess it's simply the fact that downloading writes the result to - disk, which suffers from lacking clustered pageout like everything else - <antrik> (my internet connection is too slow though to notice :-) ) - <braunr> well, if there is no I/O during downloading, downloading is faster - :) - -IRC, freenode, #hurd, 2011-06-08 - - <braunr> youpi: does xen provide disk caching options ? - <youpi> through a blktap, probably - <braunr> ok - -([[microkernel/mach/gnumach/ports/Xen]], *Host-side Writeback Caching*.) - - <braunr> we should find the pages mentioning qemu on the wiki and add the - options to enable disk image caching - <braunr> it really makes the hurd run a lot faster - <braunr> as a workaround for emulators until I/O is reworked, ofc - -IRC, freenode, #hurd, 2011-06-09 - - <gnu_srs> braunr recommends to use writeback caching with kvm. Is this - really recommended with the frequent crashes I experience? - <youpi> provided that you terminate your kvm normaly (i.e. quitting it, not - killing it), there should be no difference - <jkoenig> I think the host's stability is what matters - <jkoenig> the data presumably sits in linux's cache even if qemu dies - violently - <gnu_srs> But the freezes I see force me to kill kvm :-( - <youpi> maybe kvm doesn't even do caching indeed, I don't know - <youpi> gnu_srs: you can quit even when frozen - <youpi> use the console - <youpi> (the kvm console) - <jkoenig> gnu_srs, "Writeback caching will report data writes as completed - as soon as the data is present in the host page cache. This is safe as - long as you trust your host. If your host crashes or loses power, then - the guest may experience data corruption." (from the qemu manpage) - -IRC, freenode, #hurd, 2011-06-11 - - <gnu_srs> braunr: If you are online. For me setting the parameters -drive - cache=writeback,index=0,media=disk,file=hd0.img does not show any speed - improvement at all compared to the default. - <braunr> gnu_srs: what's your complete qemu command line ? - <gnu_srs> kvm -m 1024 -net nic,model=rtl8139 -net - user,hostfwd=tcp::5556-:22 -drive - cache=writeback,index=0,media=disk,file=hd0.img -cdrom netinst.iso - <braunr> what qemu version ? - <gnu_srs> qemu-kvm 0.14.1+dfsg-1: Sorry, I cannot be online until - tomorrow again. diff --git a/hurd/running/qemu/image_for_l4.mdwn b/hurd/running/qemu/image_for_l4.mdwn deleted file mode 100644 index 515f51bc..00000000 --- a/hurd/running/qemu/image_for_l4.mdwn +++ /dev/null @@ -1,376 +0,0 @@ -This page is initially taken from <http://perso.ens-lyon.fr/alexandre.buisse/hurd.html> with the following signature: - -> 04-02-2005 Alexandre Buisse -> -> Send any comments or ameliorations to <Nattfodd@gmailNOSPAM.com> - ----- - -This is a howto on how to get a working image of Hurd/L4 with qemu, on ia32 arch. - -# <a name="1_Floppy_image"> 1. Floppy image </a> - -You will need the following : - -* automake 1.7 (or greater) -* autoconf 2.53 (or greater) -* grub -* the CVS version of hurd-l4, which you can retrieve from the savannah server: `cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co hurd-l4` -* two flavours of Pistachio, the L4 kernel, which can be found at <http://www.l4ka.org/projects/pistachio/download.php>. Take the demodisk for ia32 (`pistachio-ia32-0.4-demodisk.bin.bz2`), we'll checkout the CVS later (the 0.4 tarball isn't recent enough). - -We will begin with the hurd itself (these steps are taken from the `README`). - - $ cd hurd-l4 - $ autoreconf -f -i -s - -You shouldn't have any warnings with this autoreconf. If that is not the case, it probably hasn't used the good version of automake or autoconf. For instance, on Gentoo Linux, you must set WANT\_AUTOCONF to 2.5 and WANT\_AUTOMAKE to 1.7. - - $ ./configure --enable-maintainer-mode --prefix=/l4 - $ make - $ make install - $ mkdir /l4/boot - $ install -s laden/laden /l4/boot - $ install -s wortel/wortel /l4/boot - $ install -s physmem/physmem /l4/boot - $ install -s task/task /l4/boot - $ install -s deva/deva /l4/boot - $ install -s ruth/ruth /l4/boot - -Now we'll prepare the Pistachio kernel : - - $ cd .. - $ cvs -d:pserver:guest:guest@cvs.l4ka.org:/public-cvs login - $ cvs -z3 -d:pserver:guest@cvs.l4ka.org:/public-cvs co pistachio - $ cd pistachio - -We must apply some patchs for it to work properly with The Hurd. They are located in `hurd-l4/README`: - - $ patch -p1 < ../hurd-l4/README - -We will first compile sigma0 (and some other tools) : - - $ cd user - $ autoreconf -f -i -s - $ mkdir BUILDDIR - $ cd BUILDDIR - -We need to change the linkbase of sigma0 : - - $ ../configure --with-s0-linkbase=0x40000 --prefix=/l4 - $ make - $ make install - -And now the kernel itself : - - $ cd ../../kernel - -You can use any builddir as long as the directory doesn't yet exist. - - $ make BUILDDIR=/tmp/pistachio-build - $ cd /tmp/pistachio-build - $ vi Makeconf.local - -You should modify the first three lines to : - - ARCH=ia32 - CPU=i586 - PLATFORM=pc99 - -now run: - - $ make menuconfig - -Set the options as they fit you but for qemu to work, you must have the following hardware : - - IA32 Basic Architecture - Pentium1 Processor Type - -You can now: - - $ make - -You should obtain a file named ia32-kernel into your build directory. - - $ cp ia32-kernel /l4/boot - $ cp /l4/libexec/l4/sigma0 /l4/boot - -We now have to modify a little bit the demodisk to use the kernel and servers we just obtained : - - $ mkdir qemu - $ mkdir qemu/image - $ cd qemu - $ cp ~/pistachio-ia32-0.4-demodisk.bin.bz2 . - $ bunzip2 pistachio-ia32-0.4-demodisk.bin.bz2 - $ mount -o loop pistachio-ia32-0.4-demodisk.bin image - $ cd image/boot - $ cp /l4/boot/* . - $ cd grub - $ vi menu.lst - -Your should edit `menu.lst` to make it look like : - - title GNU Hurd on L4 - kernel /boot/laden -D -o serial,uart1,speed=9600 - module /boot/ia32-kernel - module /boot/sigma0 - module /boot/wortel -D -o serial,uart1,speed=9600 - module /boot/physmem - module /boot/task - module /boot/deva - module /boot/task - module /boot/ruth - -The two -D are intended for debug, you can delete them if you want. It is possible that filenames are limited to 8 characters, check your image/boot directory for ia32-kernel. If it has been renamed into ia32-ker, modify the according line in menu.lst - -When you start qemu, you will have two windows : the shell from which you launched it and a VGA window. You can interact with L4 in both windows (switching with the `config/console` command in the debugger). You can choose to have wortel and laden output to the serial device (the shell), which is default behaviour, or to VGA (change `-o serial,urt1,speed=9600` by `-o vga` in your menu.lst). - -The image is now ready : - - $ cd ../../../ - $ umount image - -We can launch qemu: - - $ qemu -dummy-net -serial stdio -fda pistachio-ia32-0.4-demodisk.bin -boot a - -Congratulations, you just booted Hurd/L4 ! To start the Kernel Debugger, press `ESC`. To switch the KDB mode from character (I find it unusable) to command line, type - - > c - /conf> m - -# <a name="2_Disk_Image"> 2. Disk Image </a> - -Everything went fine, and Hurd/L4 should have shown you a nice boot on our floppy image. Our next step will be to make banner run and show us its nice ASCII Art on this brand new OS. - -However, there is one problem : banner linked with the libc weights about 6MB, and we only have a 1.44MB floppy. We will then begin with making an image of a whole hard disk instead of a simple floppy. - -We still will work with qemu, of course, but we'll also use Bochs to install Grub on the image (I have not yet tried with qemu). - -To begin with, some mathematics. We'll make a 30MB image but you can adapt this value to your need. A disk is made of heads, cylinders and sectors (we won't go in detail about what these really mean). A sector has a constant size of 512 bytes and there are at most 255 heads and 63 sectors. The total size of a disk is C \* H \* S \* 512. We'll use the maximum capacity for S and 16 sectors and that will give us how much cylinders we need : C = E(30,000,000 / (16 \* 63 \* 512)) = 58. The exact size of our image will then be : 58 \* 16 \* 63 \* 512 = 29,933,568 bytes and we will have 58 \* 16 \* 63 = 58464 pieces of 512 bytes. - -Let's create it : we use the magic command `dd` on the special device which contain an infinity of 0. - - $ dd if=/dev/zero of=hurd_l4.img bs=512 count=58464 - 58464+0 records in - 58464+0 records out - -We will mount it in loopback : - - $ losetup /dev/loop0 hurd_l4.img - -We need now to have it recognized as a hard disk : - - $ fdisk -u -C58 -S63 -H16 /dev/loop0 - Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel - Building a new DOS disklabel. Changes will remain in memory only, - until you decide to write them. After that, of course, the previous - content won't be recoverable. - - Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) - - Command (m for help): - -We should create a new primary partition (press: `'n'`, `'p'`, `'1'`, default, default) and toggle it bootable (`'a'`, `'1'`). Now, if you press `'p'`, you should see something like : - - Command (m for help): p - - Disk /dev/loop0: 29 MB, 29933568 bytes - 16 heads, 63 sectors/track, 58 cylinders, total 58464 sectors - Units = sectors of 1 * 512 = 512 bytes - - Device Boot Start End Blocks Id System - /dev/loop0p1 * 63 58463 29200+ 83 Linux - -If everything is fine (especially check the `Start` and `End` fields), you can press `'w'` to write the table on the disk: - - Command (m for help): w - The partition table has been altered! - - Calling ioctl() to re-read partition table. - - WARNING: Re-reading the partition table failed with error 22: Invalid argument. - The kernel still uses the old table. - The new table will be used at the next reboot. - Syncing disks. - -You will have noticed that the partition only starts at the 63rd sector. The beginning of the disk contains the MBR which is used for booting. We must then remount the disk making sure that this part is skipped before formating it. We know that a sector uses 512 bytes so we should begin at 63 \* 512 = 32256 : - - $ losetup -d /dev/loop0 - $ losetup -o32256 /dev/loop0 hurd_l4.img - -Now comes time to format it into a decent filesystem : - - $ mke2fs /dev/loop0 - mke2fs 1.35 (28-Feb-2004) - Filesystem label= - OS type: Linux - Block size=1024 (log=0) - Fragment size=1024 (log=0) - 7328 inodes, 29200 blocks - 1460 blocks (5.00%) reserved for the super user - First data block=1 - 4 block groups - 8192 blocks per group, 8192 fragments per group - 1832 inodes per group - Superblock backups stored on blocks: - 8193, 24577 - - Writing inode tables: done - Writing superblocks and filesystem accounting information: done - - This filesystem will be automatically checked every 22 mounts or - 180 days, whichever comes first. Use tune2fs -c or -i to override. - -We should now be able to mount it the right way : - - $ mkdir mnt - $ losetup -d /dev/loop0 - $ mount -o loop,offset=32256 hurd_l4.img mnt/ - -Here comes grub time (I assume you have the grub files in `/boot/grub` and the `menu.lst` we've obtained in the previous section is in `~/`) : - - $ mkdir -p mnt/boot/grub - $ cp /boot/grub/stage1 /boot/grub/stage2 /boot/grub/e2fs_stage1_5 mnt/boot/grub/ - $ cp ~/menu.lst mnt/boot/grub - -We will make a grub bootimage and boot it with bochs : - - $ cat stage1 stage2 > grubboot.img - -Copy the following into `.bochsrc` (replace the parts in caps by the right info) : - - config_interface: textconfig - display_library: x - romimage: file=/usr/share/bochs/BIOS-bochs-latest, address=0xf0000 - megs: 32 - vgaromimage: /usr/share/bochs/VGABIOS-elpin-2.40 - floppya: 1_44=PATH_TO_YOUR_GRUBBOOT_IMAGE, status=inserted - ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14 - ata1: enabled=0, ioaddr1=0x170, ioaddr2=0x370, irq=15 - ata0-master: type=disk, path="PATH_TO_YOUR_DISK_IMAGE", cylinders=NUMBER_OF_CYLINDERS, heads=16, spt=63 - newharddrivesupport: enabled=1 - boot: a - - log: /dev/stdout - panic: action=ask - error: action=report - info: action=report - debug: action=ignore - debugger_log: - - com1: enabled=1, dev=/dev/ttyS0 - vga_update_interval: 300000 - keyboard_serial_delay: 250 - keyboard_paste_delay: 100000 - floppy_command_delay: 500 - ips: 1000000 - mouse: enabled=0 - private_colormap: enabled=0 - fullscreen: enabled=0 - screenmode: name="sample" - keyboard_mapping: enabled=0, map=/usr/share/bochs/keymaps/x11-pc-fr.map - i440fxsupport: enabled=0 - -And start Bochs with this configuration : - - $ bochs -qf .bochsrc - -When asked, choose `5. begin simulation`. It is possible that you enter first into a debugger, answer `'c'` to make it continue. You should see a grub commandline. Tell it to install grub on the disk : - - grub> root (hd0,0) - Filesystem type is ext2fs, partition type 0x83 - - grub> setup (hd0) - Checking if "/boot/grub/stage1" exists... yes - Checking if "/boot/grub/stage2" exists... yes - Checking if "/boot/grub/e2fs_stage1_5" exists... yes - Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded. succeeded - Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2/boot/grub/menu.lst"... succeeded. - Done. - -Quit by pressing `^C q` in the shell from which you launched bochs. Our image is now ready. Copy all the releving files in `mnt/boot` like for the floppy and then umount it and launch qemu : - - $ cp /l4/boot/* mnt/boot/ - $ umount mnt - $ qemu -serial stdio -dummy-net -hda hurd_l4.img -boot c - -# <a name="3_Running_Banner"> 3. Running Banner </a> - -Still under construction but you should have no problems following `hurd-l4/libc/README` now that the hdd image works. - ----- - --- [[Main/OgnyanKulev]] - 05 Feb 2005 - -I didn't bother to licence it as it is so small, but consider it is under some sort of creative commons that allows redistribution and modification. <br /> -- Alexandre Buisse < <nattfodd@gmailNOSPAM.com> > - --- [[Main/JoachimNilsson]] - 05 Feb 2005 - -Comments from Marcus Brinkmann: - -> Thanks a lot for that. Some comments: -> -> $ ../configure --with-s0-linkbase=0x40000 --prefix=/l4 -> -> I'd recommend to explain how to use `--without-com0` here (or whatever it is called, don't remember) to choose VGA output, or how to configure the serial port. If you use vga, no `-o` option to laden and wortel should be used so you get all output on vga (but of course you can also mix it, whatever you want). -> -> Serial 1 is currently going to be used for remote debugging of userland apps. -> -> QEMU supports up to four serial ports, I use: `-serial stdio` and `-serial pty` and then I get the debugging output and kernel debugger in the terminal I started qemu in, and can use the pty for remote debugging with gdb (the latter doesn't work yet). -> -> Next: -> -> You should modify the first three lines to : -> ARCH=ia32 -> CPU=i586 -> PLATFORM=pc99 -> -> I never did that. I did change the menu item Processor Type to Pentium1 though. Maybe it has the same effect (and then your document would be a bit redundant here). -> -> Somebody should at some point document all those menu options, some are quite useful for debugging! -> -> Thanks, Marcus - --- [[Main/OgnyanKulev]] - 05 Feb 2005 - -I've been doing this sort of thing (See also `info grub` for making bootable eltorito grub cd ISOs): - - $ cd /usr/src/controlled/qemu-images - $ ls -R l4 - ls -R l4 - l4: - boot deva ia32-kernel laden physmem sigma0 task wortel - - l4/boot: - grub - - l4/boot/grub: - menu.lst stage2_eltorito - - $ cd /usr/src/controlled/qemu-images # dir above "l4" dir. - $ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot \ - -boot-load-size 4 -boot-info-table \ - -o /usr/src/controlled/qemu-images/l4.iso l4 - - $ qemu -boot d -cdrom /usr/src/controlled/qemu-images/l4.iso - --- [[Main/DerekDavies]] - 07 Feb 2005 - -You don't need a compiler targeting the Hurd. The above works with a compiler targeting Linux which are quite a bit easier to find. By adding "--target=i686-unknown-linux-gnu" to my configure line, I was able to cross compile hurd-l4 from Cygwin. - --- [[Main/MichaelAdams]] - 22 Feb 2005 - -A bootable CD iso image is now available at <http://gnuppix.org> - --- [[Main/ChristopheDevine]] - 03 Mar 2005 - -Included the anonymous password in the CVSROOT for L4. - --- [[Main/NowhereMan]] - 19 Mar 2005 - -I was able to use qemu instead of bochs to install grub on the new disk image. Just use: - - qemu -dummy-net -serial stdio -fda grubboot.img -hda hurd_l4.img -boot a - -and then the commands to type in the grub shell are the same. - --- [[Main/MatteoSettenvini]] - 05 May 2005 diff --git a/hurd/running/qemu/microsoft_windows.mdwn b/hurd/running/qemu/microsoft_windows.mdwn deleted file mode 100644 index 832b4bef..00000000 --- a/hurd/running/qemu/microsoft_windows.mdwn +++ /dev/null @@ -1,52 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -Welcome, This document is for getting you started in a few minutes. - -1. Install Qemu for Windows - - The executable can be downloaded from - <http://free.oszoo.org/ftp/qemu/win32/release/> Doble click on the - installer and follow the instructions. - -2. Obtain Qemu image - - * Debian GNU/Hurd qemu image can be downloaded from - <http://www.numenor.art.pl/balrog/hurd/>, but also see the main - [[QEMU]] page. - * Uncompress the image and rename it to debian-hurd-for-qemu.img (.img is - the only thing that matters, you can chose any name) Note: .img is for - QEMUMenu.bat, which saves you from remembering the command line options - of qemu and helps you change the settings (like chosing different - images, allocating RAM for the guest OS ...) interactivly. - * Copy this file to the directory where you installed Qemu. - -3. Start Qemu - - Double click the QEMUMenu.bat and enter the number to chose between images. - -4. Qemu short cuts - - * ctrl alt - to exit grab from qemu, get mouse cursor out from the qemu - window - * ctrl alt f - full screen - * ctrl alt 2 - qemu contrl console, use this to change devices - (eg. changing cdrom), send keys to the guest (for example if you want - to send ctrl alt del to the guest type "sendkey ctrl-alt-del" ... type - "help" for a listing of all the options. - * ctrl alt 1 - Hurd login console - -## QEmu Image Hangs on Boot -The Debian GNU/Hurd K16 QEmu image hangs during the boot process. You may have better luck by converting the image to qcow format - - ..\qemu-0.9.0-x86\qemu-img.exe convert debian-hurd-k16-qemu.img -O - qcow debian-hurd-k16-qemu.qcow - ..\qemu-0.9.0-x86\qemu.exe -L ..\qemu-0.9.0-x86 -m 512 -hda - debian-hurd-k16-qemu.qcow -localtime -M pc diff --git a/hurd/running/qemu/networking.mdwn b/hurd/running/qemu/networking.mdwn deleted file mode 100644 index 2bc9b16d..00000000 --- a/hurd/running/qemu/networking.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -## User mode network - -This is the default networking option for qemu. This does not require root -previleges. If you have DHCP running it will take the ip as 10.0.2.15 - -You can setup an ip 10.0.2.* -Gateway is 10.0.2.2 -Name server is 10.0.2.3 -Netmask is 255.255.255.0 - -You can setup the pfinet translator with the command - - $ settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0 - -Configure nameserver in /etc/resolve.conf - - nameserver 10.0.2.3 - -Setup a proxy with the command - - $ export http_proxy="http://<proxy.com>:<port>" - -Note: you can add this to your /etc/profile file so that every time you don't -have to setup this. - -If you are using a direct connection to internet install a proxy server on the -host os and use this. (I was not able to use it without proxy) - -You might be able to do it using iptables, some clues -<http://sujith-h.livejournal.com/9520.html> - -Use scp,ftp... to transfer files (also see -[[hurd/running/debian/faq#index2h1]]), read about [[sharing_files]]. diff --git a/hurd/running/qemu/networking/sharing_files.mdwn b/hurd/running/qemu/networking/sharing_files.mdwn deleted file mode 100644 index 5bdec5f1..00000000 --- a/hurd/running/qemu/networking/sharing_files.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -# SCP - -Setup OpenSSH server on host system. - -* Copying files from Guest to Host - - $ scp <file> <user>@<host>: - -* Copying files from Host to Guest. - - $ scp <user>@<host>:<file> - -Use scp -r for copying directories. - - -# FTP - -Setup ftp server (like proftpd) on the host. - -* Use ftp client from GNU inetutils - - $ ftp <host> - - Use mget to copy files from host and mput to copy files to the host. - -* The GNU way - setup an ftp translator - - $ settrans -ac ftp/<host> /hurd/ftpfs <username>:<password>@<host>:<path> |