Re: VirtualBox performance

2014-11-14 Thread Mikhail Tsatsenko
14.11.2014 4:33 пользователь "Peter Ross" 
написал:
>
> Hi all,
>
> I am running VirtualBox on a new server (a Dell T620).
>
> Inside is Oracle Linux. I run a Java app and it is very slow to start.
Hi,
In order to utilize multiple CPUs inside virtual machine you have to enable
io-apic setting.
> Memory should not be an issue. I have 32 GB and 8 GB for the VM.
>
> The server has 2 Xeon CPUs with 4 core each (hypertthreated so VBox sees
16 CPUs).
>
> I do not see any difference between using 1 CPU or 16 for the VM..
>
> Interestingly all the host CPUs are 60-70% in system calls when I run it
on 16 CPUs, according to top.
>
> I am tempted to experiment with CPU sets, btw.
>
> I wonder whether VirtualBox and multiple CPUs are a good mix at all..
>
> Do you have any recommendations how to speed up my VM and Java?
>
> Thank you
> Peter
> ___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "
freebsd-virtualization-unsubscr...@freebsd.org"
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash

2014-01-10 Thread Mikhail Tsatsenko
2014/1/10 Derek Schrock :
> On Fri, Jan 10, 2014 at 05:18:24PM +0400, Mikhail Tsatsenko wrote:
>>
>> First of all attach serial console to VM and see if there is any
>> kernel messages printed upon crash.
>>
>> Also there is a possibly similar problem:
>> http://lists.freebsd.org/pipermail/freebsd-stable/2014-January/076772.html
>> ___
>
> FreeBSD/amd64 (freebsd10testing) (ttyu0)
>
> login: Jan 10 08:35:48 freebsd10testing su: dereks to root on /dev/pts/0
> panic: handle_written_inodeblock: live inodedep 0xf80004eb1a00
> cpuid = 0
> KDB: stack backtrace:
> #0 0x808e7dd0 at kdb_backtrace+0x60
> #1 0x808af8b5 at panic+0x155
> #2 0x80ad3c85 at softdep_disk_write_complete+0x1595
> #3 0x80934cb0 at bufdone_finish+0x30
> #4 0x80934b18 at bufdone+0x78
> #5 0x809346c2 at biodone+0xe2
> #6 0x8081c561 at g_io_schedule_up+0x1b1
> #7 0x8081ca5d at g_up_procbody+0x6d
> #8 0x8088198a at fork_exit+0x9a
> #9 0x80c758ce at fork_trampoline+0xe
ok, that is completely different issue
> Uptime: 2m55s
> (ada0:ata0:0:0:0): FLUSHCACHE. ACB: e7 00 00 00 00 40 00 00 00 00 00 00
> (ada0:ata0:0:0:0): CAM status: Command timeout
> (ada0:ata0:0:0:0): Error 5, Retries exhausted
> (ada0:ata0:0:0:0): Synchronize cache failed
> Dumping 306 out of 4073 MB:(ada0:ata0:0:0:0): WRITE_DMA. ACB: ca 00 d8 6c 26 
> 46 00 00 00 00 01 00
> (ada0:ata0:0:0:0): CAM status: Command timeout
> (ada0:ata0:0:0:0): Error 5, Retries exhausted
> Aborting dump due to I/O error.
And that's why you can't get any dumps
For some reason device "disappears" from guest machine. Did you check
VirtualBox logs for something unusual?
>
> ** DUMP FAILED (ERROR 5) **
>
> ___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"



-- 
Михаил
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash

2014-01-10 Thread Mikhail Tsatsenko
2014/1/10 Derek Schrock :
> Using VirtualBox 4.2.20_2 (emulators/virtualbox-ose) on a 9.2-RELEASE
> amd64 4 core (8 CPU with HT) host a FreeBSD 10.0-RC5 amd64 (also tested
> with 3 and 4) VM with 4 allocated CPUs will repeatedly crashes when I
> try to build a pkg repo with poudriere (ports-mgmt/poudriere) via the
> bulk command.
>
> From the VM:
>  root@freebsd10testing:~ # kldstat   #VirtualBox additions loaded (tested 
> with/without)
>  Id Refs AddressSize Name
>   19 0x8020 15f0310  kernel
>   21 0x81a12000 22d50vboxguest.ko
>   31 0x81a35000 543  vboxvideo.ko
>   41 0x81a36000 16d6cdrm.ko
>  root@freebsd10testing:~ # sysctl hw.ncpu
>  hw.ncpu: 4
>  root@freebsd10testing:~ # uname -a
>  FreeBSD freebsd10testing 10.0-RC5 FreeBSD 10.0-RC5 #0 r260430: Wed Jan 8 
> 05:10:04 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>  root@freebsd10testing:~ # poudriere bulk -j testing www/firefox
>  >> Creating the reference jail... done
>  >> Mounting system devices for testing-default
>  >> Mounting ports/packages/distfiles
>  >> Mounting packages from: 
> /usr/local/poudriere/data/packages/testing-default
>  >> Logs: 
> /usr/local/poudriere/data/logs/bulk/testing-default/2014-01-09_19h23m11s
>  /etc/resolv.conf -> 
> /usr/local/poudriere/data/build/testing-default/ref/etc/resolv.conf
>  >> Starting jail testing-default
>  >> Calculating ports order and dependencies
>  >> pkg package missing, skipping sanity
>  >> Cleaning the build queue
>  >> Building 145 packages using 4 builders
>  >> Starting/Cloning builders
>  mount_nullfs: /usr/local/poudriere/data/build/testing-default/03/usr/ports: 
> Device not configured
>  >> Error: Failed to mount the ports directory
>  /usr/local/share/poudriere/bulk.sh: 5: Bad file descriptor
>  Write failed: Broken pipe
>
> At this point the ssh session dies (Write failed: Broken pipe) and the
> VM restarts (watching the console via VNC).  The crash appears to occur
> during the building of the reference jails (one per CPU - 4).
>
> I don't see anything in /var/log/messages, /var/crash/ is empty, and savecore
> doesn't dump any core files.
>
> I've tested this with 2, 3, 4, 5, and 6 CPUs allocated to the VM and it
> crashes every time.  The only way I can have the VM not crash is with 1
> allocated CPU.  I believe there's an issue with VirtualBox and FreeBSD
> 10.0 VM when the VM has multiple CPUs.
>
> I don't think this is a poudriere issue however it's the only way I've been
> able to crash the VM.  I've tried extracting multiple ports trees to different
> locations at the same time thinking it's a disk issue because of the above
> "Device not configured" (The/a disk disappears?) error, the VM didn't crash.
>
> I've tried the same command with a FreeBSD 9.2-RELEASE amd64 4 CPU VM
> under the same host with out any failure/crashes.
>
> Could anyone confirm this with a multi-CPU VM and FreeBSD 10.0RC3/4/5 or
> recommend any methods on how to debug this issue?

First of all attach serial console to VM and see if there is any
kernel messages printed upon crash.

Also there is a possibly similar problem:
http://lists.freebsd.org/pipermail/freebsd-stable/2014-January/076772.html
___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"



-- 
Mikhail
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: time drift w/virtualbox: FreeBSD Host -> FreeBSD guest w/ guest additions active

2013-12-04 Thread Mikhail Tsatsenko
2013/12/4 Marc Fournier :
>
> Why is this such a difficult thing to keep in sync? :(
>
> I have a FreeBSD Host running 4.2.18 … Guest FreeBSD Host has Additions 
> 4.2.18 installed ..
>
> On the Host, I believe all the kernel modules are loaded properly:
>
> # kldstat|grep vb
>  63 0x80c59000 59da0vboxdrv.ko
>  82 0x80e2 29f1 vboxnetflt.ko
> 111 0x80e2e000 3f8a vboxnetadp.ko
>
> On the Guest, again, I believe everything is loaded:
>
> # kldstat|grep vb
>  21 0x80c12000 26585vboxguest.ko
>
> And the VB processes are started:
>
> # ps aux | grep VB
> root  606  0.0  0.1  32244   2144 ??  Ss6:06PM2:09.26 
> /usr/local/sbin/VBoxService
>
> I don’t have ntpd running on the Guest, but have tried it with it running 
> also ...
>
> But, my time is already drifting:
>
> # ssh ruralcatholicradio.com date ; date
> Wed Dec  4 12:01:34 EST 2013
> Wed Dec  4 17:03:17 UTC 2013
>
> So, I login and run ntpdate to bring it back in sync:
>
> # ntpdate time.nist.gov
>  4 Dec 12:04:02 ntpdate[71827]: step time server 66.219.116.140 offset 
> 102.233151 sec
>
> Note that the below is run from the FreeBSD Host that the Guest is running on 
> … same physical machine … we are perfectly in sync:
>
> # ssh ruralcatholicradio.com date ; date
> Wed Dec  4 12:04:32 EST 2013
> Wed Dec  4 17:04:32 UTC 2013
>
> An hour later, we’ve now drifted by almost 2 minutes:
>
> # ssh ruralcatholicradio.com date ; date
> Wed Dec  4 13:07:18 EST 2013
> Wed Dec  4 18:09:16 UTC 2013
>
>
> Its hard to believe that anyone would be using VirtualBox if it time drifted 
> like this regularly, so I figure it has to be something that I’m doing wrong 
> in my configuration …
>
>
> Thoughts?
Please try setting sysctl kern.eventtimer.idletick=1 on the guest machine.

-- 
Mikhail
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Is it possible to install a VirtualBox_Extension_Pack in FreeBSD 9.1

2013-07-25 Thread Mikhail Tsatsenko
2013/7/25 Leslie Jensen :
>
> I'm trying to get USB support in a Windows7 guest under FreeBSD 9.1-RELEASE.
>
> I've read that I need this Extension Pack
>
> Oracle_VM_VirtualBox_Extension_Pack-4.2.16-86992.vbox-extpack
As far as I know Extension Pack can be installed only on linux/win/mac
hosts. There is neither FreeBSD version nor sources available.


> Thanks
>
> /Leslie
> ___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to
> "freebsd-virtualization-unsubscr...@freebsd.org"



-- 
Mikhail
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: VirtualBox GUI: Fix memory size computation (native implementation of RTSystemQueryTotalRam)

2013-06-30 Thread Mikhail Tsatsenko
2013/6/30 Martin Birgmeier :
> VirtualBox on FreeBSD needs an implementation of RTSystemQueryTotalRam.
> I have put together the attached patches, comments are welcome.
Hi,
Thanks for you work.
Are you agree that the patches are under the MIT license? It is
required for sending them upstream.
> Regards,
>
> Martin
>
>
> ___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"



--
Михаил
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: VirtualBox: The value of the Base Memory field on the System page is not complete

2013-06-25 Thread Mikhail Tsatsenko
2013/6/25 kron :
> On 2013/06/25 09:16, Mikhail Tsatsenko wrote:
>> 2013/6/25 kron :
>>> Greetings,
>>>
>>> I'm running virtualbox-ose-4.2.14 on FreeBSD 9.1-STABLE r252094M
>>> amd64. The GUI of VirtualBox cannot create/update virtual box
>>> definitions (the *.vbox) files. The scrollbar and the form field
>>> for "Base Memory" are broken and the following error message
>>> is displayed:
>>>
>>> "The value of the Base Memory field on the System page is not
>>> complete."
>>>
>>> I guess it comes from the base memory upper bound preset to zero
>>> but I have no clue what's the source for the zero value.
>>>
>>> The problem is just in the GUI:
>>> - I can create or update VMs using the CLI
>>> - the VMs created in older VirtualBox versions run fine
>>>
>>> I anyone facing the same problem?
>> I confirm the problem. Apparently this is a regression in the latest version.
>>
>> Currently I'm looking at full diff between  VirtualBox 4.2.12 and
>> 4.2.14, but still can't  find a change which could cause the issue.
>
> At a first glance, RTSystemQueryAvailableRam? I see some
> new occurrences in the diff. Unfortunately, it's one of
> the OS dependent functions. However, I don't speak C++,
> so I'm just guessing...
Thanks for suggestion.
Perhaps you are right, furthermore I can not see FreeBSD version of
that function, so currently we have at least two different approaches:
- Rollback to an old version of system memory calculation method
(which was a dirty hack,according to code comments)
- Or just implement such function and send it upstream.
The second way seems to me more preferable. It takes me a few days,
until that you have to use cli tools or previous VirtualBox port
revision from svn.

>
> Oli
> ___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"



--
Михаил
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: VirtualBox: The value of the Base Memory field on the System page is not complete

2013-06-25 Thread Mikhail Tsatsenko
2013/6/25 kron :
> Greetings,
>
> I'm running virtualbox-ose-4.2.14 on FreeBSD 9.1-STABLE r252094M
> amd64. The GUI of VirtualBox cannot create/update virtual box
> definitions (the *.vbox) files. The scrollbar and the form field
> for "Base Memory" are broken and the following error message
> is displayed:
>
> "The value of the Base Memory field on the System page is not
> complete."
>
> I guess it comes from the base memory upper bound preset to zero
> but I have no clue what's the source for the zero value.
>
> The problem is just in the GUI:
> - I can create or update VMs using the CLI
> - the VMs created in older VirtualBox versions run fine
>
> I anyone facing the same problem?
I confirm the problem. Apparently this is a regression in the latest version.

Currently I'm looking at full diff between  VirtualBox 4.2.12 and
4.2.14, but still can't  find a change which could cause the issue.

> BR,
> Oli
> ___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"



--
Mikhail
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Virtualbox: time sync

2013-05-27 Thread Mikhail Tsatsenko
2013/5/26 Marc Fournier :
>
> On 2013-05-26, at 2:54 AM, Mikhail Tsatsenko  wrote:
>
>> 2013/5/26 Marc Fournier :
>> Hi
>>>
>>> First, thank you for the answer about switching from straight bridge to 
>>> using a tap device ... that made a *huge* difference ... I'm not able to 
>>> actually run a build world within the environment without having the whole 
>>> machine lock up ...
>>>
>>> So, went next step ... now that I can successfully build, I added the Guest 
>>> Additions ... from what I've read, its what is required in order to get 
>>> time sync to work between host and guest ... but doesn't quite seem to do 
>>> it:
>>>
>>> # ssh ams "(uptime; date)" ; date
>>> 1:55AM  up 1 day, 20:30, 0 users, load averages: 0.05, 0.07, 0.08
>>> Sun May 26 01:55:16 ADT 2013
>>> Sun May 26 04:57:57 UTC 2013
>>>
>>> kldstat shows the vboxguest.ko module has been loaded ... I have ntpd 
>>> disabled, so I don't believe I'm *supposed* to need it, correct?
>> try setting sysctl kern.eventtimer.idletick=1
>> It should resolve the issue
>
> Just to confirm …is this within the Guest, or on the Host itself?
> Thx
within the Guest


--
Mikhail
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Virtualbox: time sync

2013-05-26 Thread Mikhail Tsatsenko
2013/5/26 Marc Fournier :
Hi
>
> First, thank you for the answer about switching from straight bridge to using 
> a tap device ... that made a *huge* difference ... I'm not able to actually 
> run a build world within the environment without having the whole machine 
> lock up ...
>
> So, went next step ... now that I can successfully build, I added the Guest 
> Additions ... from what I've read, its what is required in order to get time 
> sync to work between host and guest ... but doesn't quite seem to do it:
>
> # ssh ams "(uptime; date)" ; date
>  1:55AM  up 1 day, 20:30, 0 users, load averages: 0.05, 0.07, 0.08
> Sun May 26 01:55:16 ADT 2013
> Sun May 26 04:57:57 UTC 2013
>
> kldstat shows the vboxguest.ko module has been loaded ... I have ntpd 
> disabled, so I don't believe I'm *supposed* to need it, correct?
try setting sysctl kern.eventtimer.idletick=1
It should resolve the issue
> Are there known issues with this, or have I missed a setting somewhere?   Or 
> should I actually need ntpd to be running even with the Guest additions?
>
> Thanks ...
>
>
>
>
>
>
> ___
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"



--
Михаил
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"