Re: So close..

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

Looks like you're reproducing the bug described here:

http://mail-index.netbsd.org/port-xen/2008/08/20/msg004155.html

Christoph


B. Cook wrote:
> Hello all,
> 
> NetBSD as dom0, and trying to get netbsd as domU running para virtualized.
> 
> All of this is from the 200811010002Z daily-build.
> 
>  uname -a
> NetBSD xen0.at.home 5.0_BETA NetBSD 5.0_BETA (XEN3_DOM0) #0: Sat Nov  1
> 00:24:22 PDT 2008 
> builds@wb28:/home/builds/ab/netbsd-5/amd64/200811010002Z-obj/home/builds/ab/netbsd-5/src/sys/arch/amd64/compile/XEN3_DOM0
> amd64
> 
> 
> cat -n dom1
>      1  #kernel = "/netbsd-INSTALL_XEN3_DOMU"
>      2  kernel = "/netbsd-XEN3_DOMU"
>      3  memory = 64
>      4  name = "dom1"
>      5  #vcpus = 1
>      6  #disk = [ 'phy:/dev/wd0e,0x03,w','file:/root/boot.iso,0x04,r' ]
>      7  disk = [ 'phy:/dev/wd0e,0x03,w','phy:/dev/cd0a,0x04,r' ]
>      8  vif = [ 'bridge=bridge0' ]
>      9  root = "/dev/wd0d"
> 
> I have already completed the install successfully inside the domU, and I
> am attempting to start it for the first time..
> 
> # xm create dom1 -c
> Using config file "./dom1".
> Started domain dom1
> : Intel 686-class, 2393MHz, id 0x6fb
> xenbus0 at hypervisor0: Xen Virtual Bus Interface
> xencons0 at hypervisor0: Xen Virtual Console Driver
> xencons0: using event channel 2
> xbd0 at xenbus0 id 3: Xen Virtual Block Device Interface
> xbd1 at xenbus0 id 4: Xen Virtual Block Device Interface
> xennet0 at xenbus0 id 0: Xen Virtual Network Interface
> xennet0: MAC address 00:16:3e:10:54:60
> unknown type console at xenbus0 id 0 not configured
> unknown type console at xenbus0 id 0 not configured
> unknown type console at xenbus0 id 0 not configured
> 
> (nothing more)
> 
> # xm list
> Name                                        ID   Mem VCPUs      State  
> Time(s)
> Domain-0                                     0   256     1    
> r-----     13.7
> dom1                                         5    64     1    
> -b----      0.7
> 
> looks like its running..
> 
> # xenstore-ls /local/domain/5
> vm = "/vm/0a710da9-1bf0-91bc-7097-4b9f7a244a4b"
> device = ""
>  vbd = ""
>   3 = ""
>    virtual-device = "3"
>    device-type = "disk"
>    protocol = "x86_64-abi"
>    backend-id = "0"
>    state = "4"
>    backend = "/local/domain/0/backend/vbd/5/3"
>    ring-ref = "511"
>    event-channel = "5"
>   4 = ""
>    virtual-device = "4"
>    device-type = "disk"
>    protocol = "x86_64-abi"
>    backend-id = "0"
>    state = "3"
>    backend = "/local/domain/0/backend/vbd/5/4"
>    ring-ref = "510"
>    event-channel = "6"
>  vif = ""
>   0 = ""
>    mac = "00:16:3e:10:54:60"
>    handle = "0"
>    protocol = "x86_64-abi"
>    backend-id = "0"
>    state = "4"
>    backend = "/local/domain/0/backend/vif/5/0"
>    tx-ring-ref = "509"
>    rx-ring-ref = "508"
>    event-channel = "7"
>  console = ""
>   0 = ""
>    protocol = "x86_64-abi"
>    state = "1"
>    backend-id = "0"
>    backend = "/local/domain/0/backend/console/5/0"
> control = ""
>  platform-feature-multiprocessor-suspend = "1"
> error = ""
> device-misc = ""
>  vif = ""
>   nextDeviceID = "1"
>  console = ""
>   nextDeviceID = "1"
> console = ""
>  ring-ref = "1138399"
>  port = "2"
>  limit = "1048576"
>  type = "xenconsoled"
>  tty = "/dev/pts/1"
> name = "dom1"
> domid = "5"
> cpu = ""
>  0 = ""
>   availability = "online"
> memory = ""
>  target = "65536"
> store = ""
>  ring-ref = "1141616"
>  port = "1"
> serial = ""
>  0 = ""
>   tty = "/dev/pts/1"
> 
> and this..
> # ps aux | grep xen
> root     614  0.0  0.5 2076  1264 ?     Il    7:47AM 0:00.07 xenconsoled
> root     616  0.0  1.6 2056  4132 ?     I     7:47AM 0:00.00
> /usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start
> root     625  0.0  5.8 2056 15236 ?     Il    7:47AM 0:01.28
> /usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start
> root     682  0.0  0.4 2064  1156 ?     Isl   7:47AM 0:00.02
> /usr/pkg/sbin/xenbackendd
> root     713  0.0  0.6 2124  1596 ?     I     7:47AM 0:01.08 xenstored
> --pid-file /var/run/xenstore.pid
> root     709  0.0  0.4 2060  1136 ttyp0 Il+   7:55AM 0:00.14
> /usr/pkg/bin/xenconsole 5
> 
> (looks like xenconsoled is running and I am attached.. )
> 
> I see here:
> http://wiki.netbsd.se/How_to_set_up_a_guest_OS_using_xen3#Configuring_and_installing_a_NetBSD_DOMU
> 
> 
> that I have to edit /etc/ttys and set the wscons to no.. and doing that,
> or not seems to have no visible change to this.
> 
> pkg_info:
> xen0# pkg_info
> csup-20070216       Rewrite of the CVSup file updating client in C
> digest-20080510     Message digest wrapper utility
> bash-3.2.33         The GNU Bourne Again Shell
> dev86-0.16.17nb2    Linux 8086 development environment
> gmake-3.81          GNU version of 'make' utility
> perl-5.10.0nb2      Practical Extraction and Report Language
> libtool-base-1.5.24nb6 Generic shared library support script (the script
> itself)
> readline-5.2nb2     GNU library that can recall and edit previous input
> python24-2.4.5nb2   Interpreted, interactive, object-oriented
> programming language
> py24-readline-0nb3  Line editing support for Python
> expat-2.0.1         XML parser library written in C
> py24-xml-0.8.4nb2   Collection of libraries to process XML with Python
> ncurses-5.6nb2      CRT screen handling and optimization package
> py24-curses-0nb4    Curses module for Python
> xentools33-3.3.0nb3 Userland Tools for Xen 3.3.x
> xenkernel33-3.3.0nb1 Xen 3.3.0 Kernel
> 
> # cat -n /boot.cfg
>      1  banner=Welcome to NetBSD
>      2  banner==================
>      3  banner=
>      4  banner=Please choose an option from the following menu:
>      5  menu=Boot Xen with 256MB for dom0:load /netbsd-XEN3_DOM0
> console=pc;multiboot /usr/pkg/xen3-kernel/xen.gz dom0_mem=256M
>      6  menu=Boot normally:boot netbsd
>      7  menu=Boot single user:boot netbsd -s
>      8  menu=Disable ACPI:boot netbsd -2
>      9  menu=Disable ACPI and SMP:boot netbsd -12
>     10  menu=Drop to boot prompt:prompt
>     11  default=1
>     12  timeout=5
> 
> Can anyone help?
> 
> Thanks in advance