Search results

@frankar I think you used this, right? (I've just seen it) https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster

@frankar How did you install Proxmos through Debian 10? I'm just bought a new server for one year and now they don't have any Proxmox listed in the install options...

Hope you're ok. If I can help you in any way, just tell me.

@wolfgang Maybe it would be nice to have a sticky post in the forum. I've lost two weeks trying to debug this and the information is between 3 different posts in the forum. Just a suggestion. Thanks for the effort to track down the issue.

Can anyone share the upstream bug report to search for some info? Is this just people that cannot start kvm machines? I'm having problems on a Win10 machine that gives me blue screens from time to time and I cannot seem to find a reason. Don't know if this could be the problem. Thanks!

Yes, I do: root@ktechoubuntu:/var/www# ps axwww | grep qemu 956 ? Ss 0:04 /usr/sbin/qemu-ga --daemonize -m virtio-serial -p /dev/virtio-ports/org.qemu.guest_agent.0

Yes, it's a real production server. By PVE logs I mean "logs in the proxmox host". Yes, I also give a look to syslog and dmesg. This happened this night: Nov 23 04:30:03 ns204651 vzdump[10705]: INFO: starting new backup job: vzdump 104 100 --mailto ktecho@ktecho.com --mode snapshot --compress...

Hi there, Back a few months ago I started having problems with my Proxmox 4.4 server: corrupted disks while doing or deleting snapshots / backups and things like that. Because of this and the need to go for LVM-thin to improve snapshots capabilities, a few weeks ago I upgraded to 5.1 by using...

Some users are reporting massive improvements in Win10 machines by changing discs from VirtIO to IDE. I still don't know how to do that, but if you know, maybe you can try. As you said, in some place Proxmox recommends installing ballooning driver and in another place, they recommend not to use...

Hi! Do you know a "howto" on changing from VirtIO to IDE? Thanks!

Wow... didn't read that reporter is using Proxmox 4.4 with an old kernel. So maybe a different problem, a change in Windows 10 or a problem with VirtIO drivers...

The same is happening to me. Did your CPU goes to 100% too in Proxmox admin? I'm getting crazy to try and fix this. I tried disabling ballooning, but it's still failing. I was thinking the problem could be this one: https://bugzilla.kernel.org/show_bug.cgi?id=197449 I've contacted the guy...

Thanks, will reinstall using official ISO.

root@nsxxxxxx:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content rootdir,images,iso,vztmpl maxfiles 0 dir: backup path /vz/backup content backup maxfiles 2 shared 0 dir: backupDiarios path /vz/backupDiarios...

root@nsxxxxxx:~# pvesm lvmthinscan pve root@nsxxxxxx:~# Does this means that I don't have LVM-thin? I installed Proxmox 5 from OVH templates (not the ZFS beta template, but the standard one). I thoght the default was LVM-thin...

I do that yesterday and it started working ok, so I thought "wow... cannot be true...". And today it started failing again. Sometimes it fails 6 to 8 times... so I leave it for 10 to 15 seconds and the next time it woks ok. So weird!

Thanks for your reply. I just installed Proxmox 5.0 and then upgraded to 5.1, so I should be using LVM-thin by default, right? How can I see if I'm using LVM-thin, and if yes, how can I create containers that uses its capabilities? Thanks!

Hi, I'm having problems trying to snapshot my newly created Ubuntu LXC container. It was installed using the 17.04 template and then upgraded to 17.10. I don't have bind mounts that I know of: root@ns2xxxx:~# pct config 110 arch: amd64 cores: 4 hostname: ubuntu2018 memory: 8192 net0...

Hi, I've had a problem for years in Proxmox 3 and Proxmox 4.x. But a few weeks ago I made a new Proxmox 5.1 install in a new machine (not upgrade) and the problem is there, so I don't know why a cannot read more people with the problem in the forums. When I go to the proxmox url, I already...

@dcsapak when are you adding ubuntu_17.10 images? I just did "pveam update" but it's not available yet.