search for: xen_balloon

Hi All Back in August there was a report of these errors popping up in dmesg, and as far as I can tell it's still unresolved even in the latest kernel. System RAM resource [mem 0xc8000000-0xcfffffff] cannot be added xen_balloon: reserve_additional_memory: add_memory() failed: -17 On this example its running 3.10.20-11.el6.centos.alt.x86_64 To replicate this just disable Dom0 memory ballooning in /etc/xen/xend-config.sxp and these errors will over time completely fill up dmesg. This is because the amount of memory withi...

My /var/log/messages log is being flooded with kernel messages showing the following messages Aug 1 11:22:52 host43 kernel: System RAM resource 48000000 - 4fffffff cannot be added Aug 1 11:22:52 host43 kernel: xen_balloon: reserve_additional_memory: add_memory() failed: ?17 Doing a search I found a thread from xen-devel that talks a bit about it. I?m not sure if this is related to the same issue or if that issue was ever fixed. When I cat current_kb and target_kb the values don?t match, they are just barely off....

Hi, > biting this behavior. The specific > error I''m seeing is > > xen_balloon: reserve_additional_memory: add_memory() failed: -17 > System RAM resource 88000000 - 8fffffff cannot be added > > This is a lab system that I''m actively working on so I can give > whatever info you need or run whatever. Below is the xl info and xl > dmesg output [...] Th...

Hi, I have encountered an apparently benign error on two systems where the dom0 kernel log is flooded with messages like: [52482.163855] System RAM resource [mem 0x1b8000000-0x1bfffffff] cannot be added [52482.163860] xen_balloon: reserve_additional_memory: add_memory() failed: -17 The first line is from drivers/xen/xen-balloon.c, the second from mm/memory_hotplug.c The trigger for the messages seems to be the first occasion that a Xen guest is shutdown. I have noted this in a vanilla 3.6.7 and kernel 3.5.0-18 built...

...32 The error xend.log report is: DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib64/xen/bin/xc_save 4 3 0 0 4 INFO (XendCheckpoint:423) xc_save: failed to get the suspend evtchn port The pv driver of redhat-4.6-32bit are: [root@localhost ~]# lsmod|grep xen xen_vnif 28672 0 xen_balloon 17488 1 xen_vnif xen_vbd 20592 3 xen_platform_pci 73692 3 xen_vnif,xen_balloon,xen_vbd,[permanent] [root@localhost ~]# modinfo xen_vnif filename: /lib/modules/2.6.9-67.ELsmp/extra/xenpv/0.1-10.el4/xen-vnif.ko alias: xen:vif alias: xen:vif...

...32 The error xend.log report is: DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib64/xen/bin/xc_save 4 3 0 0 4 INFO (XendCheckpoint:423) xc_save: failed to get the suspend evtchn port The pv driver of redhat-4.6-32bit are: [root@localhost ~]# lsmod|grep xen xen_vnif 28672 0 xen_balloon 17488 1 xen_vnif xen_vbd 20592 3 xen_platform_pci 73692 3 xen_vnif,xen_balloon,xen_vbd,[permanent] [root@localhost ~]# modinfo xen_vnif filename: /lib/modules/2.6.9-67.ELsmp/extra/xenpv/0.1-10.el4/xen-vnif.ko alias: xen:vif alias: xen:vif...

Hello, I wants to make a self compiled kernel for my domUs on a debian etch server with Xen 3.1.4 and 2.6.18.8 dom0 kernel. So, I download sources for linux-2.6.26.8, and I enabled all the Xen features : Symbol: HVC_XEN [=y] Symbol: XEN_BALLOON [=y] Symbol: XEN_FBDEV_FRONTEND [=y] Symbol: XEN_SCRUB_PAGES [=y] Symbol: XEN_KBDDEV_FRONTEND [=y] Symbol: XEN_BLKDEV_FRONTEND [=y] Symbol: XEN_NETDEV_FRONTEND [=y] Symbol: XEN [=y] my domu configuration file is : kernel = ''/boot/vmlinuz-2.6.26.8''...

all, On latest tip, following symbols are unresolved when inserting modules xen_balloon: Unknown symbol totalhigh_pages xen_vnif: Unknown symbol netfront_accelerator_call_resume xen_vnif: Unknown symbol netfront_accelerator_call_suspend_cancel xen_vnif: Unknown symbol netfront_accelerator_call_stop_napi_irq xen_vnif: Unknown symbol balloon_update_driver_allowance xen_vnif: Unknown sym...

...d Ver. 2.6.34.1. This patch cleanly applys > >to Ver. 2.6.34.1 > > Thanks. I''ve pushed this into xen.git as xen/memory-hotplug so people > can play with it more easily (but I haven''t merged it into any of the > other branches yet). Thx. > >+#ifdef CONFIG_XEN_BALLOON_MEMORY_HOTPLUG > >+static inline unsigned long current_target(void) > >+{ > >+ return balloon_stats.target_pages; > > Why does this need its own version? Because original version return values not bigger then initial memory allocation which does not allow memory hotplug to...

...> > repository, 2.6.34-pvhvm head, > > Good. I noticed you have some specific tests for "xen_pv_domain()" - > are there many differences between pv and hvm? No. Only those changes are needed where xen_domain()/xen_pv_domain() is used. > >>>+#ifdef CONFIG_XEN_BALLOON_MEMORY_HOTPLUG > >>>+static inline unsigned long current_target(void) > >>>+{ > >>>+ return balloon_stats.target_pages; > >>Why does this need its own version? > >Because original version return values not bigger > >then initial memory alloca...

...28514] PCI: Fatal: No config space access function found [ 0.128539] Setting up standard PCI resources [ 0.129993] ACPI: Interpreter disabled. [ 0.130011] Linux Plug and Play Support v0.97 (c) Adam Belay [ 0.130085] pnp: PnP ACPI: disabled [ 0.130094] PnPBIOS: Disabled [ 0.130221] xen_balloon: Initialising balloon driver. [ 0.207205] PCI: System does not support PCI [ 0.207228] PCI: System does not support PCI [ 0.208384] NET: Registered protocol family 2 [ 0.208602] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.208864] TCP established hash table entr...

...Apr 19 11:12:22 CEST 2009 [ OK ] Starting udev: Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: [<ffffffff80064b3e>] _spin_lock+0x1/0xa PGD d77e067 PUD c536067 PMD 0 Oops: 0002 [1] SMP last sysfs file: /class/net/lo/type CPU 0 Modules linked in: xen_vbd xen_vnif xen_balloon ide_cd 8139too parport_pc xen_platform_pci cdrom 8139cp parport serio_raw i2c_piix4 mii pcspkr i2c_core dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ata_piix libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 895, comm: modprobe Not tainted 2.6.18-128.1.6.el5 #1 RI...

...g Xen timer for CPU 3 [ 0.250784] Booting paravirtualized kernel on Xen [ 0.250840] Xen version: 3.4.2 (preserve-AD) (dom0) [ 0.269000] xenbus_probe_init ok [ 0.334534] xenbus_probe_backend_init bus registered ok [ 0.334620] xenbus_probe_frontend_init bus registered ok [ 0.334677] xen_balloon: Initialising balloon driver with page order 0. [ 0.890440] xen: registering gsi 13 triggering 1 polarity 0 [ 0.890443] xen_allocate_pirq: returning irq 13 for gsi 13 [ 0.890500] xen: --> irq=13 [ 0.890503] xen_set_ioapic_routing: irq 13 gsi 13 vector 120 ioapic 0 pin 13 triggering...

...lized [ 0.010984] Grant table initialized [ 0.012000] regulator: core version 0.5 [ 0.012119] NET: Registered protocol family 16 [ 0.016000] PCI: setting up Xen PCI frontend stub [ 0.016914] bio: create slab <bio-0> at 0 [ 0.019056] ACPI: Interpreter disabled. [ 0.020000] xen_balloon: Initialising balloon driver with page order 0. [ 0.020000] vgaarb: loaded [ 0.020114] PCI: System does not support PCI [ 0.020124] PCI: System does not support PCI [ 0.020260] Switching to clocksource xen [ 0.023166] pnp: PnP ACPI: disabled [ 0.023176] PnPBIOS: Disabled [ 0.02...

...stered protocol family 16 [ 0.027059] xen:grant_table: Grant tables using version 1 layout [ 0.027068] Grant table initialized [ 0.027203] PCI: setting up Xen PCI frontend stub [ 0.028138] ACPI: Interpreter disabled. [ 0.028149] xen:balloon: Initialising balloon driver [ 0.028157] xen_balloon: Initialising balloon driver [ 0.028157] vgaarb: loaded [ 0.028157] PCI: System does not support PCI [ 0.028157] PCI: System does not support PCI [ 0.028157] Switched to clocksource xen [ 0.030689] pnp: PnP ACPI: disabled [ 0.031438] NET: Registered protocol family 2 [ 0.031482...

...361] RTC time: 165:165:165, date: 165/165/65 [ 0.174560] NET: Registered protocol family 16 [ 0.175213] random: fast init done [ 0.177033] PCI: setting up Xen PCI frontend stub [ 0.182179] ACPI: Interpreter disabled. [ 0.183029] xen:balloon: Initialising balloon driver [ 0.187043] xen_balloon: Initialising balloon driver [ 0.187130] vgaarb: loaded [ 0.187131] SCSI subsystem initialized [ 0.187244] usbcore: registered new interface driver usbfs [ 0.187291] usbcore: registered new interface driver hub [ 0.188102] usbcore: registered new device driver usb [ 0.188102] dmi:...

...0.025662] print_constraints: dummy: [ 0.045566] Time: 165:165:165 Date: 165/165/65 [ 0.045675] NET: Registered protocol family 16 [ 0.047224] PCI: setting up Xen PCI frontend stub [ 0.048452] bio: create slab <bio-0> at 0 [ 0.048615] ACPI: Interpreter disabled. [ 0.050201] xen_balloon: Initialising balloon driver. [ 0.050244] last_pfn = 0x10800 max_arch_pfn = 0x400000000 [ 0.050838] vgaarb: loaded [ 0.051105] SCSI subsystem initialized [ 0.054024] usbcore: registered new interface driver usbfs [ 0.054050] usbcore: registered new interface driver hub [ 0.054135]...

...476] RTC time: 165:165:165, date: 165/165/65 [ 0.119675] NET: Registered protocol family 16 [ 0.121015] PCI: setting up Xen PCI frontend stub [ 0.127086] ACPI: Interpreter disabled. [ 0.127121] xen:balloon: Initialising balloon driver [ 0.129017] random: fast init done [ 0.130054] xen_balloon: Initialising balloon driver [ 0.131072] vgaarb: loaded [ 0.131195] SCSI subsystem initialized [ 0.131195] usbcore: registered new interface driver usbfs [ 0.131195] usbcore: registered new interface driver hub [ 0.131195] usbcore: registered new device driver usb [ 0.131195] dmi:...

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

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here: