similar to: Bug#599520: (no subject)

Package: xen Version: 4.0.1-1 Tags: patch Attached is a patch which I already sent upstream that replaces the python-xml (pyxml/xmlproc) based validation code with validation code based on python-lxml. The obvious gain from this is that XenAPI works on Squeeze and Sid, where python-xml is not available anymore. Additionally this patch adds a dependency on python-lxml for the xen-utils-4.0

Processing commands for control at bugs.debian.org: > user pkg-xen-devel at lists.alioth.debian.org Setting user to pkg-xen-devel at lists.alioth.debian.org (was ijc at debian.org). > usertags 599520 toolstack-xend There were no usertags set. Usertags are now: toolstack-xend. > close 599520 4.4.0-1 Failed to add fixed version '4.4.0-1' to 599520: Not altering archived bugs; see

Bastian, can you confirm the problem with "xm new" (instead of "xm create") ? -- Laurent L?onard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url :

I want to add some information When the "50 minute shift" occurs. It occurs simultaneously on all domU and dom0. on all domU and dom0, the syslog says Clocksource tsc unstable (delta = -2999660303146 ns) (or something very near 3000 seconds) Using ntp is ok to resync the clock but does not prevent the problem from occuring.

I think it should be interesting to correct this bug into Lenny. Perhaps the severity of this bug should be set to "normal" instead of "wishlist" ? -- Laurent L?onard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url :

Thanks Mike and Thomas for clarifying the issue. The reason I picked Critical was because of it's "description"... The part that applied to me was "makes unrelated software on the system (or the whole system) break" when i loose network connectivity, to me, that is broken. In my case, the severity comes from a business standpoint. I manage the servers and someone else

Content-Type: multipart/mixed; boundary="===============0382030028==" MIME-Version: 1.0 From: Albert Dengg <a_d@gmx.at> To: Debian Bug Tracking System <395305@bugs.debian.org> Subject: xen-utils-common: here is a small patch to correctly handle long domU names in parseln Message-ID: <20070317182707.16837.48971.reportbug@audhumbla.dengg.priv.at> X-Mailer: reportbug 3.31

I'm afraid this still doesn't work even after upgrading to jessie (xen-utils-4.3 4.3.0-3+b1). Should I open a new bug against xen-utils-4.3 or can this bug somehow be applied to that package as well?

As far as I know, this bug can be closed, it was a mistake on our side: The script /etc/xen/scripts/block-iscsi had been modified from the package version and it was outputting some debug values, which seem to be what caused migrations to now fail.

I was wrong, that bug persists in 1.3.2-7 I've recheck it on clean installation: xe host-disable; xe host-reboot After reboot do not enable host back and manual attempt is rejected: xe host-enable uuid=6510efef-2063-b32c-2169-870bde43406a The specified host is disabled and cannot be re-enabled until after it has rebooted. host: <unknown>

Agreed, the severity should be bumped up on this, I spent many hours after a lenny to squeeze upgrade figuring out what the problem was. I request that the previously attached patch (a simple one liner) be applied for a squeeze update.

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

Package: xen-utils-4.0 Version: 4.0.1-2 Right after another Wheezy distribution update I've faced the following issue with "xm". ===== host:~# xm new /etc/xen/domains/test.cfg Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130616/96753239/attachment.html>

?????????/?????????????????(?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????QQ?3/7/0/3.3.3.8/.9.4( 93.?????,??????????????,????,??????.??????,?:?????,??????,?????????????? -------------- next part -------------- An HTML attachment was scrubbed... URL:

????????????? ?????? ??3000????????????? ???????????????????? ???????????????????????? ???????????????????????400? ????15813351772??? ?????? Q2809906464 -------------- next part -------------- An HTML attachment was scrubbed... URL:

?????????????????.????

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

Hi, Here is patch that i mean: http://www.listware.net/201010/xen-devel/26206-xen-devel-patch-replace-pyxmlxmlproc-based-xml-validator-with-lxml-based-one.html and it's accepted already to upstream. -- WBR, Dmytro Sirant

On Tue, 2015-05-12 at 17:28 +0200, zer0 divide wrote: > Package: xen-hypervisor-4.5-amd64_4.5.0-1_amd64.deb > Version: 4.5.0-1 > > > Hi, > > I use xen with sdl, not with vnc. When I boot on > xen-hypervisor-4.4-amd64, everything is fine. With Debian or Windows > 8.1 I have a good display, > > But when I choose at boot, the xen-hypervisor-4.5-amd64, things go