WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen 3.3 NetBSD DOM0: xenconsole: Could not read tty from

To: Roger Pau Monné <roger.pau@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen 3.3 NetBSD DOM0: xenconsole: Could not read tty from store: No such file or directory
From: Ron McDowell <rcm@xxxxxxxxxxx>
Date: Mon, 17 Oct 2011 10:20:03 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 17 Oct 2011 08:29:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAPLaKK6JgyEf+wA_Dzts72sEA2-RdR2ksY+CxA-ffn7HBXBYUw@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4E971542.8060008@xxxxxxxxxxx> <CAPLaKK5bjF3-iZRV9a6Q9-mrTq9nV-+Nc1ieuZqC__YE1HUd7g@xxxxxxxxxxxxxx> <4E99BB61.3050208@xxxxxxxxxxx> <CAPLaKK6JgyEf+wA_Dzts72sEA2-RdR2ksY+CxA-ffn7HBXBYUw@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
Roger Pau Monné wrote:
Thanks, Roger.  I got sidetracked with other problems for a day or so.  That
indeed does work fine.
Now I've got bridging problems, though.

On my DOM0:

voodoo# cat /etc/ifconfig.bridge0
 create
!brconfig $int add bge0 up

voodoo# ifconfig -a
 bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
      enabled=0
      address: bc:30:5b:d0:a1:46
      media: Ethernet autoselect (1000baseT
full-duplex,flowcontrol,rxpause,txpause)
      status: active
      inet 172.17.9.38 netmask 0xffffff00 broadcast 172.17.9.255
      inet6 fe80::be30:5bff:fed0:a146%bge0 prefixlen 64 scopeid 0x1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
      inet 127.0.0.1 netmask 0xff000000
      inet6 ::1 prefixlen 128
      inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
bridge0: flags=41<UP,RUNNING> mtu 1500

voodoo# cat /usr/pkg/etc/xen/juju                                     kernel
= '/usr/pkg/lib/xen/boot/hvmloader'
builder = 'hvm'
memory = 4096
vcpus = 4
name = 'juju'
vif = [ 'mac=00:16:3e:00:00:01, bridge=bridge0, type=ioemu' ]
    

Have you tried with:

vif = [ 'mac=00:16:3e:00:00:01, bridge=bridge0' ]
  

yes, and also with
vif = [ 'bridge=bridge0' ]
vif = [ 'mac=00:16:3e:00:00:01' ]
vif = [ '' ]


device_model = '/usr/pkg/libexec/qemu-dm'
disk = [ 'file:/Xen/Disks/juju0000.img,ioemu:hda,w' ]
boot = 'c'
vnc = 1
vnclisten = '0.0.0.0'
vncpasswd = 'XXXXXX'
vncdisplay = 1

voodoo# xm create /usr/pkg/etc/xen/juju
Using config file "/usr/pkg/etc/xen/juju".
Started domain juju

voodoo# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  1024     1     r-----
11.0
juju                                         1  4096     4     -b----
46.0

voodoo# ifconfig -a
 bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
      enabled=0
      address: bc:30:5b:d0:a1:46
      media: Ethernet autoselect (1000baseT
full-duplex,flowcontrol,rxpause,txpause)
      status: active
      inet 172.17.9.38 netmask 0xffffff00 broadcast 172.17.9.255
      inet6 fe80::be30:5bff:fed0:a146%bge0 prefixlen 64 scopeid 0x1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
      inet 127.0.0.1 netmask 0xff000000
      inet6 ::1 prefixlen 128
      inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
bridge0: flags=41<UP,RUNNING> mtu 1500
xvif1.0: flags=8923<UP,BROADCAST,NOTRAILERS,PROMISC,SIMPLEX,MULTICAST> mtu
1500
      capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
      enabled=0
      address: 00:16:3e:01:00:01
      inet6 fe80::216:3eff:fe01:1%xvif1.0 prefixlen 64 scopeid 0x4
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
      address: f2:0b:a4:80:47:02
      media: Ethernet autoselect
      inet6 fe80::f00b:a4ff:fe80:4702%tap0 prefixlen 64 scopeid 0x5
    


Can you post the output of "brconfig bridge0"? (only the Interfaces
section is fine). Also you could perform a tcpdump of interface bge0,
to see if packets can reach it.

  

[root@voodoo(NetBSD)]> brconfig bridge0 # on DOM0
bridge0: flags=41<UP,RUNNING>
        Configuration:
                priority 32768 hellotime 2 fwddelay 15 maxage 20
                ipfilter disabled flags 0x0
        Interfaces:
                tap0 flags=3<LEARNING,DISCOVER>
                        port 6 priority 128
                xvif1.0 flags=3<LEARNING,DISCOVER>
                        port 5 priority 128
                bge0 flags=3<LEARNING,DISCOVER>
                        port 1 priority 128
        Address cache (max cache: 100, timeout: 1200):
                00:0d:b9:21:fa:54 bge0 1174 flags=0<>

[juju is the DOM0... then I pinged it from a 3rd box...]

[root@voodoo(NetBSD)]> tcpdump -v host juju
listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes
10:09:16.994741 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:09:17.999872 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:09:19.000298 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:09:20.000630 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:09:21.001109 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET

[...and tried to ssh to it...]

10:14:06.466718 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:14:07.424952 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:14:08.426830 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:14:09.428074 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
10:14:10.429499 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET

[and on DOMU ifconfig and netstat look right...ip address 172.17.9.33/24, default route 172.17.9.1]

The re0 device on the FreeBSD DOMU is set up on 172.17.9.33, everything
looks fine there [I can do screenshots if needed] but there's no
connectivity, DOM0->DOMU or DOMU->DOM0.  Here again, I'm pretty sure it's
some little detail I'm missing and just not seeing.

Thanks in advance.

--
Ron McDowell
San Antonio TX



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

    

-- 
Ron McDowell
San Antonio TX


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users