virt

virt@lists.centos.org

2 participants
1613 discussions

Matthias Lorch ist außer Haus.
by matthias.lorch＠kzvrlp.de 10 Aug '10

10 Aug '10

Ich werde ab 09.08.2010 nicht im Büro sein. Ich kehre zurück am 30.08.2010. Bitte wenden Sie sich in dringenden Fällen an Herrn Roth, 0261 / 9120 - 258 Vielen Dank Gruß M.Lorch

1 0

CentOS, Xen and VLANs
by Jared Ravetch 10 Aug '10

10 Aug '10

I ran into an issue when trying to create VMs in CentOS 5.5 with VLANs. My setup is as follows: -CentOS 5.5 x64 xen kernel -LVM for storage -Kickstart file hosted on apache in /var/www/html/ -VM start file in /etc/xen/ -VLAN100 interface with public IP, VLAN200 interface with private IP My vm start file is as follows: kernel = "/boot/vm-inst/vmlinuz" ramdisk = "/boot/vm-inst/initrd.img" name = "vm1-inst" memory = 1000 disk = [ 'phy:/dev/VolGroup01/vm01,xvda,w', ] vif = ['bridge=virbr0', ] vcpus = 1 ip = '172.16.1.100' netmask = '255.255.255.0' gateway = '172.16.1.1' extra = "text ks=http://172.16.1.155/vm-inst1-ks.cfg ip=172.16.1.100 netmask=255.255.255.0 gateway=172.16.1.1 dns=172.16.1.200" To start the install I run: xm create -c vm1-inst The CentOS installer finds the kernel and ramdisk files, configures the IP, then hangs for a while until it states it cannot find the kickstart file. I have to then have to exit the console and shutdown the vm To remove any issues with the kickstart file, I tried just using vm-install --prompt to create the VM and pointing to a FTP site with the install files. The CentOS installer starts, I configure the IP using a static IP, but then the it complains it cannot find any files in the FTP site. Finally, I tried using the CentOS DVD ISO as the install media for the VM. The installer starts, but then complains it does not have the drivers to load the media. I googled and found this is a limitation of CentOS when creating VMs. Has anyone had experience getting the installer over VLANs to work with a network install? Is there another way around this issue? Thanks and Regards, Jared

1 0

working config for xen which would transfer a serial interface
by Manuel Wolfshant 06 Aug '10

06 Aug '10

Hello Can anyone share a known working config for xen which would transfer a serial interface ( add-on card preferably, mine uses e880-e887 : 0000:03:05.0 / ec00-ec07 : 0000:03:05.0 ) to a DomU ? I've been trying with the stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial interface from DomU. No matter what we've tried, - in DomU there is no reference to any kind of serial ports in /proc/{interrupts,ioports} - the test program which accesses ttyS0 fails ( it works just fine in dom0) even after manually loading parport_serial in DomU /dev/ttyS{0..3} do get created by default, if that matters. Here is the content of the config file, after the last attempt (which uses gitco's xen, but we failed similarly with the stock packages): name = "testr" uuid = "57baf51a-e293-fa35-9f2e-056a1c0e322a" maxmem = 512 memory = 512 vcpus = 1 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "tap:aio:/var/lib/xen/images/testr,xvda,w" ] vif = [ "mac=00:16:36:0c:aa:1a,bridge=xenbr0,script=vif-bridge" ] irq = [11 ] ioports = [ "ec00-ec07","e080-e08f" ] // we also tried to pass all the IO ports referenced in lspci -vvv [root@Dom0]#lspci -vvv 03:05.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01) Subsystem: LSI Logic / Symbios Logic 1P2S Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at ec00 [size=8] Region 1: I/O ports at e880 [size=8] Region 2: I/O ports at e800 [size=8] Region 3: I/O ports at e480 [size=8] Region 4: I/O ports at e400 [size=8] Region 5: I/O ports at e080 [size=16] [root@Dom0 ~]# dmesg | grep ttyS [root@Dom0 ~]# cat /etc/modprobe.d/blacklist #[...] blacklist 8250 blacklist 8250_pnp blacklist serial_core blacklist parport_serial blacklist 8250_pci [root@Dom0 ~]# grep xen /etc/grub.conf title CentOS (2.6.18-194.el5xen) kernel /xen.gz-3.4.3 module /vmlinuz-2.6.18-194.el5xen ro root=/dev/VolGroup00/LogVol00 module /initrd-2.6.18-194.el5xen.img title CentOS (2.6.18-194.8.1.el5xen) kernel /xen.gz-3.4.3 module /vmlinuz-2.6.18-194.8.1.el5xen ro root=/dev/VolGroup00/LogVol00 xencons=off module /initrd-2.6.18-194.8.1.el5xen.img [root@Dom0 ~]# uname -a Linux Dom0 3 2.6.18-194.8.1.el5xen #1 SMP Thu Jul 1 19:41:05 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux sniff from the boot messages in tge DomU: XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/ioports/0 XENBUS: Device with no driver: device/ioports/1 XENBUS: Device with no driver: device/ioports/2 XENBUS: Device with no driver: device/ioports/3 XENBUS: Device with no driver: device/ioports/4 XENBUS: Device with no driver: device/ioports/5 XENBUS: Device with no driver: device/irq/0 XENBUS: Device with no driver: device/console/0 [root@DomU ~]# cat /proc/interrupts CPU0 256: 7433 Dynamic-irq timer0 257: 0 Dynamic-irq resched0 258: 0 Dynamic-irq callfunc0 259: 554 Dynamic-irq xenbus 260: 705 Dynamic-irq xencons 261: 802 Dynamic-irq xenfb 262: 0 Dynamic-irq xenkbd 263: 6607 Dynamic-irq blkif 264: 8959 Dynamic-irq eth0 NMI: 0 LOC: 0 ERR: 0 MIS: 0 [root@DomU ~]# cat /proc/ioports 0000-001f : dma1 0020-0021 : pic1 0040-0043 : timer0 0050-0053 : timer1 0060-0060 : keyboard 0064-0064 : keyboard 0080-008f : dma page reg 00a0-00a1 : pic2 00c0-00df : dma2 00f0-00ff : fpu [root@DomU ~]# lsmod Module Size Used by 8250_pnp 43969 0 parport_serial 41153 0 8250_pci 56257 1 parport_serial 8250 86057 2 8250_pnp,8250_pci serial_core 56385 1 8250 [...] [root@DomU ~]# uname -a Linux DomU 2.6.18-194.8.1.el5xen #1 SMP Thu Jul 1 19:41:05 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux TIA manuel

2 5

Re: [CentOS-virt] Arp Flip Flops make machine inaccessible.
by chaim.rieger＠gmail.com 01 Aug '10

01 Aug '10

Comment out the mac addy from eth1 and try that Sent via BlackBerry from T-Mobile

2 1

Arp Flip Flops make machine inaccessible.
by Ben M. 01 Aug '10

01 Aug '10

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the traffic pinned to the physical ethXs by their Xen bridge assignation. Segregate traffic. Current working setup: # ifcfg-eth0 # nVidia Corporation MCP55 Ethernet DEVICE=eth0 BOOTPROTO=none #BROADCAST=10.255.255.255 #HWADDR=00:e0:81:d2:0b:36 IPADDR=10.0.0.50 #NETMASK=255.255.255.0 #NETWORK=10.0.0.0 ONBOOT=yes GATEWAY=10.0.0.1 TYPE=Ethernet #ARP=yes IPV6INIT=no #ifcfg-eth1 # nVidia Corporation MCP55 Ethernet DEVICE=eth1 BOOTPROTO=dhcp ONBOOT=yes HWADDR=00:e0:81:d2:0b:37 [root@localdomain ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:E0:81:D2:0B:36 inet addr:10.0.0.50 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::2e0:81ff:fed2:b36/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:17853 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1249977 (1.1 MiB) TX bytes:8043 (7.8 KiB) eth1 Link encap:Ethernet HWaddr 00:E0:81:D2:0B:37 inet addr:10.255.252.22 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::2e0:81ff:fed2:b37/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8631 errors:0 dropped:0 overruns:0 frame:0 TX packets:13361 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:657672 (642.2 KiB) TX bytes:6476669 (6.1 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18946 errors:0 dropped:0 overruns:0 frame:0 TX packets:18946 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7802726 (7.4 MiB) TX bytes:7802726 (7.4 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:17887 errors:0 dropped:0 overruns:0 frame:0 TX packets:137 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1253769 (1.1 MiB) TX bytes:11507 (11.2 KiB) Interrupt:252 Base address:0xa000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:363575 errors:0 dropped:0 overruns:0 frame:0 TX packets:161997 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:500789617 (477.5 MiB) TX bytes:17282884 (16.4 MiB) Interrupt:251 Base address:0xc000 sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) tap0 Link encap:Ethernet HWaddr 76:A2:E4:74:CD:79 inet6 addr: fe80::74a2:e4ff:fe74:cd79/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2652 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:449235 (438.7 KiB) tap1 Link encap:Ethernet HWaddr AA:BB:F6:55:59:5E inet6 addr: fe80::a8bb:f6ff:fe55:595e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:8862 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:60 (60.0 b) TX bytes:878033 (857.4 KiB) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:100 errors:0 dropped:0 overruns:0 frame:0 TX packets:17853 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8043 (7.8 KiB) TX bytes:1249977 (1.1 MiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:13361 errors:0 dropped:0 overruns:0 frame:0 TX packets:8631 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6476669 (6.1 MiB) TX bytes:657672 (642.2 KiB) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:63 errors:0 dropped:0 overruns:0 frame:0 TX packets:8730 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:6847 (6.6 KiB) TX bytes:866585 (846.2 KiB) vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:179 errors:0 dropped:0 overruns:0 frame:0 TX packets:8627 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:15806 (15.4 KiB) TX bytes:857989 (837.8 KiB) vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:148068 errors:0 dropped:0 overruns:0 frame:0 TX packets:357556 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:6980701 (6.6 MiB) TX bytes:500418149 (477.2 MiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) virbr1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1506 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:163593 (159.7 KiB) TX bytes:0 (0.0 b) xenbr1 Link encap:Ethernet HWaddr 76:A2:E4:74:CD:79 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1503 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:161739 (157.9 KiB) TX bytes:0 (0.0 b) [root@river50 ~]# brctl show bridge name bridge id STP enabled interfaces virbr0 8000.000000000000 yes virbr1 8000.000000000000 yes xenbr0 8000.feffffffffff no peth0 vif0.0 xenbr1 8000.76a2e474cd79 no vif4.0 tap0 vif3.0 tap1 vif1.0 peth1 vif0.1 REPLACED in xend-config.sxp # (network-script network-bridge) (network-script my-network-bridge) file: my-network-bridge [root@localdomain ~]# cat /etc/xen/scripts/my-network-bridge #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 IPTABLES (not modified by any action by me) [root@localdomain ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere private.ip-address.localhost/24 state RELATED,ESTABLISHED ACCEPT all -- private.ip-address.localhost/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable ACCEPT all -- anywhere private.ip-address.localhost/24 state RELATED,ESTABLISHED ACCEPT all -- private.ip-address.localhost/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable RH-Firewall-1-INPUT all -- anywhere anywhere ACCEPT all -- private.ip-address.localhost anywhere PHYSDEV match --physdev-in vif1.0 ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.0 udp spt:bootpc dpt:bootps ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif3.0 ACCEPT all -- private.ip-address.localhost anywhere PHYSDEV match --physdev-in vif4.0 ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif4.0 udp spt:bootpc dpt:bootps Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT esp -- anywhere anywhere ACCEPT ah -- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT tcp -- anywhere anywhere tcp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:5901 ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:smtp REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

1 0

which virtualization platform to choose
by Gilberto Nunes 28 Jul '10

28 Jul '10

Friends I'm in doubt here: which virtualization platform to choose and why? If I have just installed a VM I choose Xen or KVM? And when I have more than 5 or 10 VM's? Please, I need your help to choose right. Thanks -- Gilberto Nunes

7 14

Virt-install Error on Centos 5.4 64bit and kvm
by cris rock 28 Jul '10

28 Jul '10

Hi guys, I hope you can help me on this issue with kvm/libvirt: using this command to install a kvm virtual machine: virt-install --connect qemu:///system \ --name p3k0401 \ --ram 2048 \ --file //dev/VolGroup01/p3k0401logvol \ --accelerate \ -s 10 \ --nographics \ --hvm \ --location='http://10.1.4.80' I get: Starting install... Retrieving file vmlinuz... | 1.8 MB 00:00 Retrieving file initrd.img... | 7.1 MB 00:00 ERROR internal error Domain p3k0401 didn't show up Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start p3k0401'; otherwise, please restart your installation. ERROR internal error Domain p3k0401 didn't show up Traceback (most recent call last): File "/usr/sbin/virt-install", line 889, in ? main() File "/usr/sbin/virt-install", line 751, in main start_time, guest.start_install) File "/usr/sbin/virt-install", line 813, in do_install dom = install_func(conscb, progresscb, wait=(not wait)) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error Domain p3k0401 didn't show up On the /var/log/libvirt/qemu/p3k0401.log: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/ /usr/bin/qemu-system-x86_64 -S -M rhel5.4.0 -m 1024 -smp 1 -name p3k0401 -uuid 7658c102-0738-724c-40eb-e1c58b2c2369 -domid 3 -nographic -monitor pty -pidfile /var/run/libvirt/qemu//p3k0401.pid -no-reboot -boot c -kernel /var/lib/libvirt/boot/virtinst-vmlinuz.O_SOVo -initrd /var/lib/libvirt/boot/virtinst-initrd.img.0ba0Fp -append method=http://10.1.4.80 -drive file=//dev/VolGroup01/p3k0401logvol,if=ide,index=0,cache=none -net nic,macaddr=54:52:00:15:c4:50,vlan=0 -net tap,fd=16,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb Supported machines are: pc Standard PC (alias of pc-0.12) pc-0.12 Standard PC (default) pc-0.11 Standard PC, qemu 0.11 pc-0.10 Standard PC, qemu 0.10 isapc ISA-only PC xenpv Xen Para-virtualized PC And my packages installed: # rpm -qa | grep qemu qemu-0.12.4-1.el5.rf # rpm -qa | grep kvm etherboot-zroms-kvm-5.4.4-13.el5.centos kmod-kvm-83-164.el5_5.12 kvm-83-164.el5_5.12 # rpm -qa | grep libvirt libvirt-0.6.3-33.el5_5.1 libvirt-0.6.3-33.el5_5.1 libvirt-python-0.6.3-33.el5_5.1 # uname -a Linux gs1p304 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Please any pointer is appreciated... thanks! cris _________________________________________________________________ Hotmail: Free, trusted and rich email service. https://signup.live.com/signup.aspx?id=60969

4 3

Power Management and dom0 cpus
by Ben M. 27 Jul '10

27 Jul '10

["Standard" CentOS 5.5 Xen Virtualization installation.] I'm setting up a new box on AMD Opteron platform. I'm doing some preliminary baselines (no domUs running) with an inline Watt/VA meter. It appears to enable full power management Xen dom0 must have all cpus by not limiting in kernel statement nor in xendconfig.sxp. In previous installations I cut them back to 1 or 2. The bonus of all cpus appears to be a 16% to 20% reduction in wattage/va consumption at idle. Pretty substantial when I consider that my electric utility rates have increased 75% (yep) in the past two years alone. My question is to anyone with experience with this is will I be seeing a significant performance hit on domU performance in either paravirtualized or fully virtualized guests (or both)?

1 0

Vmware to KVM - possible?
by Matt Keating 27 Jul '10

27 Jul '10

Is it possible to convert a VMWare image to KVM? As I have been building a few test machines on Vmware Fusion and would like to migrate some to a KVM server. Thanks in advance. Matt Keating Linux System Admin Dennis Interactive 30 Cleveland St, London, W1T 4JD Tel: 020 7907 6823 (direct line) Fax: 020 7907 6600 (fax) P Please consider the environment before printing this e-mail NOTE: The information in this email is confidential and may be legally privileged, unless stated to the contrary. If you are not the intended recipient, you must not read, use or disseminate that information. Any opinions or comments are personal to the writer and do not represent the official view of Dennis Publishing Ltd. If you have received this email and are not a named addressee, please contact itdirector(a)dennis.co.uk immediately by reply email and then delete this message from your system. Please do not copy it or use it for any purpose, or disclose its contents to any other person. Although this email and any attachments are believed to be free of any virus, or other defects, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Dennis Publishing Ltd for any loss or damage arising from the receipt or use thereof. Company registered in England No. 1138891 Registered office: 30, Cleveland Street, London, W1T 4JD

4 5

SOLVED: Re: CentOS 5.4 KVM: PXE boot problem
by Momonth 26 Jul '10

26 Jul '10

Having installed the following packages the problem was solved: kernel-2.6.18-194.8.1.el5 kvm-83-164.el5 kmod-kvm-83-164.el5 etherboot-roms-kvm-5.4.4-13.el5.centos etherboot-zroms-kvm-5.4.4-13.el5.centos Cheers, Vladimir 2010/7/19 Momonth <momonth(a)gmail.com>: > Hi All, > > I'm playing with KVM in order to adopt the technology for dev / > testing purposes. Installing RHEL5 from ISO images works ok, no > problems with installation. > > The problem occurs with PXE boot - it is simply doesn't try to do PXE > boot, according to what I can see: > > Booting from Hard Disk... > Boot from Hard Disk failed: not a bootable disk > FATAL: No bootable device. > _ > > I have: > > CentOS release 5.4 (Final) , 2.6.18-194.8.1.el5 x86_64 kernel > > libvirt-0.3.3-7.el5 > etherboot-roms-kvm-5.4.4-13.el5.centos > libvirt-python-0.3.3-7.el5 > etherboot-pxes-5.4.4-13.el5.centos > etherboot-zroms-5.4.4-13.el5.centos > etherboot-roms-5.4.4-13.el5.centos > kvm-36-1 > kmod-kvm-36-3 > etherboot-zroms-kvm-5.4.4-13.el5.centos > > What I'm doing wrong? Any help is appreciated. > > Thanks, > Vladimir >

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt