Discussion:
VirtualBox, Linux, ethernet question...
(too old to reply)
Yoram Halberstam
2009-06-15 18:37:36 UTC
Permalink
Hi,

I have Fedora 10 and installed the latest VirtualBox. In a virtual machine I
have Suse Linux. It doesn't managed to get an ip address through dhcp.

I know this a fedora list but maybe I could get some clues at how to
diagnose network problem on Linux (does it even see VirtualBox DHCP?)

Note: I've added the guest addition

Cheers
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/217133c9/attachment.html
Giuseppe Fuggiano
2009-06-15 18:44:13 UTC
Permalink
Post by Yoram Halberstam
Hi,
I have Fedora 10 and installed the latest VirtualBox. In a virtual machine I
have Suse Linux. It doesn't managed to get an ip address through dhcp.
I know this a fedora list but maybe I could get some clues at how to
diagnose network problem on Linux (does it even see VirtualBox DHCP?)
Note: I've added the guest addition
How is your VM network configured? Try selecting "bridge" and then
the ethernet interface the host is using.

Cheers
--
Giuseppe
Yoram Halberstam
2009-06-15 18:59:18 UTC
Permalink
I've tried them all...

it says something like this:

eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 Starting DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices: eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
waiting
eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed

2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Yoram Halberstam
Post by Yoram Halberstam
Hi,
I have Fedora 10 and installed the latest VirtualBox. In a virtual
machine I
Post by Yoram Halberstam
have Suse Linux. It doesn't managed to get an ip address through dhcp.
I know this a fedora list but maybe I could get some clues at how to
diagnose network problem on Linux (does it even see VirtualBox DHCP?)
Note: I've added the guest addition
How is your VM network configured? Try selecting "bridge" and then
the ethernet interface the host is using.
Cheers
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/2aae49dc/attachment.html
Giuseppe Fuggiano
2009-06-15 19:11:33 UTC
Permalink
Post by Yoram Halberstam
I've tried them all...
eth0? device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 Starting? DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices:?? eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0? DHCP4 client (dhcpcd) is running
eth0? . . . but is still waiting for data
waiting
eth0? interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed
If I understood your issue, you should not try to get an ip address
within the guest machine until the host one is configured well. I
suggest you to configure the host machine using a command like this:

VBoxManage modifyvm "Name of your Machine" --bridgeadapter1 eth0

where eth0 is the host interface you are using. You also can manage
the network configuration using the GUI shipped with the package. Let
me point you to the official user manual instructions:

http://www.virtualbox.org/manual/UserManual.html#networkingdetails
--
Giuseppe
Yoram Halberstam
2009-06-15 20:05:54 UTC
Permalink
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.

I've tried the command and got

[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan" --bridgeadapter1
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line 853
of file VBoxManageModifyVM.cpp

desktop.lan is what I get when I type hostname....


2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Giuseppe Fuggiano
Post by Yoram Halberstam
I've tried them all...
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev
10)
Post by Yoram Halberstam
eth0 Starting DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices: eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
waiting
eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed
If I understood your issue, you should not try to get an ip address
within the guest machine until the host one is configured well. I
VBoxManage modifyvm "Name of your Machine" --bridgeadapter1 eth0
where eth0 is the host interface you are using. You also can manage
the network configuration using the GUI shipped with the package. Let
http://www.virtualbox.org/manual/UserManual.html#networkingdetails
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/ab984240/attachment.html
Yoram Halberstam
2009-06-15 20:11:37 UTC
Permalink
ok command line works... was still in root mode doh!

VBoxManage modifyvm "Minimum Server" --bridgeadapter1 eth0

network still doesn't work....

PS: Question like this... Why use the command line if you configure it
already in the GUI?

2009/6/15 Yoram Halberstam <yoram.halberstam at gmail.com>
Post by Yoram Halberstam
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.
I've tried the command and got
[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan" --bridgeadapter1
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line 853
of file VBoxManageModifyVM.cpp
desktop.lan is what I get when I type hostname....
2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Giuseppe Fuggiano
Post by Yoram Halberstam
I've tried them all...
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev
10)
Post by Yoram Halberstam
eth0 Starting DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices: eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev
10)
Post by Yoram Halberstam
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
waiting
eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed
If I understood your issue, you should not try to get an ip address
within the guest machine until the host one is configured well. I
VBoxManage modifyvm "Name of your Machine" --bridgeadapter1 eth0
where eth0 is the host interface you are using. You also can manage
the network configuration using the GUI shipped with the package. Let
http://www.virtualbox.org/manual/UserManual.html#networkingdetails
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/3fac83f1/attachment.html
Giuseppe Fuggiano
2009-06-15 20:28:45 UTC
Permalink
Post by Yoram Halberstam
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.
Command line permits you to control *every* aspect of your operating
system faster than you could searching, installing and learning to use
such buggy tools you find for Windows.
Post by Yoram Halberstam
I've tried the command and got
[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan" --bridgeadapter1
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line 853
of file VBoxManageModifyVM.cpp
desktop.lan is what I get when I type hostname....
Learn to use the "man" command to understand how to use commands.

man VBoxManage

You'll discover that you must specify the virtual machine NAME. If
you called your virtual machine "Suse" or "Suse 10" or whatever, you
have to use that name.

Type "ifconfig" command to discover the name of the ethernet interface
you are using. Please look to Wikipedia (http://en.wikipedia.org), in
the Fedora wiki (https://fedoraproject.org/wiki/Fedora_Project_Wiki)
or simply to Google for terms or concepts you don't know or
understand.
--
Giuseppe
Yoram Halberstam
2009-06-15 20:51:38 UTC
Permalink
Errrr.... At the risk of being shot I'll say that there a lot of smart and
easy thing on linux compare to windows, installing virtualbox and running
and general gui config are not one of them!

Thanks also, I may not be a wizz kid but I do go on google (and I wouldn't
be there if I found the answers)... anyway all of this to realise that I did
configure everything from the GUI already (I think). I prefer GUI than
command line ;-)

So now I used host -only and I used bridge... both work, (I realised eth0
was disabled) - with vboxnet0 and eth1 respectively I can communicate back
to the host but not into the virtualbox Suse.... Any hint sir? (I've tried
ssh)



2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Giuseppe Fuggiano
Post by Yoram Halberstam
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.
Command line permits you to control *every* aspect of your operating
system faster than you could searching, installing and learning to use
such buggy tools you find for Windows.
Post by Yoram Halberstam
I've tried the command and got
[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan"
--bridgeadapter1
Post by Yoram Halberstam
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line
853
Post by Yoram Halberstam
of file VBoxManageModifyVM.cpp
desktop.lan is what I get when I type hostname....
Learn to use the "man" command to understand how to use commands.
man VBoxManage
You'll discover that you must specify the virtual machine NAME. If
you called your virtual machine "Suse" or "Suse 10" or whatever, you
have to use that name.
Type "ifconfig" command to discover the name of the ethernet interface
you are using. Please look to Wikipedia (http://en.wikipedia.org), in
the Fedora wiki (https://fedoraproject.org/wiki/Fedora_Project_Wiki)
or simply to Google for terms or concepts you don't know or
understand.
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/68e2c82d/attachment.html
Frank Murphy
2009-06-15 20:54:53 UTC
Permalink
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Maybe the virt list might be able to shed more light on your issue?

http://fedoraproject.org/wiki/Virtualization

Frank
Yoram Halberstam
2009-06-15 21:05:38 UTC
Permalink
How can kvm, xen, qemu and other help me? I know fedora has a lot of open
source for virtualization but I want to use virtual box as I have the images
ready, I know it, it's easy, and I find it more user friendly (some people
says it's faster too).

Any other suggestion?

2009/6/15 Frank Murphy <frankly3d at gmail.com>
Post by Frank Murphy
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Maybe the virt list might be able to shed more light on your issue?
http://fedoraproject.org/wiki/Virtualization
Frank
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/cc855b36/attachment.html
Frank Murphy
2009-06-16 07:06:17 UTC
Permalink
Post by Yoram Halberstam
How can kvm, xen, qemu and other help me? I know fedora has a lot of open
source for virtualization but I want to use virtual box as I have the images
ready, I know it, it's easy, and I find it more user friendly (some people
says it's faster too).
Any other suggestion?
My point was that they use this stuff, and may also have come across
your problem in their working lives with Virtualbox , vmware etc..


Frank
Frank Murphy
2009-06-16 07:06:17 UTC
Permalink
Post by Yoram Halberstam
How can kvm, xen, qemu and other help me? I know fedora has a lot of open
source for virtualization but I want to use virtual box as I have the images
ready, I know it, it's easy, and I find it more user friendly (some people
says it's faster too).
Any other suggestion?
My point was that they use this stuff, and may also have come across
your problem in their working lives with Virtualbox , vmware etc..


Frank
Yoram Halberstam
2009-06-15 21:05:38 UTC
Permalink
How can kvm, xen, qemu and other help me? I know fedora has a lot of open
source for virtualization but I want to use virtual box as I have the images
ready, I know it, it's easy, and I find it more user friendly (some people
says it's faster too).

Any other suggestion?

2009/6/15 Frank Murphy <frankly3d at gmail.com>
Post by Frank Murphy
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Maybe the virt list might be able to shed more light on your issue?
http://fedoraproject.org/wiki/Virtualization
Frank
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/cc855b36/attachment-0001.html
Major Péter
2009-06-15 21:14:33 UTC
Permalink
If you're using the VM in NAT mode, then you can't reach the guest
network device (or vice versa) by default with SSH or any other type of
mode. Here is a tutorial to make the SSH working (host can access to the
guest):
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html

Peter
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
Yoram Halberstam
2009-06-16 06:45:49 UTC
Permalink
Hi Peter,

I'm using it in Bridge Mode or Host-Only - neither works.

It maybe a fallback solution to try NAT and try to set it up so that I can
get into the virtualbox via TCP... I'll try tonight if I'm not getting
anywhere. thanks for your help!

2009/6/15 Major P?ter <majorpetya at sch.bme.hu>
If you're using the VM in NAT mode, then you can't reach the guest network
device (or vice versa) by default with SSH or any other type of mode. Here
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html
Peter
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090616/4857abbc/attachment.html
Major Péter
2009-06-16 06:53:03 UTC
Permalink
Hi,

also you could read this:
http://www.giannistsakiris.com/index.php/2007/11/01/host-only-networking-for-virtualbox/
This tutorial is made for Ubuntu, but maybe there are some good ideas,
which you can use.

Peter
Post by Yoram Halberstam
Hi Peter,
I'm using it in Bridge Mode or Host-Only - neither works.
It maybe a fallback solution to try NAT and try to set it up so that I
can get into the virtualbox via TCP... I'll try tonight if I'm not
getting anywhere. thanks for your help!
2009/6/15 Major P?ter <majorpetya at sch.bme.hu <mailto:majorpetya at sch.bme.hu>>
If you're using the VM in NAT mode, then you can't reach the guest
network device (or vice versa) by default with SSH or any other type
of mode. Here is a tutorial to make the SSH working (host can access
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html
Peter
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing
virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com <mailto:netfever at hotmail.com>
Kevin Martin
2009-06-16 15:13:11 UTC
Permalink
Post by Yoram Halberstam
Hi Peter,
I'm using it in Bridge Mode or Host-Only - neither works.
It maybe a fallback solution to try NAT and try to set it up so that I
can get into the virtualbox via TCP... I'll try tonight if I'm not
getting anywhere. thanks for your help!
2009/6/15 Major P?ter <majorpetya at sch.bme.hu
<mailto:majorpetya at sch.bme.hu>>
If you're using the VM in NAT mode, then you can't reach the guest
network device (or vice versa) by default with SSH or any other
type of mode. Here is a tutorial to make the SSH working (host can
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html
Peter
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing
virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
--
fedora-list mailing list
fedora-list at redhat.com <mailto:fedora-list at redhat.com>
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com <mailto:netfever at hotmail.com>
All of that being said, what is the ip address of the hard nic (eth0?)
on the host machine (ifconfig eth0 on the host os), what is the ip
address of the guest machine's nic (ifconfig or ipconfig depending on
the os), can traceroute or tracert (again, depending on the os) from the
guest to the host ip and what is that route, can you resolve host names
on the guest (nslookup www.yahoo.com)?

Kevin
Major Péter
2009-06-16 06:53:03 UTC
Permalink
Hi,

also you could read this:
http://www.giannistsakiris.com/index.php/2007/11/01/host-only-networking-for-virtualbox/
This tutorial is made for Ubuntu, but maybe there are some good ideas,
which you can use.

Peter
Post by Yoram Halberstam
Hi Peter,
I'm using it in Bridge Mode or Host-Only - neither works.
It maybe a fallback solution to try NAT and try to set it up so that I
can get into the virtualbox via TCP... I'll try tonight if I'm not
getting anywhere. thanks for your help!
2009/6/15 Major P?ter <majorpetya at sch.bme.hu <mailto:majorpetya at sch.bme.hu>>
If you're using the VM in NAT mode, then you can't reach the guest
network device (or vice versa) by default with SSH or any other type
of mode. Here is a tutorial to make the SSH working (host can access
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html
Peter
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing
virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com <mailto:netfever at hotmail.com>
Kevin Martin
2009-06-16 15:13:11 UTC
Permalink
Post by Yoram Halberstam
Hi Peter,
I'm using it in Bridge Mode or Host-Only - neither works.
It maybe a fallback solution to try NAT and try to set it up so that I
can get into the virtualbox via TCP... I'll try tonight if I'm not
getting anywhere. thanks for your help!
2009/6/15 Major P?ter <majorpetya at sch.bme.hu
<mailto:majorpetya at sch.bme.hu>>
If you're using the VM in NAT mode, then you can't reach the guest
network device (or vice versa) by default with SSH or any other
type of mode. Here is a tutorial to make the SSH working (host can
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html
Peter
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing
virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
--
fedora-list mailing list
fedora-list at redhat.com <mailto:fedora-list at redhat.com>
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com <mailto:netfever at hotmail.com>
All of that being said, what is the ip address of the hard nic (eth0?)
on the host machine (ifconfig eth0 on the host os), what is the ip
address of the guest machine's nic (ifconfig or ipconfig depending on
the os), can traceroute or tracert (again, depending on the os) from the
guest to the host ip and what is that route, can you resolve host names
on the guest (nslookup www.yahoo.com)?

Kevin

Yoram Halberstam
2009-06-16 06:45:49 UTC
Permalink
Hi Peter,

I'm using it in Bridge Mode or Host-Only - neither works.

It maybe a fallback solution to try NAT and try to set it up so that I can
get into the virtualbox via TCP... I'll try tonight if I'm not getting
anywhere. thanks for your help!

2009/6/15 Major P?ter <majorpetya at sch.bme.hu>
If you're using the VM in NAT mode, then you can't reach the guest network
device (or vice versa) by default with SSH or any other type of mode. Here
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html
Peter
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090616/4857abbc/attachment-0001.html
Frank Murphy
2009-06-15 20:54:53 UTC
Permalink
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Maybe the virt list might be able to shed more light on your issue?

http://fedoraproject.org/wiki/Virtualization

Frank
Major Péter
2009-06-15 21:14:33 UTC
Permalink
If you're using the VM in NAT mode, then you can't reach the guest
network device (or vice versa) by default with SSH or any other type of
mode. Here is a tutorial to make the SSH working (host can access to the
guest):
http://jimmyg.org/blog/2008/ssh-to-a-debian-etch-virtual-machine-in-virtualbox.html

Peter
Post by Yoram Halberstam
Errrr.... At the risk of being shot I'll say that there a lot of smart
and easy thing on linux compare to windows, installing virtualbox and
running and general gui config are not one of them!
Thanks also, I may not be a wizz kid but I do go on google (and I
wouldn't be there if I found the answers)... anyway all of this to
realise that I did configure everything from the GUI already (I think).
I prefer GUI than command line ;-)
So now I used host -only and I used bridge... both work, (I realised
eth0 was disabled) - with vboxnet0 and eth1 respectively I can
communicate back to the host but not into the virtualbox Suse.... Any
hint sir? (I've tried ssh)
Yoram Halberstam
2009-06-15 20:51:38 UTC
Permalink
Errrr.... At the risk of being shot I'll say that there a lot of smart and
easy thing on linux compare to windows, installing virtualbox and running
and general gui config are not one of them!

Thanks also, I may not be a wizz kid but I do go on google (and I wouldn't
be there if I found the answers)... anyway all of this to realise that I did
configure everything from the GUI already (I think). I prefer GUI than
command line ;-)

So now I used host -only and I used bridge... both work, (I realised eth0
was disabled) - with vboxnet0 and eth1 respectively I can communicate back
to the host but not into the virtualbox Suse.... Any hint sir? (I've tried
ssh)



2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Giuseppe Fuggiano
Post by Yoram Halberstam
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.
Command line permits you to control *every* aspect of your operating
system faster than you could searching, installing and learning to use
such buggy tools you find for Windows.
Post by Yoram Halberstam
I've tried the command and got
[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan"
--bridgeadapter1
Post by Yoram Halberstam
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line
853
Post by Yoram Halberstam
of file VBoxManageModifyVM.cpp
desktop.lan is what I get when I type hostname....
Learn to use the "man" command to understand how to use commands.
man VBoxManage
You'll discover that you must specify the virtual machine NAME. If
you called your virtual machine "Suse" or "Suse 10" or whatever, you
have to use that name.
Type "ifconfig" command to discover the name of the ethernet interface
you are using. Please look to Wikipedia (http://en.wikipedia.org), in
the Fedora wiki (https://fedoraproject.org/wiki/Fedora_Project_Wiki)
or simply to Google for terms or concepts you don't know or
understand.
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/68e2c82d/attachment-0001.html
Yoram Halberstam
2009-06-15 20:11:37 UTC
Permalink
ok command line works... was still in root mode doh!

VBoxManage modifyvm "Minimum Server" --bridgeadapter1 eth0

network still doesn't work....

PS: Question like this... Why use the command line if you configure it
already in the GUI?

2009/6/15 Yoram Halberstam <yoram.halberstam at gmail.com>
Post by Yoram Halberstam
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.
I've tried the command and got
[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan" --bridgeadapter1
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line 853
of file VBoxManageModifyVM.cpp
desktop.lan is what I get when I type hostname....
2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Giuseppe Fuggiano
Post by Yoram Halberstam
I've tried them all...
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev
10)
Post by Yoram Halberstam
eth0 Starting DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices: eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev
10)
Post by Yoram Halberstam
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
waiting
eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed
If I understood your issue, you should not try to get an ip address
within the guest machine until the host one is configured well. I
VBoxManage modifyvm "Name of your Machine" --bridgeadapter1 eth0
where eth0 is the host interface you are using. You also can manage
the network configuration using the GUI shipped with the package. Let
http://www.virtualbox.org/manual/UserManual.html#networkingdetails
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/3fac83f1/attachment-0001.html
Giuseppe Fuggiano
2009-06-15 20:28:45 UTC
Permalink
Post by Yoram Halberstam
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.
Command line permits you to control *every* aspect of your operating
system faster than you could searching, installing and learning to use
such buggy tools you find for Windows.
Post by Yoram Halberstam
I've tried the command and got
[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan" --bridgeadapter1
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line 853
of file VBoxManageModifyVM.cpp
desktop.lan is what I get when I type hostname....
Learn to use the "man" command to understand how to use commands.

man VBoxManage

You'll discover that you must specify the virtual machine NAME. If
you called your virtual machine "Suse" or "Suse 10" or whatever, you
have to use that name.

Type "ifconfig" command to discover the name of the ethernet interface
you are using. Please look to Wikipedia (http://en.wikipedia.org), in
the Fedora wiki (https://fedoraproject.org/wiki/Fedora_Project_Wiki)
or simply to Google for terms or concepts you don't know or
understand.
--
Giuseppe
Yoram Halberstam
2009-06-15 20:05:54 UTC
Permalink
Ok, here is when Linux loose me! NEver had to comand line anything on
Windows so thanks for hinting me toward the solution.

I've tried the command and got

[root at desktop eclipse]# VBoxManage modifyvm "desktop.lan" --bridgeadapter1
eth0
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

ERROR: Could not find a registered machine named 'desktop.lan'
Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]), machine.asOutParam())" at line 853
of file VBoxManageModifyVM.cpp

desktop.lan is what I get when I type hostname....


2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Giuseppe Fuggiano
Post by Yoram Halberstam
I've tried them all...
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev
10)
Post by Yoram Halberstam
eth0 Starting DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices: eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
waiting
eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed
If I understood your issue, you should not try to get an ip address
within the guest machine until the host one is configured well. I
VBoxManage modifyvm "Name of your Machine" --bridgeadapter1 eth0
where eth0 is the host interface you are using. You also can manage
the network configuration using the GUI shipped with the package. Let
http://www.virtualbox.org/manual/UserManual.html#networkingdetails
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/ab984240/attachment-0001.html
Giuseppe Fuggiano
2009-06-15 19:11:33 UTC
Permalink
Post by Yoram Halberstam
I've tried them all...
eth0? device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 Starting? DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices:?? eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0? DHCP4 client (dhcpcd) is running
eth0? . . . but is still waiting for data
waiting
eth0? interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed
If I understood your issue, you should not try to get an ip address
within the guest machine until the host one is configured well. I
suggest you to configure the host machine using a command like this:

VBoxManage modifyvm "Name of your Machine" --bridgeadapter1 eth0

where eth0 is the host interface you are using. You also can manage
the network configuration using the GUI shipped with the package. Let
me point you to the official user manual instructions:

http://www.virtualbox.org/manual/UserManual.html#networkingdetails
--
Giuseppe
Yoram Halberstam
2009-06-15 18:59:18 UTC
Permalink
I've tried them all...

it says something like this:

eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 Starting DHCP4 client . . . . . . . . .
eth0 DHCP4 continues in backround
waiting
waiting for mandatory devices: eth0 __NSC__
5 3 1
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
waiting
eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . failed

2009/6/15 Giuseppe Fuggiano <giuseppe.fuggiano at gmail.com>
Post by Yoram Halberstam
Post by Yoram Halberstam
Hi,
I have Fedora 10 and installed the latest VirtualBox. In a virtual
machine I
Post by Yoram Halberstam
have Suse Linux. It doesn't managed to get an ip address through dhcp.
I know this a fedora list but maybe I could get some clues at how to
diagnose network problem on Linux (does it even see VirtualBox DHCP?)
Note: I've added the guest addition
How is your VM network configured? Try selecting "bridge" and then
the ethernet interface the host is using.
Cheers
--
Giuseppe
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/2aae49dc/attachment-0001.html
Yoram Halberstam
2009-06-15 18:37:36 UTC
Permalink
Hi,

I have Fedora 10 and installed the latest VirtualBox. In a virtual machine I
have Suse Linux. It doesn't managed to get an ip address through dhcp.

I know this a fedora list but maybe I could get some clues at how to
diagnose network problem on Linux (does it even see VirtualBox DHCP?)

Note: I've added the guest addition

Cheers
--
Yoram Halberstam
Computer Services Provider
MSN: netfever at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20090615/217133c9/attachment-0001.html
Giuseppe Fuggiano
2009-06-15 18:44:13 UTC
Permalink
Post by Yoram Halberstam
Hi,
I have Fedora 10 and installed the latest VirtualBox. In a virtual machine I
have Suse Linux. It doesn't managed to get an ip address through dhcp.
I know this a fedora list but maybe I could get some clues at how to
diagnose network problem on Linux (does it even see VirtualBox DHCP?)
Note: I've added the guest addition
How is your VM network configured? Try selecting "bridge" and then
the ethernet interface the host is using.

Cheers
--
Giuseppe
Continue reading on narkive:
Loading...