Hello again, Alexander!
Yes, the problem was in usb_drv. Namely, vbox initially reads a pile of single blocks per read. rump_fs at first caches these reads as 8 blocks per once (i.e. single request to the part_blk and then to the usb_drv -> single answer), but at some moment changes the strategy and sends several requests for 64 blocks at once without avaiting the answers, which was not good for old storage.cc code.
Sincerely thank you for your help!
For me, it was the first step. What I want next: is it possible to passthrough at least the GPU into VM? Have you (Genode labs) some plans about that task? Or at least some guidance? AFAIK VirtualBox itself has such a possibility: https://www.virtualbox.org/manual/ch09.html#pcipassthrough
20.01.2016, 14:18, "1 2" <freescalereg@...129...>:
Hello, Alexander!
I try to run Win7 32-bit (appropriate win7.vdi is quite small, less than 2G). I've read previsously that current vbox port does not support 64-bit guest systems.
I injected several debug messages into usb_drv and rump_fs. It seems that usb_drv (and underlying layers) works correct (scsi_cmdn.result is always 0), while rump_fs reports that rump_sys_pread always return -1. Also vbox did several writes into win7.vdi, and rump_sys_pwrite always return requested amount of bytes! Moreso, vbox successfully creates /Logs dir, but it's empty. So I suspected either original rump library or part_blk.
Still investigating this puzzle.
20.01.2016, 12:57, "Alexander Boettcher" <alexander.boettcher@...1...>:
Hello,
On 19.01.2016 18:41, 1 2 wrote:
Problem description: system hangs right after "Press F12..." VirtualBox label disappears.
Environment:
MB: Asus Sabertooth Z87 Memory: 16 GB CPU: i7 4770k (Yes, I know that it does not support VT-d) USB stick: Transcend 16GB 1100
[init -> vbox] Using VMX virtualization extension. [init -> vbox] fb resize : 1280x1024@...64... -> 720x400@...361... [init -> vbox] fb resize : 720x400@...64... -> 640x480@...362... [init -> vbox] fb resize : 640x480@...64... -> 720x400@...361... [init -> vbox] fb resize : 720x400@...64... -> 1024x768@...382...
the output looks good. The VM started and is running, switches resolutions - so in general all is up.
So, things you may try: - run your setup on current genode master branch instead of the 15.11 release. We fixed issues in the usb driver (storage) and nova kernel, which may affect you. - you may set the virtual CPU count to 1 in your .vbox file for the moment - set HardwareVirtExUX to false in your .vbox file (but keep it on true if it does not change anything) - Do you run a 32bit or 64bit VM ? Which Windows version, or Linux, ... ?
Hope it helps,
Alexander.
Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main