Re: Fedora Virtualization (quemu/kvm) vs Virtualbox

2019-04-27 Thread Chris Murphy
On Tue, Apr 9, 2019 at 5:52 AM Dario Lesca  wrote:
>
> On a i7+16Gb+SSD notebook of a my friend I have install Fedora 29 workstation 
> (all work fine! ... thank to all!)
> and into qemu/kvm/libvirtd via virt-manager I have install a win10pro with 
> all virtio driver (disk, network, ecc..).
>
> After few days my friend say me that the win10 is slow and less efficient 
> than same installation on another PC with VirtualBox.
> He told me "virtualbox is better and faster"

What backing storage is the VM using? qcow2, raw, LVM? If it's a file,
what filesystem is it on?

It's worth experimenting with the virtio disk "cache mode" setting, in
virt-manager under advanced > performance options. I use unsafe, which
is bad advice to give because it really is not safe if there's a
crash, good chance the guest filesystem is toast. But it's a lot
faster. And I consider my VM's throwaway.  There may be another cache
setting that's not so dangerous but also doesn't penalize like the
default. I think what you want is cache=writeback if it's a file, and
cache=none if it's LVM. I would say test both and pick the one with
better performance.

https://doc.opensuse.org/documentation/leap/virtualization/html/book.virt/cha.cachemodes.html#cachemodes.descr

Note that some of the cache modes must be paired with a specific IO
mode, e.g. unsafe only works with threads.

-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: UEFI boot with BIOS password, am I screwed?

2019-04-27 Thread Chris Murphy
On Wed, Apr 24, 2019 at 5:24 PM Richard Shaw  wrote:
>
> On Wed, Apr 24, 2019 at 5:35 PM Chris Murphy  wrote:
>>
>> On Wed, Apr 24, 2019 at 8:02 AM Richard Shaw  wrote:
>> >
>> > While I had to run it through the shredder I finally sat down and went 
>> > through all the passwords I've ever used and figured it out :)
>> >
>> > I turned off Secure Boot but it still won't boot Fedora.
>> >
>> > I finally figured out I had to use -v to get what I wanted from efibootmgr:
>> >
>> > BootCurrent: 0001
>> > Timeout: 0 seconds
>> > BootOrder: 000E,0001,0003,2001,2002,2003
>>
>> Offhand, this looks like the problem. 000E points to Windows. You need
>> to use `efibootmgr --bootorder 0,E,1` so it boots Fedora first. It's
>> not strictly necessary to list everything in bootorder, you can just
>> have one. The idea of populating it fully is to have exactly the
>> predictable fallback boot behavior the user wants, whatever that is.
>> e.g. if something with the Fedora bootloader gets nerfed then it'd
>> boot Windows.
>
>
> I'm pressing F12 and manually selecting Fedora, but I did later try to change 
> the boot order, both with efibootmgr and in the BIOS to no avail.

OK you changed the bootorder using 'efibootmgr --bootorder' and you
got what result from that command? Whether it works or doesn't, it
returns a result that might be useful. And then you can confirm it
with 'efibootmgr -v' and that also would be useful. And whenever there
are unexplained results, I like to look at dmesg right before and
after running efibootmgr (or use journalctl -f in another shell) to
see if there are any kernel messages at the time. Ultimately the NVRAM
is modified by the kernel, and efibootmgr is just the user interface
to those kernel ioctls that do the actual modification of NVRAM.

Also, there's a bunch of bugs in this area, so I suggest making sure
the firmware is up to date. I've seen all kinds of weird garbage
collection issues where entries don't get deleted, or even bootorder
not sticking, or bootnext not getting set.

> I can confirm it's the correct UUID for the EFI partition. I have also 
> reinstalled Fedora after deleting all the superfluous entries... Looks the 
> same, still doesn't boot.

Sounds like a bug. Question is figuring out whose bug and how to work
around it. Anyway, in addition to making sure the firmware is up to
date, I'd go into the firmware setup, and choose the 'load defaults'
or 'reset configs' option, and then exit (which will involve saving
the defaults).


>> Also, firmware password and UEFI Secure Boot are two different things.
>> Secure Boot I don't recommend disabling, it's a feature that
>> cryptographically verifies the bootloaders, the kernel and kernel
>> modules. If you're building out of tree kernel modules, then it's
>> understandable to run without Secure Boot but I would still go through
>> the effort to create your own signing cert, register it in the
>> firmware, and then use it to sign your modules so that you can enable
>> secure boot.
>
>
> I disabled it to remove it as the problem, still won't boot Fedora. Once I 
> get it working I can mark the efi file (presumably shimx64.efi) as trusted 
> and re-enable.

There should be no need to mark any of the Fedora bootloaders,
shimx64.efi or grubx64.efi, as trusted. The shimx64.efi file is signed
by both Microsoft and Fedora, the computer firmware should have in its
database the Microsoft UEFI X.509 cert, and therefore will trust
shimx64.efi. And shimx64.efi provides the firmware with the Fedora
X.509 cert so that the firmware will trust grubx64.efi and the kernel
and kernel modules, all of which are signed by Fedora's signing key.
If you have to do something special to get the firmware to trust any
of these things, and you're not compiling your own binaries somewhere
somehow, then something's wrong - and that needs to be figured out.


--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: IcedTeaWeb: (/usr/bin/javaws): how to run it from firefox with -noupdate option?

2019-04-27 Thread Dario Lesca
Il giorno ven, 26/04/2019 alle 15.49 -0700, stan via users ha scritto:
> I think this is what you want.
> In about:config in firefox there is an optionapp.update.autoIf you
> set that to false, it should only update manually (when youupdate).

Thank for reply, but this is not what I want, and this option in
firefox is already set to false.

I want run javaws with one more  option and reduce the
annoying  waiting (10/15 minutes) when web java app start via javaws

Someone can help me?

Thanks 

-- 
Dario Lesca
(inviato dal mio Linux Fedora 29 Workstation)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org