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). Pvm work still. # 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 PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001ef 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 6 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exited # dpkg -l |grep xen ii libxen-4.3 4.3.0-3+b1 amd64 Public libs for Xen ii libxen-4.4 4.4.0-2 amd64 Public libs for Xen ii libxenstore3.0 4.4.0-2 amd64 Xenstore communications library for Xen ii xen-hypervisor-4.3-amd64 4.3.0-3+b1 amd64 Xen Hypervisor on AMD64 ii xen-hypervisor-4.4-amd64 4.4.0-2 amd64 Xen Hypervisor on AMD64 ii xen-linux-system-3.14-2-amd64 3.14.15-2 amd64 Xen system with Linux 3.14 on 64-bit PCs (meta-package) ii xen-linux-system-amd64 3.14+59 amd64 Xen system with Linux for 64-bit PCs (meta-package) ii xen-system-amd64 4.4.0-2 amd64 Xen System on AMD64 (meta-package) ii xen-tools 4.4-1 all Tools to manage Xen virtual servers ii xen-utils-4.3 4.3.0-3+b1 amd64 XEN administrative tools ii xen-utils-4.4 4.4.0-2 amd64 XEN administrative tools ii xen-utils-common 4.4.0-2 all Xen administrative tools - common files ii xenstore-utils 4.4.0-2 amd64 Xenstore utilities for Xen # dpkg -l |grep qemu ii ipxe-qemu 1.0.0+git-20131111.c3d1e78-2 all PXE boot firmware - ROM images for qemu ii qemu 2.1+dfsg-2 amd64 fast processor emulator ii qemu-slof 20140630+dfsg-1 all Slimline Open Firmware -- QEMU PowerPC version ii qemu-system 2.1+dfsg-2 amd64 QEMU full system emulation binaries ii qemu-system-arm 2.1+dfsg-2 amd64 QEMU full system emulation binaries (arm) ii qemu-system-common 2.1+dfsg-2 amd64 QEMU full system emulation binaries (common files) ii qemu-system-mips 2.1+dfsg-2 amd64 QEMU full system emulation binaries (mips) ii qemu-system-misc 2.1+dfsg-2 amd64 QEMU full system emulation binaries (miscelaneous) ii qemu-system-ppc 2.1+dfsg-2 amd64 QEMU full system emulation binaries (ppc) ii qemu-system-sparc 2.1+dfsg-2 amd64 QEMU full system emulation binaries (sparc) ii qemu-system-x86 2.1+dfsg-2 amd64 QEMU full system emulation binaries (x86) ii qemu-user 2.1+dfsg-2 amd64 QEMU user mode emulation binaries ii qemu-user-binfmt 2.1+dfsg-2 amd64 QEMU user mode binfmt registration for qemu-user ii qemu-utils 2.1+dfsg-2 amd64 QEMU utilities There is no qemu-dm and no qemu-system-x86_64 but there is a file /usr/bin/qemu-system-x86_64 # ls -l /usr/bin/qemu-system-x86_64 -rwxr-xr-x 1 root root 5996128 Aug 2 00:39 /usr/bin/qemu-system-x86_64 # /usr/lib/xen-common/bin/xen-toolstack /usr/lib/xen-4.4/bin/xl # cat mywin7.xm device_model_version = "qemu-xen" device_model_override = "/usr/bin/qemu-system-i386" bios = "seabios" builder = "hvm" name = "mywin7" memory = 1000 vcpus = 4 vif = [ 'ip=192.168.1.19,mac=00:16:3E:8C:84:8B,bridge=xenbr0' ] disk = [ '/dev/vg0/mywin7,raw,xvda,rw' ] sdl = 0 vnc = 1 on_xend_stop = 'shutdown' on_xend_start = 'start' Thanks for every idea! Hermann -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20140826/f17a9ac3/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: debian_news.vcf Type: text/x-vcard Size: 89 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20140826/f17a9ac3/attachment.vcf>
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.
On 26 Aug 2014, at 16:33, Hermann Maier <debian.news at mader.info> 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 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). Pvm work still. > > # 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 PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000001ef > 1GB PAGES: 0x0000000000000000 > libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 6 device model: spawn failed (rc=-3) > libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 > libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exitedTry adding: device_model_version = "qemu-xen" device_model_override = "/usr/bin/qemu-system-x86_64" bios = ?seabios" to your VM conf. This gets my VMs to start booting, at which point they triple fault repeatedly - but the triple faulting doesn?t show device model errors for me. The commit I reference in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737905 works if you build packages manually though. Thomas Jepp tom at tomjepp.co.uk -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20140826/50b55da6/attachment.sig>
Am 26.08.2014 um 18:55 schrieb Ian Campbell:> 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.I don't think, that it is the bug 737905 because I get no 'Triple fault ..' xl create mywin7.cfg show no 'Triple fault ..' and 'grep Triple /var/log -r' find nothing. My seabios is newer like the versions be under discussion: <http://www.dict.cc/englisch-deutsch/discussion.html> # dpkg -l |grep seabios ii seabios 1.7.5-1 all Legacy BIOS implementation All the xen and qemu is installed by apt-get and I only used binary-packets. So probably the is a Error in one of an xen- or qemu- or seabios-packet. My problem is now that I can't create a correct bug-report because I don't know the right packet. By the way: why there is not packet xen within all xen- and qemu-stoff? @Thomas Jepp I tryed device_model_version = "qemu-xen" device_model_override = "/usr/bin/qemu-system-x86_64" bios = ?seabios" but the bug is unaltered. (thats nearly my configuration, I used qemu-system-x86_64 instead of qemu-system-x86_64) Hermann -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20140829/136ea64e/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: debian_news.vcf Type: text/x-vcard Size: 89 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20140829/136ea64e/attachment.vcf>
Maybe Matching Threads
- hvm and qemu-system-i386 broken
- hvm and qemu-system-i386 broken
- libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) when creating VM using upstream qemu on Xen 4.2.
- [PATCH v10 0/7] build upstream qemu and seabios by default
- Bug#737905: Xen: hvmloader causes immediate VCPU triple fault with SeaBIOS 1.7.4