I've installed an Intel Gigabit ET card listed on the F12 SR-IOV page.
I used the SR-IOV test day instructions. I'm not seeing any
additional listing for the intel card except for the two ports when
The only issue thing that I can think of is that the motherboard
doesn't support AMD's IOMMU. It's a Gigabyte board using the 790GX
chipset with a Phenom II processor.
Does anyone have any suggestions?
I have a qcow Windows 7 image created from VBox with qemu-img.
VBoxManage clonehd --format RAW Windows-7-32bit-copy.vdi
VirtualBox Command Line Management Interface Version 3.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
Clone hard disk created in format 'RAW'. UUID:
qemu-img convert -O qcow2 Windows-7-32bit-raw.img Windows-7-32bit.qcow
qemu-img info Windows-7-32bit.qcow
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 18G
I've got qemu/kvm installed an F12 machine.
With virt-manager the dialog to install Create a new VM only allows
DVD, iso, ftp, etc. Not a local .qcow image.
I tried restore saved machine and got:
image magic is incorrect
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/manager.py", line 652, in
File "/usr/share/virt-manager/virtManager/connection.py", line 657, in restore
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1420, in restore
if ret == -1: raise libvirtError ('virDomainRestore() failed', conn=self)
libvirtError: operation failed: image magic is incorrect
So how do I add this image to kvm?
The new QEMU packages added to the F12 virt-preview repository in the
last few days apparently require a new BIOS but that doesn't seem to be
present in the repository.
As it stands any attempt to start QEMU after updating just gives me a
Tom Hughes (tom(a)compton.nu)
I've setup a Windows 7 guest on a new F12 box. Initially, it was
fine. However, a couple of times now the guest's networking has been
lost and it has allocate itself a 169.254. address. When I tried
installing a Centos 5.4 guest for comparison, that wasn't able to pick
up an IP via DHCP either.
Here are the current iptables rules:
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -s 192.168.122.0/24 -m tcp -p tcp --dport 445 -j ACCEPT
-A INPUT -s 192.168.122.0/24 -i vnet0 -m udp -p udp --dport 137:139 -j ACCEPT
-A INPUT -s 192.168.122.0/24 -i vnet0 -m tcp -p tcp --dport 137:139 -j ACCEPT
-I FORWARD -m physdev --physdev-is-bridged -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
dnsmasq is running.
Is this correct?
Yum results on guest show kernel.i686 version 18.104.22.168-174.fc12 yet KVM
config file shows arch is x86_64
<type arch='x86_64' machine='pc-0.11'>hvm</type>
Please advise if this should be reported as a bug.
I can't get any sound out of a windows xp guest. I've tried <sound
model='es1370'/> and <sound model='ac97'/> and windows seems to recognize
them ok but no sound at all.
My audio setup in the host is fairly simple, fedora12 and an integrated
sound card + a USB headset, both are successfully detected by fedora and I
can switch between the 2 without problems.
I feel like something is missing here, the host_sound and guest_sound
doesn't seem to be integrated properly. What setting can I change to get
sound out of the guest?
Thanks in advance,
My host crashes when I use the autostart function in
This command sequence works fine:
service libvirtd stop
virsh autostart mydomain --disable
service lib virtd start
virsh start mydomain
This command sequence will crash the host:
service libvirtd stop
virsh autostart mydomain
service libvirtd start
I can't find any error messages related to this. The host system
freezes, the keyboard starts blinking the caps-lock and scroll-lock,
and as best I can tell, the kernel has stopped running.
If I starting up the host system with the VM autostarted, I sometimes
get messages that look like kernel errors on the screen, but I don't
find them in any log files so far. They seem to be related to networking.
Here's some configuration information--I don't know really what all is
needed, but this, I guess is a start:
Host and VM both Fedora 11 with the lastest updates.
Host machine in Intel based with the virtual support turned on.
In the /var/log/libvirtd/qemu directory, the command line to start
the virtual machine is different when started from autostart. The
difference is in this portion:
-net tap,fd=11,vlan=0 for failure (autostart) and
-net tap,fd=18,vlan=0 for success
I am using a bridged connection.
Here's the command line that's used, split over
lines for some degree of readability:
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc
-m 1024 -smp 1 -name mydomain
-monitor pty -pidfile /var/run/libvirt/qemu//mydomain.pid
-boot c -drive file=,if=ide,media=cdrom,index=2
-net tap,fd=11,vlan=0 -serial pty -parallel none
-usb -usbdevice tablet -vnc 127.0.0.1:0
hi, I have 'yum install xen*' on fedora 12 64 bit and reboot.
But the service xen* not start, the folder /proc/xen is missing.
What should I do now?
How to start and Use XEN?
Dario Lesca <d.lesca(a)solinos.it>
I am using F12 x86_64 as a host and have created a F12 i686 guest from
the Live CD - I can successfully ssh from the host TO the guest
(192.168.0.10 => 192.168.122.212) but not the other way around. It did
actually work for a little while just after creating the guest but after
trying stuff to get sound working on the guest and a couple of reboots,
it no longer works (I can't think what has changed).
says that the lines:
"can be used in the guest" - but what file do they go in? The only
appropriate file mentioned above those comments is regarding the host:
- /usr/share/libvirt does not even exist on the guest . .
I would like to get NAT networking going satisfactorily before having to
look at bridged networking.
Any suggestions appreciated.
GPO Box 3411
Sydney NSW 2001