From: Ian Murray <murrayie@yahoo.co.uk>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Alex Bligh <alex@alex.org.uk>,
xen-devel@lists.xen.org
Subject: Re: Problem starting HVM guest in Xen 4.3 RC6 when NOT using device_model_version="qemu-xen-traditional"
Date: Sat, 29 Jun 2013 17:45:21 +0100 [thread overview]
Message-ID: <51CF0F21.5070606@yahoo.co.uk> (raw)
In-Reply-To: <956778643.20130629164038@eikelenboom.it>
>>> 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@xxxxxx.com>
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
>
>> 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
>
>> Thanks for all your help.
>
next prev parent reply other threads:[~2013-06-29 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 1:33 Problem starting HVM guest in Xen 4.3 RC6 when NOT using device_model_version="qemu-xen-traditional" Ian Murray
2013-06-29 8:35 ` Alex Bligh
2013-06-29 10:49 ` Ian Murray
2013-06-29 11:33 ` Ian Murray
2013-06-29 12:36 ` Sander Eikelenboom
2013-06-29 12:47 ` Ian Murray
2013-06-29 13:13 ` Sander Eikelenboom
2013-06-29 14:33 ` Ian Murray
2013-06-29 14:40 ` Sander Eikelenboom
2013-06-29 16:45 ` Ian Murray [this message]
2013-06-29 20:34 ` Sander Eikelenboom
2013-06-29 21:07 ` Ian Murray
2013-07-01 8:35 ` Ian Campbell
2013-07-01 12:26 ` Ian Murray
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=51CF0F21.5070606@yahoo.co.uk \
--to=murrayie@yahoo.co.uk \
--cc=Ian.Campbell@citrix.com \
--cc=alex@alex.org.uk \
--cc=linux@eikelenboom.it \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.