Search results

Auch ich habe seit Version 6 massive Probleme mit der Benutzung der Tastatur auf der Konsole, speziell bei Debian-VMs. Sonderzeichen gehen gerne mal nicht, auch springt öfter die Caps-Lock-Taste herein, wenn ich ein beliebiges Zeichen tippe, das weder Buchstabe noch Ziffer ist. Und nicht selten...

No progress here? I just tried it again, installed all available updates and... problem persists. After an uptime of 1 day I shut down all VMs first, then I hit the "Shutdown" button in the web GUI. The server hanged at "reached target shutdown". I waited 45 Minutes - nothing happened. Finally...

Same problem here: After a few days uptime I have shutdown all virtual machines first. Then I used the "Restart" Button in the Proxmox web GUI to reboot the host. The system hangs at "reached target shutdown". After approx. 10-15 minutes the reboot continues.

Yes, the network is well cabled gigabit ethernet, the NICs are Intel PT server grade and everything works perfectly. As I said before: this happens from time to time only. But it happened right at first this morning and led to this annoying "Reached target shutdown"-message. Not even 5 minutes...

Thanks a lot for your efforts to help me. I've tried the proposed workaround "soft": 1) I changed the config file and rebooted while the NFS-server was online > Success. 2) After the reboot (with the soft option active now) I took the NFS server offline and rebooted again after a few minutes...

The simple idea that there seems to be a clear reason and that there might be a workaround or even a solution compensates my frustration. I've tried different shutdown and reboot methods with Proxmox 4.0 and had no success at all. But I'll try again with Proxmox 4.1. By the way: As I already...

I made a fresh install yesterday so everything should be up to date. Before that I tested Proxmox 4.0 for about a month and had shutdown/reboot issues nearly all the time and experienced failures of the WebGui every once in a while. Good question. After the fresh install yesterday the file...

I habe been using several Proxmox versions from 2.x to 3.x and I was (nearly) almost very happy with them. But v4.x drives me crazy. My use scenario: I have a Proxmox standalone server that is running 24/7. The machine is fully encrypted. For backup purposes only I have an additional file...

"Reached target shutdown" is really a big issue for me too. I tried to install proxmox several times on different hardware, using EFI or BIOS. Most of the time neither reboot nor shutdown work: The server hangs with "Reached target shutdown" and I have to use the power button manually.

Now I reinstalled on the same hardware using the same procedure I used last time (installed a fully encrypted Debian 8.2 64 bit first, then installed Proxmox on top of it). The only difference is that I used ext3 instead of ext4. Now the problem seems to be gone. Fingers crossed...

Tested with Win7 and 8, Firefox, PaleMoon, Chrome. As I already said: "Flickering" means that after a few seconds the console disconnects and reconnects very quickly before it finally disconnects. The syslog repeats lots of lines like these::

I'm having the same problem with a fresh installed Proxmox 4.1 using the default self signed certificates. As a result the console window of virtual machines "flickers" in my browser, that means after a few seconds it starts to connect and disconnect quickly several times and then gets finally...

After quite a long time I'm back with the same problem. This time I have installed a fresh non encrypted Proxmox using the standard Proxmox ISO installation media. When I try to snapshot a Debian 8 32 bit virtual machine including RAM the snapshot fails. Formatting...

Sorry, I'm in a hurry, so I will have to continue with the troubleshooting later. Just wanted to report that I was able to take Snaphots of an imported vm with Windows Server 2008 using two cores and 3 Gigs of RAM! But snapshots of a basically identical vm created on the encrypted Proxmox...

Thanks for your reply. This is the conf of the vm with working snapshots (created on unencryptet Proxmox, backupped and restored on encrypted Proxmox): ________________________________________________________________ bootdisk: virtio0 cores: 1 ide2...

Unfortunately for me the problem persists. As described above I have installed Proxmox manually on top of a fully encrypted Debian. This setup has worked flawlessly with versions lower than Proxmox 3.3. Since then my snapshots failed with the symptoms described above. The upgrade to qemu 2.2...

Yes, I have this problem with snapshotting, too. Snapshots seem to work with Windows VMs but fail with Linux (Ubuntu) VMs. Only when I choose not to include RAM Ubuntu snapshots work. For me this problem started with version 3.3 and still exists in 3.4. I thought there might be some problem...

I reported the same issue a few months ago. Only solution I found was to downgrade the three packages you mentioned. I thought that the problem might be fixed after almost half a year, but I was wrong. "aptitude full-upgrade" made my fully encrypted test machine unbootable. And it got even...

I was so lucky that I still had an entry in grub for the old standard debian kernel that was still working. 1) I booted up using the old still working standard debian kernel 2) I made an aptitude remove libdevmapper1.02.1 3) I answered "no" to the proposals how to resolve the conflicts that a...

A newer Proxmox update obviously makes (some?) encrypted systems unbootable. I have been running a fully encrypted Proxmox System (incl. root) for several weeks now without any problems (using a 3ware raid controller). But today I tried to reboot and the reboot failed: Instead of showing the...