similar to: (no subject)

[This email is either empty or too large to be displayed at this time]

[This email is either empty or too large to be displayed at this time]

[This email is either empty or too large to be displayed at this time]

[This email is either empty or too large to be displayed at this time]

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Package: xen-linux-system-amd64 Version: 3.2+46 Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Package: xenwatch Version: 0.5.4-3 Package: xenstore-utils Version: 4.1.4-3+deb7u1 Package: xen-tools Version: 4.3.1-1 I installed Debian 7 (amd64) in a HX5 blade server (IBM Bladecenter H) 32 GB RAM, 2 Intel Xeon SixCore 2.Ghz, Internal

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 :

Package: xen-system-amd64 Version: 4.3.0-3+b1 Severity: wishlist --- Please enter the report below this line. --- Please package Xen 4.4: http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/ It has experimental support for PVH mode among other improvements: http://wiki.xenproject.org/wiki/Xen_4.4_Feature_List#Experimental_Support_for_ParaVirtualization_Hardware_.28PVH.29_Mode_for_Guests

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.

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

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

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

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?

Package: xen-utils-common Version: 4.0.0-1 Severity: important Tags: patch --- Please enter the report below this line. --- when you use "hardware" virtual machine (with qemu) with xen configured for bridging the network script treates a tap interface and then /etc/xen/scripts/qemu-ifup adds it to the bridge. That would be ok but tap interfaces have a random mac address and the bridge

capabilities of the enviorment, in the script it is *only* called when checking if the dom0 supports running 64-bit pvguests, i.e. the supports64bitPVguest() function. Anyway it doesn't seem like a piece of code that is necessary for most users. In fact, deleting this import line worked just as well. The only thing that bothers me is that it is called used in the bit of code labeled: