All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Andrea Bolognani <abologna@redhat.com>,
	qemu-devel@nongnu.org, marcel@redhat.com, drjones@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 2/2] mach-virt: Provide sample configuration files
Date: Mon, 13 Feb 2017 14:19:41 +0100	[thread overview]
Message-ID: <1486991981.19677.16.camel@redhat.com> (raw)
In-Reply-To: <d039b4d9-4c9a-ed49-dd36-304b290a013b@redhat.com>

  Hi,

> Clearly, for reviewing both files, I applied your patches, and then
> diffed the two files created by this patch. :)
> 
> So, what speaks against adding "-serial mon:stdio" here too? Even with a
> graphical guest, the monitor is useful. And, if you care about firmware
> logs (who doesn't? ;)), seeing serial output is good. (Same applies to
> the guest kernel -- sooner or later everyone enables serial output for
> grub2 and kernel, for reporting bugs.)

Depends on the target audience.  I'd expect users don't care much,
developers probably do.

Yes, most of my virtual machines have a serial console too, even if they
boot into graphic mode.  If I screwed up graphics with a bad virtio-gpu
patch it is very useful to have serial console to figure what exactly
broke ...

> * I'm a *huge* fan of saving disk space on the host. So, thin
> provisioning FTW! Virtio-scsi is definitely a step in the right
> direction, but for the disk drive, please add these wo properties:
> 
>   discard = "unmap"
>   werror = "enospc"

Good idea!

cheers,
  Gerd

      parent reply	other threads:[~2017-02-13 13:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 10:27 [Qemu-devel] [PATCH v6 0/2] docs: Improve sample configuration files Andrea Bolognani
2017-02-10 10:38 ` [Qemu-devel] [PATCH v6 1/2] q35: " Andrea Bolognani
2017-02-10 10:38   ` [Qemu-devel] [PATCH v6 2/2] mach-virt: Provide " Andrea Bolognani
2017-02-10 11:43     ` Laszlo Ersek
2017-02-10 15:13       ` Andrea Bolognani
2017-02-13 13:19       ` Gerd Hoffmann [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=1486991981.19677.16.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=abologna@redhat.com \
    --cc=drjones@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcel@redhat.com \
    --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 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.