virt

virt@lists.centos.org

1608 discussions

Installing Ubuntu 10.04 Lucid guest on Centos 5 using virt-manager
by Dennis Jacobfeuerborn 19 Mar '12

19 Mar '12

Hi, i'm trying to install an Ubuntu Lucid PV guest on a Centos host but I can't seem to find a working installation URL. I tried "http://ftp.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/" and various subdirectories but I always get the error "Could not find an installable distributio at ...". In the OS Variant box I chose Ubuntu 9.04 as that is the closest to what I'm trying to install. Any idea how this works? Regards, Dennis

1 0

routing problem with domU bridged to two networks
by Peter Peltonen 16 Mar '12

16 Mar '12

As I received no response on the general CentOS list, I'll repost it here as the question is about Xen virtual machine routing. This is my network setup: http://pastebin.com/kyWpTQYU Lets assume my dom0's eth2 public ip is 1.2.3.33 and my dmz network 11.22.33.96/255.255.255.224 . I have created NAT from my LAN with iptables. You can see my /etc/sysconfig/iptables here: http://pastebin.com/1FqSTvPH And this is my dom0 routing table: http://pastebin.com/gNjTFHp5 My goal: To access NFS shares on a (non-virtualized) file server in the LAN network from the domU web server in the DMZ network. What I tried: I attached the domU to both bridges using this Xen config: vif = [ "mac=00:0c:29:de:3a:fe,bridge=xenbr0","mac=00:0C:29:76:19:85,bridge=xenbr1" ] and then created two eth interfaces inside the domU mapping to the MAC addresses above, giving eth1 an IP from the DMZ (11.22.33.111) and giving eth2 an IP from the LAN (192.168.0.12). After this I mounted the NFS share from the file server (192.168.0.2). My problem: If my domU web server is connected to both LAN and DMZ using the two bridges xenbr0 and xenbr1, I can access the NFS share from the domU web server and everything else works as expected, except for one thing -- my workstations in the LAN cannot anymore access the web server: web pages do not open anymore and from the workstations I cannot ping the domU. If the web server domU is only connected to DMZ via xenbr0, the workstations can access it ok. Any advice what I am doing wrong and I could fix my setup? Regards, Peter

2 3

IDE mapping to SATA in virtual guest
by Bradley Leonard 15 Mar '12

15 Mar '12

Hi, I'm trying to map a logical volume (sata) as an ide drive from my centos 6.2 host to my centos 6.2 guest. Here is xml snippet: <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/VolGroup02/LogVol00'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> Dmesg shows this: sd 0:0:0:0: [sda] 5859368960 512-byte logical blocks: (2.99 TB/2.72 TiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: unknown partition table sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg0 type 0 Inside the guest, it shows up as a sata drive: [root@nemedia ~]# sfdisk -l /dev/sda Disk /dev/sda: 364728 cylinders, 255 heads, 63 sectors/track sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type No partitions found [root@nemedia ~]# sfdisk -l /dev/hda /dev/hda: No such file or directory sfdisk: cannot open /dev/hda for reading I don't see how this would be a problem except for the fact that no matter what kind of filesystem I try to create on /dev/sda from the guest, I get errors when I try to mount it. No matter what I do, I cannot mount any filesystem from that device inside the guest. Both the cdrom and block device are showing up as scsi devices even though I'm passing them through as ide devices. Am I doing something wrong or am I missing something completely? I've try searching for solution or a hint, but I must not be searching for the right thing. Can anybody provide me some advice or point me somewhere? Thanks in advance. Brad -- Bradley Leonard EMail: bradley at stygianresearch.com Rob - "The hills are alive with the..the..sound of monkeys?" Bucky - "It's in the key of delicious." Life is simple. Humans make it complicated. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

KVM, VLAN and Bridges and bonding
by Baptiste AGASSE 03 Mar '12

03 Mar '12

Hi all, I use CentOS5.x + Xen in production for virtualization. I use it with bridged vlan networks and bonding (active-backup) like that: eth0 eth1 | | ------- | bond0-------bond0.10---------bond0.12 ... | | | | vlanbr10 vlanbr12 dom0 | | ------------- -------------- | | | | | | ... domU1 domU2 domU3 domU4 domU5 domU6 For future hypervisors, i want to implement the same things with CentOS6.x + KVM. In test env i've setup CentOS6.2 + KVM (with last updates) with the same network config, but guest lose network connection very often, and i don't know why. Network config: /etc/sysconfig/network-scripts/ifcfg-bond0.6: DEVICE=bond0.6 BRIDGE=vlanbr6 ONBOOT=yes BOOTPROTO=none VLAN=yes TYPE=Ethernet /etc/sysconfig/network-scripts/ifcfg-vlanbr6: DEVICE=vlanbr6 TYPE=Bridge ONBOOT=yes BOOTPROTO=none DELAY=0 I've installed guest like that (with a lot of retry because of network loss during installation) virt-install --name=guest02-c6 --disk path=/var/lib/libvirt/images/guest02-c6.img,size=10,sparse=false --graphics=spice,keymap=fr --vcpus=2 --ram=2048 --location=http://spacewalk.example.com/pub/dist/centos/6/x86_64/ --extra-args="ks=http://spacewalk.example.com/pub/ks/el6/guest02.el6.cfg ip=192.168.2.12 netmask=255.255.255.224 gateway=192.168.2.10 dns=192.168.2.10" --os-type=linux --os-variant=rhel6 --network=bridge:vlanbr6,model=virtio Someone have setup similar environment ? Regards. Baptiste.

2 1

Re: [CentOS-virt] Resize guest filesystem question
by Jeff Boyce 27 Feb '12

27 Feb '12

Responding to the daily digest, see comment at bottom. > Message: 1 > Date: Mon, 27 Feb 2012 14:01:27 +0100 > From: Markus Falb <markus.falb(a)fasel.at> > Subject: Re: [CentOS-virt] Resize guest filesystem question > To: centos-virt(a)centos.org > Message-ID: <jifur8$pmi$1(a)dough.gmane.org> > Content-Type: text/plain; charset="iso-8859-1" > > On 24.2.2012 21:28, Sergiy Yegorov wrote: >> Fri, 24-Feb-2012 12:05:55 Jeff Boyce wrote: >> >>> 6. Then I ran resize2fs /dev/vda2 and got the result that the >>> filesystem >>> is already xx blocks long. Nothing to do! >> Before you can resize filesystem, you have to resize partition. >> If it is only 2 partitions on /dev/vda, you can use one of two ways: >> 1. Resize partition from host system (I think it is not the best idea for >> root >> partition operations): >> Run fdisk /dev/vg/lv_guest1root, delete second partition and create new >> one >> which starts from the same place but takes all available space, after it >> you >> can boot guest (in single mode) and run resize2fs. >> 2. Boot VM from any 3-party (LiveCD or any) with access to virtual disk, >> and >> do the same: in fdisk delete existing partition, create new one and run >> resize2fs on it. Or just use parted to do it in one command. > > 3. You can repartition from the guest itself > Do as in 2. After saving the new partition table fdisk will probably > request a reboot for using the new table. reboot, then resize the fs. > > -- > Kind Regards, Markus Falb > Thanks to everyone that replied. Ed gave me the right clue that I was missing (and is apparently missing in a lot of the how-to's that I reviewed which only said to expand the LV, then expand the filesystem). I had to expand the partition before expanding the filesystem. So for my solution I rebooted that particular VM using SystemRescue LiveCD, then started GParted and expanded the partition which also expanded the filesystem in a single step. Then rebooted using the VM's image and #df -h now shows the expanded LV and a file system on the full space. Jeff

2 1

Resize guest filesystem question
by Jeff Boyce 27 Feb '12

27 Feb '12

Greetings - I am going through some testing steps to expand a logical volume and the corresponding filesystem on a KVM guest and have run across a deficiency in my knowledge. I spent the afternoon yesterday googling for answers, but had have come up blank still. What I am trying to do is resize the file system to use the additional disk space that I added to the logical volume that the guest uses. Here is what I have done and the details of my system. 0. Both my host and guest are running Centos 6.2. 1. My KVM host system has the LVM volume group that is divided into logical volumes which are then presented to the KVM guests as raw space. 2. A guest may use 2 or 3 logical volumes from the host system for its filesystem (/, /var, /data) and I have logical volumes named within the host system by guest and mount point so that I know what each logical volume is assigned to by it's name. 3. I expanded a specific logical volume on the host (/dev/vg/lv_guest1root) that is used by Guest1, and I can see in vgdisplay and lvdisplay that the logical volume was properly expanded. 4. I then issued a resize2fs /dev/vg/lv_guest1root command (on the host) to resize the filesystem to the expanded logical volume. This resulted in a message that it essentially couldn't find a valid filesystem superblock. Well of course then I realized that there is no filesystem on the logical volume from the perspective of the host. The filesystem wasn't set on the logical volume until the guest installation occurred. 5. So then I switched over to the guest system and ran df -h to see the existing filesystem [root@guest1 jeffb]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda2 4.5G 2.3G 2.0G 53% / tmpfs 1004M 88K 1004M 1% /dev/shm /dev/vda1 485M 30M 430M 7% /boot /dev/vdb1 2.0G 219M 1.7G 12% /var 6. Then I ran resize2fs /dev/vda2 and got the result that the filesystem is already xx blocks long. Nothing to do! So here is where I am stuck. Guest1 is my test system so it only has the / and /var logical volumes, whereas the production guest (guest2) that I will be expanding also has /data, which will be the logical volume that I will expand. So two things I did not do where, I did not shut down the guest VM, and I did not unmount the filesystem before asking it to resize. However my research before doing this did not seem to indicate that I had to do either, and the message about nothing to do also seems to indicate that they were not necessary. So I am missing a hole in my knowledge and additional googling has not helped to fill it. I must be missing something simple. Is this result due to the fact that I am testing on expanding the / filesystem, and it would work properly on a guest system that had /data? Do I need to unmount the filesystem, or shut down the guest VM, or mount the guest from a LiveCD? Or do I need to give it resize2fs /dev/vda rather than specifically /dev/vda2 ? Any clues, or pointers to good documentation is greatly appreciated. Thanks. Jeff Boyce Meridian Environmental www.meridianenv.com

4 4

Re: [CentOS-virt] How many virtual guest 'cpus' can a core duo 'quad' core support
by James B. Byrne 25 Feb '12

25 Feb '12

On Wed, February 22, 2012 12:25, Todd And Margo Chester > > Therefore, in your given case, think six not twelve. > Common advice is > to leave > one core for the host OS/scheduler. Which leaves you with > 5 physical > CPUs to > allocate. > Thank you. I never planned to allocate to any guest more cpus that were physically available. What I was checking was that a single physical cpu with four cores actually counted as four cpus insofar as kvm itself was concerned. I have allocated guests their processors on the basis that 1 core = 1 cpu. But it occurred to me that core might actually mean something different and so I wanted to verify my understanding. -- *** 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

SELinux killed my qemu-kvm
by David McGuffey 24 Feb '12

24 Feb '12

All of a sudden, Virtual Machine Manager (VMM) on a CentOS 5.7 load will no longer run any VMs. The VM worked A-OK on the morning of 23 Feb, when I brought it up, applied the Microsoft updates, rebooted it, installed an application, rebooted again and ran several tests. Later that day, it wouldn't run. I didn't have time to diagnose, so I did some investigation a few minutes ago. Working my way through some checks, it appears to be an SELinux problem (new). [root@desk log]# uname -r 2.6.18-274.18.1.el5 >From /var/log/yum.log: Feb 21 19:07:01 Updated: 2:libpng-1.2.10-15.el5_7.x86_64 Feb 21 19:07:01 Updated: 2:libpng-devel-1.2.10-15.el5_7.x86_64 Feb 21 19:07:01 Updated: 2:libpng-1.2.10-15.el5_7.i386 Previous yum update ran on 19 Feb. However, the virtual machine ran very well on the morning of 23 Feb, when I brought it up, so it can't be any updates from yum on the host. Here is the VMM Error Message: Error starting domain: internal error Process exited while reading console log output: qemu: could not open disk image /dev/hda And the VMM Details: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 501, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 576, in startup self.vm.create() File "/usr/lib64/python2.4/site-packages/libvirt.py", line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Process exited while reading console log output: qemu: could not open disk image /dev/hda Excerpt from /var/log/messages: Feb 24 17:25:28 desk libvirtd: 17:25:28.531: error : virDomainDiskDefForeachPath:7637 : unable to open disk path /dev/hda: No medium found Feb 24 17:25:28 desk kernel: tun: Universal TUN/TAP device driver, 1.6 Feb 24 17:25:28 desk kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk(a)qualcomm.com> Feb 24 17:25:28 desk kernel: device vnet0 entered promiscuous mode Feb 24 17:25:28 desk kernel: New device vnet0 does not support netpoll Feb 24 17:25:28 desk kernel: Disabling netpoll for virbr0 Feb 24 17:25:28 desk kernel: virbr0: topology change detected, propagating Feb 24 17:25:28 desk kernel: virbr0: port 1(vnet0) entering forwarding state Feb 24 17:25:28 desk kernel: virbr0: port 1(vnet0) entering disabled state Feb 24 17:25:28 desk kernel: virbr0: port 1(vnet0) entering disabled state Feb 24 17:25:28 desk kernel: device vnet0 left promiscuous mode Feb 24 17:25:28 desk kernel: virbr0: port 1(vnet0) entering disabled state Feb 24 17:25:28 desk setroubleshoot: SELinux is preventing pam_console_app (pam_console_t) "getattr" to /dev/hda (virt_content_t). For complete SELinux messages. run sealert -l 9ee6c9a9-3eda-4082-84d3-5741ea9ff688 SELinux alert summary SELinux is preventing pam_console_app (pam_console_t) "getattr" to /dev/hda (virt_content_t). Detailed Description: SELinux denied access requested by pam_console_app. It is not expected that this access is required by pam_console_app 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: Sometimes labeling problems can cause SELinux denials. You could try to restore the default system file context for /dev/hda, restorecon -v '/dev/hda' If this does not work, there is currently no automatic way to allow this access. Instead, you can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Or you can disable SELinux protection altogether. Disabling SELinux protection is not recommended. Please file a bug report (http://bugzilla.redhat.com/bugzilla/enter_bug.cgi) against this package. Additional Information: Source Context system_u:system_r:pam_console_t:SystemLow- SystemHigh Target Context system_u:object_r:virt_content_t Target Objects /dev/hda [ blk_file ] Source pam_console_app Source Path /sbin/pam_console_apply Port <Unknown> Host desk.mcguffeyfamily.net Source RPM Packages internallab pam-0.99.6.2-6.el5_5.2 Target RPM Packages Policy RPM selinux-policy-2.4.6-316.el5_7.1 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Enforcing Plugin Name catchall_file Host Name desk.mcguffeyfamily.net Platform Linux desk.mcguffeyfamily.net 2.6.18-274.18.1.el5 #1 SMP Thu Feb 9 12:45:44 EST 2012 x86_64 x86_64 Alert Count 163 First Seen Wed 13 Apr 2011 08:41:32 AM EDT Last Seen Fri 24 Feb 2012 05:25:28 PM EST Local ID 9ee6c9a9-3eda-4082-84d3-5741ea9ff688 Line Numbers Raw Audit Messages host=desk.internallab.net type=AVC msg=audit(1330122328.766:39): avc: denied { getattr } for pid=3427 comm="pam_console_app" path="/dev/hda" dev=tmpfs ino=6316 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c1023 tcontext=system_u:object_r:virt_content_t:s0 tclass=blk_file host=desk.internallab.net type=SYSCALL msg=audit(1330122328.766:39): arch=c000003e syscall=4 success=no exit=-13 a0=7fff56fe6140 a1=7fff56fe6170 a2=7fff56fe6170 a3=c5df105 items=0 ppid=3417 pid=3427 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="pam_console_app" exe="/sbin/pam_console_apply" subj=system_u:system_r:pam_console_t:s0-s0:c0.c1023 key=(null) I did a touch /.autorelabel; sync; reboot and received the same error message. I then followed the guidance in the sealert: [root@desk log]# restorecon -v /dev/hda restorecon reset /dev/hda context system_u:object_r:virt_content_t:s0->system_u:object_r:fixed_disk_device_t:s0 And tried to start the VM with no success: [root@desk images]# virsh start Win7-base error: Failed to start domain Win7-base error: internal error Process exited while reading console log output: qemu: could not open disk image /dev/hda Any thoughts? Dave

1 0

new libvirt: CentOS 6.2 versus 6.0
by Dmitry E. Mikhailov 23 Feb '12

23 Feb '12

Hi, About half a year ago I installed a stock CentOS 6.0/64bit onto an Intel server to virtualize our Linux fileserver and four WinXP boxes with rdp each. Since recent times I didn't do any upgrades of the server's OS. Now I have CentOS 6.2. After an upgrade I noticed that all virtual cpu name changed to QEMU Virtual CPU version (cpu64-rhel6) The new features were 1) The ability to specify cpu type and even exact capabilities 2) The ability to set the topology. It's good because before this ability appears WinXP guests won't use more than two cores. I got problem with both of these features. First, I can't manually specify cpu type 'qemu64' - virtmanager says my physical CPU doesn't have some abilities. But if no CPU is specified, it is reported as 64bit Second, a killer app on one of WinXP servers stopped working since upgrade. It's a russian proprietary accounting app named 1C ver. 8.1 (1cv8.exe). It would just hang loading single virtual CPU to 100%. I traced by trial-and-error that the problem is related to virtual CPU identification. Following solution would help: <cpu match='exact'> <model>Penryn</model> <vendor>Intel</vendor> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='monitor'/> <feature policy='require' name='ds'/> <feature policy='require' name='ss'/> <feature policy='require' name='vme'/> <feature policy='require' name='ht'/> <feature policy='require' name='dca'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> <feature policy='disable' name='nx'/> <feature policy='disable' name='pae'/> </cpu> It wasn't working before I disabled PAE and NX. Double checked. If I delete <cpu> part and thus leave it 'default', the application won't work. Third, initially I couldn't use more than two cores with single instance of WinXP because every core was identified as a whole CPU and WinXP is limited to two CPU's. So the idea is to allocate 4 cores and specify topology as 2 cpu, 2 cores, 1 thead. But if I specify ANY cpu topology manually, WinXP uses 100% of all physical CPU cores assigned to them even if guest OS's load is zero. By the way, I got this behaviour from the very beginning if ACPI was turned off for guest OS (which was default). So I rolled back to NOT specifying CPU topology and allocating only two cores to WinXP. Bad... BUT it started working properly after I did the aforementioned 'optimisation' for tnat WinXP instance. Now I have it with 4 cores assigned. Mystery! Help me please, what did I do wrong way? Best regards, Dmitry Mikhailov Server configuration: 2x Intel(R) Xeon(R) CPU E5420 @ 2.50GHz 2x 2GB DDR-II FBDIMM Intel motherboard with 5000P Chipset Server's Mission: virtualization host system. Virtualized OS's: 1xFile server on CentOS 5.5/32bit 4xWinXP machines for rdesktop each. Software versions: Before: The kernel was 2.6.32-71.el6.x86_64 I'm sorry I don't have any data on software versions before upgrade. But it was stock CentOS 6.0. I didn't use CR. After: kernel-2.6.32-220.4.1.el6.x86_64 libvirt-0.9.4-23.el6_2.4.x86_64 qemu-kvm-0.12.1.2-2.209.el6_2.4.x86_64

2 1

How many virtual guest 'cpus' can a core duo 'quad' core support
by James B. Byrne 22 Feb '12

22 Feb '12

CentOS-6.2 What is the maximum number of cpus can I configure for a single vm guest running on a host with this hardware? # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 CPU socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 23 Stepping: 10 CPU MHz: 1998.000 BogoMIPS: 5331.76 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 2048K NUMA node0 CPU(s): 0-3 I ask this because it occurs to me that I may have missed something fundamental respecting the use of the initialism CPU vice the term Cores. -- *** 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

5 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt