similar to: Paravirtualization Issue

Hi. I''ve subscribed my self to participate of GSoC''11. The project that Im interested is the parallax sm backend. My project is the integration with Xen Cloud Platform and Parallax. In end of this project, We expect a simple way of managing VMs with Parallax and if possible, to ease fail-over, migration and perform very low overhead snapshots. I’m open for suggestions and

Hi. I''ve subscribed my self to participate of GSoC''11. The project that Im interested is the parallax sm backend. My project is the integration with Xen Cloud Platform and Parallax. In end of this project, We expect a simple way of managing VMs with Parallax and if possible, to ease fail-over, migration and perform very low overhead snapshots. I’m open for suggestions and

I setup postfix/dovecot on a new machine and now all works well with the small exception of dovecot triggering selinux avc denials on some temp... files here is a sample alert: Summary SELinux is preventing /usr/libexec/dovecot/deliver (dovecot_deliver_t) "link" to temp.localhost.678.40caaf5592891c46 (user_home_dir_t). Detailed Description SELinux denied access requested

These patches provide the infrastructure for paravirtualized MMU operations while at the same time cleaning up and optimizing the pagetable accessors for i386. They should be largely uncontroversial and are well tested. There are still some performance gains to be had for paravirtualization, but it is more important to get the native code base that will enable them checked in first. Zach

These patches provide the infrastructure for paravirtualized MMU operations while at the same time cleaning up and optimizing the pagetable accessors for i386. They should be largely uncontroversial and are well tested. There are still some performance gains to be had for paravirtualization, but it is more important to get the native code base that will enable them checked in first. Zach

Ok, I am running NUT in dummy mode. I have added a new ups in ups.conf [dummy] driver = dummy-ups port = upsc.dev desc = "dummy ups for testing purposes" upsc.dev has been generated by exporting the Elit configuration. I have added the monitor line in upsmon.conf and the "exec" flags (all the events) MONITOR dummy at artu 1 user pass master SHUTDOWNCMD

So....seems so better... Each time I rebbot, I miss the /var/run/nut folder... root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) root at artu:~# upsd Network UPS Tools upsd 2.7.2 fopen

Hi, We ran a few experiments to compare performance of VMware's paravirtualization technique (VMI) and hardware MMU technologies (HWMMU) on VMware's hypervisor. To give some background, VMI is VMware's paravirtualization specification which tries to optimize CPU and MMU operations of the guest operating system. For more information take a look at this

Hi, We ran a few experiments to compare performance of VMware's paravirtualization technique (VMI) and hardware MMU technologies (HWMMU) on VMware's hypervisor. To give some background, VMI is VMware's paravirtualization specification which tries to optimize CPU and MMU operations of the guest operating system. For more information take a look at this

2017-06-11 14:10 GMT+02:00 Andrea de Lutti <adelutti at gmail.com>: > So....seems so better... > > Each time I rebbot, I miss the /var/run/nut folder... > > root at artu:~# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.2 > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) > Can't chdir to /var/run/nut: No such file or directory >

Hi. Im writing a kernel module to extract some information from kernel, the module is working really fine in an AMD (AMD Athlon(tm) 64 X2 Dual Core Processor 3800+), but, when trying to run the module in a i7 (Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz) Im facing some strange errors (see below). The kernel versions are just the same on both machines (2.6.34.10-0.2-xen #1 SMP x86_64 x86_64 x86_64

Hi. Im writing a kernel module to extract some information from kernel, the module is working really fine in an AMD (AMD Athlon(tm) 64 X2 Dual Core Processor 3800+), but, when trying to run the module in a i7 (Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz) Im facing some strange errors (see below). The kernel versions are just the same on both machines (2.6.34.10-0.2-xen #1 SMP x86_64 x86_64 x86_64

Hello. I use Centos 4.4 on desktop now and I was looking for gnome-commander, I see that RHEL or any RHEL based distro provides RPMs, only FC5 and FC7. Also Dag repository have this only for FC1. I would like know if there is anyo ther package better or similar to this, or any other package similar to Norton Commander. Thanks Josep --------------------------------- LLama Gratis a

Not that I really believe it but I read somewhere (cant find it again) that microsoft was releasing paravirtualization drivers for kvm that would be adaptable to xen. Is this rumor or is this true?   I honestly can''t imagine why Microsoft would do this so I am skeptical, can anyone confirm or deny this? Provide a link perhaps?   thanks,   hikenboot

On Mon, 3 Jul 2017, Andrea de Lutti wrote: > MONITOR dummy at artu 1 user pass master > SHUTDOWNCMD "/sbin/shutdown -h +0" > NOTIFYCMD /usr/local/bin/upssched-script Hi, As far as I can see, what you are getting in syslog corresponds correctly to what you have specified. You have specified that upsmon is to call upssched-script _directly_. This means that the argument to

> > hmm, apparently the UPS doesn't close the replies to our queries with > the expected CR and we (I) did not consider that case in nutdrv_qx -- > noted: > https://github.com/networkupstools/nut/issues/441 > > But blazer_usb, being less strict on the terminating CR of Q1 replies, > should work with your device. > > > root at artu:~# upsc Elit at artu > >

Hi,Chris? I wonder which version of Xen did the para-Linux works with. I applied the patches, compiled them and tried them on both xen-3.0.2 and the latest xen-unstable. Both result in panics when booting Xen and complain as follows: (XEN) Domain 0 kernel supports features = { 00000005 }. (XEN) Domain 0 kernel requires features = { 00000005 }. (XEN) (XEN)

Hi linux/ia64 developers. Few days before Eddie posted the mail for Linux/IA64 paravirtualization. But only a few responded partially because there was no reviewable patches. Here is the patches for xen/ia64 Linux paravirtualization. The goal is to merge IA64 xen Linux paravirtualization for both domU and dom0 eventually. However the first step is to merge domU portion. As you can see from the

Newbie here. My hardware supports HVM (full virtualization), but I only need to run Linux on it. I initially tried to create a HVM domU, but couldn''t get pciback to work with a telephony card I need for use with Asterisk. However everything seems to be working fine under a paravirtualized guest as long as I use permissive mode on the card. (Knock on wood-I''ve had some weird

> Starting the driver with debug level 5 seems happier, but continue to cycle It is meant to 'cycle', it's working correctly. When you run the driver normally (i.e. not in debug mode), you don't see all that output (plus, after having established a connection with the device, the driver goes into the background), but it's doing exactly the same thing. > nutdrv_qx....