I'm not sure if this was something I did or if it's a bug.
A reboot resolved it.
I just finished restoring a snapshot & afterward any VNC console I opened showed only a solid white screen with 3 or 4 of the top-bar buttons greyed out. Options was one that appeared to remain pressable, although I didn't try.
I was in a panic & didn't think to get a screenshot. Or to switch browsers or VNC viewers. I still haven't taken the time to figure out how to use something like TightVNC.
I've recently upgraded to pve 1.5/4627 from 1.4/4390 and use kernel 2.6.24.9-pve.
The restored .tar was 79GB & it took approximately 100 minutes to recreate a 100GB VM. All VMs were stopped during in hopes of speeding things up.
During the process I watched the home screen of the web interface, syslog & top. While dd was churning away, in an attempt to consolidate screens, I installed htop about halfway through.
I started 1 tiny VM a few times & looked at it's console, so I know it worked at least for awhile during the first half. Also were 2 30-second network outages while I tinkered with the router.
A quick diversion to an unrelated item- aptitude wanted to remove the kernel saying it's not required by anything. It doesn't seem right so I figure I'll mention it.
The console(s) were working prior to installing htop- I didn't try after it was installed to know if that's what did it.
After rebooting the host machine the console was back to normal.
Apparently the VMs that didn't display were indeed running, as evidenced by the guest wanting to boot into safe mode when I could see.
Assuming as a result of the host's shutting down to reboot while the guest was starting up & not because of the restore operation.
A reboot resolved it.
I just finished restoring a snapshot & afterward any VNC console I opened showed only a solid white screen with 3 or 4 of the top-bar buttons greyed out. Options was one that appeared to remain pressable, although I didn't try.
I was in a panic & didn't think to get a screenshot. Or to switch browsers or VNC viewers. I still haven't taken the time to figure out how to use something like TightVNC.
I've recently upgraded to pve 1.5/4627 from 1.4/4390 and use kernel 2.6.24.9-pve.
The restored .tar was 79GB & it took approximately 100 minutes to recreate a 100GB VM. All VMs were stopped during in hopes of speeding things up.
During the process I watched the home screen of the web interface, syslog & top. While dd was churning away, in an attempt to consolidate screens, I installed htop about halfway through.
I started 1 tiny VM a few times & looked at it's console, so I know it worked at least for awhile during the first half. Also were 2 30-second network outages while I tinkered with the router.
A quick diversion to an unrelated item- aptitude wanted to remove the kernel saying it's not required by anything. It doesn't seem right so I figure I'll mention it.
The console(s) were working prior to installing htop- I didn't try after it was installed to know if that's what did it.
After rebooting the host machine the console was back to normal.
Apparently the VMs that didn't display were indeed running, as evidenced by the guest wanting to boot into safe mode when I could see.
Assuming as a result of the host's shutting down to reboot while the guest was starting up & not because of the restore operation.
