| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <500E9CC7.9020201@gmail.com> Date: Tue, 24 Jul 2012 15:01:59 +0200 From: Sasha Levin <levinsasha928@...il.com> To: dlaor@...hat.com CC: Rusty Russell <rusty@...tcorp.com.au>, mst@...hat.com, penberg@...nel.org, asias.hejun@...il.com, virtualization@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, kvm@...r.kernel.org, avi@...hat.com, anthony@...emonkey.ws, wency@...fujitsu.com Subject: Re: [RFC 0/2] virtio: provide a way for host to monitor critical events in the device On 07/24/2012 02:46 PM, Dor Laor wrote: > On 07/24/2012 03:30 PM, Sasha Levin wrote: >> On 07/24/2012 10:26 AM, Dor Laor wrote: >>> On 07/24/2012 07:55 AM, Rusty Russell wrote: >>>> On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin <levinsasha928@...il.com> wrote: >>>>> As it was discussed recently, there's currently no way for the guest to notify >>>>> the host about panics. Further more, there's no reasonable way to notify the >>>>> host of other critical events such as an OOM kill. >>>> >>>> I clearly missed the discussion. Is this actually useful? In practice, >>> >>> Admit this is not a killer feature.. >>> >>>> won't you want the log from the guest? What makes a virtual guest >>>> different from a physical guest? >>> >>> Most times virt guest can do better than a physical OS. In that sense, this is where virtualization shines (live migration, hotplug for any virtual resource including net/block/cpu/memory/..). >>> >>> There are plenty of niche but worth while small features such as the virtio-trace series and other that allow the host/virt-mgmt to get more insight into the guest w/o a need to configure the guest. >>> >>> In theory guest OOM can trigger a host memory hot plug action. Again, I don't see it as a key feature.. >>> >>>> >>>> Guest watchdog functionality might be useful, but that's simpler to >>> >>> There is already a fully emulated watchdog device in qemu. >> >> There is, but why emulate physical devices when you can take advantage of virtio? >> >> You could say the same about the rest of the virtio family - "There is already a fully emulated NIC device in qemu". > > The single issue virtio-nic solves is performance enhancements that can be done w/ a fully emulated NIC. The reason is that such NIC tend to access pio/mmio space a lot while virtio is designed for virtualization. virtio on it's own was introduced to help solve the fragmentation around virtualized devices, so I don't think that the main purpose of doing virtio drivers is due to any performance benefits virtio may provide. Also consider virtio devices which don't exactly have strict performance considerations such as virtio-9p or virtio-rng. I mean, why implement virtio-rng when qemu could just emulate some sort of a hardware RNG and just grab randomness from the host? > Standard watchdog device (isn't it time you'll try qemu?) isn't about performance and if that's all the functionality you need it should work fine. Don't understand me wrong, I'm not saying that there's something with the watchdog driver in qemu. All I want is to write a watchdog driver for lkvm which can take advantage of the fact it runs within a guest. > btw: check the virtio-trace series that was just send in a parallel thread. Will do! > Cheers, > Dor > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists