search for: pysic

Displaying 12 results from an estimated 12 matches for "pysic".

Did you mean: pasic
2008 Oct 17
1
Preventing DomU corruption in case of Split-Brain of heartbeat
Hi Xen-Users! We run an large HA XEN system based on heartbeat2. Storage base is an infiniband storage cluster exporting iSCSI devices to the frontend HA XEN Machines. The iSCSI devices are used as pysical devices for the domUs using the block-iscsi mechanism (by the way thanks for this cool script). Recently we had a split brain in our heartbeat system. This causes both of our XEN servers to fetch the iSCSI-Device and run the domU on it. This resulted in severe damage of the filesystem of the dom...
2012 Feb 29
2
Guests pausing suddenly
...due to I/O error on dm-0 Feb 29 08:23:56 achernar kernel: Buffer I/O error on device dm-0, logical block 14252053 Feb 29 08:23:56 achernar kernel: lost page write due to I/O error on dm-0 Feb 29 08:23:57 achernar fcoemon: error 111 Connection refused I could not find any sensible message on the pysical host, neither in /var/log/messages nor in /var/log/libvirt. We do have an almost identical server, same hardware, same software which does not have this problem. How could I proceed to better diagnose the cause of the troubles? Regards, -- Peter Hopfgartner web : www.r3-gis.com
2018 Jul 21
2
Finding scratch register after function call
...ted: "Suitable" for option 1 means that it shall be any of the 4 physical registers AF, HL, DE, BC. When invoked after a function call to do caller-cleans-stack, none of the register(s) used for return value of the function call shall be used. The calling convention uses - one specific pysical 8 bit register (lower 8 bits of AF) for 8 bit return values - one specific physical 16 bit register (reg HL) for 16 bit - two 16 bit regs (regs HL + DE) for 32 bits return value When determining if one of those registers is available for the option 1 way of cleaning-up the stack after a functi...
2012 Mar 29
1
virsh create failed: cannot set CPU affinity on process 0
Hello Everyone: We can't create vm on a physical server with 64 CPU(as reported by /proc/cpuinfo). The error message is: "cannot set CPU affinity on process 0" The following is the capabilities detected by libvirt: <arch>x86_64</arch> <model>Westmere</model> <vendor>Intel</vendor> <topology sockets='4'
2008 Nov 13
1
Fwd: Samba memory usage - how big is it?
Sorry forgot to include the list. > From: Mike Gallamore <mike@mpi-cbg.de> > Date: November 13, 2008 3:49:21 PM GMT+01:00 > To: Volker.Lendecke@SerNet.DE > Subject: Re: [Samba] Samba memory usage - how big is it? > > I didn't include the whole output which would be about a page. Yeah > it is just a total of the columns. There is commands for excluding > shared
2016 Jan 13
2
Allowing virtual registers after register allocation
...ly >> growing physreg lists and it may take a while until we have flushed out all >> places that relied on a fixed-register number assumption. >> > > This seems like a really big deal to me; plus a lot of the discussion > above e.g. with regard to what the behavior of the pysical register > classes, is about properties which are really only relevant for register > allocation (and again I think we agree that we probably don't want to be > using the normal register allocator anyway). > > >> - You probably do not want to compute/modify some informati...
2007 Jul 15
1
bridging and peth0
Hi, If one sets xend to use network-bridge and there are no bridges already present then it seems that xend will clone eth0 to peth0, create xenbr0 and add peth0 and vif0.0 as ports on that bridge. If on the other hand xenbr0 is created in /etc/network/interfaces then xend will not do any of that peth0 stuff, nor will it add vif0.0 to xenbr0, yet (barring some changes in iptables rules) things
2016 Jan 22
2
Allowing virtual registers after register allocation
...physreg lists and it may take a while until we have flushed out all >>> places that relied on a fixed-register number assumption. >>> >> >> This seems like a really big deal to me; plus a lot of the discussion >> above e.g. with regard to what the behavior of the pysical register >> classes, is about properties which are really only relevant for register >> allocation (and again I think we agree that we probably don't want to be >> using the normal register allocator anyway). >> >> >>> - You probably do not want to compu...
2015 Dec 10
3
Allowing virtual registers after register allocation
To say this first: This whole discussion about using virtregs until emit or having growable physregs is hard to argue without actually having experience trying to go either way. Problems when using virtregs throughout the backend until emit time: - The MC layer is using MCPhysReg (which is an uint16_t) and would need retrofitting to support virtregs - VirtRegs are assumed to have a definition,
2005 Nov 23
8
a question about popen() performance on domU
Dear all, When I compared the performance of some application on both a Xen domU and a standard linux machine (where domU runs on a similar physical mahine), I notice the application runs faster on the domU than on the physical machine. Instrumenting the application code shows the application spends more time on popen() calls on domU than on the physical machine. I wonder if xenlinux does some
2004 Nov 16
0
metadata switches for ffmpeg2theora
..._add_video (uint8_t * data, int width, int height, int linesize,int e_o_s){ +int theoraframes_add_video (theoraframes_info *info, uint8_t * data, int width, int height, int linesize,int e_o_s){ /* map some things from info struk to local variables, * just to understand the code better */ /* pysical pages */ @@ -186,10 +184,10 @@ yuv.u = data + width * height; yuv.v = data + width * height * 5 / 4; } - theora_encode_YUVin (&info.td, &yuv); - theora_encode_packetout (&info.td, e_o_s, &info.op); - ogg_stream_packetin (&info.to, &info.op); - info.videoflag=1; + t...
2016 Jan 22
2
Allowing virtual registers after register allocation
...pport dynamically growing physreg lists and it may take a while until we have flushed out all places that relied on a fixed-register number assumption. >>> >>> This seems like a really big deal to me; plus a lot of the discussion above e.g. with regard to what the behavior of the pysical register classes, is about properties which are really only relevant for register allocation (and again I think we agree that we probably don't want to be using the normal register allocator anyway). >>> >>> - You probably do not want to compute/modify some information lik...