Link to home
Create AccountLog in
Avatar of indigo42
indigo42

asked on

How to set up hosting Virtual Win XP box on RHEL with VBoxHeadless

All,
I have imported a WinXP appliance onto my RHEL server in a remote co-location site.

I can start up the image with VBoxHeadless. and VBoxManage says it's running. Now I have some questions...

1) I have an unused network interface (with public IP addr) on my box. Do I use Virtual Box's 'bridged connection' to one of the ethernet interface?

2) How to I open up port 3389 for rdp so I can actually log into the darn thing?
A simple step by step would be appreciated. There is no iptables file, so it must be using some other method of opening ports. The server is hosting a website and it's refusing connections to port 3389. So something is set up right?

I tried
/sbin/iptables -A INPUT -p tcp --dport 3389 -j ACCEPT
/etc/init.d/iptables restart

Open in new window


It did not work..help!

SOLUTION
Avatar of arnold
arnold
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of indigo42
indigo42

ASKER

OK,
I have checked and the vrde is enabled an listening on port 3380.

Since I'm running an WindowsXP guest, will I need to set the IP address in windows to be the same as the IP address of the host's NIC I'm gong to bridge to?

I suppose I can make this setting on my home box and re-export it as an appliance?

Thanks!
I think I am close here!

Okay, so launch RDC from another machine.  In the Connect dialog box, enter the HOST_MACHINE_IPADDR:3380.  This will connect you to the GUEST machine.  You maybe prompted for a User ID / Password., depending on the GUEST.

No, if you are running a bridged network, the GUEST machine has it own IP_ADDRESS, etc... The Interface is configured on the GUEST.

Regards
Ok,
First..thanks for patience!!

Here is where I 'm a bit confused...If I fire up this appliance on my local box...I see that the IP is set at the default DHCP...blah blah..... This is the vmdk I put on my remote system.

So I think what you are telling me is that if I use VBoxManange (on my remote headless server) and set the Adapter to bridged, then it does not matterwhat the host's network settings are?

So if that's the case could you kindly post the VBoxMange syntax as to how I would accomplish this?

Thanks!
Here is what I have tried...
VBoxManage modifyvm KeyServer --nic1 bridged --bridgeadapter1 eth0:1

Open in new window


Then when I start it...I get this...
Error: failed to start machine. Error message: Failed to open/create the internal network 'HostInterfaceNetworking-eth0:1' (VERR_INTNET_FLT_IF_NOT_FOUND).
Unknown error creating VM (VERR_INTNET_FLT_IF_NOT_FOUND)

Open in new window


Here is the info on the host's NIC and the IP <obfuscated...of course> that I'd like to use..
eth0:1    Link encap:Ethernet  HWaddr AA:BB:CC:DD:EE:FF  
          inet addr:10.10.10.11  Bcast: 10.10.10.19  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Open in new window


Thanks!

I will have to test this but I think the issue is you are trying to utilize a sub-interface.  When you create the virtual interface it should be associated with a real device.  Note: Once the GUEST system is brought up the Interface will appear and be configured as a real device.  This will also be true for the HOST system.

Regards
Ok,
I did this instead...
VBoxManage modifyvm KeyServer --nic1 bridged --bridgeadapter1 eth0

Open in new window


and it started up.

Here is the VRDE stats
VRDE:            enabled (Address 0.0.0.0, Ports 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)

Open in new window


Here's the NIC
NIC 1:           MAC: 080027162441, Attachment: Bridged Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps, 

Open in new window


So...I see the address is 0.0.0.0, this is a default, out of the box WinXP host. How then, do I change this to one of the IPs assigned to my NIC?

Ok,
I did this instead...
VBoxManage modifyvm KeyServer --nic1 bridged --bridgeadapter1 eth0

Open in new window


and it started up.

Here is the VRDE stats
VRDE:            enabled (Address 0.0.0.0, Ports 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)

Open in new window


Here's the NIC
NIC 1:           MAC: xxxxxxxxxxx, Attachment: Bridged Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps, 

Open in new window


So...I see the address is 0.0.0.0, this is a default, out of the box WinXP host. How then, do I change this to one of the IPs assigned to my NIC?

Okay, now that the Virtual Machine is up, you signon to it's console and configure it just like a standard Windows XP system.  To access the VRDP (Guest Machine) console. You use RDC with the <Host_IP_ADDR:VRDP_Port>

Regards
In your case the VRDE port number is 3389.  In the RDC dialog box enter <Host_IP_Addr:3389>

Regards
I'm checking this today...I had a database crash to take care of the last couple of days....
I'll let you know how it goes.
Thanks for all the help above and ond BIG problem I had was with VirtualBox 4.0

The RDP server is NOT included in the base install! You have to download and install the Extention Pack.

I totally did not read that when installing it.

You are welcome.  Enjoy the Virtual Machines.  I would recommend that you take a snapshot to the machine once you get it running.  This feature allows you to roll back the VM in a very quick time frame, better than having to re-install the OS....

Regards,
Oh I'm enjoying them already!

This was the first VBox install on a headless server for me,and now that I see how it works, I see how dumb some of my questions were.

I could not get it in my head that port 3389 was VBox's CONSOLE to the VM. I was stuck on the idea that the Guest must have something like VNC running inside it! So I was convinced I'd never get to it without first configuring the Guest's network interface
and..

The biggest setback was not noticing till late in the game that VRDP is NOT included in the base install of VBox with version 4.0. It's installed in with the Extension Pack.

I hope this helps others not to be as dense as I was about the whole thing.

J