All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Keith Coleman <list.keith@scaltro.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Stub domains broken in 3.4.0-rc3?
Date: Fri, 8 May 2009 19:44:25 +0100	[thread overview]
Message-ID: <4A047D89.60002@eu.citrix.com> (raw)
In-Reply-To: <5411dbdc0905080928m58ca21c3jab7992114dc55f85@mail.gmail.com>

The problem seems to be the "phy" disk that does not work correctly, but
I don't think it is caused by a bug in the new stubdomain config file
generator.
In fact I can reproduce the bug even using the old stubdom-dm script.

Keith Coleman wrote:

> 
> My current config file is just a slightly modified version of the
> xmexample.hvm. It works for regular HVM mode if I switch the
> stubdom-dm for qemu-dm. I have fs-backend running in the background.
> 
> # cat stub1-clean
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 512
> name = "stub1"
> vif = [ 'type=ioemu, bridge=eth0' ]
> disk = [ 'phy:/dev/testvg/stub1,hda,w',
>          'file:/root/isos/win2003entR2.iso,hdc:cdrom,r' ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/stubdom-dm'
> #device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> boot="dca"
> sdl=0
> opengl=1
> vnc=1
> vnclisten="0.0.0.0"
> vncpasswd=''
> stdvga=0
> serial='pty'
> usb=1
> usbdevice='tablet'
> 
> 
> # cat /var/log/xen/qemu-dm-stub1.log
> Error: Device 768 (vbd) could not be connected.
> Device /dev/mapper/testvg-stub1 is mounted in a guest domain,
> and so cannot be mounted now.
> Using config file "/etc/xen/stubdoms/stub1-dm".
> Using config file "/etc/xen/stubdoms/stub1-dm".
> 
> # cat /var/log/xen/qemu-dm-stub1-dm.log
> domid: 71
> Warning: vlan 0 is not connected to host network
> Strip off blktap sub-type prefix to /root/isos/win2003entR2.iso (drv 'aio')
> Watching /local/domain/0/device-model/71/logdirty/next-active
> Watching /local/domain/0/device-model/71/command
> char device redirected to /dev/pts/3
> /root/xen-3.4-rc3/xen-unstable.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
> Init blktap pipes
> xs_read(): vncpasswd get error.
> /vm/e0dd1e52-a827-8c47-7e3d-cc26941e4419/vncpasswd.
> medium change watch on `hdc' (index: 1): aio:/root/isos/win2003entR2.iso
> 
> 
> 
> -Keith
> 

  reply	other threads:[~2009-05-08 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 19:56 Stub domains broken in 3.4.0-rc3? Keith Coleman
2009-05-08  4:47 ` Dulloor
2009-05-08 14:20 ` Stefano Stabellini
2009-05-08 16:28   ` Keith Coleman
2009-05-08 18:44     ` Stefano Stabellini [this message]
2009-05-08 21:35       ` Keith Coleman
2009-05-08 23:41         ` Thiago Camargo Martins Cordeiro
2009-05-09  7:57           ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A047D89.60002@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=list.keith@scaltro.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.