I''m looking at XCP with interest. My environment right now is SLES10 and SLES11 servers. I''ve always had issues with memory where the servers stop responding after an undetermined amount of time even though xm info says plenty of RAM is available. Sometimes xm itself hangs. Sometimes a hard reboot is even required. It got better with SLES11 and xen 3.4.2 with ballooning disabled, but I don''t think it''s entirely gone. I''m also interested in having some tools that make managing my domUs a little bit easier. It would be nice to be able to safely give others more access to administration as well. I looked at moving to XenServer a few months ago and even built a XenServer, but it didn''t appear to support ocfs2 which I use for my shared storage. I could get probably get away from ocfs2, but it seems to work well for me. I see that this is planned for XCP. The other issue I had with XenServer was converting my 35-40 domU''s over looked like it would be a huge project by itself. My questions are: Is anyone using XCP yet? Any guesses on how long before it would be considered acceptable for production use? Any eta on ocfs2 support? It''s currently listed at the bottom of the Roadmap if that has any significance. Will I be able to easily move my file based domU''s over to XCP? Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Jan 20, 2010 at 01:55:35PM -0500, James Pifer wrote:> I''m looking at XCP with interest. My environment right now is SLES10 and > SLES11 servers. I''ve always had issues with memory where the servers > stop responding after an undetermined amount of time even though xm info > says plenty of RAM is available. Sometimes xm itself hangs. Sometimes a > hard reboot is even required. It got better with SLES11 and xen 3.4.2 > with ballooning disabled, but I don''t think it''s entirely gone. >Hmm.. nothing in the logs? Do you have serial consoles set up so you can log the errors/crashes? XCP is currently using Xen 3.4.2 hypervisor, but the management tools are different in dom0.. XCP has xapi/xe and different xenstored implementation.> I''m also interested in having some tools that make managing my domUs a > little bit easier. It would be nice to be able to safely give others > more access to administration as well. > > I looked at moving to XenServer a few months ago and even built a > XenServer, but it didn''t appear to support ocfs2 which I use for my > shared storage. I could get probably get away from ocfs2, but it seems > to work well for me. I see that this is planned for XCP. The other issue > I had with XenServer was converting my 35-40 domU''s over looked like it > would be a huge project by itself. > > My questions are: > Is anyone using XCP yet? >I''ve heard of many people using/testing it.> Any guesses on how long before it would be considered acceptable for > production use? > > Any eta on ocfs2 support? It''s currently listed at the bottom of the > Roadmap if that has any significance. > > Will I be able to easily move my file based domU''s over to XCP? >XCP is pretty much like XenServer, so similar V2V process is needed for both.. you could use some of the products made for that purpose, or create a custom script that does it.. (especially if your'' domUs are pretty similar). -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hmm.. nothing in the logs? Do you have serial consoles set up so you can > log the errors/crashes?No, I''ve never found anything in the logs. How would I setup serial consoles to do this?> > > > XCP is pretty much like XenServer, so similar V2V process is needed for both.. > you could use some of the products made for that purpose, or create a custom > script that does it.. (especially if your'' domUs are pretty similar).Is there a documented V2V process somewhere? My domU''s are very similar. Most of my windows domU are created from a master "image" and modifications/customizations made after creation. Same with linux domU''s which are all sles10 SP1 or SP2. Some 32bit some 64bit. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Jan 20, 2010 at 03:23:42PM -0500, James Pifer wrote:> > Hmm.. nothing in the logs? Do you have serial consoles set up so you can > > log the errors/crashes? > > No, I''ve never found anything in the logs. How would I setup serial > consoles to do this? >In the usual way.. I guess you''re not familiar with serial consoles? The "oldskool" way is to use serial cables ("null-modem cables") and connect the serial ports of the servers to other computers or terminal servers. Then configure the Xen-hosts to use the serial port as a console logging/printing everything there, and the other computers or terminal servers to log everything from the serial ports and write to disk. If you''re using a laptop to log, you can get an USB serial adapter for the laptop for logging. USB serial adapter cannot be used on the Xen hosts, since the serial port needs to be accessible before USB drivers are loaded in the dom0 kernel. This allows you to capture and store everything that happens (=is printed on the console) on the Xen-hosts. The ''newskool'' way is to use serial console over SOL (Serial Over Lan). SOL devices can be found from most new servers nowadays, usually from the management processor (for example HP iLO or IPMI). Basicly SOL presents a (PCI) serial port to the OS, but the management processor makes it possible to use/attach to that serial port over the network over an IP connection. Some desktop computers also have Intel AMT/vPro (Active Management Technology), which also has virtual serial port over the network implemented.> > > > > > > XCP is pretty much like XenServer, so similar V2V process is needed for both.. > > you could use some of the products made for that purpose, or create a custom > > script that does it.. (especially if your'' domUs are pretty similar). > > Is there a documented V2V process somewhere? My domU''s are very similar. > Most of my windows domU are created from a master "image" and > modifications/customizations made after creation. Same with linux domU''s > which are all sles10 SP1 or SP2. Some 32bit some 64bit. >You might want to check XenConvert. V2V can be also done manually, but it''s a bit tricky with the drivers and stuff.. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> In the usual way.. I guess you''re not familiar with serial consoles? > > The "oldskool" way is to use serial cables ("null-modem cables") and > connect the serial ports of the servers to other computers or > terminal servers. Then configure the Xen-hosts to use the serial port > as a console logging/printing everything there, and the other computers > or terminal servers to log everything from the serial ports and write to disk. > > If you''re using a laptop to log, you can get an USB serial adapter > for the laptop for logging. > > USB serial adapter cannot be used on the Xen hosts, since the serial port > needs to be accessible before USB drivers are loaded in the dom0 kernel. > > This allows you to capture and store everything that happens (=is printed on the console) > on the Xen-hosts. > > The ''newskool'' way is to use serial console over SOL (Serial Over Lan). SOL devices > can be found from most new servers nowadays, usually from the management processor > (for example HP iLO or IPMI). > > Basicly SOL presents a (PCI) serial port to the OS, but the management processor > makes it possible to use/attach to that serial port over the network over an IP connection. > > Some desktop computers also have Intel AMT/vPro (Active Management Technology), > which also has virtual serial port over the network implemented. >Yeah, I''m not familiar with serial consoles and I''m remote to the servers. We do have iLO cards in the servers where I can take over the servers console. In these cases where the server has problems, it''s a black screen and you can''t do anything.> > > > You might want to check XenConvert. > > V2V can be also done manually, but it''s a bit tricky with the drivers and stuff..Yeah, tried both of these when I tried XenServer 5.5 and had no success with either of them. At the time, a couple months ago, I did a lot of searching for answers and it seemed that a lot of people were having similar problems. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Jan 20, 2010 at 05:53:40PM -0500, James Pifer wrote:> > In the usual way.. I guess you''re not familiar with serial consoles? > > > > The "oldskool" way is to use serial cables ("null-modem cables") and > > connect the serial ports of the servers to other computers or > > terminal servers. Then configure the Xen-hosts to use the serial port > > as a console logging/printing everything there, and the other computers > > or terminal servers to log everything from the serial ports and write to disk. > > > > If you''re using a laptop to log, you can get an USB serial adapter > > for the laptop for logging. > > > > USB serial adapter cannot be used on the Xen hosts, since the serial port > > needs to be accessible before USB drivers are loaded in the dom0 kernel. > > > > This allows you to capture and store everything that happens (=is printed on the console) > > on the Xen-hosts. > > > > The ''newskool'' way is to use serial console over SOL (Serial Over Lan). SOL devices > > can be found from most new servers nowadays, usually from the management processor > > (for example HP iLO or IPMI). > > > > Basicly SOL presents a (PCI) serial port to the OS, but the management processor > > makes it possible to use/attach to that serial port over the network over an IP connection. > > > > Some desktop computers also have Intel AMT/vPro (Active Management Technology), > > which also has virtual serial port over the network implemented. > > > > Yeah, I''m not familiar with serial consoles and I''m remote to the > servers. We do have iLO cards in the servers where I can take over the > servers console. In these cases where the server has problems, it''s a > black screen and you can''t do anything. >Indeed that''s exactly the problem with VGA consoles. It doesn''t help you at all in a error/crash condition. HP iLO should provide SOL for you. You can set it up, and configure other server to log the serial console over the network. Please run "lspci -vvv" in the dom0/host. Do you see a serial port? Check the IO port and interrupt (IRQ) it''s using and I can help you to set up the SOL. If you don''t see a serial port, I believe then you have to enable it in iLO settings. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 2010-01-21 at 09:56 +0200, Pasi Kärkkäinen wrote:> lspci -vvvPasi, Here''s the output in relation to the iLo. Thanks, James 01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03) Subsystem: Hewlett-Packard Company Device 3305 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 21 Region 0: I/O ports at 2800 [size=256] Region 1: Memory at f5fe0000 (32-bit, non-prefetchable) [size=512] Capabilities: [f0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: hpwdt Kernel modules: hpwdt 01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 03) Subsystem: Hewlett-Packard Company Device 3305 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 22 BIST result: 00 Region 0: I/O ports at 3400 [size=256] Region 1: Memory at f5fd0000 (32-bit, non-prefetchable) [size=2K] Region 2: Memory at f5fc0000 (32-bit, non-prefetchable) [size=16K] Region 3: Memory at f5f00000 (32-bit, non-prefetchable) [size=512K] [virtual] Expansion ROM at f5e20000 [disabled] [size=64K] Capabilities: [f0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: hpilo Kernel modules: hpilo 01:04.4 USB Controller: Hewlett-Packard Company Proliant iLO2 virtual USB controller (prog-if 00 [UHCI]) Subsystem: Hewlett-Packard Company Device 3305 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 Interrupt: pin B routed to IRQ 22 Region 4: I/O ports at 3800 [size=32] Capabilities: [f0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 01:04.6 IPMI SMIC interface: Hewlett-Packard Company Proliant iLO2 virtual UART (prog-if 01) Subsystem: Hewlett-Packard Company Device 3305 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 21 Region 0: Memory at f5ef0000 (32-bit, non-prefetchable) [size=256] Capabilities: [f0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ipmi_si Kernel modules: ipmi_si _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jan 21, 2010 at 09:46:27AM -0500, James Pifer wrote:> On Thu, 2010-01-21 at 09:56 +0200, Pasi Kärkkäinen wrote: > > lspci -vvv > > ???Pasi, > > Here''s the output in relation to the iLo. >Hmm.. The 01:04.0 device seems to have an I/O port, and the last one is called UART. So I''m wondering which one of those it is.. What does "dmesg | grep -i ttys" say in dom0? Does it detect a serial port? What''s the model of your server? "Integrated Lights-Out Virtual Serial Port configuration and operation HOWTO, 4th edition": http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00263709/c00263709.pdf "HP Integrated Lights-Out 2 User Guide": http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00553302/c00553302.pdf -- Pasi> Thanks, > James > > 01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out Controller (rev 03) > Subsystem: Hewlett-Packard Company Device 3305 > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin A routed to IRQ 21 > Region 0: I/O ports at 2800 [size=256] > Region 1: Memory at f5fe0000 (32-bit, non-prefetchable) [size=512] > Capabilities: [f0] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: hpwdt > Kernel modules: hpwdt > > 01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out Processor (rev 03) > Subsystem: Hewlett-Packard Company Device 3305 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 64, Cache Line Size: 64 bytes > Interrupt: pin B routed to IRQ 22 > BIST result: 00 > Region 0: I/O ports at 3400 [size=256] > Region 1: Memory at f5fd0000 (32-bit, non-prefetchable) [size=2K] > Region 2: Memory at f5fc0000 (32-bit, non-prefetchable) [size=16K] > Region 3: Memory at f5f00000 (32-bit, non-prefetchable) [size=512K] > [virtual] Expansion ROM at f5e20000 [disabled] [size=64K] > Capabilities: [f0] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: hpilo > Kernel modules: hpilo > > 01:04.4 USB Controller: Hewlett-Packard Company Proliant iLO2 virtual USB controller (prog-if 00 [UHCI]) > Subsystem: Hewlett-Packard Company Device 3305 > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 64 > Interrupt: pin B routed to IRQ 22 > Region 4: I/O ports at 3800 [size=32] > Capabilities: [f0] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: uhci_hcd > Kernel modules: uhci-hcd > > 01:04.6 IPMI SMIC interface: Hewlett-Packard Company Proliant iLO2 virtual UART (prog-if 01) > Subsystem: Hewlett-Packard Company Device 3305 > Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin A routed to IRQ 21 > Region 0: Memory at f5ef0000 (32-bit, non-prefetchable) [size=256] > Capabilities: [f0] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: ipmi_si > Kernel modules: ipmi_si > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 2010-01-22 at 09:51 +0200, Pasi Kärkkäinen wrote:> dmesg | grep -i ttys# dmesg | grep -i ttys serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A The server is a HP DL360-G6. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users