From: Wei Liu <liuw@liuw.name>
To: Daniel Castro <evil.dani@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Problems with VNC with upstream Qemu
Date: Mon, 13 Jun 2011 17:06:31 +0800 [thread overview]
Message-ID: <1307955991.5604.9.camel@limbo> (raw)
In-Reply-To: <BANLkTikvpMJgTuCk0QGmm82wTC27qA=q4g@mail.gmail.com>
On Mon, 2011-06-13 at 17:54 +0900, Daniel Castro wrote:
> > No qemu process found?
> >
> > Is your hvm guest running? Please also check /var/log/xen for qemu's
> > log.
> Here is the creation process:
> daniel@dani-ubuntu-xen:/var/xen$ sudo xl create winxp2.cfg
> Parsing config file winxp2.cfg
> xc: info: VIRTUAL MEMORY ARRANGEMENT:
> Loader: 0000000000100000->0000000000199aac
> TOTAL: 0000000000000000->000000001f800000
> ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
> 4KB PAGES: 0x0000000000000200
> 2MB PAGES: 0x00000000000000fb
> 1GB PAGES: 0x0000000000000000
> Daemon running with PID 5176
> daniel@dani-ubuntu-xen:/var/xen$ tail /var/log/xen/xl-test.log
> Waiting for domain test (domid 4) to die [pid 5180]
> daniel@dani-ubuntu-xen:/var/xen$ tail /var/log/xen/qemu-dm-test.log
> EFER=0000000000000000
> FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
> XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
> XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
> XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
>
> The VM is up:
> Name ID Mem VCPUs State Time(s)
> Domain-0 0 2300 4 r----- 2757.4
> test 4 512 1 ------ 0.0
> Yet time is allways 0.0 and there is no qemu-xen process running...
> What could it be? A bug or problem in xl maybe? If I call qemu-xen
> directly it will open qemu normally.
>
>
The guest is waiting for qemu backend. It's not running. Your qemu dies
early.
I use Anthony's qemu as device model, it's working.
git://xenbits.xensource.com/people/aperard/qemu-dm.git
Wei.
> >
> > And, please always use "reply to all" when you're replying back. So that
> > you can post to all people (including the list).
> >
> > Wei.
> >
> >
> >
>
>
>
next prev parent reply other threads:[~2011-06-13 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 0:45 Problems with VNC with upstream Qemu Daniel Castro
2011-06-13 6:02 ` Wei Liu
[not found] ` <BANLkTi=KyyVFtgR3dc-jRPFJkh0G_uw8Tw@mail.gmail.com>
[not found] ` <BANLkTik66gkpBJQzTciMAYqba76kPov4JA@mail.gmail.com>
[not found] ` <BANLkTi=VdD0FT4M7pr6Sy-PFE=jUF-+G4Q@mail.gmail.com>
2011-06-13 8:44 ` Daniel Castro
2011-06-13 8:46 ` Wei Liu
2011-06-13 8:54 ` Daniel Castro
2011-06-13 9:06 ` Wei Liu [this message]
2011-06-13 9:08 ` Daniel Castro
2011-06-13 9:19 ` Wei Liu
2011-06-13 14:19 ` Daniel Castro
2011-06-13 17:04 ` Konrad Rzeszutek Wilk
2011-06-13 17:43 ` Konrad Rzeszutek Wilk
2011-06-13 22:55 ` Daniel Castro
2011-06-14 1:39 ` Konrad Rzeszutek Wilk
2011-06-14 5:58 ` Wei Liu
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=1307955991.5604.9.camel@limbo \
--to=liuw@liuw.name \
--cc=evil.dani@gmail.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.