similar to: Bug#618576: xen-3.2-1: VNC display over HVM XEN 3/Lenny AMD64, displays a blank screen when Debian-Installer Squeeze AMD64 is running on it

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important I've a Debian Lenny AMD64 as production server, where it has important HVMs that runs correctly. The problem occurs when i try to create a HVM from a Debian Squeeze AMD64 iso file. At first, the VNC display specified shows perfectly the Debian Installer menu, but when I choose an option (Install or Graphical Install),

Hello community! I need help with a problem I haven''t been solved with the network team. I manage a network that has over a thousand computers, and the most of the servers are virtualized over Debian / Xen by me. The specific issue arises when I try to set up a DomU HVM running Debian Squeeze, the VM doesn''''t recognize the network but it runs. It gives an error

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: serious Tags: squeeze Hi there! Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64 installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually to have it installed after a dist-upgrade. This for sure, isn't the expected behavior. Also, after the dist-upgrade, I did: apt-get

Hi, In Debian lenny I used the following in upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL webinterface 192.168.0.2/32 ACL slave 192.168.50.22/32 ACCEPT localhost ACCEPT webinterface ACCEPT slave REJECT all and in upsd.users: [monmaster] password = secret0 allowfrom = localhost upsmon master [monslave] password = secret1 allowfrom =

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: important I upgraded today from Lenny to Squeeze. I upgraded via apt-get dist-upgrade and then installed the new xen-packages (including hypervisor and kernel). But I wasn't able to boot the system after the upgrade anymore with Xen enabled: On every boot-attempt, I just get "elf_init: not an ELF binary". I googled a

Processing commands for control at bugs.debian.org: > tags 496359 secuirity Unknown tag/s: secuirity. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny lenny-ignore. Bug#496359: The possibility of attack with the help

Control: tag -1 +moreinfo Hi Marco, Thanks for your report. Unfortunately the logs you've provided are from a system booted without Xen, and due to the nature of the bug it is unlikely that any relevant logs made it onto the disk in order to survive the resulting reboot. Please could you try setting up a serial console and collect the full boot log.

hi xen cracks, i know that this formum might be the wrong one for my question but maybe the last and/or only one what can give me my questions answered. i know how to setup and run a xen infrastructure, i have several server in production. the new thing is, that i started to use the debian squeeze, cause of the native suport of remus (kernel support), as everyone say: hardware ******* hp dl

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny

Hi all, ? ? ? I tried to get my query of how to use rsync by the mailing list debian-user at lists.debian.org but the answers were not satisfactory. You can see the whole thread starting from http://lists.debian.org/debian-user/2010/12/msg00651.html What I want to do is to keep the weekly amd64 squeeze build , from t its

hi xen cracks :-) i managed sucessfully to install xen4 on a debian 6.0 squeeze amd64 box, running 3 hosts windows 2008r2 server and 1 host squeeze. i use a hp server dl 160g6 dual processor with 48gb ram and 2 tb disks with sw raid 1. i have an indentical hardware box to setup remus. now, the problem is, i cant find remus on my box, like i saw it in several descriptions: /usr/bin/remus!

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important about every 1 in 10 boots I am getting the following error: (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This seems to happen in the CPU detection

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I

Control: tags -1 +moreinfo Sorry this bug seems to have fallen through the cracks. On Thu, 27 Nov 2008 09:34:19 +0100 Paul van der Vlis <paul at vandervlis.nl> wrote: > You may find bringing this up on xen-devel useful. Did you bring this up on the upstream list? Does this bug still occur for you? Thanks, Ian.

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, Just upgraded a Supermicro server (X9SCM-F motherboard) from Squeeze to Wheezy. And now the IPMI serial console no longer work as it used to. It hangs like this: [...] (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) Platform timer

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: grave File: xen Justification: renders package unusable Debian Squeeze Dom0, up to date. Networking is handled by OS scripts, such that br0 and br1 are bridge interfaces. Without warning, the DomU (Ubuntu 10.04 LTS) loses inbound connectivity. It tends to happen after several hours. It doesn't seem to be affected by throughput

Hello, I see the new Xen packages now really in Sid and even in Lenny on packages.debian.org: http://packages.debian.org/search?keywords=linux-image+xen+amd64&searchon=names&suite=testing&section=all http://packages.debian.org/lenny/xen-linux-system-2.6.26-1-xen-amd64 Does this mean there is now official Xen amb64 and dom0 support in Lenny? I am running it now for a while without

Package: xen-utils-common Version: 3.4.2-4 Severity: normal Tags: patch xen-version does not include the "extra" component, only major.minor. This keeps makes /etc/init.d/xend bail out with xen 3.2-1 from lenny. patch attached. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (600, 'testing'), (600, 'stable'), (500,

Hi. First, I would like to thank all the contributors to this project for their efforts. Given that we primarily use Debian and R as our computing platform, having access to these backports has been very beneficial. I have been looking in the last couple of days for AMD64 lenny backports of the R 2.9.0 packages in lenny-cran. Will these appear in due course or are there issues backporting