Search results

I stand corrected, I just looked at the wrong files I guess. Thanks Nemesiz for the added post. Here is my /var/log/boot showing that even though my init.d seems to say zfs would come first it did not: Tue May 19 16:31:50 2015: Starting pve cluster filesystem : pve-cluster. Tue May 19...

Yes, of course I checked the logs, but this is all early in the boot process. Nothing that I see in logs / dmesg that offers any insight.

Yes, you would think that would do it, but looking at /etc/rc2.d shows: -rw-r--r-- 1 root root 677 Jul 14 2013 README lrwxrwxrwx 1 root root 18 Feb 18 23:41 S01bootlogs -> ../init.d/bootlogs lrwxrwxrwx 1 root root 14 Feb 18 23:41 S01motd -> ../init.d/motd lrwxrwxrwx 1 root root 19 Feb...

Linux version 2.6.32-39-pve (root@lola) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Fri May 8 11:27:35 CEST 2015 The two built in controllers on the SuperMicro X10DRW-iT board (GREAT BOARD BTW - 2 10G Ethernet) SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller...

Ok, so I have a zfs RAID1 pool for boot on two SSD's and 8 drive ZFS10 pool for storage. Was working fine, could reboot server... until updates today. This had a new kernel, grub updates, zfs updates... Now I reboot and my 8 drive pool does not get mounted before Proxmox decides to create the...

The UI will not allow spaces in these settings even though it does appear you can edit the .conf directly and add options with spaces as long as you put quotes around them. However, as soon as the Web UI notices this it simply wipes all of the settings in the SMBIOS option. Please fix this.

Yes, I realize all of those things. The purpose is that the application server we are needing to use ONLY supports running as a VMWare Image (well at least according to them, I intend to try and just run it KVM direct when it comes). So rather than dedicating the entire machine to this one...

I realize that many times this is not discussed prior to being here. However, I have need of getting a very recent version of qemu / kvm up and running so that we are able to put ESXi inside of a KVM system AND run a 64 bit operating system. We LOVE Proxmox, but currently with limited 3.x /...

I saw some posts related to this, but nothing that offers a solution. We have just installed a new Proxmox 3.4 server and during installation setup the boot SSD's to use ZFS mirrored for them. The installation proceeded without issue and system booted fine. We then went into via SSH to create...

I can confirm that this did work for me and now all nodes are running 3.3! I also have to say that the HTML5 console is AWESOME - great job!

Thanks for the reply. So you have moved systems back over to a 3.3 system from a 3.2 system offline? We have really never had issues with online migration in the past, but I will give this a try. Will have to wait until early hours of the morning as the servers are critical and cannot be...

We recently decided to migrate our Proxmox servers from 3.2 to 3.3. As we have done in the past we used live migration and moved all the running servers off one of the devices, ran the apt-get update; apt-get dist-upgrade and then rebooted the machine. Started moving back the guests and had no...

Thanks for the link, that will help. Guess I missed it since 90% of my machines are containers (only Windows based servers for KVM's) and that is not implemented in the GUI yet. So, I guess the request changes to allow start order between ALL machines - KVM and CT based and GUI configuration...

Is this still not implemented? Sometimes there are server dependencies and we cannot simply make sure the numbers are in the correct order.

Yes, I can confirm this is the case as well. We have now upgraded all of our servers to 3.1 and the issue between them is gone.

Not sure this is the same issue for us as what you linked though the result seems the same. We were previously running all 2.6.32-22 kernels on all of our hosts and had no issues migrating around servers. In fact the remaining ones still running that version, that have not been upgraded this...

We upgraded one of our host systems to VE 3.1 which was just released. Prior to that we live migrated a few containers and a few KVM guests to another server which of course went smoothly with no issues. After upgrading the host, rebooting for new kernel we tried to migrate back the machines...

Thanks for the suggestions. We actually decided to go with updating the the Build 48 drivers across all three servers since these now have specific drivers for Windows 8 (Windows 2012 Server). We have had this running now for about 6 hours with no crashing which is FAR longer than any other...

I would have argued that this is the case as well. However, the 2 machines have NEVER crashed before I started up the third one and I am trying to figure out the cause. The 2008r2 machines both are running the 61.61.101.58000 drivers dated 4/11/2011 and have been for quite some time. They...

Thanks, I knew that I had seen that somewhere, but was not finding it. That answers the 2nd question. Now, how about the crashing 2008 servers? ALL systems are running virtio drivers, just not necessarily the same version. Is that a problem?