similar to: hypervisor and utils

Subject: xen-hypervisor-unstable-amd64: Post update from 3.2 -> 3.3, initrd which previously worked failes Package: xen-hypervisor-unstable-amd64 Version: 3.3-unstable+hg17961-1 Severity: normal *** Please type your report below this line *** System was running hypervisor 3.2, and domUs were working correctly. System was updated to -unstable (3.3) hypervisor and utils. Unchanged kernel and

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 514918 src:xen 3.3-unstable+hg17961-1 Bug #514918 [xen-utils-unstable] xen-utils-unstable: xend starts with errors Warning: Unknown package 'xen-utils-unstable' Bug reassigned from package

tag 502123 patch severity 502123 serious thanks Confirmed. This regression was introduced by a copy-and-paste error in debian/patches/tools-python-xen-xm-relative-path.diff (svn://svn.debian.org/pkg-xen -r531). Please apply this fix. --- debian/changelog 2008-12-04 16:50:04.000000000 -0500 +++ debian/changelog 2008-12-04 16:59:09.000000000 -0500 @@ -1,3 +1,10 @@ +xen-unstable

Package: xen-unstable Version: 3.3-unstable+hg17961-1 Severity: normal Tags: sid User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.5 The package fails to build in a test rebuild on at least amd64 with gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4. For the compiler version used, see: http://lists.debian.org/debian-devel/2010/01/msg00230.html The full build log can be found

Package: xen-utils-unstable Version: 3.3-unstable+hg17961-1 Severity: important if I try to start or restart xend, I get this errors: /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-unstable/bin/xend", line 146, in <module> sys.exit(main()) File "/usr/lib/xen-unstable/bin/xend", line 123, in main

How should I be detecting a block-configure operation done in Dom0 in a HVM DomU? Under Debian Lenny''s Xen 3.2.1, when I execute such a command, Dom0 writes to the backend values ''params'' and ''type'', twice, but doesn''t update the ''sectors'' value to match the new device, or initiate a state change. Given that, the best I can

Package: xen-utils-3.2-1 Version: 3.2.1-2 Followup-For: Bug #477525 I have the same problem after updating from etch to lenny. (Thus updating Xen from 3.0 to 3.2) Does anyone know how to fix this? -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores) Locale:

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** Hi, Recently I've experienced some crashes of Xen domU (also debian Lenny, running same kernel as dom0 (linux-image-2.6.26-xen-amd64)). At xm top that domain appears as running, but hogs all CPUs, because this problem has appeared on two identic servers (Supermicro X7SBi,

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Severity: minor Instead of running GRUB configuration directly, the package should use a trigger for that, to avoid doing it more than once when multiple hypervisor packages are installed (not speaking about other kernels). -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (502,

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When my domU uses this configuration: --- root = '/dev/sda2 ro' disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', ] --- Pygrub gives the error "Error: Boot loader didn't return

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal Hi, Is the e1000 network card within domU no longer available? With model=e1000 a Xen domain refuses to start while with etch this was possible. There are some Windows guests on which I can not install gplpv, so with lenny they will just get 100mbit ethernet emulated. Cheers, Andreas -- System Information: Debian Release:

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** When live migrating a PV guest from one Lenny dom0 to another, the migration fails with the following error: libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err '/usr/lib/xen-3.2-1/bin/xc_save 28 39 0 0 1 failed') The kernel messages

Package: xen-utils-unstable Version: 3.3-unstable+hg17192-1 Severity: important Tags: patch In tools/firmware/Makefile, INST_DIR is $(DESTDIR)/usr/$(PREFIX)/boot but $(PREFIX) is empty. hvmloader doesn't get installed. diff -ru xen-unstable-3.3-unstable+hg17192.orig/debian/patches/tools-prefix.diff xen-unstable-3.3-unstable+hg17192/debian/patches/tools-prefix.diff ---

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Please can you add python-xml as a dependancy for xen-utils-3.2-1 on lenny and above. Without python-xml a dependancy for "xm new" isn't satified. Thanks, Matthew Millar -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important The xm command has an option to define a domain in Xen: xm new vm_config_file.cfg Using default dependences it isn't working: :~# xm new oromigration-oromail.cfg Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Once installed, the python library of Xen are not in the python search path. Concequently, it's impossible to import anything from the xen-utils in another application. The only way to fix it is to do: cd /usr/lib/python2.5/site-packages ln -s /usr/lib/xen-3.2-1/lib/python/xen xen xen-utils-3.2-1 should in fact use the folder

Processing commands for control at bugs.debian.org: > reassign 502123 xen-utils-unstable 3.3-unstable+hg17961-1 Bug#502123: xen-utils-unstable: Debian patch breaks paravirtualized guest initrd Bug reassigned from package `xen-hypervisor-unstable-amd64' to `xen-utils-unstable'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: grave Justification: renders package unusable This packages should depend on the 3.4 version of xenstore utils and library, because it the Lenny versions are installed, xend crashes instead of starting up. (Many users choose to run lenny/sid hybrid systems, with lenny as default, so it's completely plausible that the wrong package will be

Package: xen-3 Severity: important After testing with waldi, he found out that the kernel arch cant be different as the xen-utils. So when using xen-amd64 with xen-utils-i386 the dom'Us wont work. xm create /etc/xen/test2.cfg gets: VmError: (22, 'Invalid argument') Debug: [2008-10-23 18:01:48 4211] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name',