[SOLVED] Is there a way to virtualization to use Windows on OpenBSD
*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is there a way to virtualization to use Windows on OpenBSD
Hi everyone, I want to give a chance to OpenBSD but I have to use Windows7 at the same time because I have .exe books on Windows 7 which are wine can not handle it. So can I use Windows7 on OpenBSD as vm or maybe with ssh?
MS offered some VM's to be used for building but they would be fine to import to your VM. To use a current physical windows 7 isn't easy since hal will be different.
You also can build off the newer Windows 10 iso's that will work for some limited time maybe an hour after 30 days.
I know you've already marked this [SOLVED], but if you are considering operating Windows as a guest of OpenBSD:
The vmm(4) hypervisor does not support Windows guests. Graphics consoles for guests are not available.
There is no WINE or other Windows emulator available with OpenBSD.
Generally, if someone needs both of these OSes on a single workstation, multibooting is the usual choice. Be advised: caution and care is needed to configure multibooting, and backing up data to prevent inadvertent loss is strongly advised.
I know you've already marked this [SOLVED], but if you are considering operating Windows as a guest of OpenBSD:
The vmm(4) hypervisor does not support Windows guests. Graphics consoles for guests are not available.
There is no WINE or other Windows emulator available with OpenBSD.
Generally, if someone needs both of these OSes on a single workstation, multibooting is the usual choice. Be advised: caution and care is needed to configure multibooting, and backing up data to prevent inadvertent loss is strongly advised.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,006
Rep:
Quote:
Originally Posted by Otakuch
Hi everyone, I want to give a chance to OpenBSD but I have to use Windows7 at the same time because I have .exe books on Windows 7 which are wine can not handle it. So can I use Windows7 on OpenBSD as vm or maybe with ssh?
you can set up the opposite:
Windows VM host and OpenBSD VM client.
The real reason is that OpenBSD multicore cpu support is quite rudimental and all that requires CPU power will run slow. Running Windows as VM client in OpenBSD VM host would be real pain.
while OpenBSD does not support VirtualBox it runs quite happily as VM client in full screen resolution which makes it usable.
While you will not have clipboard and seamless mouse support you can share files by settin up nfs shares.
I have Slackware linux VM host and OpenBSD VM client running.
I did compile custom kernel for OpenBSD but this is not necessary.
Running VM is just more confortable now than multibooting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.