Search results

then why are backups failing, since i moved ISO storage to NFS? FAILED00:00:04volume 'local:iso/debian-503-i386-businesscard.iso' does not exist

hi, why is /boot formatted ext3? it's almost static, so without journal as ext2 it should be fine. does it need to be that big per default 64M-128M should be enough.

works fine again.

editing an article fails with: Internal error From Proxmox VE Jump to: navigation, search Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.

ok, 2.6.18-2-pve works fine without these issues here. even my ssh session kept alive while migrating. another observation i made on kernel 2.6.32-1-pve: suddenly the pings came back (after a long time) but still no ssh: 64 bytes from 192.168.2.21: icmp_seq=1089 ttl=63 time=0.911 ms 64 bytes...

i've got the same symptoms here, but my machines are running on Intel Xeon. summary: * KVM (kernel 2.6.32-1-pve) * shared storage on NFS * VM is ubuntu 9.10 * net is VIRTIO * offline migration works well * after online migration: * VM has high CPU load (being idle) * VNC is available...

i'm not running out of space ;-) it's fine for me if it's in the queue. i'm just adding requests if i see possible improvements for PVE.

no, if i had one, i would have posted it. sorry for the misunderstanding. in the backend just exchange gzip with bzip2 or lzma. the frontend is a bit more complicated, but that's where you are experts. either implement a dropdown box to select a method or give the user a field to enter a...

of course: different compression algorithms implement different trade-off between size and time/load. i want to be able to choose the solution that's best for me. take an ubuntu kvm backup (tar=1.9G): 486M lzma (default options, 18min) 634M bz2 (-9, 5min) 695M gz (your...

hi, it would be great, if you could provide alternate compression methods for backups, instead of just gzip. i'd like to see bzip2 and lzma.

ok, i did a test-install in a KVM and the login-locale is POSIX. you're right an this is not a bug, just ssh inheriting LC_* env vars. they are always set to be like the source i came from...

don't know. as I said: did bare-metal-install, saw wrong locale and setup for en_US.UTF-8. does your installer uses time-zone config for locale? because that's the only choice i made that may refer to german language.

yesterday i did a fresh bare-metal-install using the iso mentioned above. the default locale is de_DE.utf8, while only C, POSIX an en_US.utf8 are generated. sure the solution isn't hard, especially as I prefer the last one, but I would consider this a bug as I expect a fresh install to be coherent.

this bug is still present in current install media (1.5 4627-3)

http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny_on_32-Bit_Processor

hi proxmox team, sorry for posting off-topic, but this message doesn't fit in any forum I'm allowed to post in. until your relocation of this forum I used https://www.prox.../forum/ but your new server isn't configured for encrypted connections. can you please do so again. pille

besides your double assigned IP addresses i'm just wondering if this is a typo ("eth") ...

hi cwells, i'm using the stock debian lenny kernel on my 32bit proxmox installations. linux-image-openvz-686 (2.6.26+17+lenny1) is doing fine without KVM.

hi, it would be a great benefit to be able to upgrade a cluster node-by-node. therefore you'll hava a time where your cluster exists of nodes of different versions (e.g. 1.4 and 1.5). this should be possible to do a smooth upgrade with minimal downtime (just moving the VMs) I don't need fancy...

ok, for the last month we had a total of 60 users (should be unique, since no updates and they actually fetched .deb files). hit rates on Packages.gz are higher, but show same distribution and indicate regular usage. 14 GeoIP Country Edition: FR, France 7 GeoIP Country Edition: DE...