[SOLVED] KVM machines don't boot after apt-get install virt-manager

viniciusmunich

New Member
Jul 1, 2012
3
0
1
Hi,

I installed virt-manager.
Since then, my KVM VMs don't boot, and they show only a black screen on the console.

Is it dangerous to remove virt-manager using apt-get remove virt-manager?
I just notice that my KVM/Windows VMs are consuming just between 10~15 mbs of RAM.

I did apt-get remove virt-manager however I got no apparent results.

Is there any way to reinstall/re setup KVM without lost my openvz containers, or even better, without format my entire disk?

pveversion -v
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-68
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-16
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

root@luck:~# qm start 101
Could not open option rom 'kvmvapic.bin': No such file or directory
kvm: pci_add_option_rom: failed to find romfile "vgabios-stdvga.bin"
kvm: -device virtio-net-pci,mac=42:24:67:03:75:B1,netdev=net0,bus=pci.0,ad dr=0x12,id=net0,bootindex=300: pci_add_option_rom: failed to find romfile "pxe-virtio.rom"

root@luck:~# kvm --version
QEMU emulator version 1.0.50 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard
root@luck:~# md5sum /usr/share/kvm/*
9649e5d3cebac9106af3d6555dbf4ae7 /usr/share/kvm/bios.bin
md5sum: /usr/share/kvm/keymaps: Is a directory
b8cec9572e408a3259914f9aba8664cb /usr/share/kvm/kvmvapic.bin
e78b7ffa1c47e5ffb1992e45f9d01fcc /usr/share/kvm/linuxboot.bin
c3b0e694ef0a6ac0c90a1a17039f3fe8 /usr/share/kvm/multiboot.bin
898d7d0b3ed4a030c877b9185b4ef6be /usr/share/kvm/pxe-e1000.rom
2f8279177fdc2ce5abc47d9f1e303db1 /usr/share/kvm/pxe-eepro100.rom
095cdf2b26084ce22adb883e9c43fc5a /usr/share/kvm/pxe-ne2k_pci.rom
15e38b82922a058c6df6eaffbad1b916 /usr/share/kvm/pxe-pcnet.rom
22f4b6ae5650988f999ee651a3734462 /usr/share/kvm/pxe-rtl8139.rom
91ad9770f5717a89d518534f45f1332d /usr/share/kvm/pxe-virtio.rom
6611fe7b0768d4caf0540cfbd121518e /usr/share/kvm/sgabios.bin
48ca43ec7b5ccbc05f3125a01496c52c /usr/share/kvm/vgabios.bin
4481197bf050d6c3f4dd5b2cb43ed633 /usr/share/kvm/vgabios-cirrus.bin
946180134acdffcb4619a2ef95383c0a /usr/share/kvm/vgabios-qxl.bin
07b43dd3441aad915bcf30811d81cc3d /usr/share/kvm/vgabios-stdvga.bin
f3f86e8ba387ca6a4772a3576c37bace /usr/share/kvm/vgabios-vmware.bin
root@luck:~#



^Is that the problem?

How can I reinstall proxmox's KVM?

Thank you in advance.
By the way, Proxmox is a great software. Thank you!

Admins, please close the Thread
http://forum.proxmox.com/threads/10164-Console-problems-after-install-SSL-Cert-Black-screen .
Sorry about that.

EDIT:

I saw this thread: http://forum.proxmox.com/threads/8557-Virtio-disk-boot-problem?p=48359#post48359

Then I did dpkg -r qemu-system
And now this is what I get:

root@luck:~# qm start 101start failed: command '/usr/bin/kvm -id 101 -chardev 'socket,id=monitor,path=/var/run/qemu-server/101.mon,server,nowait' -mon 'chardev=monitor,mode=readline' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -usbdevice tablet -name Windows2008R2-64bits -smp 'sockets=1,cores=2' -nodefaults -boot 'menu=on' -vga std -localtime -rtc-td-hack -no-kvm-pit-reinjection -no-hpet -k en-us -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-virtio0,cache=writeback,aio=native' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -m 4096 -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,vhost=on' -device 'virtio-net-pci,mac=42:24:67:03:75:B1,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
root@luck:~#

What about this:
root@luck:~# dpkg -l | grep qemuii etherboot-qemu 5.4.4-9 Bootstrapping for various network adapters (qemu)
ii pve-qemu-kvm 1.0-9 Full virtualization on x86 hardware
ii qemu-keymaps 0.12.5+dfsg-3squeeze1 QEMU keyboard maps
ii qemu-server 2.0-39 Qemu Server Tools
rc qemu-system 0.12.5+dfsg-3squeeze1 QEMU full system emulation binaries
ii qemu-user 0.12.5+dfsg-3squeeze1 QEMU user mode emulation binaries
root@luck:~# dpkg -l | grep kvm
ii pve-qemu-kvm 1.0-9 Full virtualization on x86 hardware
root@luck:~#

Everything was working fine, but then I tried to install virt-manager and boom, trouble.
Is it ok to do what this guy did:
http://forum.proxmox.com/threads/8557-Virtio-disk-boot-problem?p=48714#post48714 ?



------------ SOLUTION ------------
OK, I did what dietmar
said on this post:

http://forum.proxmox.com/threads/8557-Virtio-disk-boot-problem?p=48747#post48747
Please remove all debian related qemu packages:

etherboot-qemu
qemu-keymaps
qemu-system
qemu-user

I have no idea how you managed to install them together with pve-qemu-kvm - package tools should prevent that.

So,
root@luck:~# dpkg -r etherboot-qemu(Reading database ... 101839 files and directories currently installed.)
Removing etherboot-qemu ...
root@luck:~# dpkg -r qemu-keymaps
(Reading database ... 101829 files and directories currently installed.)
Removing qemu-keymaps ...
root@luck:~# dpkg -r qemu-system
dpkg: warning: ignoring request to remove qemu-system, only the config
files of which are on the system. Use --purge to remove them too.
root@luck:~# dpkg -r qemu-user
(Reading database ... 101788 files and directories currently installed.)
Removing qemu-user ...
Processing triggers for man-db ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

And now, my VMs are booting !!

Thank you dietmar!
lol

I hope you guys use the search button, the results can be really helpful!

btw, sorry for my english.
 
Last edited by a moderator:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!