On 07/12/2017 05:03 PM, Samuel Sieb wrote:
> On 07/12/2017 04:48 PM, Cole Robinson wrote:
>> There's a bug about this issue with that's lingered in a lot of forms
>> for a while:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1380893
>>
>> But with my testing, kernel > 4.9 inside the VM fixes th
On 07/12/2017 04:48 PM, Cole Robinson wrote:
There's a bug about this issue with that's lingered in a lot of forms for a
while:
https://bugzilla.redhat.com/show_bug.cgi?id=1380893
But with my testing, kernel > 4.9 inside the VM fixes the issue. So supported
fedora releases in the VM aren't aff
There's a bug about this issue with that's lingered in a lot of forms for a
while:
https://bugzilla.redhat.com/show_bug.cgi?id=1380893
But with my testing, kernel > 4.9 inside the VM fixes the issue. So supported
fedora releases in the VM aren't affected anymore. You can work around it by
disabl
On 07/11/2017 04:01 AM, Robert Moskowitz wrote:
This is an ongoing pain in the hind side. All too often, when I resume
my F24 system after a suspend, my QEMU is running away at 100% and my
F21 image (that I use for a few apps that I like from F21) is
non-responsive.
Is it qemu itself that is
On 07/11/2017 06:15 AM, Tom Horsley wrote:
On Tue, 11 Jul 2017 13:01:48 +0200
Robert Moskowitz wrote:
The only option, so far, has been to force the image off, then restart
it, then get everything working again.
There appear to be a near limitless number of things which systemd
doesn't proper
On Tue, 11 Jul 2017 13:01:48 +0200
Robert Moskowitz wrote:
> The only option, so far, has been to force the image off, then restart
> it, then get everything working again.
There appear to be a near limitless number of things which systemd
doesn't properly wait for at boot time. This may be anot
This is an ongoing pain in the hind side. All too often, when I resume
my F24 system after a suspend, my QEMU is running away at 100% and my
F21 image (that I use for a few apps that I like from F21) is
non-responsive.
The only option, so far, has been to force the image off, then restart
it
