Hi,
when I shut down a netvm the whole system freezes, exept when there was
a change which need the netmv restart to take effect like
assigning/removing network interfaces or after changing the template.
Because it doesn't crash when netvm restart is needed I think that could
be a feature, or is it a bug after all?
Never saw such "crash"... so you should be more specific.
What do you mean crash?
Sorry for using my old gmail now, I didn’t get the mails with my “regular” mail account so I couldn’t reply…
The system just freezes (screen doesn’t get updated anymore). changing to console with CTRL+ALT+F-keys don’t work as well.
But meanwhile I know that it also happens if there are changes to the netvm.
So when I shutdown a netvm the system freezes ~4 out of 5 times. When not shutting down a netvm it’s stable so far. No crashes without shutting down a netvm.
BTW, using R2 Beta2
I'm not sure exactly what you mean, but you should be aware that there is a known Xen issue which causes the netvm to take a rather long time to shut down. This is especially noticeable if you issue a system shutdown command from dom0 without first shutting down all running VMs. Basically, you find yourself sitting at the Qubes logo shutdown screen for a very, very long time before the system actually shuts down.
(PS - Please don't top-post.)
What I mean with system freezes is that I can’t move mouse, the RAM and CPU usage in Qubes VM manager doesn’t change anymore, CTRL+ALT+F-keys don’t get me the tty’s. Just showing a frozen screen and I can’t interact with the system.
It was always after the dialog popup to give the netvm another 20 seconds to shutdown IIRC. It didn’t happen on system shutdown.
There’s not much need for me to shutdown netvm. So it doesn’t really bother me but I thought others would be interested to know.
Sorry for using my old gmail now, I didn't get the mails with my
"regular"
mail account so I couldn't reply...
The system just freezes (screen doesn't get updated anymore). changing
to
console with CTRL+ALT+F-keys don't work as well.
But meanwhile I know that it also happens if there are changes to thenetvm.
So when I shutdown a netvm the system freezes ~4 out of 5 times. When
not
shutting down a netvm it's stable so far. No crashes without shutting
down
a netvm.
BTW, using R2 Beta2
Because it doesn't crash when netvm restart is needed I think that
could
be a feature, or is it a bug after all?
Never saw such "crash"... so you should be more specific.
What do you mean crash?--
ZrubiI'm not sure exactly what you mean, but you should be aware that there
is a known Xen issue which causes the netvm to take a rather long time
to shut down. This is especially noticeable if you issue a system
shutdown command from dom0 without first shutting down all running VMs.
Basically, you find yourself sitting at the Qubes logo shutdown screen
for a very, very long time before the system actually shuts down.(PS - Please don't top-post.)
What I mean with system freezes is that I can't move mouse, the RAM and CPU
usage in Qubes VM manager doesn't change anymore, CTRL+ALT+F-keys don't get
me the tty's. Just showing a frozen screen and I can't interact with the
system.
Ah, so it must actually be a Xen or dom0 issue, then. If it was just the netvm that was broken, it wouldn't affect the entire system GUI (which is the point of GUI isolation).
Still... I'm afraid I don't have any idea as to what could be causing it. Perhaps you should take a look at the logs in dom0. Or just reinstall the system...
Did you make any unusual changes in dom0?
It was always after the dialog popup to give the netvm another 20 seconds
to shutdown IIRC. It didn't happen on system shutdown.
This must be a Xen/kernel issue about the PCI assigments.
There are 1 other known bug wich makes the assigned PCI devices
unusable after a system suspend...
It is only affencting netVM because this is the VM you assign yout
networking devices.
And please do not reinstall Qubes. This is not a shitty windows 
I updated Dom0 with sudo qubes-dom0-update.
Perhaps that causes it. So downgrade could be the solution but as I see this just works on a per package base and I have to know the versions of the original packages. I never used Fedora/yum beforeQubes…
Perhaps it’s easyer to reinstall?
Sorry for using my old gmail now, I didn't get the mails with my
"regular"
mail account so I couldn't reply...
The system just freezes (screen doesn't get updated anymore). changing
to
console with CTRL+ALT+F-keys don't work as well.
But meanwhile I know that it also happens if there are changes to thenetvm.
So when I shutdown a netvm the system freezes ~4 out of 5 times. When
not
shutting down a netvm it's stable so far. No crashes without shutting
down
a netvm.
BTW, using R2 Beta2
Because it doesn't crash when netvm restart is needed I think that
could
be a feature, or is it a bug after all?
Never saw such "crash"... so you should be more specific.
What do you mean crash?--
ZrubiI'm not sure exactly what you mean, but you should be aware that there
is a known Xen issue which causes the netvm to take a rather long time
to shut down. This is especially noticeable if you issue a system
shutdown command from dom0 without first shutting down all running VMs.
Basically, you find yourself sitting at the Qubes logo shutdown screen
for a very, very long time before the system actually shuts down.(PS - Please don't top-post.)
What I mean with system freezes is that I can't move mouse, the RAM and
CPU
usage in Qubes VM manager doesn't change anymore, CTRL+ALT+F-keys don't
get
me the tty's. Just showing a frozen screen and I can't interact with the
system.Ah, so it must actually be a Xen or dom0 issue, then. If it was just the
netvm that was broken, it wouldn't affect the entire system GUI (which
is the point of GUI isolation).Still... I'm afraid I don't have any idea as to what could be causing
it. Perhaps you should take a look at the logs in dom0. Or just
reinstall the system...Did you make any unusual changes in dom0?
It was always after the dialog popup to give the netvm another 20
seconds
to shutdown IIRC. It didn't happen on system shutdown.
There's not much need for me to shutdown netvm. So it doesn't really
bother
me but I thought others would be interested to know.
I updated Dom0 with sudo qubes-dom0-update.
Perhaps that causes it.
No, qubes-dom0-update should not break anything. That's the correct way to update dom0.
So downgrade could be the solution but as I see
this just works on a per package base and I have to know the versions of
the original packages.
Well, you could use the yum history command to undo whole updates. (I've never tried it in dom0, though, so not sure if there's any special catch there.) If you believe that the problem was caused by some recent update, then perhaps you may want to try it out.
I never used Fedora/yum beforeQubes...
Perhaps it's easyer to reinstall?
Well, I honestly don't know if that is your best option at this point or not, so I will just leave it for someone with better knowledge to advise you on it.
Of course I agree with Zrubi that Qubes is not shitty Windows, but I do not think reinstalling means that it is.
I suppose that if it is ultimately a hardware problem, then reinstalling may not solve it. But to find this out, I imagine you will have to search the logs (as a starting point).
Try switch to text console, login there and shutdown netvm from there. If this
is some kernel panic or so, you should see the messages.
Any chance to attach serial console to this hardware (real serial, not via usb)?
I had a iptables issue on the netvm which forced me to do many netvm restarts. It seems that it don’t happen anymore. IIRC the system freeze just happened after the dialog which asks to give the netvm another 20 seconds to shutdown. It didn’t show up this time.
Thanks to all for taking the time to answer me and sorry that I can’t give new information now…