After a closer inspection I realised that I received "martians" in my /var/log/warn. Having absolutely no idea what it meant, I googled it without being much wiser.
I then realised I had a problem with my routes since I couldn't resolve any DNS or ping the outside world.
I found that a static route was missing, so after issuing
Code:
route add -net 0.0.0.0 gw 192.168.1.1 br0
Which made my route look much better
Code:
ivmsles01:/var/log # ip route sh
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.77
127.0.0.0/8 dev lo scope link
default via 192.168.1.1 dev br0
I got back on track, the martians went back to Mars and after a bit of firewalling, my server responded nicely to external hosts as well on SSH.
I'm really sorry that I didn't really do my homework completely before crying out for help - if you get to Denmark some day, I'll buy you a beer for your trouble
Last edited by brightstorm; 11-05-2010 at 01:00 PM..
Reason: changed "ip route add" to "route add" which is the correct command
hi All,
I require your help and suggestion in this. I have a solaris 10 (guest) installed on a vmware and my host OS is windows 2003 server. i am trying to conenct to the solaris 10 from my local Pc through putty, but unable to connect. please advice what setup or prerequitsites are required to... (4 Replies)
Hello i have CentOS installed on vmware , few days ago every thing was working fine. today every time im connect with putty to the CentOs server after few minutes it disconnect me , how can i find what is the reason ? (5 Replies)
Hello,
I have a Solaris 10 x86 VM and I am trying to access the Solaris install menu.
I have the ISO set to connect on startup, and I can see that it is mounted in my system. But when I power on the VM, the GRUB menu comes up and I only have the option of booting Solaris.
Also I have... (4 Replies)
Hello,
Please, I would like to connect a VM to another:
I typed as follows:
ssh root@192.168.1.4
root@192.168.1.4 's password:
Permission denied, please try again.
root@192.168.1.4 's password:
Permission denied, please try again.
root@192.168.1.4 's password:
Permission denied... (6 Replies)
I have a log with entries like:
out/target/product/imx53_smd/obj/STATIC_LIBRARIES/libwebcore_intermediates/Source/WebCore/bindings/V8HTMLVideoElement.cpp
: target thumb C++: libwebcore <=... (8 Replies)
I swear I have no other devices on the vmnet 192.168.142.2, but after I configured one of the solaris x86 os, I kept getting warning ..node xx xxxxx have our ip addresss 192.168.142.2, and it scrolled thru it forever ..
I tried to boot it into single user mode , still having the same issue..
... (1 Reply)
I have searched through google, and this forum to try and find the answer, but alas, nothing quite hits the whole answer.
I am trying to read the last line (or lines) of some log files. I do this often.
The files are named sequentially, using the date as part of the file name, and appending... (18 Replies)
Hi!
I am not sure if this is the right place to post this question. What I did was to download vmware onto my laptop, them install a linux distro as a guest O.S., on VM network configuration I have used "bridge", them I used Virtual Network Editor to chose the network interface, but as I write... (4 Replies)
Discussion started by: fretagi
4 Replies
LEARN ABOUT NETBSD
xbdback
XBDBACK(4) BSD/xen Kernel Interfaces Manual XBDBACK(4)NAME
xbdback -- Xen backend paravirtualized block device interface
SYNOPSIS
pseudo-device xbdback
DESCRIPTION
The xbdback interface forms the backend part of the paravirtualized drivers used by Xen domains to offer a block device interface, similar to
a hard disk. xbdback interfaces are backed either by a physical device directly, or an image file mounted through vnd(4).
All xbdback interfaces follow the ``xbdbackXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary
identifier. This identifier is usually associated to the device node as seen by the guest using major(3) and minor(3) numbers. For example,
identifier ``769'' (0x301) means major 3 and minor 1, identified as ``hda1'' under Linux convention. For NetBSD, the guest device name spec-
ified in the guest configuration file does not matter, and can be chosen arbitrarily.
A xbdback interface will appear as a xbd(4) block device inside a NetBSD guest domain. In the XenStore, xbd and xbdback are identified by
``vbd'' (virtual block device) entries.
DIAGNOSTICS
xbd backend: attach device %s (size %d) for domain %d Gives the device used as xbdback interface for the given guest domain, and its size,
in bytes.
xbd backend 0x%x for domain %d using event channel %d, protocol %s Gives the backend identifier, guest domain ID, event channel ID, and pro-
tocol used for block level communication.
xbdback %s: can't VOP_OPEN device 0x%x: %d When this message appears in the system message buffer with error 16 (EBUSY), the device is
likely to be already mounted. It must be unmounted first, as the system will refuse to open it a second time.
SEE ALSO vnd(4), xbd(4), xenbus(4)HISTORY
The xbdback driver first appeared in NetBSD 4.0.
AUTHORS
The xbdback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.
BSD June 7, 2011 BSD
11-04-2010
