VMLite VBoot - Boot any Windows from VHD/VMDK/VDI/Raw
#26
Posted 22 December 2010 - 08:24 PM
since you guys are commercial, by coming here, obviously you want people to get diverted to your forum next?
there, let me help you http://www.vmlite.com/index.php/forums
#27
Posted 22 December 2010 - 08:30 PM
As a Stanford PhD, I have high standard.
Edited by huisinro, 22 December 2010 - 08:30 PM.
#28
Posted 22 December 2010 - 08:41 PM
Why Win98 VHD requires a different approach to boot compare to Win2000?When writes are supported, win98/95 vhd should boot nicely too.
Will you add a feature to prepare a Win98 VHD from a hard drive to your VHD app?
Since we're talking about old PCs and OSs now (having old archives accessible is an important part of what virtual environment is about), do you see a way to convert to VHD & emulate & boot a Classic Motorola specific MacOS install (the one developed by Steve Wozniak )
#29
Posted 22 December 2010 - 08:42 PM
Edited by huisinro, 22 December 2010 - 08:45 PM.
#30
Posted 22 December 2010 - 08:44 PM
edit: amazing how after two years, a highly respected PhD guy finally drops but... here
#31
Posted 22 December 2010 - 08:49 PM
As for MAC, totally different stuff. We have made Linux boot from vhd files, we may implement to make latest Mac OS X to boot from vhd, but not our top priority for now.
Why Win98 VHD requires a different approach to boot compare to Win2000?
Will you add a feature to prepare a Win98 VHD from a hard drive to your VHD app?
Since we're talking about old PCs and OSs now (having old archives accessible is an important part of what virtual environment is about), do you see a way to convert to VHD & emulate & boot a Classic Motorola specific MacOS install (the one developed by Steve Wozniak )
#32
Posted 22 December 2010 - 09:16 PM
#33
Posted 22 December 2010 - 09:26 PM
About license, as I said, right now it's a temporary thing, most likely we may offer a limited license to personal use. As you can see from VMLite, we are not the type of guys that want to make $ from any product. We started development since 2005 on vmlite, haven't made any money yet from it.
Maybe i would have started to respect if i knew more about you? but that was not the case... it clearly looked like bombing G4D+FiraDisk+WinvBlock+NT6.x fast installer+MSFN. Let me get this straight, this software is not even free for Home use?
#34
Posted 22 December 2010 - 09:54 PM
#35
Posted 22 December 2010 - 09:58 PM
#36
Posted 22 December 2010 - 10:05 PM
Internally, vboot does support ram loading, but it takes long time to load the image, so i am so sure how useful it is. We will try to export the features for people to use if they want to load the image to ram.
#37
Posted 22 December 2010 - 10:14 PM
looking at your joined date, and your current blasting product information, you've kept silent for quite a while (unless i've missed your earlier post )
#38
Posted 23 December 2010 - 12:18 AM
http://bbs.wuyou.com...16&extra=page=1
http://u.115.com/file/f364c84d92#
#39
Posted 23 December 2010 - 10:20 AM
Take it easy man, no reason to accuse anyone of stealing anything.
@huisinro
With all due respect to you and Stanford , the licensing of the app is NOT - as you may seem to think - a triviality.
I mean you are perfectly free (as in freedom ) to release your app with whatever License you like, but you have to respect the terms of the license and it would be nice if the Terms of it are:
- clear
- correct
Right now the status seems like :
a Commercial app released as a time-limited trial with the limitation of non-business use, using Open Source software WITHOUT releasing the accompanying source code for it and re-distributing non-redistributable Microsoft files.
If it's Commercial, you may be very near the border (or beyond it) of breaking Rule #4 of the board:
http://reboot.pro/82/
If it contains Open Source code, the GNU license binds you to release the source of the modifications also.
If it contains non-redistributable files you may be violating your MS EULA and what not (BTW your problem, not ours ).
In any case, it would be nice if you could highlight the time-limited status of the app, since most people won't read the license, the limitation:
appears like a severe one, as it may cause people - in perfect good faith - to have their PC's unable to boot on Feb 16, 2011.(2) This trial version expires on Feb 15, 2011. After expiration, you won't
be able to use the SOFTWARE to boot your physical computer, and a crash
BSOD error will occur.
Wonko
#40
Posted 23 December 2010 - 02:56 PM
funny trial expiry method by the way . who has the time for making and testing something to be expired on 16th feb ? not me .
thanks.
#41
Posted 23 December 2010 - 03:07 PM
...
#42
Posted 23 December 2010 - 03:53 PM
Again, if any of you don't like it, feel free not to use it. It's your own choice. We posted the product here because I thought that it's releated to this community, we have more than enough users in our forums to test our products, and so far, people like it very much from emails feedbacks.
#43
Posted 23 December 2010 - 04:15 PM
No need to become aggressive.GNU license is there not for showing off, the code we modified on virtualbox has commited back to vbox, and GRUB2 we implement an independent module on most stuff, which doesn't have to be open sourced. We modified the parser and display system, which we can submit to GRUB2 team anytime, and we will post the source code.
Again, if any of you don't like it, feel free not to use it. It's your own choice. We posted the product here because I thought that it's releated to this community, we have more than enough users in our forums to test our products, and so far, people like it very much from emails feedbacks.
The issue I raised is NOT about the quality of the software or it's usability (which everyone might like or dislike) only about the confusing or lacking information about it's licensing scheme and it's limitations.
It seems to me that you have not yet a clear idea of the future of the project (Open Source/Commercial/Free for non-business users, etc.), and the "we will" is not in any way a compliance (now) with the GNU license.
The fact that vboot is currently a time-limited trial was NOT publicized.
That's all.
The (few) users getting to vboot through
Before, anyone had (like I did) to register BEFORE knowing that what is offered is a time-limited trial. (which again, is a perfectly legitimate choice).
I just like calling things with their names and - whenever possible - avoid misunderstandings.
Specifically what I was interested in avoiding was that a less experienced user could "adopt" your Beta as "main" means of booting and find himself/herself with an unbootable system on February 16th, 2011.
or, if you prefer, when and if someone will come here whining about this problem, I will be able to say, "See, I had TOLD you!"
Wonko
#44
Posted 23 December 2010 - 04:21 PM
#45
Posted 23 December 2010 - 06:33 PM
Basically you reserve a memory region at boot time, and VBoot will use this region to cache disk read/writes. In contrast to other RAM booting, ours is not slow even at the first start time. We don't load all bits to memory at the very first beginning, we do it at the first read of sectors.
This way, you will be able to load 16G disk file with 2G memory reserved for use, for example. So it can handle large disk files, and also possible to persist changes back to disk if configured to do so.
#46
Posted 23 December 2010 - 07:42 PM
Regarding 16Gb disk to fit into 2Gb reserved RAM by subsequent reads, are you saying that discarded previous portion will never be required to access any longer? Or read will be repeated each time, when access is again required to that portion? It may actually slow down overall performance after boot, hence sounds like a tradeoff rather then clear performance improvement.
Would you consider offering a Free Licence for personal use for Vboot, while requiring Pay Licence for VMLite (or vice versa, or a product line with raising feature sets)? The reason seems to be in the very basic fact that you use Grub 2 for booting files, and its free. Or it won't work that way? Generally, asking to pay doesn't guarantee by itself much profit, unless suplemented by a strong marketing plan, especially when market (demand) is under-developed, while offering strong free boot soft choices.
#47
Posted 23 December 2010 - 07:54 PM
current ram booting only handles small file size, we are trying to see if this can extend to real hard disk image, like the one I have is 250G vhd file from my laptop cloning. Our boot loader can handle reading/parsing a huge file.
Yes, it's a trade off, need lots of experimenting as how much performance gain.
For small size of virtual disk file, our algorithm is same as other ones, as it will cache all disk operations in memory, except it boots very fast since not loading the whole file at once. For example, if you have xp vhd which is 2G in capacity, and you reseve 2G memory, then eveything will be done in RAM.
#48
Posted 23 December 2010 - 08:11 PM
VBoot has 2 parts, the boot loader portion never expires. The one that currently expires is the windows disk driver inside the virtual disk file.
Even the boot loader itself has lots of development work as how to read a huge file in real mode. To the best of my knowledge, no other boot loaders can read a large (e.g. 250G) file stored randomly on real hard disk, and treat it as virtual disk.
#49
Posted 23 December 2010 - 08:11 PM
#50
Posted 23 December 2010 - 08:24 PM
I tested it on 3 different computers, worked fine.
Here is how can we do this:
Start installing xp to a vhd.
When it copied the files, don't continue with the 2nd step.
Boot into other Windows download UsbBootWatcher.zip from here: www.911cd.net/forums//index.php?showtopic=22473&st=0
Also download usb_xp_init.cmd from here: www.911cd.net/forums//index.php?showtopi...920&#entry153920
Unzip UsbBootWatcher.zip and put usb_xp_init.cmd into the folder we have just extracted UsbBootWatcher. The directory structure should look like this:
amd64 - directory
x86 - directory
usb_xp_init.cmd
Boot into a Windows as SYSTEM (for example Win7PE) and mount vhd.
You can also use in XP the "at hours:minutes /interactive cmd" command to get a command promt with SYSTEM user privileges.
Run usb_xp_init.cmd and type the path of system32 directory of the mounted vhd. (for examle D:\Windows\system32)
When it completed unmount the vhd, put it in the USB hard disk and create entry in grub.cfg for it (We need to use UUID= or LABEL= format).
(We need to create one for continue setup, and one without cdrom to run normally)
I suggest to set registry setting DisablePagingExecutive to 1 in HKLM\SYSTEM\ControlSet001\Control\Session Manager\Memory Management before continue setup.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users