Search results

I am researching if I can run Proxmox with a ZFS root nested on a cloud style hosting service like vultr.com who allow me to install from a custom iso eg. Proxmox, instead of a canned distro they provide Their cpuinfo flags are as follows: Flags : fpu de pse tsc msr pae mce cx8 apic...

Ah I see, thanks for noticing that. I have to use external VNC because the noVNC console never seems to work on my Mac and Firefox.

It does in proxmox 3.4 I have been using passwords in the conf for years without error. This is the proxmox wiki page on the syntax I use. https://pve.proxmox.com/wiki/Vnc_2.0

I am getting an error when I try and use the same args, that I use successfully for proxmox 3.4 conf files, in the new 4.0 beta 1 eg. args: -vnc 0.0.0.0:1,ABC123 Gives an error: Running as unit 101.scope. kvm: -vnc 0.0.0.0:1,ABC123: Invalid parameter 'ABC123' So the VM wont start up...

I was looking at that card too. What's the cheapest model in the Adaptec cards that will work with Proxmox? I am after 2 SATA ports for a RAID1 mirror, that's it, not other fancy features as long as it works with Proxmox.

You probably need to do: modprobe ipmi_msghandler modprobe ipmi_devintf modprobe ipmi-si I think /etc/init.d/ipmievd is just a syslog thing.

Finally found out what my problem was: http://serverfault.com/questions/193114/linux-e1000e-intel-networking-driver-problems-galore-where-do-i-start The fix is at the bottom of the linked page, and what a difference it made!

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3 The file in that post is only half the size of the bios.bin it's replacing. Might be truncated?

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3 I am having the same problem on FreeBSD 9.0 how can I roll back to QEMU1.2 where it was working? - Ernie. /EDIT mine did eventually boot, when I clicked on shutdown in the vnc console it continued the boot process from the point it...

Another command which will give you all the kvm VM at once is /bin/ps axo pid,cmd,etime | grep chard 1941 /usr/bin/kvm -id 301 -chard 20-00:01:30 1960 /usr/bin/kvm -id 302 -chard 20-00:01:26 1990 /usr/bin/kvm -id 303 -chard 20-00:01:22 2040 /usr/bin/kvm -id 305 -chard 20-00:01:14...

http://www.drbd.org/users-guide/s-three-nodes.html

Sorry, I can't help you there, I recently updated all my Proxmox servers to 2.1 don't have any 1.9 to test it on.

qm status 101 -verbose | tail -1 | cut -f2 -d":" will give you the uptime of VM 101 in seconds.

The Mac does funny things to mounted file systems, it's sticks all this meta data into each directory which takes time. It should get faster once it's done, also the permissions might slow that process.

The scripts that kick in when you try join a cluster will prevent you from adding a machine that has existing VM's. If you try and force it, the .conf files for the existing VM's will get trashed, and you will be forced to restore from a backup even though the VM will be still running until you...

Native linux as described in this blog http://alexsluiter.com/blog/native-zfs-proxmox

One trick I found for ZFS, to improve the FSYNC rate as reported by pveperf I did a: zfs set zfs:zfs_nocacheflush = 1 Where /zfs was my zfs mount point. Obviously you would do that on the freenas server, my zfs was local on the proxmox machine.

I followed those instructions. I had a two node cluster with a 1TB drive as /dev/sdb in each. /dev/sdb1 DRBD 400GB /dev/sdb2 ext4 600GB local VM backups. The initial sync of the 400GB DRBD partition between the servers took ages, it copies all the garbage blocks too. It ran fine until the...

Sheepdog looks like it might do that. Still not a solution for a DR site joined via a WAN, but good for the LAN in a single datacenter. Sheepdog is in the pvetest kernel, not quite ready yet, but you can play. Here is some info https://github.com/collie/sheepdog/wiki/Getting-Started...

When you do relative tests from a VM vs the host, you have to remember with the VM that you are passing though multiple i/o subsystems with many variables. What you need to work our it exactly how much throughput you need for the VM, and it's nature, is it manly reads or writes, small or large...