similar to: Bug#502123: xen-utils-unstable: Debian patch breaks paravirtualized guest initrd

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

retitle 502123 xen-utils-unstable: Debian patch breaks paravirtualized guest initrd thanks I see that this bug is still present in pkg-xen svn: http://svn.debian.org/wsvn/pkg-xen/trunk/xen-unstable/debian/patches/tools-python-xen-xm-relative-path.diff?op=file Perhaps I wasn?t clear how severe this problem is. Using the current Debianized xen-utils-unstable, it is impossible to boot any

Is there any update on this? Something which prevents applying the patch? Thanks, De

On ia64 we have a desire to know the guest OS the user plans to run in an HVM domain. With this information we can make certain optimizations, for instance knowing if a guest identity maps a memory region can change how we handle page faults. In the past we''ve tried to do this via the guest firmware detecting the guest type, but this is error prone and doesn''t allow the user to

Using the 2.0.6 demo cd image, I booted the supplied freebsd image and rsync''d the file system to an NFS server. However I don not seem to be able to succesfully boot from it the system just hangs here: xn0: bpf attached xn0: Ethernet address: aa:00:00:61:1c:d4 lo0: bpf I have modified /sbin/start_freebsd.sh and /etc/xen/freebsd.py to generate the following configuration: xendemo:~#

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

https://bugzilla.mindrot.org/show_bug.cgi?id=2063 Bug ID: 2063 Summary: RFE: export principal which was used for .k5login Classification: Unclassified Product: Portable OpenSSH Version: 6.1p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

[HVM] enable sound card support for qemu Signed-off-by: Edwin Zhai <edwin.zhai@intel.com> diff -r 2abb1c801ab7 tools/examples/xmexample.hvm --- a/tools/examples/xmexample.hvm Wed Jul 19 16:09:59 2006 +0800 +++ b/tools/examples/xmexample.hvm Thu Jul 20 21:19:07 2006 +0800 @@ -153,8 +153,8 @@ serial=''pty''

Package: xen-3 Version: 3.2.1-2 Severity: wishlist Xen 3.2.1 is now over a year old, and was obsoleted by Xen 3.3 eight months ago. The xen-unstable snapshot in sid is also about a year old. It would be nice to have updated Xen packages in Debian.

How about this: for (int i = 0; i != NumWChars; ++i) absPath[i] = std::tolower(absPath[i], std::locale()); seems to be working just fine? On Mon, Oct 3, 2011 at 9:27 PM, Bryce Cogswell <bryceco at gmail.com> wrote: > Right, but maybe if you switch to using tolower_l() and pass an appropriate > locale you can get it to work the same way. I'm not sure what locale that

Am 03.10.2011 22:12, schrieb Nikola Smiljanic: > How about this: > > for (int i = 0; i != NumWChars; ++i) > absPath[i] = std::tolower(absPath[i], std::locale()); > > seems to be working just fine? You have two assumptions here: Assumption 1: For each lowercase character, there is an equivalent uppercase character, and vice versa. This is not true in half a dozen

I am seeing a problem with the Xen emulated serial console. When running a Linux 2.6.20 HVM guest that has CONFIG_HOTPLUG_CPU=n, the guest blocks on output to the console until it receives input keypresses from `xm console`. This prevents the guest from booting up without banging on some keys, and makes interactive use of the console difficult. By bisecting Linux kernel commits, I found that

Hi fellows, As the NUT-NG draft will take me more time than I currently have (I found myself too optimistic since I got a baby ;-), below is the beginning of an answer to the "Common Power Management with UPS support" problem... First, NUT is pure userspace code, for portability issue, and will remain. USB is through libusb, snmp through net-snmp and serial through standard read/write.

Hi Powermen ;-) I recently came across the Powerman project (http://sourceforge.net/projects/powerman/), pointed by Tony Merenda, from Opengear (thanks Tony). Congrats for your work in this area! I've thought a bit about Powerman and NUT since then... NUT currently supports hosts of UPSs and few PDUs (RPCs), and provides tons of features: http://test.networkupstools.org

On 10/03/2011 11:59 PM, Joachim Durchholz wrote: > Am 03.10.2011 22:12, schrieb Nikola Smiljanic: >> How about this: >> >> for (int i = 0; i != NumWChars; ++i) >> absPath[i] = std::tolower(absPath[i], std::locale()); >> >> seems to be working just fine? > > You have two assumptions here: > > Assumption 1: For each lowercase character,

I am having problems installing the latest samba4 git checkout as of 3/30/13 I keep getting this error message when trying to install samba4 it says: checking project rules ... Project rules pass [ 1/4152] Generating replace.vscript [ 2/4152] Generating interfaces.vscript [ 3/4152] Generating talloc.vscript [ 4/4152] Generating pytalloc-util.vscript [ 5/4152] Generating tevent.vscript [

On Fri, Nov 6, 2009 at 12:49 AM, Gabriel Genellina <gagsl-py2 at yahoo.com.ar> wrote: > En Fri, 06 Nov 2009 00:53:14 -0300, Chris Rebert <clp2 at rebertia.com> > escribi?: >> >> On Thu, Nov 5, 2009 at 7:41 PM, Peng Yu <pengyu.ut at gmail.com> wrote: > >>> I looked though the os.path manual. I don't find a function that can >>> test if a

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

On Sun, 29 Jan 2017 17:07:39 -0500 Sonic <sonicsmith at gmail.com> wrote: > On Sun, Jan 29, 2017 at 4:54 PM, Rowland Penny <rpenny at samba.org> > wrote: > > > When you built Samba, did you use the '--with-ntvfs-fileserver' or > > '--enable-selftest' options with configure ? > > > > I used '--without-ntvfs-fileserver'. OK,

That should be fine. I don't believe the concern about performing a char-by-char conversion is valid; for example the NTFS-3G driver uses a simplistic upcase table and seems to work fine. I suspect Windows does the same. On Oct 3, 2011, at 1:12 PM, Nikola Smiljanic wrote: > How about this: > > for (int i = 0; i != NumWChars; ++i) > absPath[i] = std::tolower(absPath[i],