Re: [Xen-devel] Problem starting HVM guest in Xen 4.3 RC6 when NOT using device_model_version="qemu-xen-traditional"

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Saturday, June 29, 2013, 6:45:21 PM, you wrote:


>>>> And in fact it is the latest ?
>>>>
>>>> Hrmmm it seems a make clean && git pull && make in the xen dir, does 
>>>> update the commit id for the qemu tree in Config.mk
>>>> But the tree it self in /tools/qemu-xen-dir doesn't seem to be updated 
>>>> accordingly ..
>>>>
>>>> Could it be your tools/qemu-xen-dir is also not on the latest commit ?
> Yes, you were correct. Well done and thank-you.

>>> This is beyond my knowledge, to please persevere with me :)
>>> Here are what I think are the relevant bits of my Config.mk. That qemu
>>> commit ID seems to match the change in the last commit before RC6,
>>> according to gitweb.
>>> How can I tell if tools/qemu-xen-dir matches this?
>> Just do a git log in the tools/qemu-xen-dir and seem what the latest commit 
>> is (and compare to what it should be according to the Config.mk).
> I did try this but I wasn't convinced I understood what I was looking 
> at. Here is the top few lines...

> commit 59e2fb7252dbdc008a63d144b19be0cd8d873128
> Author: Felipe Franciosi <felipe.franciosi@xxxxxxxxxx>
> Date:   Fri Apr 5 15:47:59 2013 +0000



>> When you are working with an old xen clone it seems you also have the change 
>> running an old(er) qemu since it doesn't seem to be auto updated to the 
>> commit id from the Config.mk
> I am not quite following your logic here. Without understanding how it 
> actually does it, I would presume the logical thing to do is to bring 
> the repository up to date then checkout the specified commit. This 
> wouldn't necessarily be the latest commit as you may wish to go back in 
> time. OTH if it can't checkout the required commit IMHO it should be a 
> fatal situation because you can end-up in an unknown state (like I did).

> Maybe I am misunderstanding what is at work here

Yes it's not very ideal. Since the xen build depends on other git trees 
(seabios, qemu) and these are pulled automatically on the first build after a 
clone.
It's not strange to assume that these trees also get updates automatically when 
you update you local xen tree. But it seems to be not a valid assumption :-)

Don't know if it is easy to fix, because it could interfere with the workflow 
of active developers/maintainers i guess.

>>
>>> I think I will make a new clone of Xen.
>> A fresh clone should fix that up since that also pulls a fresh qemu tree in.

> Which it did. Thanks again

So after a fresh clone and build of the xen tree your hvm guests now boots 
without problem ?

>>
>>> Thanks for all your help.
>>




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel