9 a.m.
Just made some tests this morning with latest F16 packages
kernel-3.1.0-7.fc16.x86_64
qemu-kvm-0.15.1-1.fc16.x86_64
virt-manager-0.9.0-7.fc16.noarch
host is Asus u36sd laptop with 8Gb of ram and an ssd disk
its cpu is:
model name : Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
on host:
$ sudo systool -m kvm_intel -v|grep nested
[sudo] password for g.cecchi:
nested = "Y"
Preliminary results are not so good.
I created an F16 guest (f16vm), with default options
I then put its virito disk in cache mode = none and I/O=native
I then selected "copy to guest" as cpu and it was put to "nehalem".
Inside the guest I create a windows xp with default values proposed by
virt-manager
(cd iso is winxp sp3)
Until now not able to complete installation
Better results if I choose "core2duo" as the cpu of f16vm.
But installations blocks in different points never arriving at the end
of the first "copy files" of windows xp install.
This because f16vm freezes (no more network, no more console...)
I have t power off it
I set up f16vm with serial console to see if something appears.. but
nothing appears when f16vm freezes
host run its F16 guest (f16vm) with this command:
# ps -ef|grep qemu
qemu 18638 1 85 15:39 ? 00:03:45 /usr/bin/qemu-kvm -S
-M pc-0.14 -cpu
core2duo,+rdtscp,+x2apic,+xtpr,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds
-enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -name f16 -uuid
690251ac-b691-f320-1eba-9f7f61c2e0d3 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/f16.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive
file=/var/lib/libvirt/images/f16.img,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native
-device
virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=23,id=hostnet0 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:62:12:4a,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-usb -device usb-tablet,id=input0 -spice
port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -global
qxl-vga.vram_size=67108864 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
F16 guest (f16vm) runs its windows xp install guest with this command:
qemu 1355 1 92 15:40 ? 00:03:38 /usr/bin/qemu-kvm -S
-M pc-0.14 -cpu
core2duo,+lahf_lm,+rdtscp,+hypervisor,+x2apic,+cx16,+vmx,+ss,-monitor
-enable-kvm -m 768 -smp 1,sockets=1,cores=1,threads=1 -name winxp
-uuid 9e7ed89e-1bab-b354-cccb-b545d0cc2c29 -nodefconfig -nodefaults
-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
-drive file=/var/lib/libvirt/images/winxp.img,if=none,id=drive-ide0-0-0,format=raw
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2
-drive
file=/var/lib/libvirt/images/winxp_sp3.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
-netdev tap,fd=24,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:91:6b:e6,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -usb -device
usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga std -device
intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
root 1602 1251 0 15:44 pts/0 00:00:00 grep --color=auto qemu
F16 guest (f16vm) serial console output:
Fedora release 16 (Verne)
Kernel 3.1.0-7.fc16.x86_64 on an x86_64 (ttyS0)
f16vm login:
Fedora release 16 (Verne)
Kernel 3.1.0-7.fc16.x86_64 on an x86_64 (ttyS0)
f16vm login: [ 0.443443] ioremap error for 0x7ffff000-0x80000000,
requested 0x10, got 0x0
[ 3.885697] microcode: CPU0 update to revision 0xba failed
Started LSB: daemon for libvirt virtualization API.
Starting LSB: suspend/resume libvirt guests on shutdown/boot...
Started NFS file locking service..
Started Sendmail Mail Transport Client.
Started LSB: suspend/resume libvirt guests on shutdown/boot.
Started LSB: Starts and stops login and scanning of iSCSI devices..
Fedora release 16 (Verne)
Kernel 3.1.0-7.fc16.x86_64 on an x86_64 (ttyS0)
f16vm login:
---> no more output until it then freezes
/var/log/messages of f16vm
[root@f16vm ~]# tail -f /var/log/messages
Nov 9 15:40:33 f16vm dbus-daemon[783]: ** Message: No devices in use, exit
Nov 9 15:40:42 f16vm kernel: [ 50.520366] device vnet0 entered
promiscuous mode
Nov 9 15:40:42 f16vm kernel: [ 50.521677] virbr1: topology change
detected, propagating
Nov 9 15:40:42 f16vm kernel: [ 50.521680] virbr1: port 2(vnet0)
entering forwarding state
Nov 9 15:40:42 f16vm kernel: [ 50.521687] virbr1: port 2(vnet0)
entering forwarding state
Nov 9 15:40:42 f16vm kernel: [ 50.521773] ADDRCONF(NETDEV_CHANGE):
virbr1: link becomes ready
Nov 9 15:40:42 f16vm NetworkManager[752]: <warn>
/sys/devices/virtual/net/vnet0: couldn't determine device driver;
ignoring...
Nov 9 15:40:42 f16vm NetworkManager[752]: NetworkManager[752]: <warn>
/sys/devices/virtual/net/vnet0: couldn't determine device driver;
ignoring...
Nov 9 15:40:42 f16vm qemu-kvm: Could not find keytab file:
/etc/qemu/krb5.tab: No such file or directory
Nov 9 15:40:43 f16vm avahi-daemon[755]: Registering new address
record for fe80::fc54:ff:fe91:6be6 on vnet0.*.
---> no more until it freezes
more tests to come....
Probably needs to adjust particular features to enable/disable about
cpu to pass to f16vm guest...
I'm going try f16 host --> f16vm --> f16vmvm
and see what happens...
Gianluca