Discuss October 2011

discuss@lists.centos.org

186 participants
146 discussions

CentOS 6.0 i386 DVD
by William L. Maltby 18 Oct '11

18 Oct '11

Anybody have tricks to write the i386 ISO image to DVD? I've tried DVD+-RW, DVD+R, DVD-RW, DVD-R in both Windows 7 (two different writers) and rebooted into CentOS 6 (x86_64) and tried cdrecord (now called wodim). On wodim I've tried overburn, reducing speeds, etc. All give the same results: the same number of bytes are written - indicating the disc is full (according to my calculations) and wodim exits thinking it had a buffer underflow problem. I had no problem creating the x86_64 install DVD, which is smaller, and installing it next to my Windows. I just plug in a usb thumb drive and hit <ESC> when I want to run CentOS there and it works fine. The inability to create the i386 DVD initially prevented me from trying to install a desktop system on an old Acer running 4.8 (hasn't been booted in ... nearing a year?). I got around that by deciding to put the iso image on an external usb drive, exporting it via nfs and doing a network install. It had been so long since I dinked with any of this stuff it took me a couple of days of googling around, reading man pages, ... to get that working. Mostly having to do with iptables ports not being open. Sheesh! Black Hats create a lot of grief with their shenanigans! Anyway, then it panics when it starts writing the hard drives - I'll post another mail on that. Anyway, my life would've (will be) a bit simpler if someone can clue me in to how to get that image onto a DVD using either CentOS 6 or Windows. Checksums pass. Any hints gratefully accepted. TIA, Bill

3 4

Re: [CentOS] CentOS-6 install on 1 Tb drive fails
by James B. Byrne 17 Oct '11

17 Oct '11

On Mon, October 17, 2011 14:01, James B. Byrne wrote: > I am attempting to load CentOS-6 onto a ST31000524AS 1Tb > SATA drive in a Supermicro 5015A-EHF-D525 system. The > BIOS sees the drive and the CentOS install process sees > and initializes it as well. > > However, even when I accept the default partitioning, I > get an error during the drive formatting prior to > installing the OS. The error message is: "Could not > commit to disk /dev/sda". I get this error whether the > drive is configured as IDE or AHCI in BIOS. On Mon Oct 17 14:12:26 EDT 2011, m.roth at 5-cent.us m.roth at 5-cent.us wrote: > Have you tried putting the drive in another system > and see if it's recognized correctly? I have and the drive in question is formatted and CentOS-6 is successfully installed using the same media if I employ a different system to do the work. > Also, if you put the old drive back, does it work? Yes, I can boot the Supermicro system from a previously formatted 500Gb disc that already has CentOS-6 installed on it. Further, if I install the 1Tb disk, now formatted and with CentOS installed courtesy of the other host, then the Supermicro system also boots from it. > What I'm looking for is whether you have a hardware > problem, either m/b or drive... or controller card. It does not appear to me to be hardware related, at least not directly. I suspect a bug in Anaconda. There are reports of a similar issue in Fedora last year and the bug was supposed to have been fixed in June of 2010, if indeed my problem is the same thing or something related. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

CentOS-6 install on 1 Tb drive fails
by James B. Byrne 17 Oct '11

17 Oct '11

I am attempting to load CentOS-6 onto a ST31000524AS 1Tb SATA drive in a Supermicro 5015A-EHF-D525 system. The BIOS sees the drive and the CentOS install process sees and initializes it as well. However, even when I accept the default partitioning, I get an error during the drive formatting prior to installing the OS. The error message is: "Could not commit to disk /dev/sda". I get this error whether the drive is configured as IDE or AHCI in BIOS. The advanced BIOS configuration section makes reference to LBA addressing and a maximum value of 137 Gb. However, I had previously equipped this very system with a 500 GB SATA drive and had not experienced any problems. Does anyone have any idea as to what might be happening here?

2 1

L9 - what is a value
by Jussi Hirvi 17 Oct '11

17 Oct '11

This code: var('i') = string; boolean($i); '<br>'; var('i') = array; boolean($i); '<br>'; gives: > false > true So an empty array gives "true" but an empty string "false". This is different from L8. Is this intentional? If so, why? This has consequences which I think are counterintuitive: var('i') = array(1); if($i -> find('whatever')); i 'true'; '<br>'; $i -> find('whatever'); '<br>'; /if; The if clause evaluates as true and gives as output: true array() - Jussi

1 0

L9 - what is a value
by Jussi Hirvi 17 Oct '11

17 Oct '11

1 1

SELinux triggered during Libvirt snapshots
by Trey Dockendorf 17 Oct '11

17 Oct '11

I recently began getting periodic emails from SEalert that SELinux is preventing /usr/libexec/qemu-kvm "getattr" access from the directory I store all my virtual machines for KVM. All VMs are stored under /vmstore , which is it's own mount point, and every file and folder under /vmstore currently has the correct context that was set by doing the following: semanage fcontext -a -t virt_image_t "/vmstore(/.*)?" restorecon -R /vmstore So far I've noticed then when taking snapshots and also when using virsh to make changes to a domain's XML file. I haven't had any problems for the 3 or 4 months I've run this KVM server using SELinux on Enforcing, and so I'm not really sure what information is helpful to debug this. The server is CentOS 6 x86_64 updated to CR. This is the raw audit entry, (hostname removed) node=kvmhost.tld type=AVC msg=audit(1318634450.285:28): avc: denied { getattr } for pid=1842 comm="qemu-kvm" name="/" dev=dm-2 ino=2 scontext=system_u:system_r:svirt_t:s0:c772,c779 tcontext=system_u:object_r:fs_t:s0 tclass=filesystem node=kvmhost.tld type=SYSCALL msg=audit(1318634450.285:28): arch=c000003e syscall=138 success=no exit=-13 a0=9 a1=7fff1cf153f0 a2=0 a3=7fff1cf15170 items=0 ppid=1 pid=1842 auid=4294967295 uid=107 gid=107 euid=107 suid=107 fsuid=107 egid=107 sgid=107 fsgid=107 tty=(none) ses=4294967295 comm="qemu-kvm" exe="/usr/libexec/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c772,c779 key=(null) I've attached the alert email as a quote below, (hostname removed) Any help is greatly appreciated, I've had to deal little with SELinux fortunately, but at the moment am not really sure if my snapshots are actually functional or if this is just some false positive. Thanks - Trey Summary > > SELinux is preventing /usr/libexec/qemu-kvm "getattr" access on /vmstore. > > Detailed Description > > SELinux denied access requested by qemu-kvm. It is not expected that this >> access is required by qemu-kvm and this access may signal an intrusion >> attempt. It is also possible that the specific version or configuration of >> the application is causing it to require additional access. > > Allowing Access > > You can generate a local policy module to allow this access - see FAQ >> Please file a bug report. > > Additional Information > > Source Context: system_u:system_r:svirt_t:s0:c772,c779 > > Target Context: system_u:object_r:fs_t:s0 > > Target Objects: /vmstore [ filesystem ] > > Source: qemu-kvm > > Source Path: /usr/libexec/qemu-kvm > > Port: <Unknown> > > Host: kvmhost.tld > > Source RPM Packages: qemu-kvm-0.12.1.2-2.160.el6_1.8 > > Target RPM Packages: > > Policy RPM: selinux-policy-3.7.19-93.el6_1.7 > > Selinux Enabled: True > > Policy Type: targeted > > Enforcing Mode: Enforcing > > Plugin Name: catchall > > Host Name: kvmhost.tld > > Platform: Linux kvmhost.tld 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 >> 19:49:27 BST 2011 x86_64 x86_64 > > Alert Count: 1 > > First Seen: Fri Oct 14 18:20:50 2011 > > Last Seen: Fri Oct 14 18:20:50 2011 > > Local ID: c73c7440-06ee-4611-80ac-712207ef9aa6 > > Line Numbers: > > Raw Audit Messages : > > >> node=kvmhost.tld type=AVC msg=audit(1318634450.285:28): avc: denied { >> getattr } for pid=1842 comm="qemu-kvm" name="/" dev=dm-2 ino=2 >> scontext=system_u:system_r:svirt_t:s0:c772,c779 >> tcontext=system_u:object_r:fs_t:s0 tclass=filesystem > > node=kvmhost.tld type=SYSCALL msg=audit(1318634450.285:28): arch=c000003e >> syscall=138 success=no exit=-13 a0=9 a1=7fff1cf153f0 a2=0 a3=7fff1cf15170 >> items=0 ppid=1 pid=1842 auid=4294967295 uid=107 gid=107 euid=107 suid=107 >> fsuid=107 egid=107 sgid=107 fsgid=107 tty=(none) ses=4294967295 >> comm="qemu-kvm" exe="/usr/libexec/qemu-kvm" >> subj=system_u:system_r:svirt_t:s0:c772,c779 key=(null) > > >

2 1

What's up with the mailing list?
by TE Dukes 17 Oct '11

17 Oct '11

Are we running CentOS or what? That new kernel in cr repository won't boot!! I get kernel panic. This is getting out of hand. Know you are smarter than me when it come to this stuff, but please..........

6 9

CentOS 6.0: panic installing i386 on old Acer Desktop
by William L. Maltby 16 Oct '11

16 Oct '11

Well, after much trial and tribulation I got to the point I could nfs mount the CentOS 6.0 i386 iso image and try an install. So I stuck in the net install CD (latest from CentOS), mounted the nfs iso image and gave it several shots. It goes swimmingly until I click "write disks". Then there's a kernel panic. This with both the graphic and text mode installs. As mentioned, I've not yet researched/figured how I might capture this from my KVM. I've got some 5.x and 6.0 (with cr updates) and windows units available on my homegroannetwork LAN if there's a way to do it over a network. I've got some old serial cables (and various null modem ones and/or adapters) and Wyse-60 terminals but I don't even know yet if I can boot this with output to a serial port. I'll be checking that. If someone has figured out how to capture the output in my situation during initial system install, I'm all "ears". The system still boots the old CentOS 4.8 (first boots in around a ... year(?)) and I did dmidecode and a couple other short commnds that I hope is enough for someone to offer further direction or suggestions. Apologies for the size but it's been so long since I did any low-level stuff I was afraid I'd snip something important. I tried, based on *old* memories, adding kernel arguments of noapic and nolapic (IIRC). Still no joy. TIA for any thoughts, Bill Dmidecode output: # dmidecode 2.9 SMBIOS 2.3 present. 39 structures occupying 1094 bytes. Table at 0x000F0800. Handle 0x0000, DMI type 0, 20 bytes BIOS Information Vendor: Phoenix/Award Technologies, LTD Version: 6.00 PG Release Date: 11/04/2004 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 256 kB Characteristics: ISA is supported PCI is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/360 KB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 KB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported AGP is supported LS-120 boot is supported ATAPI Zip drive boot is supported Handle 0x0001, DMI type 1, 25 bytes System Information Manufacturer: VIA Technologies, Inc. Product Name: KT400-8235 Version: Serial Number: 12 UUID: 00000000-0000-0000-0000-000000000001 Wake-up Type: Power Switch Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: AOpen Product Name: AK77-8XN Version: 918A710301 Serial Number: I0500031JE13 Handle 0x0003, DMI type 3, 17 bytes Chassis Information Manufacturer: Type: Desktop Lock: Not Present Version: Serial Number: Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: Socket A Type: Central Processor Family: Duron Manufacturer: AMD ID: 81 06 00 00 FF F9 83 03 Signature: Family 6, Model 8, Stepping 1 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) Version: AMD Athlon(tm) XP Voltage: 1.6 V External Clock: 133 MHz Max Speed: 1500 MHz Current Speed: 1800 MHz Status: Populated, Enabled Upgrade: ZIF Socket L1 Cache Handle: 0x0009 L2 Cache Handle: 0x000A L3 Cache Handle: Not Provided Serial Number: Asset Tag: Part Number: Handle 0x0005, DMI type 5, 22 bytes Memory Controller Information Error Detecting Method: 8-bit Parity Error Correcting Capabilities: None Supported Interleave: One-way Interleave Current Interleave: Four-way Interleave Maximum Memory Module Size: 32 MB Maximum Total Memory Size: 96 MB Supported Speeds: 70 ns 60 ns Supported Memory Types: Standard EDO Memory Module Voltage: 5.0 V Associated Memory Slots: 3 0x0006 0x0007 0x0308 Enabled Error Correcting Capabilities: None Handle 0x0006, DMI type 6, 12 bytes Memory Module Information Socket Designation: A0 Bank Connections: 0 1 Current Speed: 60 ns Type: DIMM SDRAM Installed Size: 1024 MB (Double-bank Connection) Enabled Size: 1024 MB (Double-bank Connection) Error Status: OK Handle 0x0007, DMI type 6, 12 bytes Memory Module Information Socket Designation: A2 Bank Connections: None Current Speed: 60 ns Type: Unknown Installed Size: Not Installed Enabled Size: Not Installed Error Status: OK Handle 0x0008, DMI type 6, 12 bytes Memory Module Information Socket Designation: A4 Bank Connections: 4 5 Current Speed: 60 ns Type: DIMM SDRAM Installed Size: 1024 MB (Double-bank Connection) Enabled Size: 1024 MB (Double-bank Connection) Error Status: OK Handle 0x0009, DMI type 7, 19 bytes Cache Information Socket Designation: Internal Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 128 KB Maximum Size: 128 KB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x000A, DMI type 7, 19 bytes Cache Information Socket Designation: External Cache Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: External Installed Size: 256 KB Maximum Size: 256 KB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x000B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: PRIMARY IDE Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SECONDARY IDE Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: FDD Internal Connector Type: On Board Floppy External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: COM1 Internal Connector Type: 9 Pin Dual Inline (pin 10 cut) External Reference Designator: External Connector Type: DB-9 male Port Type: Serial Port 16450 Compatible Handle 0x000F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: COM2 Internal Connector Type: 9 Pin Dual Inline (pin 10 cut) External Reference Designator: External Connector Type: DB-9 male Port Type: Serial Port 16450 Compatible Handle 0x0010, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: LPT1 Internal Connector Type: DB-25 female External Reference Designator: External Connector Type: DB-25 female Port Type: Parallel Port ECP/EPP Handle 0x0011, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Keyboard Internal Connector Type: PS/2 External Reference Designator: External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x0012, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: PS/2 Mouse Internal Connector Type: PS/2 External Reference Designator: External Connector Type: PS/2 Port Type: Mouse Port Handle 0x0013, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Not Specified Internal Connector Type: None External Reference Designator: USB0 External Connector Type: Other Port Type: USB Handle 0x0014, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Not Specified Internal Connector Type: None External Reference Designator: AUDIO External Connector Type: None Port Type: Audio Port Handle 0x0015, DMI type 9, 13 bytes System Slot Information Designation: PCI0 Type: 32-bit PCI Current Usage: Available Length: Long ID: 1 Characteristics: 5.0 V is provided Modem ring resume is supported PME signal is supported Handle 0x0016, DMI type 9, 13 bytes System Slot Information Designation: PCI1 Type: 32-bit PCI Current Usage: Available Length: Long ID: 2 Characteristics: 5.0 V is provided Modem ring resume is supported PME signal is supported Handle 0x0017, DMI type 9, 13 bytes System Slot Information Designation: PCI2 Type: 32-bit PCI Current Usage: Available Length: Long ID: 3 Characteristics: 5.0 V is provided Modem ring resume is supported PME signal is supported Handle 0x0018, DMI type 9, 13 bytes System Slot Information Designation: PCI3 Type: 32-bit PCI Current Usage: Available Length: Long ID: 4 Characteristics: 5.0 V is provided Modem ring resume is supported PME signal is supported Handle 0x0019, DMI type 9, 13 bytes System Slot Information Designation: PCI4 Type: 32-bit PCI Current Usage: Available Length: Long ID: 5 Characteristics: 5.0 V is provided Modem ring resume is supported PME signal is supported Handle 0x001A, DMI type 9, 13 bytes System Slot Information Designation: PCI5 Type: 32-bit PCI Current Usage: Available Length: Long ID: 6 Characteristics: 5.0 V is provided Modem ring resume is supported PME signal is supported Handle 0x001B, DMI type 9, 13 bytes System Slot Information Designation: AGP Type: 32-bit AGP Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Handle 0x001C, DMI type 13, 22 bytes BIOS Language Information Installable Languages: 2 en|US|iso8859-1 de|DE|iso8859-1 Currently Installed Language: en|US|iso8859-1 Handle 0x001D, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 768 MB Error Information Handle: Not Provided Number Of Devices: 3 Handle 0x001E, DMI type 17, 27 bytes Memory Device Array Handle: 0x001D Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 1024 MB Form Factor: DIMM Set: None Locator: A0 Bank Locator: Bank0/1 Type: Unknown Type Detail: None Speed: Unknown Manufacturer: None Serial Number: None Asset Tag: None Part Number: None Handle 0x001F, DMI type 17, 27 bytes Memory Device Array Handle: 0x001D Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: A2 Bank Locator: Bank2/3 Type: Unknown Type Detail: None Speed: Unknown Manufacturer: None Serial Number: None Asset Tag: None Part Number: None Handle 0x0020, DMI type 17, 27 bytes Memory Device Array Handle: 0x001D Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 1024 MB Form Factor: DIMM Set: None Locator: A4 Bank Locator: Bank4/5 Type: Unknown Type Detail: None Speed: Unknown Manufacturer: None Serial Number: None Asset Tag: None Part Number: None Handle 0x0021, DMI type 19, 15 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0007FFFFFFF Range Size: 2 GB Physical Array Handle: 0x001D Partition Width: 0 Handle 0x0022, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0003FFFFFFF Range Size: 1 GB Physical Device Handle: 0x001E Memory Array Mapped Address Handle: 0x0021 Partition Row Position: 1 Handle 0x0023, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000000003FF Range Size: 1 kB Physical Device Handle: 0x001F Memory Array Mapped Address Handle: 0x0021 Partition Row Position: 1 Handle 0x0024, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00040000000 Ending Address: 0x0007FFFFFFF Range Size: 1 GB Physical Device Handle: 0x0020 Memory Array Mapped Address Handle: 0x0021 Partition Row Position: 1 Handle 0x0025, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x0026, DMI type 127, 4 bytes End Of Table Uname out from the current system on that unit - running just fine. Linux centos01.homegroannetwork 2.6.9-89.0.16.EL #1 Tue Nov 3 17:15:02 EST 2009 i686 athlon i386 GNU/Linux >From lsb_release: LSB Version: :core-3.0-ia32:core-3.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch Distributor ID: CentOS Description: CentOS release 4.8 (Final) Release: 4.8 Codename: Final

2 3

CentOS-announce Digest, Vol 80, Issue 5
by centos-announce-request＠centos.org 15 Oct '11

15 Oct '11

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2011:1371 Moderate CentOS 5 i386 pidgin Update (Johnny Hughes) 2. CESA-2011:1371 Moderate CentOS 5 x86_64 pidgin Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 14 Oct 2011 18:48:12 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2011:1371 Moderate CentOS 5 i386 pidgin Update To: centos-announce(a)centos.org Message-ID: <20111014184812.GA1139(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2011:1371 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-1371.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 68aa4c27b2ce7b196957996bc3c2fd9a finch-2.6.6-5.el5_7.1.i386.rpm 6bea1f0e815a187009118d674019f729 finch-devel-2.6.6-5.el5_7.1.i386.rpm df082c1b89437a44545ae4d915fd67d6 libpurple-2.6.6-5.el5_7.1.i386.rpm f354e2cf2d61de0f4380b94652183007 libpurple-devel-2.6.6-5.el5_7.1.i386.rpm e538e160f3aeb573b6ddbaaa85623b46 libpurple-perl-2.6.6-5.el5_7.1.i386.rpm 33605059786d99489c9e74fd1fe1f151 libpurple-tcl-2.6.6-5.el5_7.1.i386.rpm 40d37edf2265173d010236149adc9964 pidgin-2.6.6-5.el5_7.1.i386.rpm 3b1eb72b2efd7a0c7d0150061cd27228 pidgin-devel-2.6.6-5.el5_7.1.i386.rpm af0adf9d5de1554eccc9b7b5075ad19b pidgin-perl-2.6.6-5.el5_7.1.i386.rpm Source: d0ff3d538b8aac7564eea808ba69984a pidgin-2.6.6-5.el5_7.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Fri, 14 Oct 2011 18:48:12 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2011:1371 Moderate CentOS 5 x86_64 pidgin Update To: centos-announce(a)centos.org Message-ID: <20111014184812.GA1154(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2011:1371 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-1371.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 68aa4c27b2ce7b196957996bc3c2fd9a finch-2.6.6-5.el5_7.1.i386.rpm b018e574ff6557a17bf7e4c35073cb28 finch-2.6.6-5.el5_7.1.x86_64.rpm 6bea1f0e815a187009118d674019f729 finch-devel-2.6.6-5.el5_7.1.i386.rpm db1b0cdcadf719727d46b44d8851cfdc finch-devel-2.6.6-5.el5_7.1.x86_64.rpm df082c1b89437a44545ae4d915fd67d6 libpurple-2.6.6-5.el5_7.1.i386.rpm 15078426e82114e237c77bace2cfd93f libpurple-2.6.6-5.el5_7.1.x86_64.rpm f354e2cf2d61de0f4380b94652183007 libpurple-devel-2.6.6-5.el5_7.1.i386.rpm 13d65e6dc8b1656dcfcc581fad6928ae libpurple-devel-2.6.6-5.el5_7.1.x86_64.rpm 42e18860d93f317699746e828a7b7c6f libpurple-perl-2.6.6-5.el5_7.1.x86_64.rpm 0769b16822e4f1da0d84e68ffa2b23f5 libpurple-tcl-2.6.6-5.el5_7.1.x86_64.rpm 40d37edf2265173d010236149adc9964 pidgin-2.6.6-5.el5_7.1.i386.rpm 9d206eb8f1f9a55971e330ba33b9c93f pidgin-2.6.6-5.el5_7.1.x86_64.rpm 3b1eb72b2efd7a0c7d0150061cd27228 pidgin-devel-2.6.6-5.el5_7.1.i386.rpm 080a6a702d1fdd886590c0fea3b3a860 pidgin-devel-2.6.6-5.el5_7.1.x86_64.rpm 1ba9a1727e770dfe582d29f39ef12ac2 pidgin-perl-2.6.6-5.el5_7.1.x86_64.rpm Source: d0ff3d538b8aac7564eea808ba69984a pidgin-2.6.6-5.el5_7.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 80, Issue 5 **********************************************

1 0

Virtual host package, command line, I need help
by Bob Hoffman 15 Oct '11

15 Oct '11

I am at wits end with this KVM. It is hard to get the information needed to do this properly with centos 6 and KVM since it is so new and the googling of 'KVM' brings up everything except kernel based virtual machines. What I have done... 1) my cpus have virtualization 2) centos 6, selected 'virtual host' package 3) it goes to command line 4) I have made virtual guests with virt-install, in LVM folders, not images 5) 'cannot display' is all I get from command line The packages installed seem to have many gnome and vnc rpms. (and x-windows stuff too) Virt-manager was installed but only produces errors when run from command line I am unable to get anything past getting the guest running since I cannot open any kind of display. I have been able to easily do this in a gnome desktop, but figure command line is going to be less overhead for the server. I have added --vnc and tried some other things, but for the life of me I cannot figure out how to get a graphic or text install to come up on the local machine to save my life. With all the gnome packages (and there are quite a few) that were installed with the 'virtual host' package I figured something would come up, but all attempts have failed miserably. I am stuck in command line with no way out. I do plan on putting up a step by step video when I finally get one working, but after a few days of this (and seeing hundreds of websites with others having the same issue) I am wondering if anyone has ever got it working and what they did? This is just a pure install of centos 6, 'virtual host' package, command line, yum updated, able to make guests, no video options working for me. what is the magic command to bring up some of that gnome stuff for virt-manager or to just see the install window for a guest?? any help appreciated and most welcomed. Thanks.

8 15

← Newer
1
...
4
5
6
7
8
9
10
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2011