similar to: Bug#805508: xen: Unable to create HVM domUs

On 19.11.2015 11:00, Ian Campbell wrote: > On Wed, 2015-11-18 at 23:07 +0000, Thomas Jepp wrote: >> >> [...] >> xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal error > > This is the wrong path, in the Debian packages it should be /usr/lib/xen- > 4.6/boot/hvmloader (and this should be arranged by

On Thu, 2015-11-26 at 14:17 +0100, Stefan Bader wrote: > On 19.11.2015 11:00, Ian Campbell wrote: > > On Wed, 2015-11-18 at 23:07 +0000, Thomas Jepp wrote: > > > > > > [...] > > > xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' > > > (2 = No such file or directory): Internal error > > > > This is the wrong

On Wed, 2015-11-18 at 23:07 +0000, Thomas Jepp wrote: > > [...] > xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal error This is the wrong path, in the Debian packages it should be?/usr/lib/xen- 4.6/boot/hvmloader (and this should be arranged by the packaging, i.e. it is not a configuration error on your part).

Package: xen-utils-4.6 Version: 4.6.0-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these

Dear Xen-Team, after an debian-update (jessie) the hvm do not start: I'm not sure it's a bug or a support-question? If it's a bug I don't know which packet is affected. <http://www.dict.cc/englisch-deutsch/affected.html> I get now response on mailing lists so it look looks like bug fore me. The hvm works fine until I did 'apt-get upgrade' ( I think on Aug 9).

hi, i am trying to create hvm in xen via libvirt but i am facing some error. i installed the packages like bltap-utils, blktap-dkms in my dom0. virsh create tiny_core.xml p11-kit: invalid config filename, will be ignored in the future: /etc/pkcs11/modules/gnome-keyring-module error: Failed to create domain from tiny_core.xml error: internal error: libxenlight failed to create new domain

On Thu, 2015-11-26 at 15:16 +0000, Ian Campbell wrote: > anything better would need to be arranged upstream. http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=de858271c16851d662b2613 699401df6ecec8ef8 has now landed upstream, which allows the leaf dir to be set at configure time and therefore allows the packaging to avoid patching some stuff. HVM guests have been broken in Stretch for ages

This small series reintroduces OVMF support in Xen You can fetch working OVMF tree on: git://xenbits.xen.org/people/liuw/ovmf.git master Working changeset that can be sticked in Config.mk is: 8833370303d3bf3153760ee42760ef1b9b5c562 Note that VNC doesn''t work properly when using OVMF, but that''s not OVMF''s problem. This issue should be addressed in Xen and I''m

Package: xen-hypervisor-4.6-amd64 Version: 4.6.0-1 Severity: normal Dear maintaners, I was using XEN 4.4 on that machine ("unstable") and want to switch to 4.6. All xen stuff was uninstalled (XEN 4.4), the machine restarted before installing 4.6. When I uninstall XEN 4.4 (libxenlight4.4) it deinstall also part of QEMU and when I reinstall QEMU libxenlight-4.4 aws reinstalled. First

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add

Control: reassign -1 src:xen On Sb, 23 aug 14, 18:18:51, Thomas Jepp wrote: > After doing a xen upgrade this morning to 4.4 I hit this same issue. > > I?ve compiled a set of test packages from this commit: http://anonscm.debian.org/cgit/pkg-xen/xen.git/commit/?h=feature/seabios&id=44daa679dc80f2df734e5471476df159bc0ad38d > > My HVM domUs now start as expected so this seems to

I do not know the history there. I could imagine it once was done to allow a stable and bleeding edge version of Xen to co-exist. Though today there might be reasons to re-think: - libvirt * 1.2.12 starts to validate configs and requires full path specifications for hvmloader, pygrub, and qemu. Things are not completely cleared up, yet. But for the future the xen build would create a

On Wed, Feb 18, 2015 at 02:53:07PM +0100, Stefan Bader wrote: > - libvirt > * 1.2.12 starts to validate configs and requires full path specifications > for hvmloader, pygrub, and qemu. Things are not completely cleared up, > yet. But for the future the xen build would create a xenlight.pc that > communicates the used paths. But still this would require to rewrite >

This patch series adds the ability to selectively disable the S3 and S4 ACPI power states for HVM guests. Since there is a general move towards retiring the hvm_info_table structure, the first patch moves the acpi_enabled flag out of the hvm_info_table and into a xenstore key (platform/acpi). The second patch then introduces the acpi_s3 and acpi_s4 configuration parameters to the xl config file

I know these are mostly gamers but they have a lot of experience doing PCI pass though: https://discord.gg/du9ecG I have found them extremely helpful in the past doing libvirt PCI passthough. *Paul O'Rorke* On 2020-02-05 10:13 a.m., Jim Fehlig wrote: > On 2/4/20 1:04 AM, Christoph wrote: >> this config does not work... why? > > Without more details, I don't know why

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

On 15/05/2015 09:41, Sebastian Pipping wrote: > * I noticed that [1] says 4.4.1-9 not to be vulnerable ("fixed") > but according to the Debian Changelog [2] 4.4.1-9 appeared > in Debian before XSA-133 was published and > xen_4.4.1-9.debian.tar.xz [3] does not seem to contain > any XSA-133 patch. Could you elaborate why 4.4.1-9 is not affected? This would

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The vast majority of the code is in second patch. The first patch merely changes the xenstore key name used by hvmloader to store the buffer address.

The following is a revised patch series to add support for a VM generation ID virtual device for HVM guests. The basic requirements of this device are as follows: - It must be exposed somewhere in ACPI namespace with a _CID of "VM_Gen_Counter". - It must also include a _DDN of "VM_Gen_Counter". - It must contain a _HID object but no particular value is required. - It must

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: normal II'm install xen-4.3 from official repository. When i try create virtulal machine got error: xl -vvvv create /etc/xen/xlexample.hvm Parsing config from /etc/xen/xlexample.hvm libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x19811c0: create: how=(nil) callback=(nil) poller=0x1981220 libxl: verbose: