similar to: Bug#684661: Workaround, patch and full trace

Having finished a round of testing in my own lab, I''ve connected to my clients test lab, and reproduced my Xen Dom0. Upon trying a test creation of a DomU, I was intrigued to receive the message: ERROR POST operation failed: xend_post: error from xen daemon: (xend.err ''Error creating domain: Creating domain failed: name=snstest00'') Domain installation does not

Fasiha Ashraf --- On Sat, 22/8/09, Fasiha Ashraf <feehapk@yahoo.co.in> wrote: From: Fasiha Ashraf <feehapk@yahoo.co.in> Subject: Re: [Xen-users] my bootlog To: "Boris Derzhavets" <bderzhavets@yahoo.com> Date: Saturday, 22 August, 2009, 11:12 AM Please check what wrong here grub.conf        title Fedora (2.6.30-rc6-tip)         root (hd0,6)         kernel

This is an early userspace type question. I have an initramfs that does some root device setup, then tries to mount the real root partition and exec /sbin/init to start the real userland. It seems to do what I want, except that bootlogd hangs while mount /proc. I can't seem to figure out why. I'm booting with init=/bin/bash. bash is dynamically linked, and the appropriate libs are in

been shared out read-only for the purposes of a script which runs on the Linux box that copies files for backup. On one ME box, I can access the C:\WINDOWS directory without difficulty from Linux, however, on the second ME box, the C:\WINDOWS directory does not show up as a directory and has a zero byte size when using 'smbmount' and 'ls' as follows: [root@vault /root]# smbmount

Is this a known problem? I've seen this problem both under 2.0.6 and 2.0.7, on my Debian Linux system (kernel 2.2.14): A Win95 share that I mounted under smbfs will show up as mounted in df, and even contain the correct Used/Available info. If I do an 'ls' on the mountpoint, I see no files. If I 'umount' the share, I get the 'not mounted' error, but then no longer

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2

>From the Wiki: 'There are aready a few bugs in 1.5.2 but more fixes some good new features' Anyone know where the bugs are being listed? I am working through a few issues: 1. When rebooting, the phone will pause for exactly 180 seconds with the screen reading 'updating initial configuration'. I know it is 180 seconds because when I tail the FTP server log the entries are

I''m still playing around with xen-3.0.2-3 and the pciback.hide option. Currently I''m trying to give the guest a pcmcia-to-pci card with a prism54 wlan card in the slot. When starting the guest the following message apears in the bootlog: ... pciback 0000:02:09.0: can''t export pci devices that don''t have a normal (0) or bridge (1) header type! ... The lspci of

Matt Fleming wrote: > On Wed, 03 Jul, at 09:53:32PM, Sebastian Herbszt wrote: >> gfxboot.c32 is supposed to work as expected if you put all required files >> inside the bootlogo archive. > > From reading com32/gfxboot/gfxboot.c, the code in the bootlog archive > calls *out* into a realmode section compiled into gfxboot.c32 > (realmode_callback.asm) to do things like

In 3.7-rc4, when starting X with the integrated GPU and suspending the discrete GPU, after one or more 32-bit applications are used (eg Skype) and X is stopped, we hit a panic. Prevent this by testing if the fini function is valid. Full panic bootlog is at: http://quora.org/2012/nouveau/dmesg-crash.txt Xorg.log is at: http://quora.org/2012/nouveau/Xorg.0.log-crash.txt Kernel log after fix is at:

OS: Linux BS801-TEC-02 2.6.32-279.22.1.el6.x86_64 #1 SMP Wed Feb 6 03:10:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux CentOS release 6.3 (Final) Nut version: nut-2.6.5 NUT installation method: from source tarball ./configure --with-user=ups --with-group=nut --with-usb --prefix=/ups --localstatedir=/ups/var --with-pidpath=/ups/var/state/ups --with-statepath=/ups/var/state/ups --enable-static UPS

On Wed, 03 Jul, at 09:53:32PM, Sebastian Herbszt wrote: > gfxboot.c32 is supposed to work as expected if you put all required files > inside the bootlogo archive. >From reading com32/gfxboot/gfxboot.c, the code in the bootlog archive calls *out* into a realmode section compiled into gfxboot.c32 (realmode_callback.asm) to do things like open files, read sectors, etc. It's these

Am 03.07.2013 23:05, schrieb Sebastian Herbszt: > Matt Fleming wrote: >> On Wed, 03 Jul, at 09:53:32PM, Sebastian Herbszt wrote: >>> gfxboot.c32 is supposed to work as expected if you put all required >>> files >>> inside the bootlogo archive. >> >> From reading com32/gfxboot/gfxboot.c, the code in the bootlog archive >> calls *out* into a

I`m trying to provision my Polycom 501s using Pure-FTP. Everything has been working fine, until I put a new bootlog.ld file. Sniffing the packets between my phone and the FTP server during transfer, I noticed that the file is not 100% sent (it seems to send about a third of it, and then the phone wisely detects it as being corrupted and reboots). I have suceeded in using other FTP clients to

I'm trying another critical piece of software, and while it installed fine, I'm getting a "Run-time error '380' Invalid property value" box and the software doesn't run. I'm using Fedora 10 with Wine ver. 1.1.15. The bootlog for the program is as follows: err:module:import_dll Library wbtapi.dll (which is needed by

Hi Wei, A Debian user has hit this message and reported it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661 I think it is the BUG_ON in: struct amd_iommu *find_iommu_for_device(int bdf) { BUG_ON ( bdf >= ivrs_bdf_entries ); return ivrs_mappings[bdf].iommu; } It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug report

Hi Wei, A Debian user has hit this message and reported it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661 I think it is the BUG_ON in: struct amd_iommu *find_iommu_for_device(int bdf) { BUG_ON ( bdf >= ivrs_bdf_entries ); return ivrs_mappings[bdf].iommu; } It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug report

Hello. log of the crashing boot process: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-14-xen331-linux-2.6.29-rc6-crash.txt 2.6.29-rc5 based pv_ops dom0 works on the same computer.. with the same Xen version. I tried with and without pci=nomsi. adding ''noapic'' doesn''t seem to help (I need that with 2.6.29-rc5 to make it work). Any ideas

also get this message machine locks and have to reboot prior to putting xen had been running squeeze with no problems. installed wheezy from new and got error. upgraded to sid and error still occurs has 4GB so not the memory as mentioned by another on a AMD opteron 275 hp proliant dl385 xen 4.1 to do more checking