Re: [Xen-devel] More on domU not starting -- HELP

[Rob Gardner <rob.gardner@xxxxxx>]

Ted Kaczmarek wrote:

> What changeset are you using?
>  
4e335372ace8

Note that I got this by just doing 'hg clone 
http://xenbits.xensource.com/xen-unstable.hg'
I did not change a thing, just did a make world and installed the stuff.

(Am I wrong to assume that this procedure will produce a xen that works?)

> Did your kernel config work before?
>  
I had no special config, just was using whatever the default is in the 
repository I cloned.
> My Xen domO
>
> CONFIG_XEN_PRIVILEGED_GUEST=y
> CONFIG_XEN_PHYSDEV_ACCESS=y
> CONFIG_XEN_BLKDEV_BACKEND=y
> # CONFIG_XEN_BLKDEV_TAP_BE is not set
> CONFIG_XEN_NETDEV_BACKEND=y
> # CONFIG_XEN_TPMDEV_FRONTEND is not set
> # CONFIG_XEN_TPMDEV_BACKEND is not set
> CONFIG_XEN_BLKDEV_FRONTEND=y
> # CONFIG_XEN_NETDEV_FRONTEND is not set
> # CONFIG_XEN_BLKDEV_TAP is not set
> # CONFIG_XEN_SHADOW_MODE is not set
> CONFIG_XEN_SCRUB_PAGES=y
> CONFIG_XEN_X86=y
> # CONFIG_XEN_X86_64 is not set
> CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
>  
My xen dom0:

CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PHYSDEV_ACCESS=y
CONFIG_XEN_BLKDEV_BACKEND=y
# CONFIG_XEN_BLKDEV_TAP_BE is not set
CONFIG_XEN_NETDEV_BACKEND=y
# CONFIG_XEN_TPMDEV_FRONTEND is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
# CONFIG_XEN_BLKDEV_TAP is not set
# CONFIG_XEN_SHADOW_MODE is not set
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_X86=y
# CONFIG_XEN_X86_64 is not set
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y



> My xen domU
>
> # CONFIG_XEN_PRIVILEGED_GUEST is not set
> # CONFIG_XEN_PHYSDEV_ACCESS is not set
> # CONFIG_XEN_TPMDEV_FRONTEND is not set
> # CONFIG_XEN_TPMDEV_BACKEND is not set
> CONFIG_XEN_BLKDEV_FRONTEND=y
> CONFIG_XEN_NETDEV_FRONTEND=y
> # CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
> # CONFIG_XEN_BLKDEV_TAP is not set
> # CONFIG_XEN_SHADOW_MODE is not set
> CONFIG_XEN_SCRUB_PAGES=y
> CONFIG_XEN_X86=y
> # CONFIG_XEN_X86_64 is not set
> CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
>
>  
My xen domU:

# CONFIG_XEN_PRIVILEGED_GUEST is not set
# CONFIG_XEN_PHYSDEV_ACCESS is not set
# CONFIG_XEN_TPMDEV_FRONTEND is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
# CONFIG_XEN_BLKDEV_TAP is not set
# CONFIG_XEN_SHADOW_MODE is not set
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_X86=y
# CONFIG_XEN_X86_64 is not set
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y




> Might also help to try a loop image as well and see if that will play
> nice.
>  
That's what I'm doing. My config file looks like this:
 ...snip...
xm_vars.check()
kernel = "/boot/vmlinuz-2.6.12-xenU"
memory = 128
name = "Rob-VM%d" % vmid
cpu = vmid  # set based on vmid (mod number of CPUs)
nics=1
disk = [ 'file:/xen/disk-images/dom1.fs,sda1,w']
ip = add_offset_to_ip(get_current_ipaddr(),vmid)
netmask = get_current_ipmask()
gateway = get_current_ipgw()
hostname= "vm%d" % vmid
root = "/dev/sda1 ro"
extra = "4 VMID=%d" % vmid

Here's another bit of info... running 'xm block-list' on the domU that 
doesn't boot successfully gives:
  (2065 ((virtual-device 2065) (backend-id 0) (backend 
/local/domain/0/backend/vbd/1/2065) (ring-ref 8) (event-channel 6) 
(error '2 reading   backend fields at /local/domain/0/backend/vbd/1/2065')))


Rob



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