[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Problems with VNC with upstream Qemu
On Mon, Jun 13, 2011 at 5:46 PM, Wei Liu <liuw@xxxxxxxxx> wrote: > Add xen-devel back in CC list. > > On Mon, 2011-06-13 at 17:36 +0900, Daniel Castro wrote: >> > >> > in your config file. >> :( >> Did not work >> > >> > And netstat -ntlp in dom0 to see if vnc is up and running. >> > >> > And run ps aux | grep qemu to see if vnc options are added to qemu >> > correctly. >> Here is the output of both commands: >> >> daniel@dani-ubuntu-xen:/var/xen$ netstat -ntlp >> (Not all processes could be identified, non-owned process info >> will not be shown, you would have to be root to see it all.) >> Active Internet connections (only servers) >> Proto Recv-Q Send-Q Local Address Foreign Address >> State PID/Program name >> tcp 0 0 192.168.122.1:53 0.0.0.0:* >> LISTEN - >> tcp 0 0 0.0.0.0:56375 0.0.0.0:* >> LISTEN - >> tcp 0 0 127.0.0.1:631 0.0.0.0:* >> LISTEN - >> tcp 0 0 0.0.0.0:36321 0.0.0.0:* >> LISTEN - >> tcp 0 0 0.0.0.0:2049 0.0.0.0:* >> LISTEN - >> tcp 0 0 0.0.0.0:55145 0.0.0.0:* >> LISTEN - >> tcp 0 0 0.0.0.0:111 0.0.0.0:* >> LISTEN - >> tcp6 0 0 ::1:631 :::* >> LISTEN - >> daniel@dani-ubuntu-xen:/var/xen$ ps aux | grep qemu >> daniel 4547 0.0 0.0 13076 1084 pts/0 S+ 17:35 0:00 grep >> --color=auto qemu >> > > 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. > > And, please always use "reply to all" when you're replying back. So that > you can post to all people (including the list). > > Wei. > > > -- +-=====---------------------------+ | +---------------------------------+ | This space intentionally blank for notetaking. | | | Daniel Castro, | | | | Consultant/Programmer.| | | | U Andes | +-------------------------------------+ _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |