online migration resets uptime

[mir]

Hi all,
Only me experiencing that the VM's uptime is reset in the GUI?

Just migrated to test:
Uptime in gui


Uptime as shown inside the VM:
mir@ns1:~$ uptime
18:19:05 up 3 days, 22:52, 1 user, load average: 0.00, 0.00, 0.00

Is this correct behavior?

 

[dietmar]

Uptime on GUI is the time from starting the kvm process (this starts on each migrate).

In future, the plan is to use qemu guest agent to get those values directly from the guest.

 

[gbr]

Sorry to bring up an old thread, but do you know when this will be completed and available to users?

Gerald

 

[dietmar]

Sorry to bring up an old thread, but do you know when this will be completed and available to users?

Just track the announcements.

 

[gbr]

Thanks for the quick response.

Is it policy for Proxmox to not specify possible release dates, or does your response mean 'coming very soon'?

Sorry for not quite understanding.

Gerald

 

[dietmar]

Is it policy for Proxmox to not specify possible release dates, or does your response mean 'coming very soon'?

We do not specify the release date of every single feature.

 

[gbr]

Thanks for the reply.

 

[m.ardito]

Thanks for the reply.

I think that it would be nice (good, pleasant) to have a more general roadmap, letting users know what developers are working on (or not), even if the feature has no release date... (or something like "planned for the future") and if one feature has an expected release date (or month, or quarter, or year), it could be easily stated there, and people will be happy. And if a date changes, or becomes undetermined, it will be perfectly understandable.

It is not about promises to be maintained, it is some kind of communication, letting people know what's going on in the near or distant future, or never, without the need to look at (and understand) git commits... something like http://www.spice-space.org/features.html

I like nice people more ;-)

Marco

 

[tom]

I think that it would be nice (good, pleasant) to have a more general roadmap, letting users know what developers are working on (or not), even if the feature has no release date... (or something like "planned for the future") and if one feature has an expected release date (or month, or quarter, or year), it could be easily stated there, and people will be happy. And if a date changes, or becomes undetermined, it will be perfectly understandable.

It is not about promises to be maintained, it is some kind of communication, letting people know what's going on in the near or distant future, or never, without the need to look at (and understand) git commits... something like http://www.spice-space.org/features.html

I like nice people more ;-)

Marco

the "future features" on the spice page looks nice, but some seems to be not possible in near future (e.g. within one year). we only list features on our roadmap which we plan to integrate soon.

Just to note, Martin just updated http://pve.proxmox.com/wiki/Roadmap

 

[m.ardito]

this is also a nice approach...
http://www.webodf.org/about/roadmap.html

Marco