From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Allow -kernel without -hda
Date: Mon, 01 May 2006 14:29:19 +0200 [thread overview]
Message-ID: <4455FF1F.9040303@bellard.org> (raw)
In-Reply-To: <c1bf1cf0604302011r7511caa4v17e56af7621f7d72@mail.gmail.com>
I agree that the feature is useful, but your patch is incomplete:
without bs_table[0], the boot sector cannot be created and the Linux
kernel cannot be launched. Maybe you have a specific Ethernet BIOS to
enable that ? Someone submitted a new block driver which simulated
"/dev/zero" and it may be another solution.
Regards,
Fabrice.
Ed Swierk wrote:
> The qemu -kernel option currently requires specifying a hard disk
> image with -hda. Ostensibly at least one hard disk is needed for
> qemu's boot loader to populate the partition table in its array of
> boot sectors.
>
> Passing -hda /dev/zero tricks qemu into booting, which demonstrates
> that the requirement is unnecessary. Booting with no disk image is
> needed to support diskless configurations where a remote NFS directory
> is used as the root filesystem. In this scenario, the user invokes
> qemu with -kernel and -initrd options, with a specially configured
> initrd that NFS-mounts a filesystem on / before passing control to the
> real init.
>
> The attached patch permits using the -kernel option with no disk
> images, and skips copying the partition table in this case.
>
> --Ed
>
>
> ------------------------------------------------------------------------
>
> diff -BurN qemu-snapshot-2006-03-27_23.orig/hw/pc.c qemu-snapshot-2006-03-27_23/hw/pc.c
> --- qemu-snapshot-2006-03-27_23.orig/hw/pc.c 2006-04-05 13:05:17.000000000 +0000
> +++ qemu-snapshot-2006-03-27_23/hw/pc.c 2006-04-05 13:12:40.000000000 +0000
> @@ -707,10 +707,6 @@
> uint8_t bootsect[512];
> uint8_t old_bootsect[512];
>
> - if (bs_table[0] == NULL) {
> - fprintf(stderr, "A disk image must be given for 'hda' when booting a Linux kernel\n");
> - exit(1);
> - }
> snprintf(buf, sizeof(buf), "%s/%s", bios_dir, LINUX_BOOT_FILENAME);
> ret = load_image(buf, bootsect);
> if (ret != sizeof(bootsect)) {
> @@ -719,12 +715,14 @@
> exit(1);
> }
>
> - if (bdrv_read(bs_table[0], 0, old_bootsect, 1) >= 0) {
> - /* copy the MSDOS partition table */
> - memcpy(bootsect + 0x1be, old_bootsect + 0x1be, 0x40);
> - }
> + if (bs_table[0]) {
> + if (bdrv_read(bs_table[0], 0, old_bootsect, 1) >= 0) {
> + /* copy the MSDOS partition table */
> + memcpy(bootsect + 0x1be, old_bootsect + 0x1be, 0x40);
> + }
>
> - bdrv_set_boot_sector(bs_table[0], bootsect, sizeof(bootsect));
> + bdrv_set_boot_sector(bs_table[0], bootsect, sizeof(bootsect));
> + }
>
> /* now we can load the kernel */
> ret = load_kernel(kernel_filename,
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
prev parent reply other threads:[~2006-05-01 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 3:11 [Qemu-devel] [PATCH] Allow -kernel without -hda Ed Swierk
2006-05-01 12:29 ` Fabrice Bellard [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=4455FF1F.9040303@bellard.org \
--to=fabrice@bellard.org \
--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).