Search results

the kvm64 bug + freebsd should be fixed with the final host kernel 3.10.

Sure no problem. Can you fill a proxmox bugzilla ? like this, I won't forget it ;)

Hi, this is strange, because "-M pc", is the default configuration of kvm. this can be used to simulate previous qemu hardware implementation (('pc is an alias of last version) # kvm -machine ? Supported machines are: none empty machine pc Standard PC (i440FX...

thanks,I'll update package next week

Re: GlusterFS & Proxmox Future & Issues Hi, vdmk should be use only for compatibility, if you import from vmware. The format is not super fast in qemu, and maybe it can have bugs depend of the version of vmdk. So, use raw, this is the fastest (but don't have snasphot features)

The external raw file is only to save the vm state (memory), if you want to rollback to a running vm. but it's optionnal. Disk data snasphot is internal in the qcow2 file.

from http://ocz.com/enterprise/download/drivers: http://ocz.com/enterprise/download/drivers/oczpcie-centos_rhel_oracle6.x-v4.0.551.x86_64.rpm you can use "alien" to install rpm. (but maybe it's better to decompress it before to see what's inside exactly)

I think you can report bug on dev mailing list, it's better than the forum.

yes sure, edit /etc/pve/datacenter.cfg and add migration_unsecure: 1

Hi, I'm not sure nexenta core have nexentastor api. (only nexentastor community and nexentastor commercial).

Hi, /etc/pve/storage.cfg is an proxmox configuration file....so it's impossible that you don't have this file on your proxmox server... (or your proxmox server install is broken)

The wiki say: " Its not recommended to run on production servers as these packages are not always heavily tested and validated" That doesn't mean that the packages are unstable and not tested ! It's only mean that packages are tested but less time.

Hi, which kernel do you use in your guest ? 2.6.32 is known to have this problem, I recommand your tu use 3.X kernels.

Well, The idea is to have access to disks in real time for any nodes. So you need a shared storage, or replicated storage. Also fo "real HA", (if a node is down, vm are automaticaly restarted), you need 3 nodes mininum and fencing devices.

Hi, I don't understand your setup. This is NAT and not Routing. So with your setup, your vms ips are translated to your host ip (eth0). Do you have tried with my setup ? (without the masquerading)

for upload through the browser, maybe something like : http://www.plupload.com could be great. it's support chunk uploads + html5 (and gpl v2 license)

also: http://wiki.hetzner.de/index.php/Proxmox_VE/en

Hi, I would like to help you, but can you post more informations about your subnets and network config ? Does Hetzner route all theses subnets to a specific ip (your proxmox ip) ? (so you need to route from your proxmox ip to yours subnets). Or can you assign directly theses ips to the vms ...

Hi, the above is wrong, can you repost it ? I have re-read proxmox doc, I think I understand how it should work. This config should work: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address xxx.xxx.164.207 netmask 255.255.255.224...

Yes, I think you didn't have understand the concept of target ;) 1 zvol != 1 target. You can have 1 iscsi target, and multiples zvols (luns) by target. (With classic iscsi on a linux host, you logon to an iscsi target, then you get all luns in /dev/....). Proxmox create 1lun(zvol) for each...