[arch-general] VirtualBox 6 on 4.20 - Anybody seeing guests become unresponsive after several hours?
All, I have a number of virtualbox guests I run from my Arch host and have for a number of years. Since update to Virtualbox 6.0 (using the following AUR packages) https://aur.archlinux.org/packages/virtualbox-bin/ https://aur.archlinux.org/packages/virtualbox-ext-oracle/ after the guests have been running for several hours, they become totally unresponsive (both Linux and Windows guests). To the point that typing 'ls' results in nothing but echoing back the path where the command lives. $ ls /usr/bin/ls .... Shutting down the desktop and moving back to the normal terminal where login: is display, attempting to login by entering a username and pressing enter does nothing but timeout and spit the uname information back to the screen and redisplay the login prompt. Regardless of guest type, a hard poweroff is required to shutdown, as the guest is otherwise unresponsive. VBoxManage controlvm "name" poweroff is required to actually terminate the guest. Restarting appears to go just fine. Looking at the virtualbox logs, there really isn't anything telling. There are a couple of VBVA and VRDP messages about display size and color depth, but nothing that stands out as an error. Nothing in the journal of the host that points to anything wrong. Has anyone else seen this with VB 6 (either the Arch or AUR packages)? -- David C. Rankin, J.D.,P.E.
On Thu, Jan 3, 2019 at 1:25 PM David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
All,
I have a number of virtualbox guests I run from my Arch host and have for a number of years. Since update to Virtualbox 6.0 (using the following AUR packages)
https://aur.archlinux.org/packages/virtualbox-bin/ https://aur.archlinux.org/packages/virtualbox-ext-oracle/
after the guests have been running for several hours, they become totally unresponsive (both Linux and Windows guests). To the point that typing 'ls' results in nothing but echoing back the path where the command lives.
$ ls /usr/bin/ls ....
Shutting down the desktop and moving back to the normal terminal where login: is display, attempting to login by entering a username and pressing enter does nothing but timeout and spit the uname information back to the screen and redisplay the login prompt.
Regardless of guest type, a hard poweroff is required to shutdown, as the guest is otherwise unresponsive.
VBoxManage controlvm "name" poweroff
is required to actually terminate the guest. Restarting appears to go just fine. Looking at the virtualbox logs, there really isn't anything telling. There are a couple of VBVA and VRDP messages about display size and color depth, but nothing that stands out as an error. Nothing in the journal of the host that points to anything wrong.
Has anyone else seen this with VB 6 (either the Arch or AUR packages)?
-- David C. Rankin, J.D.,P.E.
I have experienced similar, not lock ups like that but instead VB will report the vm running but it seems unresponsive. Trying to launch them in the foreground causes them to be marked "inaccessible". For anything critical I use KVM so this doesn't really concern me too much. Its an annoyance more than anything else -- Steve Ovens Consultant, RHCA DevOps Red Hat Canada Cell: 519-709-5775
On 1/3/19 1:24 PM, David C. Rankin wrote:
All,
I have a number of virtualbox guests I run from my Arch host and have for a number of years. Since update to Virtualbox 6.0 (using the following AUR packages)
https://aur.archlinux.org/packages/virtualbox-bin/ https://aur.archlinux.org/packages/virtualbox-ext-oracle/
after the guests have been running for several hours, they become totally unresponsive (both Linux and Windows guests). To the point that typing 'ls' results in nothing but echoing back the path where the command lives.
Maybe check if the volume where your VM's disk is stored is running out of space? HTH, DR
On 01/03/2019 12:52 PM, David Rosenstrauch wrote:
Maybe check if the volume where your VM's disk is stored is running out of space?
Thanks DR, but still 379G free on /home, so it should have plenty of space. In fact, none of the filesystems are low yet: Filesystem Size Used Avail Use% Mounted on /dev/md1 50G 21G 29G 42% / /dev/md0 469M 96M 360M 22% /boot /dev/md2 865G 486G 379G 57% /home /dev/md4 2.7T 871G 1.9T 32% /home/data I allocate 2-Core and 2G per-guest (on an 8-Core/32G host), so memory or storage should be fine. It does appear like the VM can't find its volume though. That would correspond with the system not being able to launch 'ls' (or any command). It just sits there running. What's strange is, as posted, the guests are not locked up, they are running and I can close apps, shutdown Fluxbox or KDE, I just cannot launch anything -- sort of like the filesystem is just disconnected so nothing new can be launched (including systemctl poweroff) Strange, I'll keep an eye on it, thanks to all for the feedback. -- David C. Rankin, J.D.,P.E.
Last I was aware VirtualBox has some stability issues with KDE. Maybe, try
Cinnamon or one of the lighter weight desktops.
On Thu, Jan 3, 2019, 8:28 PM David C. Rankin On 01/03/2019 12:52 PM, David Rosenstrauch wrote: Maybe check if the volume where your VM's disk is stored is running out
of space? Thanks DR, but still 379G free on /home, so it should have plenty of
space. In
fact, none of the filesystems are low yet: Filesystem Size Used Avail Use% Mounted on
/dev/md1 50G 21G 29G 42% /
/dev/md0 469M 96M 360M 22% /boot
/dev/md2 865G 486G 379G 57% /home
/dev/md4 2.7T 871G 1.9T 32% /home/data I allocate 2-Core and 2G per-guest (on an 8-Core/32G host), so memory or
storage should be fine. It does appear like the VM can't find its volume though. That would
correspond
with the system not being able to launch 'ls' (or any command). It just
sits
there running. What's strange is, as posted, the guests are not locked up,
they are running and I can close apps, shutdown Fluxbox or KDE, I just
cannot
launch anything -- sort of like the filesystem is just disconnected so
nothing
new can be launched (including systemctl poweroff) Strange, I'll keep an eye on it, thanks to all for the feedback. --
David C. Rankin, J.D.,P.E.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, 2019-01-03 at 12:24 -0600, David C. Rankin wrote:
Anybody seeing guests become unresponsive after several hours?
I think on 4.20, everyone is pretty unrespponsive after a few hours. :P Sorry, couldn't resist. - -- Greetings Ricardo Band https:// www.ricardo.band mailto:// email@ricardo.band xmpp://jabber@ricardo.band -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEhyzgFNiV8yZuI1T5Gp1lfQa1gg4FAlwuqSkACgkQGp1lfQa1 gg5ebg/+JE27mwuAhWMJlYW3M0+DjL6KH2biKxSn+Q2ZTGif9nmapkdOvD/tsE/T CweDXnsvIb3OYsfad2WDQe6qCgZmrpSt9cXdtFAmuxQbH2SxqbEGLJGObXek4ddi WYbAA5FJMeYDGohkCMHGH5DUFdfWRsrAMO56b+fqFhk5uPGc09m+OFwktwi1Jaqi P5g2HE1SsHBiYSfHL4K82YVRsZh9KQ41gGYviFqzzoZX1ssaQPwkTrtm0VYru1oj goa1PU3xwFStqO+pqwtP2p6ewdgtRNv3eVg2J77c4+4g80TvIzl8AOBzEYZ0Tdjf O39UiVOsyKHs0GCPIfEFEUtx3GVY6hThf3iQrbyC8BJwwhxUcJHI0SP11458/qyk bqAt6k7Oxw4MoloiOjaqYadicMI4iNGm4ky6ECToMUjMaGvDCxtNs3GJSvAmhf++ 970ADTj//ArjwQu611MwSRFgbyJfxdIJauw9jAcsjYoDb4F4bO4Xk6GaMJe4YUGG fHLoBxSqjih8jLg6z/t+spPtptekT+4KxmIrr3YIgkeEpG/L0OLll/GzjE3rr/4U bDQblXkYmi0YtSVLT9YVnCP12bs0msS+AztNE16rXdze1ivnApufOuzvD5DrdrVv sO9E1m3x+SqiY/F7QKsGugQhz0c8rOwjfhsLjwy6eMfqLPR4GqU= =xq/f -----END PGP SIGNATURE-----
participants (5)
-
David C. Rankin
-
David Rosenstrauch
-
mike lojkovic
-
Ricardo Band
-
Steve Ovens