Compatibility with VMware and Microsoft virtualization products? - Printable Version +- Stresslinux community (https://www.stresslinux.org/community) +-- Forum: Stresslinux Main (https://www.stresslinux.org/community/forumdisplay.php?fid=1) +--- Forum: General discussion (https://www.stresslinux.org/community/forumdisplay.php?fid=2) +--- Thread: Compatibility with VMware and Microsoft virtualization products? (/showthread.php?tid=6) |
Compatibility with VMware and Microsoft virtualization products? - alessandro.perilli - 05-31-2006 Hi there, I'd like to know if current StressLinux version is able to recognize all virtual hardware provided in virtual machines from VMware (ESX/GSX/Workstation) and Microsoft (Virtual PC/Server) products. If so I would be happy to mention this project on my post "How to stress test virtual machines": http://www.virtualization.info/2006/01/how-to-stress-test-virtual-machines.html Thank you! Alessandro Perilli, CISSP, MVP IT Security and Virtualization Technology Analyst http://www.alessandroperilli.com LinkedIn: https://www.linkedin.com/in/alessandroperilli Blogging about IT Security on http://www.securityzero.com Blogging about Virtualization on http://www.virtualization.info RE: Compatibility with VMware and Microsoft virtualization products? - stresslinux - 05-31-2006 I often tested stresslinux in VMware workstion and also tested it on the free VMware Sserver. So it should work on the comercial server version, too. Some time ago i also tested it on Qemu. Yesterday i found a page, which lists many distributions and OSes which may work on VirtualPC (http://vpc.visualwin.com/) Stresslinux is listed with different versions, but i never tried it myself, so i can not give any comments on this. RE: Compatibility with VMware and Microsoft virtualization products? - andybehm - 03-26-2007 I tried the current download 0.3.1 under Virtual PC on a HP Pavilion AMD64 laptop, and it runs the memtest fine, but when I boot the stress or noinitrd I get very frequent error messages (about 1 - 2 seconds apart) saying: hda: drive_cmd: status=0x51 { DriverReady SeekComplete Error } hda: drive_cmd: error=0x04 { DriveStatusError } ide: failed opcode was: 0xb0 That pretty makes it unusable since the display is constantly being trashed by these messages. The other limitation seems that there is no Motherboard selection that would be appropriate for a Virtual PC environment. You might want to consider adding direct support for Virtual PC. But I realize supporting everything is never practical, sigh. RE: Compatibility with VMware and Microsoft virtualization products? - hibaaryan - 01-07-2015 Thankyou, that was a very helpful reply! As you might have guessed I'm new to Linux... RE: Compatibility with VMware and Microsoft virtualization products? - bonds22 - 04-14-2015 The other limitation seems that there is no Motherboard selection that would be appropriate for a Virtual PC environment. |