similar to: Xen Balloon Driver on PVHVM CentOS6

Hi List, I''m trying to work out the balloon driver on CentOS6 HVM but it seems to be not working with default 2.6.32 or newer 3.4 kernel. Does balloon driver work on HVM linux guests with Linux Kernel 3.4 from centos repo ? PV is fine and is able to balloon. Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

Hi List, I''m trying to work out the balloon driver on CentOS6 HVM but it seems to be not working with default 2.6.32 or newer 3.4 kernel. Does balloon driver work on HVM linux guests with Linux Kernel 3.4 from centos repo ? PV is fine and is able to balloon. Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

Hi list, I try to understand memory ballooning. I have a xen server (kernel 2.6.27.54-0.2-xen) with 32 gb total memory. A domU has been started with "memory=4096" and "maxmem=8192". This is the status of the balloon driver in the domU: test:~ # cat /proc/xen/balloon Current allocation: 4194304 kB Requested target: 4194304 kB Minimum target: 565248 kB Maximum

Hi, everyone! We google a lot, but can''t find how to config the pvscsi on our ubuntu13.04 PV on HVM.There are some links http://wiki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04)

Hi, I have made the for-centos-v5 branch available on git://xenbits.xen.org/people/dvrabel/linux.git This is based on 3.4.54 and includes the following additional fixes (since the for-centos-v4 branch). * x86/xen: during early setup, only 1:1 map the ISA region Fixes a boot failure if tboot is used. * xen/evtchn: avoid a deadlock when unbinding an event channel Fixes a potential deadlock by

Apologies for missing Subject. On Wed, Jan 9, 2013 at 3:21 AM, Rushikesh Jadhav <2rushikeshj@gmail.com>wrote: > Hello List, > > Please help me in diagnosing below error in /var/log/messages > > HVM1[16586]: txftrans.c:4498 -- TXF_HARD_ERROR (0xC01A002B) for RM: > fffff8800d099000 > > Im unable to find any google reference related to above C file or its > source

Hi Linus, These patches make it possible to inhibit the Xen emulated device unplug on the kernel command line (mostly "Just In Case") and renames xen_emul_unplug=ignore to the clearer xen_emul_unplug=unnecessary. Since it changes the name of a command line option we''d like to get it in before 2.6.36 proper. The third changeset is a pure cleanup which you could ignore for

Hello users, I have a problem when I save/restore a PVHVM guest. I installed xen-4.1.2 on my server. And I run a PVHVM guest on LVM. And my PVHVM guest is ubuntu-12.04.2-desktop. Actually when I save a machine, it acts fine. (Of course, when I saved it, There were some processes like movie player) But, When I restore it, It seems more slow. Additionally, machine finally die after a while. I

Hi, I am using sendmailR package to send mails from R. I am not able to make carbon copy work properly. If I specify multiple recipients in to field, then they all receive individual emails and not carbon copies My sample code is require(sendmailR) header <- list(cc="b.mali@abc.com") to <-

hi, I'm trying to configure my newly acquired TE410P card to work as 4 E1 spans. This is supposed to be a drop-in replacement to the earlier E100P card. However, on loading the zaptel module it gets configured as T1 spans basically doing a 'cat' on /proc/zaptel/1 thru 4, it shows 24 channels per span. After this ztcfg fails saying 'ZT_CHANCONFIG failed for channel 97'.

kernel use callback linked in panic_notifier_list to notice others when panic happens. NORET_TYPE void panic(const char * fmt, ...){ ... atomic_notifier_call_chain(&panic_notifier_list, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but

kernel use callback linked in panic_notifier_list to notice others when panic happens. NORET_TYPE void panic(const char * fmt, ...){ ... atomic_notifier_call_chain(&panic_notifier_list, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but

kernel use callback linked in panic_notifier_list to notice others when panic happens. NORET_TYPE void panic(const char * fmt, ...){ ... atomic_notifier_call_chain(&panic_notifier_list, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but

Hello, I'm looking for an example configuration for a PVHVM domU that works with 4.3.1. The one at http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers causes 3 warnings and some errors: WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware WARNING: ignoring device_model directive. WARNING: Use

Checked out the latest unstable version of Xen 4.4 but failed to create a PVHVM domU Configured Xen with ./configure --prefix=/usr DomU config file: name = "pvhvm" builder=''hvm'' device_model = ''qemu-xen'' memory = ''512'' vcpus = ''4'' pae=1 acpi=1 apic=1 vif = [ ''mac=00:16:3E:51:20:8C, bridge=xenbr0,

Hi, After some more testing I thought it would be good to put this into production for my personal server. I''ve used pvhvm_v19 and built it without debugging options and installed it on a FreeBSD 9.1 system. I''ve run into some hiccups with 9.1 user land and a 10-CURRENT kernel, but that''s all solvable[0]. My VPS has some very limited memory (256M), but I''ve

Hi, On 19 Jun 2013, at 18:52, Justin T. Gibbs <gibbs@FreeBSD.org> wrote: >> I guess the kernel-toolchain takes a long time to build…and from what I can see it does a clean before rebuilding also. >> >> I''m doing the kernel-toolchain step only now and will report how long it took. This seems to be it, that took roughly 2 hours to build. The actual kernel is

On 19/06/13 14:33, Jeroen van der Ham wrote: > > On 19 Jun 2013, at 14:20, Roger Pau Monné <roger.pau@citrix.com> wrote: >> That''s because Justin recently pushed a commit that changed the ad >> translation to ada, you should change your /etc/fstab to ada0p2. It''s >> commit 526f3ad11acb296481215d7c2915b3f30f1844f6. > > > Ah, you may want

Hello, While testing Fedora 16 Xen PVHVM guests I noticed the following problem: When starting F16 PVHVM guest I can see the vifX.0 and tapX.0 interfaces appear on dom0, but after the guest kernel (Linux 3.1.0) starts and loads PVHVM drivers the vif/tap interfaces disappear from dom0.. so the bridge in dom0 doesn''t have any vifs/taps connected to it anymore. Has anyone seen that

Hello, I am a beginner in R programming and recently heard about this mailing list. Currently, I am trapped into a simple problem for which I just can't find a solution. I have a huge dataset (~81,000 observations) that has been analyzed and the final result is in the form of 0 and 1(one column). I need to write a code to process this column in a little complicated way. These 81,000