Hello guys,
I did a test installation of Suse 11 and after installing Vmware11 I realized that the software startup is much faster compared to 13.2 Opensuse: both in the soft opening, as at startup of virtual machines…
is it being charged as module at startup? how to do this?
thanks…
Don’t know what you mean by “charged as module.”
If someone wanted to identify anything that might be causing latency on bootup on an openSUSE 12.3 and later, you can run systemd-analyze.
TSU
I meant:
installing VMware on suse 11 could be compiled as a service or module ?? - This could explain the difference in load speed …
and if this is possible, how could I do in my Opensuse 13.2 ??
sorry for translate…
google needs to improve … (rsrs)
Thank you for your attention.
Are you trying to describe the difference between running as a service or an app?
AFAIK like any other virtualization technology, VMware ordinarily installs and runs some server and core functionality automatically on boot. Aside from shortening the time to load User Tools like practically everything you see in Workstation because core functionality is a fundamental functionality, this also enables virtual machines to also start up on boot.
Like anything else that might optionally start up on boot, it will take time whether it’s at boot or on demand.
TSU
systemd-analyze
Startup finished in 2.513s (kernel) + 1.586s (initrd) + 16.424s (userspace) = 20.524s
systemd-analyze blame
5.946s vmware.service
4.969s NetworkManager-wait-online.service
2.805s systemd-udev-settle.service
1.557s vmware-workstation-server.service
367ms postfix.service
356ms home.mount
349ms apparmor.service
238ms SuSEfirewall2.service
213ms SuSEfirewall2_init.service
147ms ModemManager.service
143ms display-manager.service
116ms systemd-fsck-root.service
100ms dev-mqueue.mount
100ms sys-kernel-debug.mount
97ms dev-hugepages.mount
85ms plymouth-read-write.service
79ms systemd-tmpfiles-setup.service
75ms systemd-tmpfiles-setup-dev.service
74ms alsa-restore.service
69ms bluetooth.service
68ms NetworkManager.service
67ms vmware-USBArbitrator.service
66ms systemd-user-sessions.service
63ms avahi-daemon.service
61ms polkit.service
58ms wpa_supplicant.service
46ms nscd.service
40ms udisks2.service
40ms systemd-udev-trigger.service
37ms systemd-journald.service
34ms rc-local.service
32ms systemd-logind.service
30ms rtkit-daemon.service
30ms systemd-modules-load.service
24ms lvm2-lvmetad.service
24ms iscsi.service
24ms user@1000.service
24ms dm-event.service
22ms cycle.service
18ms plymouth-start.service
18ms systemd-random-seed.service
17ms systemd-vconsole-setup.service
12ms dev-disk-by\x2duuid-ff94472f\x2daf96\x2d4cd6\x2db6f4\x2d60bdd7b947
12ms systemd-readahead-replay.service
11ms systemd-udev-root-symlink.service
10ms systemd-readahead-collect.service
10ms systemd-udevd.service
9ms lvm2-activation-early.service
9ms upower.service
9ms kmod-static-nodes.service
9ms lvm2-activation.service
8ms systemd-sysctl.service
7ms systemd-journal-flush.service
7ms auditd.service
5ms systemd-update-utmp.service
5ms systemd-remount-fs.service
4ms systemd-backlight@backlight:acpi_video0.service
4ms systemd-update-utmp-runlevel.service
3ms systemd-rfkill@rfkill0.service
3ms systemd-rfkill@rfkill1.service
3ms systemd-readahead-done.service
1- opening vmware only:
time vmware #
(vmware:5082): Gtk-WARNING **: product-register: missing action product-register
(vmware:5082): Gtk-WARNING **: product-register: missing action product-register
(vmware:5082): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-0’ to action group ‘Snapshot’
(vmware:5082): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-1’ to action group ‘Snapshot’
(vmware:5082): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-2’ to action group ‘Snapshot’
(vmware:5082): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-3’ to action group ‘Snapshot’
real 0m35.270s
user 0m5.311s
sys 0m1.849s
2- opened Vmware and start one virtual machine, I turned off the virtual machine in grub …
time vmware
(vmware:5779): Gtk-WARNING **: product-register: missing action product-register
(vmware:5779): Gtk-WARNING **: product-register: missing action product-register
(vmware:5779): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-0’ to action group ‘Snapshot’
(vmware:5779): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-1’ to action group ‘Snapshot’
(vmware:5779): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-2’ to action group ‘Snapshot’
(vmware:5779): Gtk-WARNING **: Refusing to add non-unique action ‘snapshot-mru-3’ to action group ‘Snapshot’
real 1m14.245s
user 0m8.927s
sys 0m3.018s
any comments???
Thanks.
Given today’s technology, are you really concerned about a 20.524s bootup time?
Then,
I’m not sure about the GTK warnings, I don’t know if they’re significant or not…
And if you have a specific question, then you might ask it…
TSU
Yes, my bootup team is the same. My HD is SSD 
did you see?
My measure of time of opening of VMware? - “Item 1”
My Vmware + boot opening time measure of my virtual machine (to arrive at Grub) ??? - “Item 2”
well, I assure you that this same procedure in the Suse11 (both x64 in my C2Duo P8600 with 6GB of RAM and the same Vmware 11) is 5x smaller!
unfortunately already I removed it and I can not make an accurate measurement and post here.
The difference is so great that I thought it might be a lack of fit in my Opensuse - (remembering that the burden of Suse11 took a little more), so I created this post.
any idea what could be causing this difference?
On 2015-09-02 19:56, rogeriopaju wrote:
> any idea what could be causing this difference?
Please post the result of:
systemd-analyze critical-chain
And please do so inside code tags. It is very important you post inside
code tags. Use the ‘#’ button in the forum editor
http://susepaste.org/images/15093674.jpg
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))