similar to: Xen 4.1.2 HT disaware (?)

Hi Wei, I ran into the following problem when trying to boot another guest after less than a day of uptime. (the system started 15 guests at boot already which went fine). dom0 is allocated a fixed 1536M. Both host as pv guests run the same kernel, some hvm''s run a slightly older kernel (3.9 f.e.) The are quite some granttable messages in xl dmesg, i also included these and a

Hey Jens, Please in your spare time (if there is such a thing at a conference) pull this branch: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.10 for your v3.10 branch. Sorry for being so late with this. <blurb> It has the ''feature-max-indirect-segments'' implemented in both backend and frontend. The current problem with the backend and

Hello there! I know, that this thing is discussed many times already ( http://xen.1045712.n5.nabble.com/change-console-size-of-quot-xm-console-quot-td2572700.html for example), but still can''t figure out a reason, why the possiblity to dynamically change HVC size can''t be totally implemented for a many years :''(. _______________________________________________

Hello there! I know, that this thing is discussed many times already ( http://xen.1045712.n5.nabble.com/change-console-size-of-quot-xm-console-quot-td2572700.html for example), but still can''t figure out a reason, why the possiblity to dynamically change HVC size can''t be totally implemented for a many years :''(. _______________________________________________

Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it

I am trying to hwclock to set the time. (hwclock -w) this is what I get on standard 5.2 x86_64. hwclock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found. Cannot access the Hardware Clock via any known method. [root at devcentos5x64 src]# ls -l /dev/rtc crw------- 1 root root 10, 135 Feb 6 13:32 /dev/rtc Any

I am getting this error: hwclock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy. No usable clock interface found. Cannot access the Hardware Clock via any known method. [root at devcentos5x64 src]# uname -a Linux devcentos5x64.msgnet.com 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep

Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error "Cannot access the hardware clock by any known method", and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. "hwclock" works fine. hwclock --debug does not show any error at all. The hardware clock is

Hi All, The interface manual says - grant tables provide a generic mechanism sharing between domains. Subsequent lines suggest mechanism sharing between only unpriviliged domains. Can grant tables be used for this capability based shared memory communication between dom0 and domUs? Thanks ~psr -- pradeep singh rautela "proud to be a TUXedo, BSDemons you are a little late" - me

Hi, it seems as if it is not possible to have more than 3 nics per domU right now. If I specify more, I get the usual [...] xen_net: Initialising virtual ethernet driver. #### netfront can''t alloc rx grant refs vif: probe of vif-3 failed with error -12 [...] message - see bug #183. It was pointed out to me that it might be possible to adjust this manually in

Hi all, One of our domU VMs (CentOS 5.6 x86_64) runs a cobol application, which in turn called ''clock'' to get timestamps. Changing this is non-trivial. When I try to call ''clock --debug'' I get: [root@vm0010 ~]# clock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found.

Hi, I'm seeing the following issue when attempting to update the guest's clock on a running fc32 guest (using guest agent): ``` [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --pretty Time: 2020-04-30 23:27:29 [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --sync error: internal error: unable to execute QEMU agent command 'guest-set-time': hwclock

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.16.1"> </HEAD> <BODY> Hello All, I have a problem with hwclock on centos 5.3. in xen guest environment<FONT

So I have learned that Postfix should delay until Chronyd has moved the system time from 0 to current. What other services need to be delayed? Apache? Bind? Of course if this is a nameserver, Chronyd will probably not be able to resolve the NTP server addresses until Bind is running! thanks

On Thu, Apr 30, 2020 at 2:15 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Thu, Apr 30, 2020 at 01:52:12PM +0200, Miguel Duarte de Mora Barroso wrote: > > Hi, > > > > I'm seeing the following issue when attempting to update the guest's > > clock on a running fc32 guest (using guest agent): > > > > ``` > >

Hi. I run peridocally (from cron) on all of my machines 30 * * * * root /sbin/hwclock --systohc All of those machines in question take their time via NTP from the same local server, and that server gets its time from a ntp pool. Now I had to reboot a couple of them two days ago and to my surprise all had problems with the time upon booting. Here are the important files: [root at XXXXXX ~]

Hey, I have rather new installation of xen, dom0 is running ntpd and is perfectly in time. All domU''s are ~23s in future. Running ntpd on the domU''s seem to have no effect, /proc/sys/xen/independent_wallclock appears to have no effect. I''m running xen-unstable and 2.6.16-rc4 in AMD64 box. Any tip would be appricated. Thanks, -- ++ytti

The paravirtualized guests are offered wallclock time referenced to UTC only, while fully virtualized guests are given the option via the config file (localtime parameter) of starting with UTC time or local time. What would it take to optionally provide localtime to the paravirtualized guests as well? For a guest that launches assuming localtime as its time basis, then later deriving UTC from it

https://bugzilla.netfilter.org/show_bug.cgi?id=1009 Vadim A. Misbakh-Soloviov (mva) <netfilter at mva.name> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netfilter at mva.name --- Comment #1 from Vadim A. Misbakh-Soloviov (mva) <netfilter at

We have found a critical problem with the XEN 3.1 release (for those who are running 15-20 VMs on a single server). We are using the official XEN 3.1 release on a rackable server (Dual-Core AMD Opteron, 8GB RAM). The problem we are seeing is that intermittently vifs fail to work properly in VMs after we create around 15-17 VMs on our server (all running at the same time, created one by