similar to: Some odd quriks of libvirt and xen on fedora 20.

Displaying 20 results from an estimated 1000 matches similar to: "Some odd quriks of libvirt and xen on fedora 20."

2014 Oct 31
0
Re: reboot problem with libxl
On Fri, Oct 31, 2014 at 08:34:48AM -0400, Alvin Starr wrote: >I was sort of hoping that is was something simple like setting the >"do_the_right_thing" flag. > > >The libvirtd kicks out >2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 >: driver in virRegisterNetworkDriver must not be NULL >2014-10-31 11:59:29.379+0000: 8840: error :
2014 Oct 31
2
Re: reboot problem with libxl
I was sort of hoping that is was something simple like setting the "do_the_right_thing" flag. The libvirtd kicks out 2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31 11:59:29.379+0000: 8840: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31
2016 Feb 08
1
KVM
>>> If you run top what are you seeing on the %Cpu(s) line? http://i.hizliresim.com/NrmV9Y.png On Mon, Feb 8, 2016 at 10:53 PM, Alvin Starr <alvin at netvel.net> wrote: > You need to provide more information. > 20% is what number. > There are something like 6 numbers on that line. > > > On 02/08/2016 02:56 PM, Gokan Atmaca wrote: >>> >>> If you
2018 Feb 08
2
georeplication over ssh.
That makes for an interesting problem. I cannot open port 24007 to allow RPC access. On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is > of glusterd. > glusterd will be listening in this port and all volume management > communication > happens via RPC. > > Thanks, >
2014 Oct 30
2
reboot problem with libxl
If I reboot a single vm through libvirt/libxl the system reboots normally. If I have several vm's reboot at the same time then The systems go into a paused state and do not reboot. I then have to kill them via xl and restart them. -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net ||
2016 Feb 08
0
KVM
You need to provide more information. 20% is what number. There are something like 6 numbers on that line. On 02/08/2016 02:56 PM, Gokan Atmaca wrote: >> If you run top what are you seeing on the %Cpu(s) line? > %20 > > > On Mon, Feb 8, 2016 at 9:30 PM, Alvin Starr <alvin at netvel.net> wrote: >> Slow disks will show up as higher I/Owait times. >> If your
2016 Sep 07
0
Fwd: Centos 6 AMI does not support c4-8xlarge
Hi John On 07/09/16 15:50, John Peacock wrote: > I have done that, but the point of the request is that we would like to > have an official upstream AMI that we can use as the basis for our > work. I'm guessing that the reason for the blacked out instance type is > that early 6.x kernels didn't have the patches necessary to support 36 > vCPU's present in the
2018 Feb 08
0
georeplication over ssh.
Ccing glusterd team for information On Thu, Feb 8, 2018 at 10:02 AM, Alvin Starr <alvin at netvel.net> wrote: > That makes for an interesting problem. > > I cannot open port 24007 to allow RPC access. > > On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is of >
2012 Nov 09
1
OVMF Bios Option
Hello Xen Users, Been experimenting with upstream-qemu and wanted to try out the OVMF bios option, but I seem to be missing something. Are there additional steps to installing OVMF beyond compiling Xen? I saw notes on patching back in february, but I thought the package was included with Xen 4.2 on release. When I attempt to set it as my bios option, the machine boots then immediately closes.
2015 Sep 08
1
Beta CentOS 7 Xen packages available
On 09/08/2015 10:58 AM, Konrad Rzeszutek Wilk wrote: > On Tue, Sep 08, 2015 at 10:50:57AM -0400, Alvin Starr wrote: >> FIrstly Centos is primarily a RHEL clone. >> This means that the primary design decisions are to be as RHEL like as >> possible. >> After that there are additions and upgrades. >> >> Secondly Fedora does not actively support Xen. >
2013 Jul 14
1
Cannot VGA Passthrough Intel HD Graphics 4600 IGD
Hi, I am trying to VGA passthrough Intel HD Graphics 4600 IGD with Xen-unstable 4.4 changeset 27214 and Linux kernel 3.10.0 but was not successful. Details are as follows: =============================================================================================== teo-en-ming@intel-core-i5-4430-desktop:~$ sudo xl info [sudo] password for teo-en-ming: host :
2013 Sep 24
7
Qxl problem with xen domU, is xen spice and/or qemu bugs?
I''ve been trying to have all spice features working on xen domUs since the end of 2011. Basic functions were already working. Adding qemu parameters manually for vdagent and usbredirection was and is also working (I made the patches to support them directly on xl). Qxl was never working: one bug on xen and one on qemu about qxl are fixed, the other xen bug found months ago on the
2016 Jan 21
0
CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing
My comment was targeted more at naming than support. I appreciate that there are vanishingly few resources to throw at support. I am glad to see any xen support for C7 and am thankful of all those who are putting in time to make things happen. I try to help out when I can but it is all too infrequently. On 01/21/2016 10:29 AM, Johnny Hughes wrote: > This is a community SIG .. and
2018 Feb 08
0
georeplication over ssh.
Hi Alvin, Yes, geo-replication sync happens via SSH. Ther server port 24007 is of glusterd. glusterd will be listening in this port and all volume management communication happens via RPC. Thanks, Kotresh HR On Wed, Feb 7, 2018 at 8:29 PM, Alvin Starr <alvin at netvel.net> wrote: > I am running gluster 3.8.9 and trying to setup a geo-replicated volume > over ssh, > > It looks
2018 Feb 07
2
georeplication over ssh.
I am running gluster 3.8.9 and trying to setup a geo-replicated volume over ssh, It looks like the volume create command is trying to directly access the server over port 24007. The docs imply that all communications are over ssh. What am I missing? -- Alvin Starr || land: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin at netvel.net
2015 Sep 08
0
Beta CentOS 7 Xen packages available
On Tue, Sep 08, 2015 at 10:50:57AM -0400, Alvin Starr wrote: > FIrstly Centos is primarily a RHEL clone. > This means that the primary design decisions are to be as RHEL like as > possible. > After that there are additions and upgrades. > > Secondly Fedora does not actively support Xen. Nonsense. Have you done 'yum install xen' ? > As a long time Xen and RH/Fedora
2017 Mar 22
0
grub-bootxen.sh
Maybe you just don't need to remove anything at all but just move them to another folder that does the same goal. For *-release-*.rpm, again it is explained itself. Xlord -----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Alvin Starr Sent: Tuesday, March 21, 2017 1:45 AM To: centos-virt at centos.org Subject: [CentOS-virt] grub-bootxen.sh
2016 Feb 08
3
KVM
> If you run top what are you seeing on the %Cpu(s) line? %20 On Mon, Feb 8, 2016 at 9:30 PM, Alvin Starr <alvin at netvel.net> wrote: > Slow disks will show up as higher I/Owait times. > If your seeing 99% cpu usage then your likely looking at some other problem. > > If you run top what are you seeing on the %Cpu(s) line? > > > On 02/08/2016 02:20 PM, Gokan Atmaca
2017 Mar 20
2
grub-bootxen.sh
This is not abit issue just a minor annoyance. I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo. I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d. -- Alvin
2017 Mar 22
2
grub-bootxen.sh
I actually move the default *.repo files and replace them with "". The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don't have to install any more *-release-* rpms any more. I would argue that I should not need to install any *-release-* rpms at all to get all the required software. On 03/22/2017 09:34 AM, -=X.L.O.R.D=- wrote: