similar to: hvm and qemu-system-i386 broken

On Tue, 2014-08-26 at 17:33 +0200, Hermann Maier wrote: > 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. I believe this is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737905, the fix is pending. Ian.

Hi, after an debian-update (jessie) the hvm do not start: >xl create mywin7.xm Parsing config from mywin7.xm xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001a0164 Modules: 0000000000000000->0000000000000000 TOTAL: 0000000000000000->000000003e000000 ENTRY ADDRESS: 0000000000100608 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB

Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and

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

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: important Tags: upstream patch When using Xen compiled with seabios-1.7.4-1 (now in unstable/testing), HVMs fail immediately upon starting with a VCPU triple fault: (XEN) HVM1: Loading SeaBIOS ... (XEN) hvm.c:1253:d1 Triple fault on VCPU0 - invoking HVM shutdown action 1. This is because SeaBIOS can now be greater than 128k, which breaks an

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

As part of coreutils' bootstrap, rsync crashes on cygwin: $ /usr/bin/rsync \ --delete \ --exclude '*.s1' \ -Lrtvz 'translationproject.org::tp/latest/coreutils/' \ 'po/.reference' rsync: failed to connect to translationproject.org (*inet_ntop failed*): Connection refused (111) Segmentation fault (core dumped) $ cat rsync.exe.stackdump

I am using Xen-4.4.0, libvirt-1.2.9 My ubuntu.cfg is: ubuntu10.cfg bootloader = "/usr/local/lib/xen/boot/hvmloader" builder="hvm" memory = 512 name = "ubuntu" vif = [ "type=ioemu,bridge=ovsbr0", "type=ioemu,bridge=ovsbr0","type=ioemu,bridge=ovsbr0","type=ioemu,bridge=ovsbr0",,"type=ioemu,bridge=ovsbr0"]

Hi all, These days I installed xen 4.3 unstable from source and recompiled qemu upstream with spice support. After xl create , the windows domU started successfully and spice client can visit the VDI. However, it display blue screen before entering the windows welcome screen. Is it a bug in current upstream qemu support? My domU configuration file is: builder =

Signed-off-by: Attilio Rao <attilio.rao@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> --- Differences with previous revision: - Improvements to the manpage: * s/operated/made * s/compatbile/compatible * New paragraph for rombios, provided by Ian * s/force/request * redundant line removal in UEFI explanatory * Wrap of lines at 80 cols diff -r adcd6ab160fa

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Severity: normal When I try to create an HVW withDevian/xen, I run into trouble. It used to work, maybe with xen 4.1, but it has never worked since. Bug 688311 was filed, with the same exact problem. That bug was somehow closed and no resolution or explanation was provided. I have seen posts mentioning "traditional" and "upstream"

So how do I set up an HVM with Debian? I tried with device_model_version="qemu-xen", and I got this: libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm: device model /usr/lib/xen-4.2/bin/qemu-system-i386 is not executable: No such file or directory I also tried device_model_version="qemu-xen-traditional", and I got this: libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm:

Did something had chaqnged with spice code or settings. I just compiled latest git of 4.4 unstable and I get is a black screen all I see is the green boot image from server 2012 but I dont get blue windows logo and window does not resize it stays black. I reverted back to older git revision of 4.4 and everything is working fine with. _______________________________________________ Xen-users

On 01/02/2014 11:56 AM, Ian Campbell wrote: > You can select a non-default model use by using the > "device_model_version" directive in your config. From what I gather, for now, you MUST select a non-default model, using something like: device_model_version="qemu-xen" device_model_override="/usr/bin/qemu-system-x86_64" > In the context of Debian the

I've uploaded seabios 1.7.4-2 to debian archive which now ships 2 versions of the bios binary -- small 128Kb one and bios-256k.bin (with size = 256Kb, obviously). For now, both are built with Xen support. So for now, it is enough to just rebuild xen with seabios >= 1.7.4-2~ to get this fixed without patching. However, please apply the mentioned patch (or update to xen-4.3.1 version)

Package: xen-system-amd64 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainer, after upgrading my bullseye server to bookworm I ran into the issue that all VMs of type hvm are not starting anymore. xl throws an error: libxl: error: libxl_qmp.c:1399:qmp_ev_fd_callback: Domain 8:error on QMP socket: Connection reset by peer libxl: error: libxl_qmp.c:1438:qmp_ev_fd_callback: Domain

Hi Attilio I have updated to the upstream Xen and try to boot into OVMF bios. Instead of fetching the OVMF code from the git mirror, I just copy the OVMF bios to ovmf directory. I use the bios="ovmf" in the HVM config file. But, there is an error when I create the domain. root@gavin-laptop:~# xl create hvm_ubuntu.hvm Parsing config file /root/hvm_ubuntu.hvm WARNING: specifying

Hello, I'm looking for an example configuration for a PVHVM domU that works with 4.3.1. The one at http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers causes 3 warnings and some errors: WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware WARNING: ignoring device_model directive. WARNING: Use

On Wed, 2014-01-01 at 09:52 -0600, Marc F. Clemente wrote: > I have seen posts mentioning "traditional" and "upstream" qemu-dm. > But it is not clear to me what the difference is between "traditional" > and "upstream", or how to select either one. This is explained in the xl.cfg(5) man page. http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html