Search results

Hi all!! :D According to you it's still too dangerous put in production Proxmox 2 RC1? Thanks

Hi I read you made a VDI structure with WinXP and openthinclient. Can you tell me about? Thanks Stefano

Re: weird problem and kernel panic after uping to 1.9 I confirm Win2k can run virtio net without any problem. I have a production server up smoothly since 2 years :-D

I tried too.... on 2 production machine this night. Also in my case backups have worked without issue :-D

So in 3.0.37 do you remove "--skiplock flag" and added "sleep 1"?. I'm waiting pixelplumber results :-D

Ah. In http://bugzilla.openvz.org/show_bug.cgi?id=1878 Kir Kolyshkin suggested a solution "Available in vzctl >= 3.0.28". So I thought it was yet available 3.0.27 has some kind of patch to this problem?

Could't be better build a package with safe 3.0.28 package?

No, are production machines.... I cannot test anything :-D

I confirm: Tonight, using old versions of vzdump and vzctl, backup jobs run fine as usual. Thanks to all.

In the meantime downgrade of vzdump and vzctl works for chance :-D

old version no. Perfect as usual. New version have the error. "vzdump --quiet --stop --compress --storage backup_sab 102" command that launch manually (the same of /etc/cron.d/vzdump)

Just tried with vzctl_3.0.24-1pve4 and vzdump_1.2-11: all OK. So it's a problem of new version/s

I tried also shutdown, reboot, reinstall (after a --purge) vzdump and vzctl. I'm tryng now downgrading of these packages. The problem is that server are production server :-(

Just tried. Manually no problems at all. Stop and start like a charm

pve-manager: 1.8-17 (pve-manager/1.8/5948) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-33 pve-kernel-2.6.32-4-pve: 2.6.32-33 qemu-server: 1.1-30 pve-firmware: 1.0-11 libpve-storage-perl: 1.0-17 vncterm: 0.9-2 vzctl: 3.0.26-1pve4 vzdump: 1.2-12 vzprocps: 2.0.11-2 vzquota: 3.0.11-1...

Hi to all. I have two Proxmox setup, up to date. In last 4 days, till last upgrades of vzdump , backup of openvz container fail. The method (set by web interface) is vzdump --quiet --stop --compress. /var/run/vzdump.lock and /etc/cron.d/vzdump.lock are not deleted, and the backup log end (for...

I can only test on that production server. No other dongles :-D it's so unstable qemu-server-0.13.0 ?

There are differencies regard LPT in new version of qemu-server? It's compiled the support? Thanks

Update: I try change port settings to EPP and SPP: nothing I checked everything (permission, ovner, symlinks) in version proxmox-ve-2.6.18: the same of proxmox-ve-2.6.32. In the VM the LPT1 appers, but the dongle is not reached

Hi to all. I have taken advantage of this holidays to migrate a production environment of Proxmox from proxmox-ve-2.6.18 to proxmox-ve-2.6.32 Now it's pve-manager: 1.6-5 (pve-manager/1.6/5261) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.6-25 pve-kernel-2.6.32-4-pve: 2.6.32-25...