Search results

probably relates to this: http://seclists.org/oss-sec/2014/q2/116

d'oh. yea that would have been a smart idea. oh well

This is guess work on my end, but I guess it went like this: debian disabled the heartbeat extension in openssl and because its just an extension maybe they didnt have to produce a new build, which is why "openssl version" still reports the old build date because the fixed debian package doesnt...

I think this was changed. Most likely because dumpling is the latest fully supported release (until firefly is 1 month past release). emperor is only a community release

CephFS might be finally called stable in Q3 this year: <scuttlemonkey> I think the rough estimate that was given (napkin sketch) was sometime in Q3 <scuttlemonkey> but that's predicated on a lot of other things happening <scuttlemonkey> from a stability standpoint we're actually looking pretty...

Ive actually seen that happen too once on a fresh and vanilla proxmox 3.2 install (from iso, no debian->proxmox). Heres what I put on the wiki about it: NOTE: Due to a bug in debian/apt(?) it may be required to alter the above sources.list entry to say the following, if apt-get complains...

Just out of curiosity, may I inquire about your use case? Because that high a number of cores makes me believe that you're dealing with some sort of HPC system, which generally should not be virtualized. Additionally the most cores on a single actual (i.e. not xeon phi) x86_64 (i.e. not SPARC)...

btw: the stable branch of openssl (0.9.8) in debian 6 is not affected by this vulnerability (neither is SLES11).

One possible reason for that would be that the Ceph cluster does not have quorum. you mentioned it stating HEALTH_OK earlier, but maybe that changed?

Re: Proxmox 3.2 with 3-nodes cluster and ceph server: running openvz/containers possi ceph fs is not production stable yet. You can use Ceph RBD like any other SAN storage: mount one RBD for each node and store its containers in it. This setup won't work with HA though. If you want HA for...

I just set up a a 3node proxmox cluster thats being virtualized by proxmox. While I can't run KVM VMs on this, I can test pve-ceph. I noticed the status on the webinterface saying HEALTH_WARN, not specifying details. I can only speculate, but maybe this display does not have all the possible...

yea I liked the general idea behind that, which is why I outright tried it, but oh well :)

okay 3.10 is not an option, so Ill have to think of something else, thanks.

this seems to be problematic indeed. I was able to get fuse into the container, but don't know how to fix/bypass these: Setting up lvm2 (2.02.98-pve4) ... [....] Setting up LVM Volume Groups... /proc/misc: fopen failed: No such file or directory Failure to communicate with kernel...

Hi, I was trying to set up a testing cluster for proxmox inside proxmox, but I ran into this error: boot.log: Tue Mar 18 00:04:54 2014: Loading kernel module kvm-intel. Tue Mar 18 00:04:54 2014: ERROR: could not insert 'kvm_intel': Unknown symbol in module, or unknown parameter (see...

as far as I know they dont. However vmware has some weird ISO that it automatically boots instead of the actual installer ISO, which then calls the installer iso for OSses it knows and automates the installation process by using certain presets determined by vmware. This is sort of an automation...

as far as Im aware, only a kernel upgrade REQUIRES a VM reboot, since the whole node needs to be restarted to load the new kernel. Upgrades to kvm and qemu-server do not require a VM reboot, but you will not get access to the new features until you completely stop and start the VMs. This is...

Re: KSM-sharing like the 50% in the quoted wiki page suggests, theres a threshold that you need to hit before KSM starts doing anything. KSM requires CPU cycles, so theres no point in running KSM if you have a lot of free memory anyhow

In the Server View, you need to click on Datacenter (left), then on the Storage tab (right side), and Edit the storage you want to place backups on.

regarding you not having any backup targets: the default setting for any storage you add to proxmox is to not include backups as potential content, you need to add that in the storage view