Re: [VBox-users] Virtualbox 6.0.0 - Marked Slowdown for Window7 Guests? Linux Guests OK

2019-01-14 Thread David C. Rankin
On 01/14/2019 06:02 PM, David C. Rankin wrote:
> 
>   I straced the actual opening of VirtualBox to change from KVM back to
> Default, and strace writing to stderr blew up, e.g. over 2M of output, just to
> change from KVM to Default, e.g.
> 
> strace: Process 32452 attached
> [pid 32452] futex(0x7fffd1f3e3d8, FUTEX_WAIT_PRIVATE, 0, NULL 
> [pid 32493] execve("/usr/bin/VirtualBox", ["VirtualBox"], 0x7fff9884a800 /* 31
> vars */) = 0

Ooh... Further on, I'm betting the "+++ killed by SIGABRT (core dumped) +++"
shouldn't be there:

[pid 32452] poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3,
revents=POLLOUT}])
[pid 32452] writev(3, [{iov_base="b\0\4\0\6\0@\4", iov_len=8},
{iov_base="RENDER", iov_len=6}, {iov_base="\0\0", io
v_len=2}], 3) = 16
[pid 32452] futex(0x7fffd1f3f468, FUTEX_WAIT_PRIVATE, 0, NULL 
[pid 32493] +++ killed by SIGABRT (core dumped) +++
<... futex resumed> )   = 0
futex(0x2982778, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x2a27454, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x2a27400, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x2a3e7d8, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
read(8, "\372", 1)  = 1
poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}], 2, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\7\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="+\0\1\0", iov_len=4}], 1) = 4
futex(0x7fffd1f3e3d8, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x2982778, FUTEX_WAKE_PRIVATE, 1) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
brk(0x51c1000)  = 0x51c1000


Open a bug report?

-- 
David C. Rankin, J.D.,P.E.


___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe


Re: [VBox-users] Virtualbox 6.0.0 - Marked Slowdown for Window7 Guests? Linux Guests OK

2019-01-14 Thread David C. Rankin
On 01/14/2019 04:14 PM, Daniel Miller via VBox-users-community wrote:
> Not a direct answer to your problem as I haven't encountered it - but as I
> typically use a Windoze computer myself (you can only work so many hours...and
> my games unfortunately don't like penguins) I've had to find a remote solution
> myself.  Originally I would use NX (I still use the legacy 3.5 version) to
> access the VirtualBox server - but I can tell you a working installation of
> phpVirtualBox is a godsend for server administration!  I still use RDC with
> Windows guests (logging into the guest and using "native" services, not using
> the VirtualBox port) for interacting with guest applications.
> 
> 
> Daniel

All ideas welcome.

  I'm beginning to think that since this is Archlinux, there is some default
library or new (feature) of the kernel that is killing VirtualBox,

  I straced the actual opening of VirtualBox to change from KVM back to
Default, and strace writing to stderr blew up, e.g. over 2M of output, just to
change from KVM to Default, e.g.

strace: Process 32452 attached
[pid 32452] futex(0x7fffd1f3e3d8, FUTEX_WAIT_PRIVATE, 0, NULL 
[pid 32493] execve("/usr/bin/VirtualBox", ["VirtualBox"], 0x7fff9884a800 /* 31
vars */) = 0
[pid 32493] brk(NULL)   = 0x2dfc000
[pid 32493] arch_prctl(0x3001 /* ARCH_??? */, 0x7fff34ea9170) = -1 EINVAL
(Invalid argument)
[pid 32493] access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/tls/x86_64/x86_64/libGL.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No su
ch file or directory)
[pid 32493] stat("/opt/VirtualBox/tls/x86_64/x86_64", 0x7fff34ea83b0) = -1
ENOENT (No such file or directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/tls/x86_64/libGL.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file
 or directory)
[pid 32493] stat("/opt/VirtualBox/tls/x86_64", 0x7fff34ea83b0) = -1 ENOENT (No
such file or directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/tls/x86_64/libGL.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file
 or directory)
[pid 32493] stat("/opt/VirtualBox/tls/x86_64", 0x7fff34ea83b0) = -1 ENOENT (No
such file or directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/tls/libGL.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or dir
ectory)
[pid 32493] stat("/opt/VirtualBox/tls", 0x7fff34ea83b0) = -1 ENOENT (No such
file or directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/x86_64/x86_64/libGL.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such f
ile or directory)
[pid 32493] stat("/opt/VirtualBox/x86_64/x86_64", 0x7fff34ea83b0) = -1 ENOENT
(No such file or directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/x86_64/libGL.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
[pid 32493] stat("/opt/VirtualBox/x86_64", 0x7fff34ea83b0) = -1 ENOENT (No
such file or directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/x86_64/libGL.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
[pid 32493] stat("/opt/VirtualBox/x86_64", 0x7fff34ea83b0) = -1 ENOENT (No
such file or directory)
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/libGL.so.1", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directo
ry)
[pid 32493] stat("/opt/VirtualBox", {st_mode=S_IFDIR|0755, st_size=4096, ...}) 
= 0
[pid 32493] openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
[pid 32493] fstat(3, {st_mode=S_IFREG|0644, st_size=233151, ...}) = 0
[pid 32493] mmap(NULL, 233151, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fe0159e
[pid 32493] close(3)= 0
[pid 32493] openat(AT_FDCWD, "/usr/lib/libGL.so.1", O_RDONLY|O_CLOEXEC) = 3
[pid 32493] read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0
\4\0\0\0\0\0"..., 832) = 832
[pid 32493] fstat(3, {st_mode=S_IFREG|0755, st_size=591616, ...}) = 0
[pid 32493] mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x7fe015a4c000
[pid 32493] mmap(NULL, 600048, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fe015948000
[pid 32493] mmap(0x7fe01598a000, 126976, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x42000) = 0x
7fe01598a000
[pid 32493] mmap(0x7fe0159a9000, 86016, PROT_READ,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x61000) = 0x7fe0159a900
0
[pid 32493] mmap(0x7fe0159be000, 114688, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x75000) = 0
x7fe0159be000
[pid 32493] mmap(0x7fe0159da000, 2032, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fe015
9da000
[pid 32493] close(3)= 0
[pid 32493] openat(AT_FDCWD, "/opt/VirtualBox/libdl.so.2", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directo
ry)
[pid 32493] openat(AT_FDCWD, "/usr/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
[pid 32493] read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0
\20\0\0\0\0\0\0"..., 832) = 832
[pid 32493] fstat(3, {st_mode=S_IFREG|0755, st_size=14240, ...}) = 0
[pid 32493] mmap(NULL, 16528, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =

Re: [VBox-users] Virtualbox 6.0.0 - Marked Slowdown for Window7 Guests? Linux Guests OK

2019-01-14 Thread Daniel Miller via VBox-users-community

On 1/14/2019 1:38 PM, David C. Rankin wrote:

On 01/14/2019 02:11 PM, Daniel Miller via VBox-users-community wrote:

On 1/13/2019 6:47 PM, David C. Rankin wrote:

On 01/13/2019 01:35 AM, David C. Rankin wrote:

I don't know whether this is normal or FUBAR -- but it seems to correspond to
every line of dir output once the screen starts to scroll on cmd.exe.

Is this normal??

I probably cut the strace output off a few lines early. The only other line in
the output is:

    futex(0x19431b8, FUTEX_WAKE_PRIVATE, 1) = 1

Do we have a threading issue locked thread causing the issue?

..


So it looks like something is FUBAR with the select/read for win32 guests (I
have no win64 guests to test)

Never saw a specific reply to Bruce's earlier suggestion.  Have you tried
changing from Hyper-V to KVM to see if there's a difference?  Not saying
anything about *should* - but give it a try.

Daniel



Daniel,

   Thank you. I have made the change or virtualization to KVM and the problem
remains exactly the same. Moreover, this seems to be a problem with the 6.0.0
interface when accessed remotely. Why I don't see the marked slowdown with
Linux guests is a mystery. However, simply starting VirtualBox to make the
change to KVM (over ssh -X) is horrendously slow.

   I've often used VirtualBox over ssh to make changes to a guest config. While
it hasn't ever been crisp and snappy that way, at least in the past it was
usable. Now, it is unbearably slow. With no guests running, simply trying to
start VirtualBox over ssh takes 15 seconds just to fill in the guest details
after the window appears. Bizarre.

   If you move your mouse over the guests, there is a 4-5 second delay before
you see the TreeList items highlight. To access anything you have to put the
cursor over the button or selection and wait 4-5 seconds for focus to catch up
and actually make the button ready to be clicked.

   I suspect this is related to the problem I am having with the Win7 guest. I
went ahead and grabbed another strace with the Win7 guest running using KVM
virtualization -- exact same information output on stderr:


..


Not a direct answer to your problem as I haven't encountered it - but as 
I typically use a Windoze computer myself (you can only work so many 
hours...and my games unfortunately don't like penguins) I've had to find 
a remote solution myself.  Originally I would use NX (I still use the 
legacy 3.5 version) to access the VirtualBox server - but I can tell you 
a working installation of phpVirtualBox is a godsend for server 
administration!  I still use RDC with Windows guests (logging into the 
guest and using "native" services, not using the VirtualBox port) for 
interacting with guest applications.



Daniel



___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe


Re: [VBox-users] Virtualbox 6.0.0 - Marked Slowdown for Window7 Guests? Linux Guests OK

2019-01-14 Thread David C. Rankin
On 01/14/2019 02:11 PM, Daniel Miller via VBox-users-community wrote:
> On 1/13/2019 6:47 PM, David C. Rankin wrote:
>> On 01/13/2019 01:35 AM, David C. Rankin wrote:
>>>> I don't know whether this is normal or FUBAR -- but it seems to correspond 
>>>> to
>>>> every line of dir output once the screen starts to scroll on cmd.exe.
>>>>
>>>> Is this normal??
>>> I probably cut the strace output off a few lines early. The only other line 
>>> in
>>> the output is:
>>>
>>>    futex(0x19431b8, FUTEX_WAKE_PRIVATE, 1) = 1
>>>
>>> Do we have a threading issue locked thread causing the issue?
>> ..
>>
>>
>> So it looks like something is FUBAR with the select/read for win32 guests (I
>> have no win64 guests to test)
> 
> Never saw a specific reply to Bruce's earlier suggestion.  Have you tried
> changing from Hyper-V to KVM to see if there's a difference?  Not saying
> anything about *should* - but give it a try.
> 
> Daniel
> 
> 

Daniel,

  Thank you. I have made the change or virtualization to KVM and the problem
remains exactly the same. Moreover, this seems to be a problem with the 6.0.0
interface when accessed remotely. Why I don't see the marked slowdown with
Linux guests is a mystery. However, simply starting VirtualBox to make the
change to KVM (over ssh -X) is horrendously slow.

  I've often used VirtualBox over ssh to make changes to a guest config. While
it hasn't ever been crisp and snappy that way, at least in the past it was
usable. Now, it is unbearably slow. With no guests running, simply trying to
start VirtualBox over ssh takes 15 seconds just to fill in the guest details
after the window appears. Bizarre.

  If you move your mouse over the guests, there is a 4-5 second delay before
you see the TreeList items highlight. To access anything you have to put the
cursor over the button or selection and wait 4-5 seconds for focus to catch up
and actually make the button ready to be clicked.

  I suspect this is related to the problem I am having with the Win7 guest. I
went ahead and grabbed another strace with the Win7 guest running using KVM
virtualization -- exact same information output on stderr:

# cat 20190114-152209_win32_err.log
strace: Process 32255 attached
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
..
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
futex(0x260b1b8, FUTEX_WAKE_PRIVATE, 1) = 1
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
select(10, [9], NULL, [9], NULL)= 1 (in [9])
read(9, "\372", 1)  = 1
..

-- 
David C. Rankin, J.D.,P.E.


___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe


Re: [VBox-users] Virtualbox 6.0.0 - Marked Slowdown for Window7 Guests? Linux Guests OK

2019-01-14 Thread Daniel Miller via VBox-users-community

On 1/13/2019 6:47 PM, David C. Rankin wrote:

On 01/13/2019 01:35 AM, David C. Rankin wrote:

I don't know whether this is normal or FUBAR -- but it seems to correspond to
every line of dir output once the screen starts to scroll on cmd.exe.

Is this normal??

I probably cut the strace output off a few lines early. The only other line in
the output is:

   futex(0x19431b8, FUTEX_WAKE_PRIVATE, 1) = 1

Do we have a threading issue locked thread causing the issue?

..


So it looks like something is FUBAR with the select/read for win32 guests (I
have no win64 guests to test)


Never saw a specific reply to Bruce's earlier suggestion.  Have you 
tried changing from Hyper-V to KVM to see if there's a difference?  Not 
saying anything about *should* - but give it a try.


Daniel



___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe