From: Alexander Graf <agraf@suse.de> To: Avi Kivity <avi@redhat.com> Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, linux-fbdev-devel@lists.sourceforge.net, anthony@codemonkey.ws Subject: Re: [PATCH] Add VirtIO Frame Buffer Support Date: Tue, 3 Nov 2009 08:50:13 +0100 [thread overview] Message-ID: <8EA2855E-4209-4CCA-9E87-1D652A72F8FE@suse.de> (raw) In-Reply-To: <4AEFDF35.3020806@redhat.com> On 03.11.2009, at 08:43, Avi Kivity wrote: > On 11/03/2009 08:39 AM, Alexander Graf wrote: >> >> On 03.11.2009, at 07:34, Avi Kivity wrote: >> >>> On 11/03/2009 08:27 AM, Alexander Graf wrote: >>>> >>>>> How does it work today? >>>> >>>> You boot into a TERM=dumb line based emulation on 3270 (worst >>>> thing haunting people's nightmares ever), trying to get out of >>>> that mode as quickly as possible and off into SSH / VNC. >>> >>> Despite the coolness factor, IMO a few minutes during install time >>> do not justify a new hardware model and a new driver. >> >> It's more than just coolness factor. There are use cases out there (www.susestudio.com >> ) that don't want to rely on the guest exporting a VNC server to >> the outside just to access graphics. > > Instead you rely on the guest using virtio-fb. Since we have to make > guest modifications, why not go for the simpler ones? Ok, imagine this was not this unloved S390 odd architecture but X86. The only output choices you have are: 1) virtio-console 2) VNC / SSH over network 3) virtio-fb Now you want to configure a server, probably using yast and all those nice graphical utilities, but still enable a firewall so people outside don't intrude your machine. Well, you managed to configure the firewall by luck to allow VNC, but now you reconfigured it and something broke - but VNC was your only chance to access the machine. Oops... >> You also want to see boot messages, have a console login screen, > > virtio-console does that, except for the penguins. Better, since > you can scroll back. It doesn't do graphics. Ever used yast in text mode? >> be able to debug things without switching between virtio-console >> and vnc, etc. etc. > > Render virtio-console on your vnc session. We do that already, no? > (well, the host's vnc session, not the guest's). Yes, we do that. Still doesn't buy you graphics. >> The hardware model isn't exactly new either. It's just the next >> logical step to a full PV machine using virtio. If the virtio-fb >> stuff turns out to be really fast and reliable, I could even >> imagine it being the default target for kvm on ppc as well, as we >> can't switch resolutions on the fly there atm. >> > > We could with vmware-vga. The vmware-port stuff is pretty much tied onto X86. I don't think modifying EAX is that easy on PPC ;-). >>> Why? the guest will typically have networking when it's set up, >>> so it should have network access during install. You can easily >>> use slirp redirection and the built-in dhcp server to set this up >>> with relatively few hassles. >> >> That's how I use it right now. It's no fun. >> > > The toolstack should hide the unfun parts. You can't hide guest configuration. We as a distribution control the kernel. We don't control the user's configuration as that's by design the user's choice. The only thing we can do is give users meaningful choices to choose from - and having graphics available is definitely one of them. Seriously, try to ask someone internally to get access to an S390. I think you'll understand my motivations a lot better after having used it for a bit. Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de> To: Avi Kivity <avi@redhat.com> Cc: linux-fbdev-devel@lists.sourceforge.net, qemu-devel@nongnu.org, kvm@vger.kernel.org Subject: [Qemu-devel] Re: [PATCH] Add VirtIO Frame Buffer Support Date: Tue, 3 Nov 2009 08:50:13 +0100 [thread overview] Message-ID: <8EA2855E-4209-4CCA-9E87-1D652A72F8FE@suse.de> (raw) In-Reply-To: <4AEFDF35.3020806@redhat.com> On 03.11.2009, at 08:43, Avi Kivity wrote: > On 11/03/2009 08:39 AM, Alexander Graf wrote: >> >> On 03.11.2009, at 07:34, Avi Kivity wrote: >> >>> On 11/03/2009 08:27 AM, Alexander Graf wrote: >>>> >>>>> How does it work today? >>>> >>>> You boot into a TERM=dumb line based emulation on 3270 (worst >>>> thing haunting people's nightmares ever), trying to get out of >>>> that mode as quickly as possible and off into SSH / VNC. >>> >>> Despite the coolness factor, IMO a few minutes during install time >>> do not justify a new hardware model and a new driver. >> >> It's more than just coolness factor. There are use cases out there (www.susestudio.com >> ) that don't want to rely on the guest exporting a VNC server to >> the outside just to access graphics. > > Instead you rely on the guest using virtio-fb. Since we have to make > guest modifications, why not go for the simpler ones? Ok, imagine this was not this unloved S390 odd architecture but X86. The only output choices you have are: 1) virtio-console 2) VNC / SSH over network 3) virtio-fb Now you want to configure a server, probably using yast and all those nice graphical utilities, but still enable a firewall so people outside don't intrude your machine. Well, you managed to configure the firewall by luck to allow VNC, but now you reconfigured it and something broke - but VNC was your only chance to access the machine. Oops... >> You also want to see boot messages, have a console login screen, > > virtio-console does that, except for the penguins. Better, since > you can scroll back. It doesn't do graphics. Ever used yast in text mode? >> be able to debug things without switching between virtio-console >> and vnc, etc. etc. > > Render virtio-console on your vnc session. We do that already, no? > (well, the host's vnc session, not the guest's). Yes, we do that. Still doesn't buy you graphics. >> The hardware model isn't exactly new either. It's just the next >> logical step to a full PV machine using virtio. If the virtio-fb >> stuff turns out to be really fast and reliable, I could even >> imagine it being the default target for kvm on ppc as well, as we >> can't switch resolutions on the fly there atm. >> > > We could with vmware-vga. The vmware-port stuff is pretty much tied onto X86. I don't think modifying EAX is that easy on PPC ;-). >>> Why? the guest will typically have networking when it's set up, >>> so it should have network access during install. You can easily >>> use slirp redirection and the built-in dhcp server to set this up >>> with relatively few hassles. >> >> That's how I use it right now. It's no fun. >> > > The toolstack should hide the unfun parts. You can't hide guest configuration. We as a distribution control the kernel. We don't control the user's configuration as that's by design the user's choice. The only thing we can do is give users meaningful choices to choose from - and having graphics available is definitely one of them. Seriously, try to ask someone internally to get access to an S390. I think you'll understand my motivations a lot better after having used it for a bit. Alex
next prev parent reply other threads:[~2009-11-03 7:50 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-02 22:09 [PATCH] Add VirtIO Frame Buffer Support Alexander Graf 2009-11-02 22:09 ` [Qemu-devel] " Alexander Graf 2009-11-02 22:32 ` Ondrej Zajicek 2009-11-02 22:42 ` Alexander Graf 2009-11-02 23:24 ` [Linux-fbdev-devel] " Alexander Graf 2009-11-02 23:24 ` [Qemu-devel] " Alexander Graf 2009-11-02 23:57 ` Ondrej Zajicek 2009-11-02 23:57 ` [Qemu-devel] Re: [Linux-fbdev-devel] " Ondrej Zajicek 2009-11-02 23:59 ` Alexander Graf 2009-11-02 23:59 ` [Qemu-devel] " Alexander Graf 2009-11-02 23:51 ` Ondrej Zajicek 2009-11-02 23:53 ` Alexander Graf 2009-11-02 23:58 ` Ondrej Zajicek 2009-11-03 6:21 ` Avi Kivity 2009-11-03 6:21 ` [Qemu-devel] " Avi Kivity 2009-11-03 6:22 ` Alexander Graf 2009-11-03 6:22 ` [Qemu-devel] " Alexander Graf 2009-11-03 6:24 ` Avi Kivity 2009-11-03 6:24 ` [Qemu-devel] " Avi Kivity 2009-11-03 6:27 ` Alexander Graf 2009-11-03 6:27 ` [Qemu-devel] " Alexander Graf 2009-11-03 6:34 ` Avi Kivity 2009-11-03 6:34 ` [Qemu-devel] " Avi Kivity 2009-11-03 6:39 ` Alexander Graf 2009-11-03 6:39 ` [Qemu-devel] " Alexander Graf 2009-11-03 7:43 ` Avi Kivity 2009-11-03 7:43 ` [Qemu-devel] " Avi Kivity 2009-11-03 7:50 ` Alexander Graf [this message] 2009-11-03 7:50 ` Alexander Graf 2009-11-03 8:20 ` Avi Kivity 2009-11-03 8:20 ` [Qemu-devel] " Avi Kivity 2009-11-03 8:26 ` Alexander Graf 2009-11-03 8:26 ` [Qemu-devel] " Alexander Graf 2009-11-03 8:53 ` Avi Kivity 2009-11-03 8:53 ` [Qemu-devel] " Avi Kivity 2009-11-03 15:14 ` Anthony Liguori 2009-11-03 15:14 ` [Qemu-devel] " Anthony Liguori 2009-11-03 15:57 ` Avi Kivity 2009-11-03 15:57 ` [Qemu-devel] " Avi Kivity 2009-11-03 11:25 ` Vincent Hanquez 2009-11-03 11:25 ` Vincent Hanquez 2009-11-03 9:38 ` Avi Kivity 2009-11-03 9:38 ` Avi Kivity 2009-11-03 15:29 ` Ondrej Zajicek 2009-11-03 15:29 ` [Linux-fbdev-devel] " Ondrej Zajicek 2009-11-03 16:05 ` Avi Kivity 2009-11-03 16:05 ` Avi Kivity 2009-11-03 16:53 ` Ondrej Zajicek 2009-11-03 16:53 ` Ondrej Zajicek 2009-11-03 17:33 ` [Linux-fbdev-devel] " Paolo Bonzini 2009-11-03 17:33 ` [Linux-fbdev-devel] [Qemu-devel] " Paolo Bonzini 2009-11-03 17:33 ` [Linux-fbdev-devel] " Paolo Bonzini 2009-11-04 16:09 ` [Qemu-devel] " Vincent Hanquez 2009-11-04 16:35 ` Anthony Liguori 2009-11-04 16:35 ` Anthony Liguori 2009-11-05 9:04 ` Avi Kivity 2009-11-08 4:43 ` Thomas Fjellstrom 2009-11-06 2:39 ` Jamie Lokier 2009-11-06 2:39 ` Jamie Lokier 2009-11-06 3:05 ` Anthony Liguori 2009-11-06 3:05 ` Anthony Liguori 2009-11-05 11:36 ` Michael S. Tsirkin 2009-11-05 11:36 ` Michael S. Tsirkin 2009-11-05 11:36 ` [Qemu-devel] " Michael S. Tsirkin
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=8EA2855E-4209-4CCA-9E87-1D652A72F8FE@suse.de \ --to=agraf@suse.de \ --cc=anthony@codemonkey.ws \ --cc=avi@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=linux-fbdev-devel@lists.sourceforge.net \ --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: linkBe 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.