Search results

bump

Well Luca, did you fix the problem yet ? I am facing the same issue on a proxmox 3.4 install that was upgraded from 3.3 (it had zfsonlinux installed previously too, but using the official wheezy repository and not the proxmox one). After upgrade to 3.4 and installing zfsutils from the proxmox...

I'm not a big expert in cgroups. For some reason the nested config is not working inside the lxc container. I tried this reference with an ubuntu 14.04 guest A lxc-start does this: lxc-start -n 6000lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main...

I have a question regarding the new lxc containers in 4.0. I would like to be able to run separate processes inside a LXC container, in their own cgroups, so that a single process cannot take down a container (or the server for that matter). On bare metal this is done using cgroups. On...

A few days passed and no reaction from the developers. I think that this is a possible bug to be addressed in a future proxmox update. Shall I open a bug report or is it enough that I raised the issue here?

There are a lot of licenses out there and it is not the point to discuss here whether it is illegal or not. In fact it is perfectly legal, as it is only the boot media that is tied to be used on the vendor hardware which is selling the oem software. The license itself allows either virtualized...

I'm in a situation where I need some of the ACPI tables of the physical server to be exposed to the guest (for licensing purposes). I know about the SLIC patch for seabios, but it does not apply here. I have a media for windows 2012 server (HP) which refuses to boot on non-hp hardware...

This is confirmed. With UEFI Bios, the efi partition is required anyway. I did a manual repartitioning and created the EFI partition. Then I installed grub and voila: The server booted properly. I am not sure if this was/is a requirement on this server or generic EFI requirement, but I would...

One more hint: Perhaps, the lack of EFI partition on a disk will prevent the server bios from actually trying to boot in UEFI ?

Thank you for replying. The point is, the server will not boot from ZFS root. It will do fine with Ext4. I am not sure if efi is needed or not, but if I boot to debug and try to update-grub and grub-install on the ZFS disks, I get an error that EFI partition cannot be found. I did try the 4.0...

Hi, I've been trying to get proxmox 3.4 to boot from a native ZFS root, to no avail. I will boot from ext3 partition, but not ZFS. I don't see the grub prompt at all. Just a cursor and the server resets itself and starts the boot procedure over and over. This is an HP380 Gen9 using an HP 440ar...

bump. no ideas anyone?

I am experiencing occasional errors during live migration of openvz containers. Some times the container will fail to un-suspend after it has been copied to the new node. The errors I see in the kernel logs are: CPT ERR: ffff88072f840000,5102 :rst_file: failed to fix up file content: -22 CPT...

I would put my money on this too. Actually, I'm so desperate for this that I will try to enable ploop on proxmox 3.2 and see if it works by myself. http://pve.proxmox.com/wiki/Developer_Documentation Might be as simple as recompiling with --enable-ploop on

Perhaps it would be a good idea to start using control groups by default for controlling resources allocated to ceph/gluster and kvm/ct virtual machines. What do you think?

Hi, I'm having issues with disk corruption for glusterfs hosted kvm images. Simply, if a VM is running and I reboot one of the replicas holding the VM disk image, the running VM will start throwing disk errors and eventually die. On a reboot, I see disk corruption. I'm using cache=writetrough...

Sorry about duplicate. Thread is here: https://forum.proxmox.com/threads/18252-KVM-disk-corruption-on-glusterfs

make sure your network works properly, then try mounting gluster by hand. when that works, go to gui.

Hi All, I've set up a distributed-replicated gluster cluster with proxmox nodes and I'm running a few kvm instances on top. I'm hitting a problem during a reboot on one of the nodes, causing the KVM servers to halt and die. My guess is that there is a possible bug with the block device used...

Nice :)