How about Pre-config VM, OS-specific drivers?

[jnovax]

Hi all,

I have two suggestions that would make user love proxmox more
(like me )

Firstly, I don't see any significant change after selecting an OS (Full KVM mode).
It will be better if configuration of OS change after an selection has been made.
For example: we can recommend user by applying default values
If OS is Windows 2003 Enterprise 64 bit
RAM: 1024MB
Hard disk: Virtio - 20GB (tom told me that 2003 works best with Virtio)
Note: The feature is really easy to implement yet nice to user.

Second recommendation is about OS-specific drivers. Why don't we attached these driver into proxmox and update via apt? Depends on the guest OS, we could suggest user to install this or that driver.
Note: Although I don't know whether we could detect what OS is (in case users select Other OS), it's nice to include this feature.

In addition to these question, I wonder why we reserve too much space for Proxmox root (about 50GB in my system)?

 

[tom]

Hi all,

I have two suggestions that would make user love proxmox more
(like me )

Firstly, I don't see any significant change after selecting an OS (Full KVM mode).
It will be better if configuration of OS change after an selection has been made.
For example: we can recommend user by applying default values
If OS is Windows 2003 Enterprise 64 bit
RAM: 1024MB
Hard disk: Virtio - 20GB (tom told me that 2003 works best with Virtio)
Note: The feature is really easy to implement yet nice to user.

yes, not that important for us now.

Second recommendation is about OS-specific drivers. Why don't we attached these driver into proxmox and update via apt? Depends on the guest OS, we could suggest user to install this or that driver.
Note: Although I don't know whether we could detect what OS is (in case users select Other OS), it's nice to include this feature.

In almost all Linux distributions they are included anyway already and inside Windows its not possible to include them in the repository (we need to check the license of these drivers first, only GPL is possible to distribute on the CD/repository).

In addition to these question, I wonder why we reserve too much space for Proxmox root (about 50GB in my system)?

you can specify the size of root and swap by providing these values on the boot prompt (before you install). but it make sence to have space on root, depends on how you configure vzdump (backup).

 

[jnovax]

In almost all Linux distributions they are included anyway already and inside Windows its not possible to include them in the repository (we need to check the license of these drivers first, only GPL is possible to distribute on the CD/repository).

I think at least we could support a way for user to do this.
For ex: user install 2k3 OS, virtio -> a link of virtio driver for 2k3 will be shown -> user click on that link -> a process downloads driver (might be in image format), attach it to cdrom and leave the rest for user.

you can specify the size of root and swap by providing these values on the boot prompt (before you install). but it make sence to have space on root, depends on how you configure vzdump (backup).

As I know, the installation of Proxmox is totally covered in GUI, how can I declare these settings before installing?

 

[tom]

I think at least we could support a way for user to do this.
For ex: user install 2k3 OS, virtio -> a link of virtio driver for 2k3 will be shown -> user click on that link -> a process downloads driver (might be in image format), attach it to cdrom and leave the rest for user.


As I know, the installation of Proxmox is totally covered in GUI, how can I declare these settings before installing?

see http://www.proxmox.com/forum/showpost.php?p=10003&postcount=3

 

[jnovax]

see http://www.proxmox.com/forum/showpost.php?p=10003&postcount=3

Thank you for your help, but I don't know why couldn't we show this settings as an option in installation process? specify it directly take a risk of too small or not optimized values.

Ex: user can set "Free space for root",...

 

[tom]

Thank you for your help, but I don't know why couldn't we show this settings as an option in installation process? specify it directly take a risk of too small or not optimized values.

Ex: user can set "Free space for root",...

you are right: specifying it directly could lead to not optimized values. And therefore the installer calculate it based on the total disk size automatically.

so what do you want here? we have an automated calculation (optimized values based on the total disk size) and the possibility to specify it by hand.

 

[jnovax]

you are right: specifying it directly could lead to not optimized values. And therefore the installer calculate it based on the total disk size automatically.

so what do you want here? we have an automated calculation (optimized values based on the total disk size) and the possibility to specify it by hand.

If the installer calculate it automatically, it have no information about user's need.
If user calculate it by themself, they don't know how to do it well.

What I want here is a GUI to support user while installing software, you can give them a default value, a limit, a range or anything could guide them to go to the destination without worry.

I think it's the reason why we need an installation wizard.

 

[tom]

If the installer calculate it automatically, it have no information about user's need.
If user calculate it by themself, they don't know how to do it well.

What I want here is a GUI to support user while installing software, you can give them a default value, a limit, a range or anything could guide them to go to the destination without worry.

I think it's the reason why we need an installation wizard.

The goal is to have a fast installation without too many questions. Our experience is that in the time of installation 99 % of the users do not know what partition scheme is optimal for them - so in most cases its better to do it automatically to prevent wrong decisions. The new flexible storage model (introduced in 1.4) gives a lot of flexibility afterward. And again, you can still specify preferred values on the boot prompt.

 

[migomez]

The goal is to have a fast installation without too many questions. Our experience is that in the time of installation 99 % of the users do not know what partition scheme is optimal for them - so in most cases its better to do it automatically to prevent wrong decisions. The new flexible storage model (introduced in 1.4) gives a lot of flexibility afterward. And again, you can still specify preferred values on the boot prompt.

Tom,

I agree with Jnovax on this issue.

You said 99% of users do not know the partition model they want to use, i am sure you are referring to regular linux users.

Your system is used by sysadmins, and as a sysadmin (and having 4 servers using Proxmox ve), I like to be in control, as well as, all the other sysadmin out there (in that case your 99% number will go down).

It will be a nice feature if you add this function to the GUI, it will make things easier for everybody.

In the other hand, as you say, we can define the values a boot time.

Miguel