Test kernel worked ok.
uname -a
Linux h01 4.13.4-1-pve #1 SMP PVE 4.13.4-26~vmxtest1 (Wed, 25 Oct 2017 10:59:18 +0200) x86_64 GNU/Linux
Today, I installed the same kernel number, updated from repository and I'm having problems with KVM again:
uname -a
Linux h01 4.13.4-1-pve #1 SMP PVE 4.13.4-26...
Thanks Fabian. I prefer don't see an error on boot, but I'm quiet if it can be safely ignored. Thanks again. A personal doubt, what's the reason of this error?
I had problems too with a HP ProLiant ml110, with a Intel Xeon 3040 (no nmi support).
I installed test kernel and everything ok with VMs.
My server is still showing this error at booting:
/sbin/modprobe failed: 1
Can't process LV pve/data: thin-pool target support missing from kernel?
Can't...
Thanks Dietmar.
I'm using ext4 and LVM.
In this thread (Proxmox 4 / LXC: Chroot instead of raw images?) you recommend
With the problem of no disk quota, but a al least I can see my CT files at /var/lib/vz/private/<ct_id>
Maybe, some people like me will apreciate the posibility of choosing...
Hi,
I'm using Proxmox since 2.x version, and always has been using OpenVZ except to virtualize my only one Windows server.
Today, I installed Proxmox 4.x beta in a server. I'm new to LXC and I have some doubts:
- Is it posible to change dinamically disk size? Using Proxmox web interface it's not...
Thanks Henry,
I have a Debian 8 running on a Proxmox 3.x server, I upgraded a Debian Squeeze container to Jessie without any problem (of course still using sysvinit).
There is two beta containers of Debian 8 at OpenVz site, I don't know if these templates can be used on Proxmox 3.X (maybe they...
1. Install deb-mirror on a host conected to Internet.
2. Create a file with this, in /usr/local/bin and do it executable.
#!/bin/sh
exec debmirror \
--progress \
--verbose \
--nosource \
--host=download.proxmox.com \
--root=debian \
--dist=squeeze \
--section=pve \...
Hello again:
This bug has been marked as FIXED on the bugzilla of openvz.
http://bugzilla.openvz.org/show_bug.cgi?id=2275#c25
Please, dietmar or another friend of the Proxmox Staff Member, tell us when this fix be implemented on testing or stable branch of Proxmox.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.