search for: 536176

Processing commands for control at bugs.debian.org: > reassign 536806 xen-3 3.4.0-1 Bug#536806: xen-utils-common - xend start fails Bug reassigned from package `xen-utils-common' to `xen-3'. > reassign 536176 xen-3 3.4.0-1 Bug#536176: xen-utils-3.4: trying xen-3.4 once breaks xen-3.2 (?) Bug reassigned from package `xen-utils-3.4' to `xen-3'. > forcemerge 536176 536806 Bug#536176: xen-utils-3.4: trying xen-3.4 once breaks xen-3.2 (?) Bug#536806: xen-utils-common - xend start fails Forcibly...

Processing commands for control at bugs.debian.org: > forcemerge 536176 538766 Bug#536176: xen-utils-3.4: trying xen-3.4 once breaks xen-3.2 (?) Bug#538766: xen-utils-common: fail to start xend Bug#536806: xen-utils-common - xend start fails Forcibly Merged 536176 536806 538766. > End of message, stopping processing here. Please contact me if you need assistance....

Processing commands for control at bugs.debian.org: > close 536176 3.3.1-2 Bug#536176: xen-utils-3.4: trying xen-3.4 once breaks xen-3.2 (?) 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#536806: xen-utils-common - xend start fails Bug#538766: xen-utils-common: fail to start xend Bug marked as fixed in version 3.3.1-2, send a...

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: critical Justification: breaks unrelated software After installing xen-utils-3.4 besides my existing xen-3.2 system, I could not start xend-3.2 anymore. The message I was getting is this: "Failed to initialize dom0 state." As far as I know, xen 3.2 and 3.4 are supposed to be able to live peacefully on the same system. (The

Package: xen-3 Severity: normal Using the previous init script solves the problem for me: http://svn.debian.org/wsvn/pkg-xen/trunk/xen-common/debian/xen-utils-common.xend.init?rev=527&sc=1 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-xen-686 (SMP w/1

Here is a patch to the Debian xen-3 3.4.0-1 package that reenables ioemu. I have been using it for the last four weeks. (I understand there are reasons this cannot go into Debian yet, but hopefully it will be useful to people that depend on running HVMs today.) Anders -------------- next part -------------- --- xen-3/debian/changelog +++ xen-3/debian/changelog @@ -1,3 +1,10 @@ +xen-3

...d mail. These mails are sent twice a month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail === xen-3: = 2 bug(s) that should be fixed soon: - #536173 <http://bugs.debian.org/536173> xen-utils-3.4 need to depend on 3.4 version of xenstore - #536176 <http://bugs.debian.org/536176> xen-utils-3.4: trying xen-3.4 once breaks xen-3.2 (?) = Lintian reports 1 error(s) and 16 warning(s), you should consider fixing them. See http://lintian.debian.org/maintainer/pkg-xen-devel at lists.alioth.debian.org.html#xen-3 ------------ interesting stu...

ynohtna <wineforum-user at winehq.org> wrote: >Sent: Feb 16, 2011 7:07 AM >To: wine-users at winehq.org >Subject: [Wine] Re: mscorsvw.exe crash when wine opens > >> The program mscorsvw.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. > >Every single time I started anything with Wine, even wine regedit. I upgraded from

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: important The current version of the package does not contain the IOEMU tools. This makes HVM domains, and PV domains with emulated features like VFB impossible to run. There might be good reasons for this, but then at least the package description should contain a warning that makes this obvious, so that users know that they can not simply

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: important pygrub uses the fsimage library to read contents of the filesystems to boot. This package install the plugins for different filesystems at /usr/lib/xen-3.4/lib/fs/, but searches for them under /usr//usr/lib/fs. (The debian patch tools-libfsimage-prefix.diff explicitly tinkers with this path, but it fails.) This breaks pygrub. --