All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Duncan X. Simpson" <virtualdxs@gmail.com>
To: xen-devel@lists.xenproject.org
Subject: Re: Can't read bios file
Date: Tue, 04 Apr 2017 02:05:35 +0000	[thread overview]
Message-ID: <CAB8Qo2TVkkaq_zYA9Ds1J8sKOzRt1hWLyMvxfnCt-QabuF1Mxg@mail.gmail.com> (raw)
In-Reply-To: <CAB8Qo2RMZnS8=MM-n8tfKbPL_Kk=0sc=f5tViadgTY7P+AYVuQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2240 bytes --]

I apologize, I should probably include this information:
OS: Arch Linux
xl info:
host                   : k7dxs-laptop-r500
release                : 4.10.6-1-ARCH
version                : #1 SMP PREEMPT Mon Mar 27 08:28:22 CEST 2017
machine                : x86_64
nr_cpus                : 2
max_cpu_id             : 3
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2394
hw_caps                :
b7ebfbff:0408e3fd:20100800:00000001:00000000:00000000:00000000:00000000
virt_caps              : hvm
total_memory           : 1944
free_memory            : 517
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 8
xen_extra              : .0
xen_version            : 4.8.0
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          :
xen_commandline        : /boot/xen-4.8.0.gz xsave=1
cc_compiler            : gcc (GCC) 6.3.1 20170306
cc_compile_by          : duncan
cc_compile_domain      :
cc_compile_date        : Tue Mar 28 15:11:08 MST 2017
build_id               : 8b7628e151ee56a26b2f83b21160ee1168263b64
xend_config_format     : 4


On Mon, Apr 3, 2017 at 6:25 PM Duncan X. Simpson <virtualdxs@gmail.com>
wrote:

I'm trying to set up an HVM CentOS guest, and I've run into a problem. I
originally tried posting it on Stack Exchange (
https://superuser.com/questions/1193771/failed-to-read-bios-file-no-such-file-or-directory),
but it is not documented anywhere on the Internet that Google can see and I
have gotten no response. I regained interest in it today and used strace to
determine what bios file it was looking for, and found it was looking for a
file called 'yes' in the current directory. This is what made me decide it
was most likely a bug and post it here rather in xen-users. My
configuration is as listed on the Stack Exchange question and does not
contain the word yes anywhere in it. What should I do next?
-- 

Duncan X. Simpson, K7DXS

-- 

Duncan X. Simpson, K7DXS

[-- Attachment #1.2: Type: text/html, Size: 4373 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  reply	other threads:[~2017-04-04  2:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04  1:25 Can't read bios file Duncan X. Simpson
2017-04-04  2:05 ` Duncan X. Simpson [this message]
2017-04-04 18:03   ` Duncan X. Simpson
2017-04-05  1:39     ` Duncan X. Simpson
2017-04-05  9:57       ` Anthony PERARD
2017-04-05 13:43         ` Duncan X. Simpson

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=CAB8Qo2TVkkaq_zYA9Ds1J8sKOzRt1hWLyMvxfnCt-QabuF1Mxg@mail.gmail.com \
    --to=virtualdxs@gmail.com \
    --cc=xen-devel@lists.xenproject.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.