On Fri, Jun 17, 2011 at 9:34 PM, Anthony PERARD
> On Fri, Jun 17, 2011 at 03:21, Wei Liu <liuw@xxxxxxxxx> wrote:
>> Hi, all
>> This problem has been brought up once by Daniel Castro.
>> But he didn't post the complete log.
>> Now I'm able to reproduce this problem. I have my qemu log below.
>> I think this is a Xen problem. I use Anthony's candidate/xenpv-support
>> branch and test with several Xen reversions.
>> Xen staging unstable r23546, fail
>> Xen staging unstable r23475 (I want to work with IanJ's libxl patch,
>> that's why I choose this reversion), fail
>> Xen unstable r23369, succeed
>> This is not a thorough regression test though. FYI.
>> -----qemu log-----
>> char device redirected to /dev/pts/1
>> Warning: more nics requested than this machine supports; some have been
>> VNC server running on `127.0.0.1:5900'
>> qemu: hardware error: register_ioport_write: invalid opaque for address
>> CPU #0:
>> EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000633
>> ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
>> EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=1
> So, the branch candidate/xenpv-support is a little bit old. I did not
> update this branch since a while.
> But if you just want to run HVM guest, you could use "my" branch
> "xen-next", as it will be merge (soon I hope) in qemu-uptream.
No, I'm not running HVM guest. I'm doing pv development. That's why
I'm not debugging this problem.
> If you need the patches in candidates/xenpv-support, eithier merge it
> or cherry-pick the patch ;).
> Anthony PERARD
Xen-devel mailing list