QEMU on Bullseye

Oct 11, 2021

Bryan R Festa,

I'm using bullseye now too and can run various OSes in qemu/kvm.

You stated:

> With this change it appears the virtualization functionality no longer exists and QEMU drops back to emulation only mode.

I don't think I'm experiencing that since I haven't seen any messages or warnings about it but I honestly don't know how to check for it.

If you can let me know how you determine that I'll be glad to test it and get back to you.

Hope this helps,

~DennyL

Oct 11, 2021

I'm in the midst of copying my qcow2 file over to a microSD but I can run some stuff after to demonstrate.

Example: Windows 10 image in Buster runs seamlessly with very reasonable performance. After selecting Bullseye and kicking off dist-upgrade the packages for QEMU and Libvirt are selected to be removed. The performance is so slow that the VM takes over 30 minutes to run through the Windows startup screen and logging in is almost impossible due to lag.

It may be related, but I notice that after the Bullseye upgrade I get a message "Unable to set XATTR trusted.libvirt.security.dac ..... Operation not permitted" and the workaround is to set remember_owner = 0 in qemu.conf.

Oct 11, 2021

Bryan R Festa,

I ran into the XATTR error on one of my Chromebooks too when I upgraded from buster to bullseye and found that fix also. I didn't run into the lag that you speak of though.

Maybe starting over with a new bullseye container might work out better, that's what I did on my Pixelbook and it seems to run everything fine.

Hope this helps,

~DennyL

Oct 11, 2021

I'll try that first right after this copy finishes and get back to you.... note I miss my Pixelbook as it stopped booting. I am now running an ASUS C436.

Oct 12, 2021

DennyL,

So I have tried doing a clean install and that did not resolve the issue either. In the polling metrics I see CPU and Disk I/O usage but no memory usage. Looking at Diagnostics though I see CPU and memory consumption as expected (no Disk/IO is available in Daignostics)

The boot process though takes over 1 hour and I have not been able to enter my credentials to log in.

Oct 12, 2021

Bryan R Festa,

I have some questions to help clarify what you are talking about below, hopefully -

> "So I have tried doing a clean install and that did not resolve the issue either."

Are you talking about reinstalling a new 'termina' VM & a 'bullseye' container or Chrome OS?

> " In the polling metrics I see CPU and Disk I/O usage but no memory usage. "

What in the world are you referring to above, I have no clue, sorry.

Whatever it is I'm not sure it relates at all to your original issue.

> "The boot process though takes over 1 hour and I have not been able to enter my credentials to log in."

Sorry, but I do not understand what you are talking about in the above statement. 🤔

Are you saying you cannot sign-in to your profile at the OOBE screen or that you cannot sign-in to your user account in the container?

If you are talking about signing-in at the OOBE screen then you have a definite problem and I would suggest performing a powerwash.

If you are talking about opening the Linux Terminal app it does not / should not prompt you to sign-in / login to your user account in the container, if it does then something else is hosed.

Hope this helps,

~DennyL

Last edited Oct 12, 2021

Oct 12, 2021

I did a remove and reinstall of termina with bullseye
I only mentioned the polling metrics (part of libvirt) to show that CPU demonstrates usage...but not any of the other polls....potentially the client just hasn't loaded yet in the driver pack
The log in I am talking about is Windows 10's log in within the VM. The reason I can't log in is because it is so slow to respond to key presses the screen times out.

Everything else about ChromeOS and Termina are running fine.

I have not attempted a powerwash yet...was trying to avoid that due to multiple chrome profiles that I just don't feel like rebuilding.

If I do a revert back to Buster the performance returns no problems.

Oct 12, 2021

Bryan R Festa,

Okay, thanx for the clarifications.

You can forget the powerwash suggestion if you aren't having issues with signing-in to your profile.

At least we've gotten past your original issue with the QEMU.

Sorry, I have no experience with that login issue, I don't do Windoze. 😆

Maybe someone else can jump in and help you out.

~DennyL

Last edited Oct 12, 2021

Oct 12, 2021

The original issue still exists, which is it's not passing the hardware through, but instead virtualizing the processor. In Buster this is happening but not in Bullseye. I tried running commands to prove this but they don't operating under termina because the commands don't exist (example is modprobe).

Oct 12, 2021

Bryan R Festa,

Good thing they're upgrading the container to bullseye then.

Guess I should've said:

> "At least we've gotten past your original issue with the QEMU in bullseye.

~DennyL

Oct 12, 2021

Not until bullseye works with qemu - which it doesn't for me.

I think I may have found something that explains why it works for you and not me.

Under CPU model, I don't see the full list under Bullseye that is available in Buster. I'm thinking it's possible that your CPU is in the list and mine isn't anymore.