similar to: debian lenny domU installation

Displaying 20 results from an estimated 100 matches similar to: "debian lenny domU installation"

2008 Apr 06
3
Xen 3.2.1-rc1: ptwr_emulate: could not get_page_from_l1e()
Xen 3.2.1-rc1 64 bit Dom0: 2.6.16.33 PAE DomU: 2.6.18.8 (from a pull a few weeks ago) If you need the symbols, there from the same Xen I linked to in my post from a few days ago... (XEN) mm.c:3498:d4 ptwr_emulate: could not get_page_from_l1e() (XEN) Unhandled page fault in domain 4 on VCPU 0 (ec=0003) (XEN) Pagetable walk from 00000000c08187f0: (XEN) L4[0x000] = 00000004dfa38027
2008 Nov 30
2
(XEN) mm.c:707:d49 Error getting mfn 2fef3 (pfn 6aef3) from L1 entry
Hi, Can anybody advise me how to debug this crash? it happens when I try to start a 32 bit kernel on my 64 bit Xen system, the kernel is my own using opensuse 11.1 rc1 2.6.27.7 xen patches, the kernel works as 32 and 64 bit dom0, and as 64 bit domU PV, is there a technique to find out where in the kernel source the crash happens? i.e what line in the source code? (XEN) mm.c:707:d49 Error getting
2009 Mar 02
12
latest pv_ops dom0 (2.6.29-rc6) crashes / unhandled page fault
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
2008 Jul 03
6
2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap
Xen: 3.2.1-rc5 64bit Dom0: 2.6.18.8 (at cs 524) 32-pae DomU: 2.6.26-rc8 32-pae root at newark13:~# xm create -f /linodes/xencaker/xen.conf -c Using config file "/linodes/xencaker/xen.conf". Started domain xencaker root at newark13:~# root at newark13:~# xm dmesg ... (XEN) traps.c:413:d332 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN)
2008 Feb 07
6
Loading FreeBSD in an HVM-domain on Intel-based host with GRUB
Hello all, please tell me, is it possible (at least theoretically) to circumvent bug 622 [1] by using GRUB instead of /boot/loader to load FreeBSD kernel? Or it is silly idea: even if we bypass /boot/loader we will not be able to run FreeBSD kernel in a HVM-domain on a Intel-based host for some other reason? As far as I know, GRUB can''t load FreeBSD kernel directly, but only can
2008 Aug 21
2
doubt on releasing domain pages
Hi, I am trying to release domU pages from page_list and xenpage_list after domU shutdown while retaining the rest of the domain information. To achieve this in __domain_finalise_shutdown i call domain_relinquish_resources. This is failing to release pages from page_list for type PGT_l2_page_tables and crashing dom0. To be specific, while testing on mini-os i saw that when
2008 May 29
6
is it possible to build two privileged domain at boot time?
Hi All, I am not very familiar with xen details. Now I am thinking of building two privilged domain(domain 0 not driver domain) at boot time. The other question is that wether it is possible to create another domain 0 by domain-builder running in domain0? Does it make sense when domain 0 is shut down unexpectedly another domain 0 can run at once. Maybe it is absurd. I am looking forwards
2008 Nov 24
4
[LLVMdev] how to track down a kernel miscompilation?
Hi, I am trying to build the Linux kernel with LLVM. 'ARCH=um' appears to work, now I am trying to get 'ARCH=x86' to work. So far it seems there is something wrong with the boot vga code (it finds no video modes), the acpi code, and the serial console code. I am now trying to compile drivers/ with llvm-gcc and the rest with gcc-4.2 (I have a wrapper script), I am compiling to
2008 Nov 24
0
[LLVMdev] how to track down a kernel miscompilation?
For people who want to try hacking on the linux kernel with llvm, here is a head start: http://llvm.org/~alenhar2/k.tbz This is a 2.6.27.5 kernel with a .config file for qemu/kvm with virtio devices (I also think it will work with the default devices). The build process uses llvm-gcc -> opt -> llc so you can add your own (per-file) passes to the build process or debug specific passes.
2008 Nov 24
1
[LLVMdev] how to track down a kernel miscompilation?
One other note I forgot... sig_sysreturn (arch/x86/kernel/signal_32.c) has a magic fudge factor to fix up stack layout differences between llvm and gcc. If when you hit userspace you get signal handling errors, look at the frame addresses printed out and adjust the fudge factor to make the frame addresses match. (the code automatically enables the debug output after the first signal frame
2009 Jun 22
3
How to boot Ubuntu 9.04(Jaunty) or Debian Lenny (vmlinuz-2.6.26-2-686-bigmem) as domU under Lenny''s vmlinuz-2.6.26-2-xen-686 as dom0. PVM''s initrd issue
Hello, I guess it possible distro specific issue but is it resolvable? I have one node(testing purpose) ganeti 2.0.1 cluster installed over Debian5 Lenny. Almost everything from distro repositories. Only ganeti 2.0.1 and ganeti-debootstrap are from sources. I have it successful run with vmlinuz-2.6.26-2-xen-686 and initrd.img-2.6.26-2-xen-686 from repositories. Both Dom0 and DomU are use the
2011 Apr 14
3
Debian Squeeze hangs with kernel 2.6.32-5-xen-686
Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,
2015 May 09
4
Bug#784810: Xen domU try ton access to dom0 LVM Volume group
Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 On a fresh installation of Debian Jessie, when I try to start a domU, it try to access to a dom0 LVM Volume Group : [...] (I put all the boot at the end) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD
2020 Sep 03
3
Error while loading shared libraries: libsbz.so
Hi, I have a KVM host running ubuntu 18.04 with libguestfs-tools version 1.36.13-1ubuntu3.3 installed from the Ubuntu's repo and when I try to use virt-cat for example on a VM it fails with: libguestfs: error: appliance closed the connection unexpectedly. > libguestfs: error: guestfs_launch failed. After doing "export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1" and running the
2016 Feb 04
3
Bug#810379: [Xen-devel] [BUG] pci-passthrough generates "xen:events: Failed to obtain physical IRQ" for some devices
On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote: > > > And I wonder if the XEN_DOMCTL_irq_permission aka, > > > xc_domain_irq_permission > > > had been called. I remember that at some point we missed it for > > > Xend.. > > > > > False alarm. > > It was all in Linux. Attached are four patches (the first two > are for
2006 Sep 22
0
boot crash 2.6.16-18 xen kernel
Hi, We are running a Sun Fire X2100 with 4GB RAM. We followed the how-to which we posted on http://www.debian-administration.org/articles/423, using backports packages for a k7-machine. We have one Sun Fire X2100 running a 2.6.16-16 kernel from backports, which is working fine having used the same how-to. Now we are installing another X2100 using the 2.6.16-18 kernel, which is giving some major
2007 Apr 18
2
Xen i386 paravirtualization support
Hi,Chris? I wonder which version of Xen did the para-Linux works with. I applied the patches, compiled them and tried them on both xen-3.0.2 and the latest xen-unstable. Both result in panics when booting Xen and complain as follows: (XEN) Domain 0 kernel supports features = { 00000005 }. (XEN) Domain 0 kernel requires features = { 00000005 }. (XEN) (XEN)
2006 Sep 04
0
debian xen packages : work with 2.6.16, reboots when loading dom0 with 2.6.17
I was giving a try to Debian Xen packages (it looks very promising by the way ; I just happen to love the ? new ? grub which handles xen images, for instance!) ; I have a box which boots correctly with xen-hypervisor-3.0-i386_3.0.2+hg9697-2 and a 2.6.16 dom0 kernel, but crashes when trying to boot linux-image-2.6.17-2-xen-686_2.6.17-7 The result is the same on two boxen (my Pentium M laptop and a
2010 May 28
3
Problems with PCI pass-through
Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:
2010 May 28
3
Problems with PCI pass-through
Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting: