search for: reporting_bugs_against_xen

...quot;Read the file README_MISSING_SYSCALL_OR_IOCTL.\n"); > + VG_(dmsg)("Nevertheless we consider this a bug. Please report\n"); > + VG_(dmsg)("it at http://valgrind.org/support/bug_reports.html &\n"); > + VG_(dmsg)("http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen.\n"); > + > + SET_STATUS_Failure(VKI_EINVAL); > return; > + } > > #define __PRE_XEN_SYSCTL_READ(_sysctl, _union, _field) \ > PRE_MEM_READ("XEN_SYSCTL_" # _sysctl, \ > @@ -438,9 +456,26 @@ PRE(domctl) > PRE_MEM_READ(&q...

Hello all, I hope that it now works and there is no longer problems with my mailsystem. It could be that it already worked but it doesn''t look like because the mail don''t came back from the list. I am trying to setup stubdomains for my running domains on Xen 4.2. I read this wiki articles: http://wiki.xen.org/wiki/StubDom

Hi all, I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze Xen4.0 and now have problems with starting the Dom0 kernel. I always get the error message: Kernel panic not syncing: the kernel parameter noapic is incompatible with xen. My grub.cfg is: menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386'' --cl$ insmod part_msdos

I''ve recently upgraded SLES to use LibXenLight and have noticed that my virtual machines no longer restart when "xl restart X" or the reboot commands are used within the VM. Instead the machine seems to get destroyed. The configs for the VMs have not changed since well before the update. Here is what one looks like: name = ''vm1'' maxmem =1024 memory = 1024

Hi,all xen: 4.1.2 dom0 linux: centos 3.1.10 #1 SMP Tue Jun 26 17:13:57 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux I enabled ACM and install xen-4.1.2 correctly, dom0 can also boot successfully, but if i use command xm create to create a domU, dom0 reboots. Does xen-4.1.2 support ACM, or how can i solve this bug? please help me. many thanks !

Hi,all xen: 4.1.2 dom0 linux: centos 3.1.10 #1 SMP Tue Jun 26 17:13:57 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux I enabled ACM and install xen-4.1.2 correctly, dom0 can also boot successfully, but if i use command xm create to create a domU, dom0 reboots. Does xen-4.1.2 support ACM, or how can i solve this bug? please help me. many thanks !

Hi everyone, I am trying to do a Cold Migration with Xen, Ubuntu 12.04 and virtual machines with Ubuntu 10.04. This is my cfg file to create the VM on the primary node: # cat ubuntu.c cat: ubuntu.c: Arquivo ou diretório não encontrado root@cloud9:/etc/xen# cat ubuntu.cfg name = "ubuntu" memory = 256 disk = [''phy:/dev/vg_datastore/lv_datastore,xvda,w''] vif = [''

...table? What does "fdisk -l" report for this device? Does this still happen with pygrub from a newer Xen? I can see that much has changed around this area since 4.1.x. If you can reproduce with something newer then I think your best bet is to report this upstream: http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen Ian. > Detailed steps to reproduce: > We have a domU called blup.kassala.de, it is running Jessie, its root disk is > a LVM LV at /dev/vpsdisks/blup.kassala.de-disk. The first 512 bytes are null: > > # dd if=/dev/vpsdisks/blup.kassala.de-disk bs=1 count=512 | hexdump -C > 00000...

...thony Perard <anthony.perard@citrix.com> Change owner for #20 to `Anthony Perard <anthony.perard@citrix.com>'' > thanks Finished processing. Modified/created Bugs: - 20: http://bugs.xenproject.org/xen/bug/20 (new) --- Xen Hypervisor Bug Tracker See http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for information on reporting bugs Contact xen-bugs-owner@bugs.xenproject.org with any infrastructure issues

Hi all, I am trying to find out why the minimum memory allocation for a domu is 4MB. I am running MiniOS and a small application that requires no more than 8 KB or RAM. Can anyone give me a comprehensive answer to this question, i am really looking to get to grips with this in detail. Is this an arbitrary decision, or is there something more meaningful at work here? Thanks Paul

Hello, I want to install a DomU with Fedora 19 in a Debian Host Dom0 with the following versions... ii libc6-xen:i386 2.13-38 i386 Embedded GNU C Library: Shared libraries [Xen version] ii libxen-4.1 4.1.4-3+deb7u1 i386 Public libs for Xen ii libxenstore3.0 4.1.4-3+deb7u1 i386

In XM toolchain, we use to put pci = [ ''0000:07:11.6=0@1a'' ] but looks like in XL toolchain there is no way to specify function in the guest. Kindly let me know. XM - pci = [ ''0000:07:11.6=0@1a'' ] XL - pci = [ ''0000:07:11.6@1a'' ] In the guest VM we see that PCI device is getting 0 function in both the cases however, it may not work the

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When an LVM LV that serves as the root disk for a Xen DomU contains a boot loader (or possibly other data) in its volume boot record, pygrub fails to boot it, printing "Error: boot loader didn't return any data" before exiting. I think this is because of the function "is_disk_image" on line 45 of

Hi all, Since Xen 4.2.0, users can change time slice of the scheduler at runtime via xl command line, a very nice feature. However, it is not *correctly* implemented. Problem description -------------------- say you set the ''cap'' of one VM to 50 (a half core), -when setting the time slice to be *greater* than 30ms, the VM gets much *less* CPU cycles than its allocation -when

Hi, I''m trying to install Debian Squeeze as DomU on an openSUSE 11.4 Xen host but fail all the time. I''ve also searched Google and Debian as well as openSUSE resources but haven''t found any hint about my issue :-( First I''ve tried to install it as a paravirtualized guest but when the Debian installer tries to detect the disks I get this: [ 173.233735]

Hi, I''ve trying booting Xen Hypervisor PV with a centos5 template using kernel and initrd from mirror.centos.org/centos/5/os/i386. When i start PV this go to installation mode. However this should boot with template. Please help in this regard what Am i doing wrong. -- Best Regards Asim _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

..."); + VG_(dmsg)("Read the file README_MISSING_SYSCALL_OR_IOCTL.\n"); + VG_(dmsg)("Nevertheless we consider this a bug. Please report\n"); + VG_(dmsg)("it at http://valgrind.org/support/bug_reports.html &\n"); + VG_(dmsg)("http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen.\n"); + + SET_STATUS_Failure(VKI_ENOSYS); +} + +PRE(memory_op) +{ + PRINT("__HYPERVISOR_memory_op ( %ld, %lx )", ARG1, ARG2); + + switch (ARG1) { + case XENMEM_set_memory_map: { + xen_foreign_memory_map_t *arg = + (xen_foreign_memory_map_t *)(unsigned int)ARG2; +...

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Debian 8.2 installed on a supermicro H8SGL Board, AMD 6128 with 4x4GB ECC RAM. When booting the plain kernel (stock Jessie 3.16 or backport 4.1 or 4.3), both memory controllers (mc0 and mc1) appear under /sys/devices/system/edac/mc with two csrow* each as expected. Same happens, when booted with Xen 4.1.4-3+deb7u1. When booted with Xen

hello, I know this not quite a xen problem but im sure a fair number of people are using debian for their dom0 and maybe have some insight into this. I have a large number of dom0''s running squeeze and for a long time i was hoping for pvhvm to make into the official debian xen packages and recently during some periodic updates I noticed pvhvm working after a kernel package update. Now

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33