When opening a VM the network will disconnect the current VM and reconnect to the new VM. Hasn’t been a real issue except for now. Can not update fedora-40-xfc.
Using the update manager, I can perform all selected updates with the netwrok disconnecting/reconnecting as required. Except for fedora-40-xfc. Network disconnects and reconnects causing the update to error out.
Is there a flag I can set or do something to stop the error out?
Is there a change in fedora-40-xfce update code/process that is different than the other templates that is causing this?
Below is the error message from Update Manager:
Updating fedora-40-xfce
Install requirements
Error: Failed to download metadata for repo ‘fedora’: Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64 [CONNECT tunnel failed, response 500]
Error: Failed to download metadata for repo ‘fedora’: Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64 [CONNECT tunnel failed, response 500]
Could you be more specific about this problem?
What makes you think that the old qube is disconnected? Qubes networking
allows multiple concurrent connections so this behaviour is wholly
unexpected.
When updating templates, those templates do not have network
connections, so they should not affect existing Qubes networking. The
update proxy should remain running and network connected all the time.
Error 500 is a response code indicting a server error.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
There Qubes are popup windows followed that say:
“Connection Established
You Are Now Connected to network name)”
And
“Network Disconnected”
These popups can be set to not display.
If I go into Qubes VM manager and manually start fedora-40-xfce it will connect and keep the network connection when I hit update. fedora-40-xfc netVM is set to default (N/A)
I was curious about the concurrency. This is the way I remember Qubes operating.
I would be curious to know if the Update called from setting has the same error trapping/timeout as the call from Qubes Manager. Or are the trigger flags in fedora-40-xfce some how different in their response to the two different calling routines.
I still have fedora-39-xfce on the system. Not being used. I ran update against it. Results are the same. From Settings Update, disconnected error-ed out. Network did reconnected. Disconnected the network and verified VM was shut down. Started VM in Qube Manager and hit update. Ran fine with no disconnecting. Updates installed.
I need to go snort some more Draino to clear the head.