|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Xen 3.3 NetBSD DOM0: xenconsole: Could not read tty from store: No such file or directory
Roger Pau Monnà wrote: Thanks, Roger. I got sidetracked with other problems for a day or so. That indeed does work fine.2011/10/13 Ron McDowell <rcm@xxxxxxxxxxx>:[root@voodoo(NetBSD)]> xm create -c /Xen/Machines/juju.cnf Using config file "/Xen/Machines/juju.cnf". Started domain juju xenconsole: Could not read tty from store: No such file or directoryYou should connect to HVM DomU using VNC. Here is an example of what you should add to your config file: Now I've got bridging problems, though. On my DOM0:voodoo# cat /etc/ifconfig.bridge0 create !brconfig $int add bge0 upvoodoo# 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' ] 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 listName 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
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
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |