Virtual Environment (Ow, big words...)
- piranha
- Member
- Posts: 1391
- Joined: Thu Dec 21, 2006 7:42 pm
- Location: Unknown. Momentum is pretty certain, however.
- Contact:
Virtual Environment (Ow, big words...)
Which one do you use? Or like better?
Feel free to rant about them, or post why you use a certain one (in fact, please do so)...
I myself use VMware.
-JL
Feel free to rant about them, or post why you use a certain one (in fact, please do so)...
I myself use VMware.
-JL
SeaOS: Adding VT-x, networking, and ARM support
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
- Colonel Kernel
- Member
- Posts: 1437
- Joined: Tue Oct 17, 2006 6:06 pm
- Location: Vancouver, BC, Canada
- Contact:
I used VMWare on my old XP box, but now that I have a Mac I use Parallels (VMWare Fusion was just taking too long to ship).
Top three reasons why my OS project died:
- Too much overtime at work
- Got married
- My brain got stuck in an infinite loop while trying to design the memory manager
- jerryleecooper
- Member
- Posts: 233
- Joined: Mon Aug 06, 2007 6:32 pm
- Location: Canada
I used bochs, but I found it wasn't runnig at correct speed, It was too slow or too fast. And my kernel was buggy but it worked correctly in bochs (? ).
So now I use Virtual PC, it's faster, but sometimes I get virtual machine internal errors. But right now my kernel seems correct and virtual pc does it honnor.
So now I use Virtual PC, it's faster, but sometimes I get virtual machine internal errors. But right now my kernel seems correct and virtual pc does it honnor.
- AndrewAPrice
- Member
- Posts: 2299
- Joined: Mon Jun 05, 2006 11:00 pm
- Location: USA (and Australia)
I was using QEMU, but I've switched to InnoTek VirtualBox.
Why?
- I don't need the debugging features of QEMU and Bochs anymore since my OS's internal functions suffice.
- VirtualBox seems to be faster than QEMU and Bochs (I'm talking about Out-of-the-box performance).
- VirtualBox is easier to configure than QEMU and Bochs (adding new hardware is only a few clicks away).
- VirtualBox seems to have a lower memory footprint than the other larger emulators (VMware, Virtual PC) and therefore is faster than these when booting and saving/restoring snapeshots, etc.
Why?
- I don't need the debugging features of QEMU and Bochs anymore since my OS's internal functions suffice.
- VirtualBox seems to be faster than QEMU and Bochs (I'm talking about Out-of-the-box performance).
- VirtualBox is easier to configure than QEMU and Bochs (adding new hardware is only a few clicks away).
- VirtualBox seems to have a lower memory footprint than the other larger emulators (VMware, Virtual PC) and therefore is faster than these when booting and saving/restoring snapeshots, etc.
My OS is Perception.
Bochs for debugging, QEMU for "speedy testing" and real hardware for real testing. I do not use MS VPC for my kernel because it doesnt work right.
Regards
inflater
Regards
inflater
My web site: http://inflater.wz.cz (Slovak)
Derrick operating system: http://derrick.xf.cz (Slovak and English )
Derrick operating system: http://derrick.xf.cz (Slovak and English )
Bochs for debugging, anything for testing. The only cases I've found that were a problem were things I didn't test in bochs, so I just need to fix my testing, not the code. The only thing that was actually wrong with the code (not just setup/test related) was writing MSRs my processor didn't get. I was intending to test it on others just now. On my laptop (p4) it works for the RM/PM hello world + i586 kernel and on my main box (p-d) it runs all three hello worlds (rm/pm/lm) and the i586 kernel. The other kernels don't work in bochs either so that's a good reason they wouldn't work.
Just don't use the bochs advantages when you code. Know what you're doing and don't assume anything you aren't sure about.
Just don't use the bochs advantages when you code. Know what you're doing and don't assume anything you aren't sure about.
I use Bochs and VirtualBox. I also stopped using VPC2004 because it "doesn't work right". It mishandles V86 mode extensions (even when using a host processor which supports them) and doesn't like setting up a 'safe' TSS for handling double faults. When I had both of these problems, Googling revealed that many others had the same problems, so I guess it wasn't my kernel that was the issue.Tyler wrote:Why don't you find out what is wrong with your kernel then?inflater wrote:Bochs for debugging, QEMU for "speedy testing" and real hardware for real testing. I do not use MS VPC for my kernel because it doesnt work right.
Regards
inflater
Cheers,
Adam
Well that is fair enough, i have had problems with older version's of Bochs and QEMU, but instead of not using them, i simply upgrade. Virtual PC continues to be the most realistic (real hardware like) Virtual Machine.AJ wrote:I use Bochs and VirtualBox. I also stopped using VPC2004 because it "doesn't work right". It mishandles V86 mode extensions (even when using a host processor which supports them) and doesn't like setting up a 'safe' TSS for handling double faults. When I had both of these problems, Googling revealed that many others had the same problems, so I guess it wasn't my kernel that was the issue.Tyler wrote:Why don't you find out what is wrong with your kernel then?inflater wrote:Bochs for debugging, QEMU for "speedy testing" and real hardware for real testing. I do not use MS VPC for my kernel because it doesnt work right.
Regards
inflater
Cheers,
Adam