Problems with VNC with upstream Qemu

Problems with VNC with upstream Qemu

[Daniel Castro]

Hello All,

I have been trying to get VNC with a HVM Guest using latest
qemu-upstream, the guest goes UP but I cannot connect to the VNC I
have tried every vnc entry in the config file. If I use the old
qemu-dm device emulator the VNC works perfectly without any vnc
entries in the conf.

Does qemu-upstream support VNC? Do I need to set-up something specific?

I am running ubuntu 11.04 with Xen staging 4.1 at current tip.

Thanks,

Daniel

-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

Re: Problems with VNC with upstream Qemu

[Wei Liu]

On Mon, 2011-06-13 at 09:45 +0900, Daniel Castro wrote:
> Hello All,
> 
> I have been trying to get VNC with a HVM Guest using latest
> qemu-upstream, the guest goes UP but I cannot connect to the VNC I
> have tried every vnc entry in the config file. If I use the old
> qemu-dm device emulator the VNC works perfectly without any vnc
> entries in the conf.
> 
> Does qemu-upstream support VNC? Do I need to set-up something specific?
> 

Yes, it supports VNC out of the box. No specific configuration is
needed.

> I am running ubuntu 11.04 with Xen staging 4.1 at current tip.
> 

Could you post your config file?

Wei.

> Thanks,
> 
> Daniel
> 

Re: Problems with VNC with upstream Qemu

[Daniel Castro]

Sorry I did not copy the list.

On Mon, Jun 13, 2011 at 5:36 PM, Daniel Castro <evil.dani@gmail.com> wrote:
> On Mon, Jun 13, 2011 at 5:28 PM, Wei Liu <liuw@liuw.name> wrote:
>> On Mon, Jun 13, 2011 at 4:22 PM, Daniel Castro <evil.dani@gmail.com> wrote:
>>> On Mon, Jun 13, 2011 at 3:02 PM, Wei Liu <liuw@liuw.name> wrote:
>>>> On Mon, 2011-06-13 at 09:45 +0900, Daniel Castro wrote:
>>>>> Hello All,
>>>>>
>>>>> I have been trying to get VNC with a HVM Guest using latest
>>>>> qemu-upstream, the guest goes UP but I cannot connect to the VNC I
>>>>> have tried every vnc entry in the config file. If I use the old
>>>>> qemu-dm device emulator the VNC works perfectly without any vnc
>>>>> entries in the conf.
>>>>>
>>>>> Does qemu-upstream support VNC? Do I need to set-up something specific?
>>>>>
>>>>
>>>> Yes, it supports VNC out of the box. No specific configuration is
>>>> needed.
>>>>
>>>>> I am running ubuntu 11.04 with Xen staging 4.1 at current tip.
>>>>>
>>>>
>>>> Could you post your config file?
>>>>
>>> This is the non working:
>>>
>>> device_model_override = "/usr/src/qemu/i386-softmmu/qemu"
>>> builder = 'hvm'
>>> memory = "512"
>>> device_model_version = 'qemu-xen'
>>> disk = [ 'file:/media/Vms/winxp.img,hda,w',
>>> 'file:/media/Vms/isos/en_windows_xp_professional_n_with_service_pack_3_x86_cd_vl_x14-78118.iso,hdb:cdrom,r'
>>> ,  ]
>>> boot = 'dc'
>>> vif = [ '', ]
>>> vcpus='1'}
>>>
>>>> Wei.
>>>>
>>>>> Thanks,
>>>>>
>>>>> Daniel
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>> Try adding:
>>
>> vnc=1
>> vnclisten='0.0.0.0'
>> vncunused=1
>>
>> 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
>

Also here is a working example with a different qemu device model.

The config file:

builder = 'hvm'
name = "winxp"
memory = "512"
disk = [ 'file:/media/Vms/winxp.img,hda,w',
'file:/media/Vms/isos/en_windows_xp_professional_n_with_service_pack_3_x86_cd_vl_x14-78118.iso,hdb:cdrom,r'
,  ]
boot = 'dc'
vif = [ 'bridge=virbr0', ]
vcpus='1'

Output:
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 127.0.0.1:5900          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$
daniel@dani-ubuntu-xen:/var/xen$
daniel@dani-ubuntu-xen:/var/xen$
daniel@dani-ubuntu-xen:/var/xen$ ps aux | grep qemu
root      4767 47.4  0.1 131496  5484 ?        RLsl 17:37   0:05
/usr/lib/xen/bin/qemu-dm -d 3 -domain-name winxp -vnc 127.0.0.1:0
-vncunused -videoram 8 -boot dc -acpi -vcpu_avail 0x1 -net
nic,vlan=0,macaddr=00:16:3e:72:7d:eb,model=rtl8139 -net
tap,vlan=0,ifname=tap3.0,bridge=virbr0,script=no -M xenfv
daniel    4860  0.0  0.0  13076  1080 pts/0    S+   17:37   0:00 grep
--color=auto qemu
daniel@dani-ubuntu-xen:/var/xen$

>
>>
>> Wei.
>>
>>>
>>>
>>> --
>>> +-=====---------------------------+
>>> | +---------------------------------+ | This space intentionally blank
>>> for notetaking.
>>> | |   | Daniel Castro,                |
>>> | |   | Consultant/Programmer.|
>>> | |   | U Andes                         |
>>> +-------------------------------------+
>>>
>>
>
>
>
> --
> +-=====---------------------------+
> | +---------------------------------+ | This space intentionally blank
> for notetaking.
> | |   | Daniel Castro,                |
> | |   | Consultant/Programmer.|
> | |   | U Andes                         |
> +-------------------------------------+
>



-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

Re: Problems with VNC with upstream Qemu

[Wei Liu]

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.

And, please always use "reply to all" when you're replying back. So that
you can post to all people (including the list).

Wei.

Re: Problems with VNC with upstream Qemu

[Daniel Castro]

On Mon, Jun 13, 2011 at 5:46 PM, Wei Liu <liuw@liuw.name> 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                         |
+-------------------------------------+

Re: Problems with VNC with upstream Qemu

[Wei Liu]

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.
> >
> >
> >
> 
> 
> 

Re: Problems with VNC with upstream Qemu

[Daniel Castro]

On Mon, Jun 13, 2011 at 6:06 PM, Wei Liu <liuw@liuw.name> wrote:
> 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

I need to use the same qemu upstream and use that same repository! :(

>
> 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.
>> >
>> >
>> >
>>
>>
>>
>
>
>



-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

Re: Problems with VNC with upstream Qemu

[Wei Liu]

On Mon, 2011-06-13 at 18:08 +0900, Daniel Castro wrote:
> 
> I need to use the same qemu upstream and use that same repository! :(
> 

Anthony is responsible for developing xen support in qemu upstream. Some
of his changesets have been upstreamed. So I think it is ok to use his
repository. I'm doing upstream qemu development, too.

If you insist using the upstream qemu repository, you'd better post
complete log here and CC Anthony <anthony.perard@citrix.com> for help.

Wei.

Re: Problems with VNC with upstream Qemu

[Daniel Castro]

On Mon, Jun 13, 2011 at 6:19 PM, Wei Liu <liuw@liuw.name> wrote:
> On Mon, 2011-06-13 at 18:08 +0900, Daniel Castro wrote:
>>
>> I need to use the same qemu upstream and use that same repository! :(
>>
>
> Anthony is responsible for developing xen support in qemu upstream. Some
> of his changesets have been upstreamed. So I think it is ok to use his
> repository. I'm doing upstream qemu development, too.
>
> If you insist using the upstream qemu repository, you'd better post
> complete log here and CC Anthony <anthony.perard@citrix.com> for help.
>
> Wei.
>
>

Well I decided to recompile following Anthony's wiki page, and
stumbled on this error:
This is extracted from configure.log on
/usr/include/xenctrl.h:970:21: fatal error: xc_e820.h: No such file or directory
compilation terminated.
xe3nctrl.h is found at the location but xc_e820 is not found there.
I am using candidates/xenpv-support branch for qemu and staging
xen-unstable jun 10 tip.
Since I had already compiled qemu I suspected something had changed,
so I decided to switch back to the unstable branch and compile xen
again. Now qemu will configure and compile without errors.

Here is the configure I am using:
daniel@dani-ubuntu-xen:/usr/src/qemu/qemu-dm$ sudo ./configure
--enable-xen --target-list=i386-softmmu
--extra-cflags="-I$/usr/src/staging-xen-unstable/dist/install/usr/include"
--extra-ldflags="-L$/usr/src/staging-xen-unstable/dist/install/usr/lib"
This is the error I am getting:
ERROR
ERROR: User requested feature xen
ERROR: configure was not able to find it
ERROR

If anyone needs me to reproduce it just drop me a line.


-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

Re: Problems with VNC with upstream Qemu

[Konrad Rzeszutek Wilk]

On Mon, Jun 13, 2011 at 11:19:26PM +0900, Daniel Castro wrote:
> On Mon, Jun 13, 2011 at 6:19 PM, Wei Liu <liuw@liuw.name> wrote:
> > On Mon, 2011-06-13 at 18:08 +0900, Daniel Castro wrote:
> >>
> >> I need to use the same qemu upstream and use that same repository! :(
> >>
> >
> > Anthony is responsible for developing xen support in qemu upstream. Some
> > of his changesets have been upstreamed. So I think it is ok to use his
> > repository. I'm doing upstream qemu development, too.
> >
> > If you insist using the upstream qemu repository, you'd better post
> > complete log here and CC Anthony <anthony.perard@citrix.com> for help.
> >
> > Wei.
> >
> >
> 
> Well I decided to recompile following Anthony's wiki page, and
> stumbled on this error:
> This is extracted from configure.log on
> /usr/include/xenctrl.h:970:21: fatal error: xc_e820.h: No such file or directory
> compilation terminated.
> xe3nctrl.h is found at the location but xc_e820 is not found there.

Hmmm..Let me send you a patch for that.

Re: Problems with VNC with upstream Qemu

[Konrad Rzeszutek Wilk]

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

On Mon, Jun 13, 2011 at 01:04:22PM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 13, 2011 at 11:19:26PM +0900, Daniel Castro wrote:
> > On Mon, Jun 13, 2011 at 6:19 PM, Wei Liu <liuw@liuw.name> wrote:
> > > On Mon, 2011-06-13 at 18:08 +0900, Daniel Castro wrote:
> > >>
> > >> I need to use the same qemu upstream and use that same repository! :(
> > >>
> > >
> > > Anthony is responsible for developing xen support in qemu upstream. Some
> > > of his changesets have been upstreamed. So I think it is ok to use his
> > > repository. I'm doing upstream qemu development, too.
> > >
> > > If you insist using the upstream qemu repository, you'd better post
> > > complete log here and CC Anthony <anthony.perard@citrix.com> for help.
> > >
> > > Wei.
> > >
> > >
> > 
> > Well I decided to recompile following Anthony's wiki page, and
> > stumbled on this error:
> > This is extracted from configure.log on
> > /usr/include/xenctrl.h:970:21: fatal error: xc_e820.h: No such file or directory
> > compilation terminated.
> > xe3nctrl.h is found at the location but xc_e820 is not found there.
> 
> Hmmm..Let me send you a patch for that.

Can you try the attached file please?

[-- Attachment #2: tools-fix-compile-error-out-of-tree.patch --]
[-- Type: text/x-diff, Size: 3469 bytes --]

# HG changeset patch
# Parent 5d31bd0eb8d040c0b44fe2a3b737fd752a607e74
Squash xc_e820.h (and delete) into xenctrl.h

.. as there is no need to keep that internal header file anymore.
We export two functions xc_domain_[set|get]_memory_map which
depend on the 'struct e820entry' defined in 'xc_e820.h'.

We move the contents of the 'xc_e820.h' to the 'xenctrl.h' fixing
compiler errors when applications outside the Xen tree are trying
to compile against the libraries.

Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

diff -r 5d31bd0eb8d0 tools/libxc/xc_core_x86.c
--- a/tools/libxc/xc_core_x86.c	Wed Jun 01 16:10:50 2011 -0400
+++ b/tools/libxc/xc_core_x86.c	Mon Jun 13 13:41:31 2011 -0400
@@ -20,7 +20,7 @@
 
 #include "xg_private.h"
 #include "xc_core.h"
-#include "xc_e820.h"
+#include <xen/hvm/e820.h>
 
 #define GET_FIELD(_p, _f) ((dinfo->guest_width==8) ? ((_p)->x64._f) : ((_p)->x32._f))
 
diff -r 5d31bd0eb8d0 tools/libxc/xc_domain_save.c
--- a/tools/libxc/xc_domain_save.c	Wed Jun 01 16:10:50 2011 -0400
+++ b/tools/libxc/xc_domain_save.c	Mon Jun 13 13:41:31 2011 -0400
@@ -32,7 +32,6 @@
 #include "xg_save_restore.h"
 
 #include <xen/hvm/params.h>
-#include "xc_e820.h"
 
 /*
 ** Default values for important tuning parameters. Can override by passing
diff -r 5d31bd0eb8d0 tools/libxc/xc_e820.h
--- a/tools/libxc/xc_e820.h	Wed Jun 01 16:10:50 2011 -0400
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,39 +0,0 @@
-/*
- * This library is free software; you can redistribute it and/or
- * modify it under the terms of the GNU Lesser General Public
- * License as published by the Free Software Foundation;
- * version 2.1 of the License.
- *
- * This library is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
- * Lesser General Public License for more details.
- *
- * You should have received a copy of the GNU Lesser General Public
- * License along with this library; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
- */
-
-#ifndef __XC_E820_H__
-#define __XC_E820_H__
-
-#include <xen/hvm/e820.h>
-
-/*
- * PC BIOS standard E820 types and structure.
- */
-#define E820_RAM          1
-#define E820_RESERVED     2
-#define E820_ACPI         3
-#define E820_NVS          4
-#define E820_UNUSABLE     5
-
-#define E820MAX           (128)
-
-struct e820entry {
-    uint64_t addr;
-    uint64_t size;
-    uint32_t type;
-} __attribute__((packed));
-
-#endif /* __XC_E820_H__ */
diff -r 5d31bd0eb8d0 tools/libxc/xenctrl.h
--- a/tools/libxc/xenctrl.h	Wed Jun 01 16:10:50 2011 -0400
+++ b/tools/libxc/xenctrl.h	Mon Jun 13 13:41:31 2011 -0400
@@ -967,7 +967,22 @@ int xc_domain_set_memmap_limit(xc_interf
                                unsigned long map_limitkb);
 
 #if defined(__i386__) || defined(__x86_64__)
-#include "xc_e820.h"
+/*
+ * PC BIOS standard E820 types and structure.
+ */
+#define E820_RAM          1
+#define E820_RESERVED     2
+#define E820_ACPI         3
+#define E820_NVS          4
+#define E820_UNUSABLE     5
+
+#define E820MAX           (128)
+
+struct e820entry {
+    uint64_t addr;
+    uint64_t size;
+    uint32_t type;
+} __attribute__((packed));
 int xc_domain_set_memory_map(xc_interface *xch,
                                uint32_t domid,
                                struct e820entry entries[],

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Problems with VNC with upstream Qemu

[Daniel Castro]

On Tue, Jun 14, 2011 at 2:43 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Jun 13, 2011 at 01:04:22PM -0400, Konrad Rzeszutek Wilk wrote:
>> On Mon, Jun 13, 2011 at 11:19:26PM +0900, Daniel Castro wrote:
>> > On Mon, Jun 13, 2011 at 6:19 PM, Wei Liu <liuw@liuw.name> wrote:
>> > > On Mon, 2011-06-13 at 18:08 +0900, Daniel Castro wrote:
>> > >>
>> > >> I need to use the same qemu upstream and use that same repository! :(
>> > >>
>> > >
>> > > Anthony is responsible for developing xen support in qemu upstream. Some
>> > > of his changesets have been upstreamed. So I think it is ok to use his
>> > > repository. I'm doing upstream qemu development, too.
>> > >
>> > > If you insist using the upstream qemu repository, you'd better post
>> > > complete log here and CC Anthony <anthony.perard@citrix.com> for help.
>> > >
>> > > Wei.
>> > >
>> > >
>> >
>> > Well I decided to recompile following Anthony's wiki page, and
>> > stumbled on this error:
>> > This is extracted from configure.log on
>> > /usr/include/xenctrl.h:970:21: fatal error: xc_e820.h: No such file or directory
>> > compilation terminated.
>> > xe3nctrl.h is found at the location but xc_e820 is not found there.
>>
>> Hmmm..Let me send you a patch for that.
>
> Can you try the attached file please?
>

Thanks for the help but the patch fails, it was already part of the source.

-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

Re: Problems with VNC with upstream Qemu

[Konrad Rzeszutek Wilk]

> >> > Well I decided to recompile following Anthony's wiki page, and
> >> > stumbled on this error:
> >> > This is extracted from configure.log on
> >> > /usr/include/xenctrl.h:970:21: fatal error: xc_e820.h: No such file or directory
> >> > compilation terminated.
> >> > xe3nctrl.h is found at the location but xc_e820 is not found there.
> >>
> >> Hmmm..Let me send you a patch for that.
> >
> > Can you try the attached file please?
> >
> 
> Thanks for the help but the patch fails, it was already part of the source.

Really? That I find quite surprising. What Xen tree are you using then? What is
the error you get when you apply the patch?

Re: Problems with VNC with upstream Qemu

[Wei Liu]

On Mon, 2011-06-13 at 23:19 +0900, Daniel Castro wrote:
> 
> Well I decided to recompile following Anthony's wiki page, and
> stumbled on this error:
> This is extracted from configure.log on
> /usr/include/xenctrl.h:970:21: fatal error: xc_e820.h: No such file or directory
> compilation terminated.
> xe3nctrl.h is found at the location but xc_e820 is not found there.
> I am using candidates/xenpv-support branch for qemu and staging
> xen-unstable jun 10 tip.
> Since I had already compiled qemu I suspected something had changed,
> so I decided to switch back to the unstable branch and compile xen
> again. Now qemu will configure and compile without errors.
> 
> Here is the configure I am using:
> daniel@dani-ubuntu-xen:/usr/src/qemu/qemu-dm$ sudo ./configure
> --enable-xen --target-list=i386-softmmu
> --extra-cflags="-I$/usr/src/staging-xen-unstable/dist/install/usr/include"
> --extra-ldflags="-L$/usr/src/staging-xen-unstable/dist/install/usr/lib"
> This is the error I am getting:
> ERROR
> ERROR: User requested feature xen
> ERROR: configure was not able to find it
> ERROR
> 
> If anyone needs me to reproduce it just drop me a line.
> 
> 

I've come across this error before, which is caused by incorrect header
path and lib path.

I am using xen unstable, not the *staging* unstable. I use
candidates/xenpv-support branch, too.

Hope this helps.

Wei.