From: Javier Marcet <jmarcet@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen Devel Mailing list <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2.0-rc4 bugs with GigaByte H77M-D3H + Core i7 3770
Date: Mon, 3 Sep 2012 13:48:11 +0200 [thread overview]
Message-ID: <CAAnFQG_4GwS0CKQnJ2gTW9v3GCmepy51Nw2BpyxtYNRX25D+6g@mail.gmail.com> (raw)
In-Reply-To: <504478B40200007800098286@nat28.tlf.novell.com>
On Mon, Sep 3, 2012 at 9:30 AM, Jan Beulich <JBeulich@suse.com> wrote:
>> I'm sorry I didn't make myself clearer. That dmesg output is when booting
>> WITHOUT xen, that is, linux directly over the bare hardware. Under xen
>> those errors dissapear.
>>
>> The big issue I'm having running xen is that I can't use it since xen can't
>> get the cpu capabilities.
>
> What "cpu capabilities"? I just looked at your original mail again,
> and I cannot see what failure you're referring to (in fact, I'm not
> able to spot any failure in that log at all). And of course you didn't
> even attach a hypervisor log. What am I missing?
I´m sorry for not including that log. I´m still getting to know xen.
I´m using virt-manager to create and manage the VMs. It´s within
virt-manager which xen complains it cannot get the cpu capabilities,
hence the VM can´t boot. I´ll try to check the hypervisor logs.
All the other issues concern the Linux kernel not xen.
--
Javier Marcet <jmarcet@gmail.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-09-03 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 10:43 Xen 4.2.0-rc4 bugs with GigaByte H77M-D3H + Core i7 3770 Javier Marcet
2012-08-30 16:33 ` Konrad Rzeszutek Wilk
2012-08-31 11:09 ` Jan Beulich
2012-09-02 16:30 ` Javier Marcet
2012-09-02 16:35 ` Javier Marcet
2012-09-03 7:30 ` Jan Beulich
2012-09-03 11:48 ` Javier Marcet [this message]
2012-09-04 7:59 ` Javier Marcet
2012-09-04 8:09 ` Jan Beulich
2012-09-04 8:21 ` Javier Marcet
2012-09-02 17:05 ` Javier Marcet
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=CAAnFQG_4GwS0CKQnJ2gTW9v3GCmepy51Nw2BpyxtYNRX25D+6g@mail.gmail.com \
--to=jmarcet@gmail.com \
--cc=JBeulich@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).