Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
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.
I just installed ReactOS-0.4.8-RC.iso in AQEMU 0.9.2. All is fine except there's no internet. Is there a way to get it working? Attached is an image of my network settings that work fine for Debian, Solus, Windows 7, etc. in AQEMU.
I take it you are aware that ReactOS has been in 'alpha' stage since the mid-1990s, yes? I've heard about this problem from several other folks, and it appears to be, shall we say, 'on-going...'
I don't think there is an actual 'solution' at this point in time. From what I can understand of it, there's a fundamental flaw in the network address translation coding...the 'DHCP' stuff, apparently.
You might like to take a look at ClassicOS. I've been a sometime member of the XP Forums for a few years (trying to convince folks to switch away from the darn thing!), and one of their members made an announcement last year that a small start-up company that he and a few friends had begun was working on a 'development' of ReactOS, building on the same source code.
I've no idea how far they've progressed with it (if at all), but they (did) have a FaceBook page:-
I take it you are aware that ReactOS has been in 'alpha' stage since the mid-1990s, yes? I've heard about this problem from several other folks, and it appears to be, shall we say, 'on-going...'
I don't think there is an actual 'solution' at this point in time. From what I can understand of it, there's a fundamental flaw in the network address translation coding...the 'DHCP' stuff, apparently.
You might like to take a look at ClassicOS. I've been a sometime member of the XP Forums for a few years (trying to convince folks to switch away from the darn thing!), and one of their members made an announcement last year that a small start-up company that he and a few friends had begun was working on a 'development' of ReactOS, building on the same source code.
I've no idea how far they've progressed with it (if at all), but they (did) have a FaceBook page:-
Then you'll have to configure it. Not sure what default nic card you have but you can change it if it's not a supported on.
Also in qemu it uses a virtual router like other vm's do if you set it to nat. Sometimes it is easier to use bridged. Those names may change in qemu.
In BeOS I had to create two nics and then use the second one.
Anyway start by changing the default nic to a supported one.
@jefro, linustalman:-
Huh. I'd forgotten about the 'nic' stuff. I don't do 'virtual' very often; can't remember the last time I did run VirtualBox, TBH.....
Sounds as though the ReactOS team have got the NAT stuff sorted out, anyway. It was a fair while ago when I last looked at it; must have been easily 18 months or more, if not longer.
Mike.
Last edited by Mike_Walsh; 03-05-2018 at 08:21 PM.
We (me too) all have to remember that it has nothing to do with the client OS or the host hardware. It has to do with the virtual hardware the VM presents to the client in most cases. A VM is a software presentation of a physical machine.
Thanks for the update and solution and the good screenshots marked.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.