Hi, I want to place a blktap device on top of a partition. Is this possible? Thanks! -Jack
We are running HP ProLiant DL580 G7 E7540 with four sockets. The Dom0 VCPU0 is pinned to the CPU 0 on the socket 0. What is going to happen if socket 0 starts malfunctioning? Thanks, Vitaly.
On Fri, Jan 13, 2012 at 4:36 AM, Grinberg, Vitaly <Vitaly.Grinberg@marriott.com> wrote:> > We are running HP ProLiant DL580 G7 E7540 with four sockets. > > The Dom0 VCPU0 is pinned to the CPU 0 on the socket 0. > > What is going to happen if socket 0 starts malfunctioning?Your server will be dead. Or at least crashed and needs to be restarted, and then (in the case of multi-socket servers) it would have less available CPU than before. Regardless of whether it''s using xen, windows, linux, or whatever, there are no x86 server that I know of that can keep functioning in the case of a failed cpu socket. -- Fajar
If it is correct, the Dom0 which is pinned to this CPU is not available. -----Original Message----- From: Fajar A. Nugraha [mailto:list@fajar.net] Sent: Thursday, January 12, 2012 5:33 PM To: Grinberg, Vitaly Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Dom0 issue On Fri, Jan 13, 2012 at 4:36 AM, Grinberg, Vitaly <Vitaly.Grinberg@marriott.com> wrote:> > We are running HP ProLiant DL580 G7 E7540 with four sockets. > > The Dom0 VCPU0 is pinned to the CPU 0 on the socket 0. > > What is going to happen if socket 0 starts malfunctioning?Your server will be dead. Or at least crashed and needs to be restarted, and then (in the case of multi-socket servers) it would have less available CPU than before. Regardless of whether it''s using xen, windows, linux, or whatever, there are no x86 server that I know of that can keep functioning in the case of a failed cpu socket. -- Fajar
You''re missing the point. What did you mean by "if socket 0 starts malfunctioning"? The CPU got overheat and dead? If a CPU is dead, then an x86 server is dead. That''s it. There''s no difference whether it''s xen or not, or whether you use cpu pin or not. Unless you have another definition of "malfunctioning"? -- Fajar On Fri, Jan 13, 2012 at 10:41 PM, Grinberg, Vitaly <Vitaly.Grinberg@marriott.com> wrote:> If it is correct, the Dom0 which is pinned to this CPU is not available. > > > -----Original Message----- > From: Fajar A. Nugraha [mailto:list@fajar.net] > Sent: Thursday, January 12, 2012 5:33 PM > To: Grinberg, Vitaly > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Dom0 issue > > On Fri, Jan 13, 2012 at 4:36 AM, Grinberg, Vitaly > <Vitaly.Grinberg@marriott.com> wrote: >> >> We are running HP ProLiant DL580 G7 E7540 with four sockets. >> >> The Dom0 VCPU0 is pinned to the CPU 0 on the socket 0. >> >> What is going to happen if socket 0 starts malfunctioning? > > Your server will be dead. Or at least crashed and needs to be > restarted, and then (in the case of multi-socket servers) it would > have less available CPU than before. > > Regardless of whether it''s using xen, windows, linux, or whatever, > there are no x86 server that I know of that can keep functioning in > the case of a failed cpu socket. > > -- > Fajar
Are you saying that after the reboot what was CPU 1 will become CPU 0? -----Original Message----- From: Fajar A. Nugraha [mailto:list@fajar.net] Sent: Friday, January 13, 2012 10:50 AM To: Grinberg, Vitaly Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Dom0 issue You''re missing the point. What did you mean by "if socket 0 starts malfunctioning"? The CPU got overheat and dead? If a CPU is dead, then an x86 server is dead. That''s it. There''s no difference whether it''s xen or not, or whether you use cpu pin or not. Unless you have another definition of "malfunctioning"? -- Fajar On Fri, Jan 13, 2012 at 10:41 PM, Grinberg, Vitaly <Vitaly.Grinberg@marriott.com> wrote:> If it is correct, the Dom0 which is pinned to this CPU is notavailable.> > > -----Original Message----- > From: Fajar A. Nugraha [mailto:list@fajar.net] > Sent: Thursday, January 12, 2012 5:33 PM > To: Grinberg, Vitaly > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Dom0 issue > > On Fri, Jan 13, 2012 at 4:36 AM, Grinberg, Vitaly > <Vitaly.Grinberg@marriott.com> wrote: >> >> We are running HP ProLiant DL580 G7 E7540 with four sockets. >> >> The Dom0 VCPU0 is pinned to the CPU 0 on the socket 0. >> >> What is going to happen if socket 0 starts malfunctioning? > > Your server will be dead. Or at least crashed and needs to be > restarted, and then (in the case of multi-socket servers) it would > have less available CPU than before. > > Regardless of whether it''s using xen, windows, linux, or whatever, > there are no x86 server that I know of that can keep functioning in > the case of a failed cpu socket. > > -- > Fajar
On Fri, Jan 13, 2012 at 11:03 PM, Grinberg, Vitaly <Vitaly.Grinberg@marriott.com> wrote:> Are you saying that after the reboot what was CPU 1 will become CPU 0?If the system can boot, then the first available cpu (or rather, the first available hyperthread, in the first core, in the first CPU socket) will always be CPU0. It doesn''t matter whether the system has only one physical cpu and you''re moving it around on different sockets. Of course, that''s assuming that the server can boot if you move around the cpu on different sockets, or that the server can boot with one good cpu and one bad cpu connected. -- Fajar