Proxmox VE 3.4 released!

Status
Not open for further replies.
Since grub is not installed in the installer image then what you are seeing is the result of a boot initiated from the disk. Eg. your computer/server does not use the usb stick as boot media.
 
But, it was categorically specified in the BIOS that the first boot media is CF, then UEFI disk and then HDD. I tried both with USB stick as well as SD card, in both case that does not boot.

I found https://pcbsd.org/showthread.php?t=23488 which finally leads to the conclusion that it has something to do with the ISO as this bug report https://bugs.pcbsd.org/issues/5830 It is from the FreeBSD-distro but seems relevant.

Since grub is not installed in the installer image then what you are seeing is the result of a boot initiated from the disk. Eg. your computer/server does not use the usb stick as boot media.
 
It is my impression that there seems to be quite a bit of issues with v3.4. To my opinion, quite a few more than on previous version upgrades v3.0 to v3.3. Some issues are old and recurring and some issues have to do with new features.

Although a few experienced users indicated the upgrade was fine, I am still reluctant to upgrade my small 3-node cluster setup (I also use Ceph).

Grub installation issues, browser cache cleaning, noVNC, Spice... and other such issue are well known but are only solved with a workaround (pointing to the solution back to the forum...). Repeating the same thing over and over takes time and as we are all humans, we should look for something easier...

The forum is great but it is quite large. Is there a page showing, other the release notes (low in details) and the bug report (too much technical), what the issues are and what was fixed from earlier versions?

New users or users that do not have a strong linux/proxmox technical background would greatly benefit from such information if it is prominently advertized.

I could start something but I do not feel qualified to properly identify the issues and solutions. I also thing this should be a sticky or even a separate forum where only experienced users would be able to contribute in order to make it an authoritative source of information.

Can anyone at either Proxmox or in the group of senior contributor comment on this proposal?

Thanks.

Serge
 
Try making your usb stick using unetbootin: http://unetbootin.sourceforge.net

1. I used unetbootin in linux and windows in the windows. That did not work and it was categorically stated at http://pve.proxmox.com/wiki/Install_from_USB_Stick#Write_the_ISO_image_to_USB that using unetbootin does not work.

2. Then I tried http://www.osforensics.com/tools/write-usb-images.html as described at http://pve.proxmox.com/wiki/Install_from_USB_Stick#Instructions_for_Windows didn't work either.

3. I then used dd to write with a larger chunk bs=1M as well as different sector sizes (512, 4k, 64k), all of them failed. Fyi, all the usb and sd cards were zeroed by dd before dd'ing the proxmox image.

There must be some glitch (bug) with the ISO, I guess. Any inputs from developers. Thanks!
 
Last edited:
ZFS is for KVM (OpenVZ does not officially support ZFS - although most things works).

Ok, do we know exactly what DOES NOT WORK? Has anyone tested OpenVZ on ZFS?

We are planning to convert a Hyper-V server to Proxmox KVM, but would be great if it could host OpenVZ as well if needed.
 
I have the same problem with UEFI boot from flash drive. Connecting a CD-ROM is a bit difficult a.t.m.

Yep, my guess about the bug with the ISO image is confirmed as of below.

This seems to be the upstream Debian Wheezy problem as found at https://www.debian.org/releases/wheezy/debian-installer/ which reads:

Potential issues with UEFI booting on amd64
There have been some reports of issues booting the Debian Installer in UEFI mode on amd64 systems. Some systems apparently do not boot reliably using grub-efi, and some others show graphics corruption problems when displaying the initial installation splash screen.
If you encounter either of these issues, please file a bug report and give as much detail as possible, both about the symptoms and your hardware - this should assist the team to fix these bugs. As a workaround for now, try switching off UEFI and installing using Legacy BIOS or Fallback mode instead.
Status: More bug fixes might appear in the various Wheezy point releases.


UPDATE: This (https://lists.debian.org/debian-user/2014/03/msg01376.html) could be relevant for proxmox developers as the thread recommends for an installation in expert mode in that case which proxmox does not provide.

Haven't tried with the proxmox installer. Shall try later.
 
Last edited:
I have updated Proxmox and now I'm getting error on vnc console: ClassNotFoundException com.tigervnc.vncviewer.VncViewer. Anyone knows how to repair it?
Did you find anything? I have exactly the same issue and no idea where to look at. Too bad that no developer dives into this question/issue. I'm running a 4-Node Ceph Cluster without issues besides the broken VNC stuff. No-VNC is no option because of the poor keyboard support with mac clients.
 
VZFASTBOOT not working in 3.4

We had an unexpected power loss couple of days ago on one of our Proxmox 3.4 cluster members, and staring at the boot console we realized that VZFASTBOOT (starting all guests without quota, then restarting each for quota calculation) does not work anymore, quota calculation is happening before each guest startup. Total boot took almost an hour, so the guest with the highest ID was offline for that amount of time.

Yes, it is turned on in vz.conf:
Code:
## Disk quota parameters
DISK_QUOTA=yes
VZFASTBOOT=yes

Last time we had an unclean reboot on 3.3 or 3.2, VZFASTBOOT worked without any issues.
 
Last edited:
Hi
I just installed proxmox 3.4 and after fresh installation i cant make any updates, apt-get update doesn`t work
Here is output of apt-get update:
root@proxmox:~# apt-get update
Ign https://enterprise.proxmox.com wheezy Release.gpg
Ign https://enterprise.proxmox.com wheezy Release
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en_US
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
Err http://ftp.pl.debian.org wheezy Release.gpg
Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]
Ign http://ftp.pl.debian.org wheezy Release
Err http://ftp.pl.debian.org wheezy/main amd64 Packages
Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]
Err http://ftp.pl.debian.org wheezy/contrib amd64 Packages
Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]
Err http://ftp.pl.debian.org wheezy/contrib Translation-en_US
Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]
Err http://ftp.pl.debian.org wheezy/contrib Translation-en
Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]
Err http://ftp.pl.debian.org wheezy/main Translation-en_US
Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]
Err http://ftp.pl.debian.org wheezy/main Translation-en
Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]
Err http://security.debian.org wheezy/updates Release.gpg
Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]
Ign http://security.debian.org wheezy/updates Release
Err http://security.debian.org wheezy/updates/main amd64 Packages
Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]
Err http://security.debian.org wheezy/updates/contrib amd64 Packages
Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]
Err http://security.debian.org wheezy/updates/contrib Translation-en_US
Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]
Err http://security.debian.org wheezy/updates/contrib Translation-en
Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]
Err http://security.debian.org wheezy/updates/main Translation-en_US
Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]
Err http://security.debian.org wheezy/updates/main Translation-en
Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]
W: Failed to fetch http://ftp.pl.debian.org/debian/dists/wheezy/Release.gpg Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/Release.gpg Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]

W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages The requested URL returned error: 401

W: Failed to fetch http://ftp.pl.debian.org/debian/dists/wheezy/main/binary-amd64/Packages Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]

W: Failed to fetch http://ftp.pl.debian.org/debian/dists/wheezy/contrib/binary-amd64/Packages Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]

W: Failed to fetch http://ftp.pl.debian.org/debian/dists/wheezy/contrib/i18n/Translation-en_US Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]

W: Failed to fetch http://ftp.pl.debian.org/debian/dists/wheezy/contrib/i18n/Translation-en Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]

W: Failed to fetch http://ftp.pl.debian.org/debian/dists/wheezy/main/i18n/Translation-en_US Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]

W: Failed to fetch http://ftp.pl.debian.org/debian/dists/wheezy/main/i18n/Translation-en Cannot initiate the connection to ftp.pl.debian.org:80 (2001:4070:1::fafb). - connect (101: Network is unreachable) [IP: 2001:4070:1::fafb 80]

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/main/binary-amd64/Packages Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/contrib/binary-amd64/Packages Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/contrib/i18n/Translation-en_US Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/contrib/i18n/Translation-en Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/main/i18n/Translation-en_US Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]

W: Failed to fetch http://security.debian.org/dists/wheezy/updates/main/i18n/Translation-en Cannot initiate the connection to security.debian.org:80 (2610:148:1f10:3::73). - connect (101: Network is unreachable) [IP: 2610:148:1f10:3::73 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.

I dont unredstand this output, I dont use IPv6, I have only Ipv4
Can You help Me ?
 
Status
Not open for further replies.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!