Search results

you don't need a special config file vmbr0 will be your WAN connected with eth0 of the host vmbr1 will be your internal network, so you have on the pfsense guest vmbr0 and vmbr1 connected on the xp/linux client you just need vmbr1 and in the VM you assign the IP 192.168.1.2 and then connect with...

thats not gonna work you have to have a VM that can reach the private ip of pfsense first, i.e. a small xp or linux client that can reach the default ip 192.168.1.1

that would be very nice, thank you

the same problem as in 2012 R2 http://forum.proxmox.com/threads/16206-Windows-Server-2012-R2-and-0x0000005D-Error hopefully sometime it will be solved with the default cpu type

hi, i have troubles installing Windows Server 2012 R2 on an actual PVE System. Every time the VM boots from the win2k12r2 iso i get the following error: (immediately after the windows logo appears the first time) Your PC needs to restart. Please hold down the power button. Error Code...

ah sorry, damn threaded mode, i must have missed it thanks

are the problems with the latest updates fixed or do i have to do some steps manualy when i update to 2.3? thanks

in the meantime i did a test with a better filled guest and i can't complain INFO: transferred 644245 MB in 7119 seconds (90 MB/s) INFO: archive file size: 231.79GB INFO: Finished Backup of VM 101 (01:58:43) but with pvetest2.3 a new unknown pci device appeared in the device manager PCI Slot 3...

i have no problem on my R420 with H710i

ah, thx, good to know i think i have to try a backup-szenario with a full filled guest, cause the rising time from 5 minutes to 25 is heavy (at the test with 30gb in the guest) is there a chance that this will speed up a little bit in final? (i'm thinking of my other PVE Hosts where i backup...

yes, as im still in the test phase i did what you ordered ;) in the case of the "empty" guest, it got better INFO: starting new backup job: vzdump 102 --remove 0 --mode snapshot --compress lzo --storage nem --node pvenem01 INFO: Starting Backup of VM 102 (qemu) INFO: status = stopped INFO...

This week i installed a new PVE Host in a new environment with PVE 2.2 ISO and all updates and i found an annoying behaviour in the backup/restore-procedure. I created a new guest with 2 disks, one 400GiB and one 200GiB and even if i start a backup of the complete empty vm it takes about...

thx, thats a real nice workaround :)

is there any chance that this will work in future with the actual pve-qemu-kvm version? (cause i need acronis quite often) what are the cons if i downgrade to 1.1-8? thanks in advance edit: i tried it with 2010, 2011, 2012 and 2013 iso images as well as the acronis echo server

perfect, thank you for you explanation

fine, thank you one additional question: is it by design that now qcow2s are as big as they are defined? in the past they grew in size only when necessary?

hello, no, i haven't done any manual entries in these config file cause the vm is only 2 days old bootdisk: sata0 cores: 2 ide2: pve:iso/en_windows_server_2012_x64_dvd_915478.iso,media=cdrom,size=3608574K memory: 4096 name: dc03 net0: e1000=62:DB:64:0D:FF:06,bridge=vmbr0 onboot: 1 ostype...

hi, it seems like there is a restore bug in 2.2 i have a cluster of 3 nodes and backuped the system 210 on node 2 after the backup was successfull i did a restore on node 3 with the id 303 the restore itself was ok but the machine couldn't be started cause in the config file the wrong hdd...

3 months later i have a solution :D (more or less) last week freenas 8.3 was released and with this release the support of zfs v28 after installing the update and upgrading the zfs pool from v15 to v28 the backup speed was as good as with PVE1.9 und freenas8.2 so for me it seems like there is an...

my probably last status-update unfortunately illumian won't work on my nas server, there are some driver issues with the NICs so i installed freenas 8.2.0 beta4 completely new and made a new raidz1 and the poor performance kept i even tried it with a raid-1 log device, nothing changed so i...