Displaying 11 results from an estimated 11 matches for "betterm".
Did you mean:
better
2016 Apr 19
2
[PATCH RFC] fixup! virtio: convert to use DMA api
...ome older kernels to OOPS.
>
> --Andy
Since it's experimental, it might be OK to change *guest kernels*
such that they oops on old QEMU.
But guest kernels were not experimental - so we need a QEMU mode that
makes them work fine. The more functionality is available in this QEMU
mode, the betterm because it's going to be the default for a while. For
the same reason, it is preferable to also have new kernels not crash in
this mode.
--
MST
2016 Apr 19
2
[PATCH RFC] fixup! virtio: convert to use DMA api
...ome older kernels to OOPS.
>
> --Andy
Since it's experimental, it might be OK to change *guest kernels*
such that they oops on old QEMU.
But guest kernels were not experimental - so we need a QEMU mode that
makes them work fine. The more functionality is available in this QEMU
mode, the betterm because it's going to be the default for a while. For
the same reason, it is preferable to also have new kernels not crash in
this mode.
--
MST
2016 Apr 19
2
[PATCH RFC] fixup! virtio: convert to use DMA api
...> Since it's experimental, it might be OK to change *guest kernels*
> > such that they oops on old QEMU.
> > But guest kernels were not experimental - so we need a QEMU mode that
> > makes them work fine. The more functionality is available in this QEMU
> > mode, the betterm because it's going to be the default for a while. For
> > the same reason, it is preferable to also have new kernels not crash in
> > this mode.
> >
>
> People add QEMU features that need new guest kernels all time time.
> If you enable virtio-scsi and try to boot a...
2016 Apr 19
2
[PATCH RFC] fixup! virtio: convert to use DMA api
...> Since it's experimental, it might be OK to change *guest kernels*
> > such that they oops on old QEMU.
> > But guest kernels were not experimental - so we need a QEMU mode that
> > makes them work fine. The more functionality is available in this QEMU
> > mode, the betterm because it's going to be the default for a while. For
> > the same reason, it is preferable to also have new kernels not crash in
> > this mode.
> >
>
> People add QEMU features that need new guest kernels all time time.
> If you enable virtio-scsi and try to boot a...
2016 Apr 19
0
[PATCH RFC] fixup! virtio: convert to use DMA api
...>> --Andy
>
> Since it's experimental, it might be OK to change *guest kernels*
> such that they oops on old QEMU.
> But guest kernels were not experimental - so we need a QEMU mode that
> makes them work fine. The more functionality is available in this QEMU
> mode, the betterm because it's going to be the default for a while. For
> the same reason, it is preferable to also have new kernels not crash in
> this mode.
>
People add QEMU features that need new guest kernels all time time.
If you enable virtio-scsi and try to boot a guest that's too old, it
w...
2011 May 28
3
Ubuntu: World of Warcraft 3.3.5a OpenGL and Intel GMA issue
ok, I'll get straight to the point:
I'm trying to run World of Warcraft (Version 3.3.5 Build 12340) and I have an Intel GMA 4500MHD Integrated chipset, and I can login just fine, but when it tries to render a character, it crashes and spits out an error via the WowError.exe, and if I don't use OpenGL, it can play, but the FPS will spike horribly at random times, and all player
2016 Apr 19
0
[PATCH RFC] fixup! virtio: convert to use DMA api
...39;s experimental, it might be OK to change *guest kernels*
>> > such that they oops on old QEMU.
>> > But guest kernels were not experimental - so we need a QEMU mode that
>> > makes them work fine. The more functionality is available in this QEMU
>> > mode, the betterm because it's going to be the default for a while. For
>> > the same reason, it is preferable to also have new kernels not crash in
>> > this mode.
>> >
>>
>> People add QEMU features that need new guest kernels all time time.
>> If you enable virtio-...
2016 Apr 19
2
[PATCH RFC] fixup! virtio: convert to use DMA api
...t might be OK to change *guest kernels*
> >> > such that they oops on old QEMU.
> >> > But guest kernels were not experimental - so we need a QEMU mode that
> >> > makes them work fine. The more functionality is available in this QEMU
> >> > mode, the betterm because it's going to be the default for a while. For
> >> > the same reason, it is preferable to also have new kernels not crash in
> >> > this mode.
> >> >
> >>
> >> People add QEMU features that need new guest kernels all time time.
>...
2016 Apr 19
2
[PATCH RFC] fixup! virtio: convert to use DMA api
...t might be OK to change *guest kernels*
> >> > such that they oops on old QEMU.
> >> > But guest kernels were not experimental - so we need a QEMU mode that
> >> > makes them work fine. The more functionality is available in this QEMU
> >> > mode, the betterm because it's going to be the default for a while. For
> >> > the same reason, it is preferable to also have new kernels not crash in
> >> > this mode.
> >> >
> >>
> >> People add QEMU features that need new guest kernels all time time.
>...
2016 Apr 18
5
[PATCH RFC] fixup! virtio: convert to use DMA api
On Mon, 2016-04-18 at 19:27 +0300, Michael S. Tsirkin wrote:
> I balk at adding more hacks to a broken system. My goals are
> merely to
> - make things work correctly with an IOMMU and new guests,
> ? so people can use userspace drivers with virtio devices
> - prevent security risks when guest kernel mistakenly thinks
> ? it's protected by an IOMMU, but in fact isn't
>
2016 Apr 18
5
[PATCH RFC] fixup! virtio: convert to use DMA api
On Mon, 2016-04-18 at 19:27 +0300, Michael S. Tsirkin wrote:
> I balk at adding more hacks to a broken system. My goals are
> merely to
> - make things work correctly with an IOMMU and new guests,
> ? so people can use userspace drivers with virtio devices
> - prevent security risks when guest kernel mistakenly thinks
> ? it's protected by an IOMMU, but in fact isn't
>