search for: mrvn

Package: xen-3 Version: 3.1.0-2 Severity: minor Hi, when I build xen-3 for etch I get the following error: mrvn at book:~/src/xen/xen-3-3.1.0% debuild -us -uc -sa fakeroot debian/rules clean if [ -f debian/control ] && [ -f debian/control.md5sum ] && [ -f debian/rules.gen ]; then \ if md5sum debian/changelog debian/templates/control.hypervisor.in debian/templates/control.main...

...management daemo ii xenstore-utils 4.0.1~rc3-1 Xenstore utilities for Xen xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- no debconf information -------------- next part -------------- A non-text attachment was scrubbed... Name: xen-common-4.0.0-mrvn.patch Type: text/x-diff Size: 2617 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20100715/3061d461/attachment.patch>

...: xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) cc_compile_by : mrvn cc_compile_domain : book.localnet cc_compile_date : Sat Sep 22 01:27:47 CEST 2007 xend_config_format : 3 Domain Config: #---------------------------------------------------------------------------- # Kernel image file. kernel = "kernel.gz" # Initial memory allocation (in...

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub looks for extlinux config files "/boot/isolinux/isolinux.cfg" and "/boot/extlinux.conf", but the default Debian installation uses the config file "/boot/extlinux/extlinux.conf". (See /usr/lib/xen-4.1/bin/pygrub lines 405-407.) ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The function is_disk_image in /usr/lib/xen-4.1/bin/pygrub at line 45 distinguishes a partitioned disk from a partition by looking for 0xaa55 at offset 0x1fe in the image, but this is the bootsector signature, not the partition table signature. extlinux and other bootloaders put this signature there on bootable partitions (which don't

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The grub.cfg created by a default Debian installation uses many configuration statements that pygrub does not recognize, and pygrub is unable to find any kernel to load. ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500,

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub does not recognize the include statement in extlinux.conf. The default Debian installation of extlinux creates a stub extlinux.conf which includes linux.cfg, where all the linux image entries are. This means that even if bugs 697407 and 697409 are fixed, pygrub still can't find the right kernel on a default Debian installation

Package: xen-utils-common Version: 4.0.0-1 Severity: normal I am also struggling with this. I got farther by creating a .sxp file (xmexample.hvm.cfg is from /usr/share/doc/xen-utils-common/examples): # xm create -n -f xmexample.hvm.cfg | tail -n +2 > xmexample.hvm.sxp (why xm create -n mixes diagnostics with the output of -n on stdout, I do not know) and then specifying it on the command

Package: blktap-dkms Version: 2.0.93-0.3 Severity: normal With both linux-image-3.2.0-4-amd64 and linux-image-3.16-2-amd64 installed, blktap fails to compile for the 3.2.0-4 kernel, but succeeds for the 3.16-2 kernel. (Headers for both kernel versions are installed.) I am attaching the build log. Note that bug 764132 is for blktap-dkms version 2.0.91-1 and fails for the opposite kernel

Package: xen-utils-common Version: 4.0.0-1 Severity: normal This is an offshoot of Bug#588888, but is really a separate issue. It appears that with hvmloader, the disk device names presented to the vm must by from a specific set that hvmloader knows how to emulate. Names like hd[a-c] and sd[a-c] work, but sr0 does not. While this makes sense, when you think about what hvmloader is doing, it is

Package: blktap-dkms Version: 2.0.91-1 Severity: normal With both linux-image-3.2.0-4-amd64 and linux-image-3.16-2-amd64 installed, blktap fails to compile for the 3.16-2 kernel, but succeeds for the 3.2.0-4 kernel. (Contrary to the dependency listing below, I do have the headers for 3.16-2 installed.) I am attaching the build log. -- System Information: Debian Release: 7.6 APT prefers