On 06/21/2010 09:51 AM, Kangkook Jee wrote:
Does KVM hook into NetFilter to intercept packets destined for the guest, or
PF_PACKET?
None of the above.
With -net user, KVM uses techniques derived from SLiRP to simulate a
network stack with only traditional userspace UNIX socket calls. With
-
This is the libvirt default network configuration. Please see the
libvirt documentation and mailing list for support.
As an aside -- you'll probably want to use a bridged configuration
rather than the NATted one. If you really do want to stick with the NAT
configuration, you'll need to make su
Gordan Bobic wrote:
Lastly, do you use cache=wb on qemu? it's just a fun mode, we use
cache=off only.
I don't see the option being set in the logs, so I'd guess it's whatever
qemu-kvm defaults to.
You can set this through libvirt by putting an element such as the
following within your elem
Ross Boylan wrote:
http://www.linux-kvm.org/page/HOWTO1 says to build kvm I should get the
latest kvm-release.tar.gz.
http://www.linux-kvm.org/page/Downloads says "If you want to use the
latest version of KVM kernel modules and supporting userspace, you can
download the latest version from
http:
For a heavily I/O-bound load such as media streaming, it's better not to
use virtualization. There are some newer technologies such as SR-IOV
which may mitigate these problems, but I don't particularly suggest
straying that close to the bleeding edge on a presumably
mission-critical system.
I
Daniel Bareiro wrote:
inet_listen: bind(ipv4,0.0.0.0,5903): Address already in use
inet_listen: FAILED
If you check with netstat, I expect you'll see the port in TIME_WAIT
state; if so, this will eventually clean itself up if you just wait a
little bit before restarting.
One option to avoid
Figured this out --
It's actually a consequence of the Fedora packaging I'm using relying on
an external BIOS (built as part of the Bochs package); the BIOS
installed by qemu-kvm-0.11.0-rc1 works just fine.
Apologies for the noise.
--
To unsubscribe from this list: send the line "unsubscribe
Charles Duffy wrote:
Howdy.
The libguestfs kernel and appliance I've been using successfully with
qemu-kvm-0.10.6 and prior fails horribly with qemu-kvm-0.11.0-rc1 unless
'noapic' is passed on the kernel command line:
To follow up with a quick note -- I have quite a lot
Howdy.
The libguestfs kernel and appliance I've been using successfully with
qemu-kvm-0.10.6 and prior fails horribly with qemu-kvm-0.11.0-rc1 unless
'noapic' is passed on the kernel command line:
/usr/bin/qemu-kvm /usr/bin/qemu-kvm -drive
file=/local/fvte-q/.fvte/states/vms/15a54e63c1d84e2e
This doesn't speak directly to your live migration issue -- but
copy-and-pasting a libvirt-generated command line (as you're doing here)
and using it by hand is perilous.
As I mentioned when you asked in the IRC channel, you shouldn't be using
fd= here when starting kvm by hand -- it expects t
To echo Michael a little here -- posting this on the KVM mailing list
implies that it shouldn't have dependencies beyond KVM; as such, the
libvirt mailing list would probably be a better place for these scripts.
That said -- no, there isn't an option within libvirt to save or
gracefully shut d
Michael Jinks wrote:
On Wed, Jul 15, 2009 at 6:24 PM, Chris Webb wrote:
You want
-net nic,vlan=0 -net tap,vlan=0,ifname=tap11 -net nic,vlan=1 -net
tap,vlan=1,ifname=tap12
Progress! This works, I can bring up the guest and watch it boot, but
both of its NICs came up bound to the first bridg
John Wong wrote:
> Can i mount the qcow2.img image on my linux-2.6.30/amd64 host?
> the qcow2.img is winxp(ntfs) qcow2.img image.
See qemu-nbd, nbd-client and kpartx.
For simpler manipulations, however, you might find Guestfish (or other
libguestfs components) an appropriate tool.
--
To unsubscr
Michael Jinks wrote:
On Thu, Jul 2, 2009 at 5:45 PM, Sterling Windmill wrote:
What do you mean by "rejected"? Is the installer not taking your key (I doubt
this would be caused by anything KVM specific),
Right, that. I don't have the screen in front of me so I might be
getting the exact word
Zhang Qian wrote:
I'd like to know if there is a configuration file for each KVM virtual
machine? I can define a domain by "virsh define" command, but where
the configuraiton parameters are persisted for the VM?
virsh is not a part of kvm, but rather libvirt; you should ask for
support for it
Michael Jinks wrote:
Given the way qemu and screen interact, using the same keystrokes to
initiate commands, it would be really useful to have some other way to
detach and re-attach to a kvm guest on the fly.
It's pretty easy to configure screen to use a different set of
keystrokes. I find tha
Nikola Ciprich wrote:
using
... -incoming exec:cat /home/...image.vm
seems to start the machine, but it seems to be stuck, even though I removed -S
parameter.
That may well be a guest issue rather than a qemu migration problem --
I've seen similar difficulties for guests being resumed via in
Bike & Snow wrote:
Is anyone using OCFS2 on a SAN based setup (in my case iSCSI) for a
shared storage setup for KVM?
I've got a really nice setup that works really well and gives very
good performance.
However, the QEMU disk images (raw format) keep corrupting.
Is OCFS2 to be avoided in the se
David Huff wrote:
I had some issues getting the guest to read a vvfat floppy passed to the guest
via qemu option "-fda fat:floppy:rw:./floppy" it would pass the dir as a vfat
disk and the guest could mount it, however guest could not read the files on the
vdisk..
I'm surprised you opted to
Ross Boylan wrote:
Or do you mean I should back each virtual disk with an LVM volume?
Yes, this option is what was meant.
That does seem cleaner; I've just been following the docs and they
use regular files. They say I can't just use a raw partition, but
maybe kvm-img -f qcow2 /dev/MyVolumeGr
Marcelo Tosatti wrote:
There's no savevm handler at all:
Ahh! Thank you for the explanation.
There was an incomplete patch posted to qemu-devel a while ago, which I
can't find.
I'm guessing that would be "[PATCH] save/restore for LSI SCSI", by Nolan
:
http://permalink.gmane.org/gmane.comp
Evert wrote:
Can I conclude from that that Debian is the best host distro to go for?
Better than Red Hat & Gentoo?
I'm not really convinced there's a big enough difference that it matters
-- particularly on a production system where you intend to stick to
stable, well-tested software. That sa
Per subject. Observed on kvm-83 through kvm-85; haven't traced back
further. No longer occurs when switching to IDE. Manifests with messages
similar to the following on restore:
sd 0:0:0:0: [sda] ABORT operation started
sd 0:0:0:0: ABORT operation timed-out.
sd 0:0:0:0: [sda] ABORT operation st
Armindo Silva wrote:
On Tue, Apr 14, 2009 at 12:40 AM, Charles Duffy
wrote:
What problems with the VNC window?
The mouse is always out of sync.
That's what -usbdevice tablet is for.
Other problem is that all my guest lost their default network config -
they all had static ips
Armindo Silva wrote:
There are a few glitches/problems with this version (at least using
win2k3 server as guest). The problems with the vnc window only
disappear when i create a new guest, with the old ones the mouse is
still out of sync.
What problems with the VNC window?
Other problem is th
David Huff wrote:
Submitting new test for review and comments.
This test was originally developed by the Red Hat QE team.
It starts a new guest saves it and reloads the saved state.
looking for comments and or improvements that can be made to this test.
I have some code (aimed at testing s
You should ask about this on the libvirt mailing list and IRC channel,
not here.
That said, a few quick points:
1. the libvirt you're running is very old.
2. you might consider setting the emulator to point to a shell script
which records the command line it's called with to a file before doin
Gerry Reno wrote:
Well, you're missing a set of opening quotation marks here... and your
file doesn't have a .iso extension? That's rather unusual.
Anyhow, inasmuch as you're unable to run a define successfully, this is
a libvirt usage problem, not a kvm issue; I suggest you try irc.oftc.n
Gerry Reno wrote:
Charles Duffy wrote:
Gerry Reno wrote:
What is GUI VMM?
virt-manager
To get support for kvm proper here, you'll want to use ps to see the
command line with which libvirtd is invoking kvm and provide that.
/usr/bin/qemu-kvm -S -M pc -m 512 -smp 2 -name MX_3 -monito
Gerry Reno wrote:
What is GUI VMM?
virt-manager
The libvirt mailing list is the right place to get support for
virt-manager. To get support for kvm proper here, you'll want to use ps
to see the command line with which libvirtd is invoking kvm and provide
that.
That said, the XML you copie
Bill Davidsen wrote:
Ryan Harper wrote:
-vnc localhost:1 -- will display the guest VGA display on the localhost.
A remote system can do:
vncviewer ${kvmhost}:1
to view the guest VGA.
Thanks, will try later tonight. Have to have a bit of care getting the
number right (unique) since there might
PCI passthrough for video cards isn't expected to work, even if the host
isn't using them at all. See prior on-list discussion for details; my
understanding is that the guest won't run the card's video BIOS at
boot-time.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the
Matthias Hovestadt wrote:
This mail seems to be somehow related to the bug report of Justin Keogh
from 30th Dec 2008. He was able to fix his problem by simply setting
CONFIG_KVM=m, but I'm already using modules, so his workaround can't be
applied here.
Quick question -- does your dmesg output i
Daniel Schwager wrote:
My devicemanager shows me a unknown device with the following ID:
PCI\VEN_1AF4&DEV_1003&SUBSYS_00031AF4&REV_00\3&13C0B0C5&0&28
This would be the virtio replacement for the serial console. Windows
doesn't really have a "serial" console at all, so don't worry abou
heinz wrote:
This kernel does support kvm and the prement patch to make it pretty
good for real time things.
A kvm virtual machine is running for example windows xp with some WPF
gui. That would be a nice solution,
and for many problems - including those windows gui guys needing real
time as we
Василец Дмитрий wrote:
Xen hypervisor can increase and decrease cpu and ram.
will be able this function on kvm/qemu ?
Last time I was familiar with Xen's balloon driver, it had the exact
same limitation as the kvm one.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the
Let's back up here a bit --
When you say "no disk was found at all" when using SCSI emulation, do
you mean the kernel booted and was unable to find the hard drives, or
did it not even get that far?
The SCSI emulation uses the sym53c8xx driver, which was first developed
against 2.0.36; it's b
Zhang, Xiantao wrote:
Charles Duffy wrote:
Speaking with my end-user hat on, this seems to violate the principal
of least surprise:
I would expect NVRAM contents to be discarded, not saved to a file in
the current working directory, if no relevant option were given on the
command line.
Maybe
Zhang, Yang wrote:
Hi
Please drop former.
This is the modify patch for save nvram.
I add the new command line arg of "-nvram file" to specify the location
Of the file. Without the arg ,it will save the nvram in the current dir
and named as "nvram.dat". Also, it will read the saved file "nvram.
Philipp Wehrheim wrote:
Hey,
I lately tried to live migrate a VM but had to find out that the
syntax shown in the KVM examples and the actual syntax expected
by the code do not match.
from the Wiki:
tcp:// migration protocol
[...]
So the syntax expected by the code is *with
paolo pedaletti wrote:
Ciao,
sorry for this silly question, but I can't compile kvm-79 for AMD 64bit
Please pardon me for following up on one silly question with another --
but is your host running a 64-bit userland? (What is the output of
"uname -m"?)
--
To unsubscribe from this list: send
walt wrote:
Any chance that 'commit' could be added to raw as
well as qcow2?
Raw images by their nature can't contain metadata -- they have only the
exact contents of the virtual drive, which is what makes them "raw" --
so they by definition can't support copy-on-write (and thus commit) or
o
Jan Kiszka wrote:
Farkas Levente wrote:
- guest fedora-9 latest kernel-2.6.26.6-79.fc9.i686 still not boot,
- guest centos-5 x86_64's kernel-2.6.18-92.1.17.el5 still gives the same
crash as kvm-78 (screenshot attached),
Those two should be fine with this patch [1]. You are welcome to test it
a
Jan Kiszka wrote:
Charles Duffy wrote:
irq 25, desc: 803afc80, depth: 1, count: 0, unhandled: 0
->handle_irq(): 800b54e3, handle_bad_irq+0x0/0x1f6
->chip(): 802ea700, 0x802ea700
->action():
IRQ_DISABLED set
unexpected IRQ trap at
This happens every other use of system_reset -- ie. resetting the system
using system_reset while in this panic'd state results in correct
functionality. Following the suggestion and booting the guest with
noapic results in other IRQ-related errors.
The guest kernel is CentOS 5 2.6.18-53.el5
Bill Davidsen wrote:
I agree completely with the "no way" and "FAILS" evaluation, it
continues to hang during install from the CD image with
- FC6 Intel 6600 dual core with kvm 65
- FC9 Intel quad core 9400 2.6.27-3 kernel and latest kvm and qemu upgrades
- FC9 AMD dual core (number in another b
Bill Davidsen wrote:
I need a Win98SE VM to do some software testing and support.
Unfortunately KVM seems to not be able to run 98SE, although it runs a
bunch of more recent Windows versions I can't use for this. I really
don't want to support multiple VM servers, and there is pressure to go
t
jd wrote:
Now when I create new VM, using the command line...
qemu-system-x86_64 -net nic,vlan=0,macaddr=00:16:3e:70:8f:33 -net tap,vlan=0
-hda /mnt/vm_data/test_xp.hda.disk.xm -m 256
The VM does not seem to get the IP address :( (may be dhcp request is failing)
You aren't providing ifname o
Ian Kirk wrote:
I thought that updating qemu-img to have quasi-fdisk functionality was a
good idea myself. Is there a respected libfdisk.so thing that could be
used to abstract most of the work ?
Exporting textual output and piping that to sfdisk is one approach.
--
To unsubscribe from this li
Would it not address your security concerns to build a modular kernel,
load the current kvm module, and then drop CAP_SYS_MODULE as part of
your boot scripts?
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Sorry -- tftp configuration error on my end; hit "send" before finishing
environment valiadation; my apologies.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Per subject; etherboot is requiring tens of minutes just to partially
download pxelinux.0:
Probing pci nic...
[e1000-82540em]Ethernet addr: 00:16:3E:ED:DA:6A
Searching for server (DHCP)..
Me: 169.254.1.254, DHCP: 192.168.66.1, TFTP: 169.254.0.1, Gateway
169.254.0.1
Loading 169.254.0.1:/pxe
A few quick notes:
- The extboot.bin regression from kvm-71 (SCSI drives being
unavailable after reboot) is still outstanding.
- kvm (and presumably qemu) doesn't check for fd= parameters pointing
to file descriptor numbers which are not, in fact, open; this results in
select() spinning on
Michael Malone wrote:
If you're trying to use virt-manager, then don't.
Virt-manager stops you from having access to a bunch of the underlying
features
of kvm/qemu such as serial ports. I'm told they're working on it, but
it's only useful
for a basic setup at the moment.
Serial ports *are*
Anthony Liguori wrote:
diff --git a/qemu/hw/e1000.c b/qemu/hw/e1000.c
index 1be69ec..6a07b0c 100644
--- a/qemu/hw/e1000.c
+++ b/qemu/hw/e1000.c
@@ -521,8 +521,8 @@ e1000_can_receive(void *opaque)
{
E1000State *s = opaque;
-return ((s->mac_reg[RCTL] & E1000_RCTL_EN) &&
- s->mac_
Anthony Liguori wrote:
Charles Duffy wrote:
Anthony Liguori wrote:
Charles Duffy wrote:
Per subject. "git bisect run" script (and libvirt xml helper) attached.
Does the problem go away if you make the e1000_can_receive() function
always return 1?
Yes.
Presumably, this is the
Anthony Liguori wrote:
Charles Duffy wrote:
Per subject. "git bisect run" script (and libvirt xml helper) attached.
Does the problem go away if you make the e1000_can_receive() function
always return 1?
Yes.
--
To unsubscribe from this list: send the line "unsubscribe kvm&
Per subject. "git bisect run" script (and libvirt xml helper) attached.
87b5acf6125d205119e3194c02ed6e71715517dc is first bad commit
commit 87b5acf6125d205119e3194c02ed6e71715517dc
Author: Anthony Liguori <[EMAIL PROTECTED]>
Date: Wed May 7 13:09:40 2008 -0500
kvm: qemu: stop dropping so
I have observed downloads to stall on an RHEL4 i386 guest (on an x86_64
host), such that creating additional network traffic (ie. pinging the
virtual host in question) will "unstick" the download. This does not
happen to a RHEL5 x86_64 guest on the same host, and is quite reliably
reproducible
Per subject; if autoport is in use for a host, the current
virDomainGraphicsDefFormat code always emits "port=-1", even if a port
is assigned to the host; this leaves no way for a client to find the VNC
port assigned to the host in question.
diff --git a/src/domain_conf.c b/src/domain_conf.c
in
FYI,
I'm experiencing this as well, and note that the issue still occurs with
-no-kvm, but not with current qemu-trunk (r4955); that said,
qemu-trunk's behavior doesn't seem to be perfect either -- there are
several "No IP address" responses before one is acknowledged.
--
To unsubscribe from
Per subject. Etherboot comes up but is unable to get an IP address,
despite perfectly valid-looking incoming responses. Once booted, Linux
has no problem with DHCP.
Switching to the rtl8139 (while changing nothing else) works around the
issue.
--
To unsubscribe from this list: send the line
Switching from e1000 to rtl8139 appears to work around the issue.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Several times over the last few days, I've lost network connectivity
from one of my guests. This has happened only during interactive
sessions in which I take an action resulting in a large screen update. I
have tried flood pinging (only with the default, small packet size), and
not been able t
Per subject. As the below log makes evident, ACPI is quite certainly
enabled:
Halting system...
md: stopping all md devices.
Shutdown: hda
ACPI: PCI interrupt for device :00:06.0 disabled
ACPI: PCI interrupt for device :00:05.0 disabled
ACPI: PCI interrupt for device :00:04.0 di
CONFIG_KALLSYMS is indeed defined, but kallsyms_lookup_name doesn't
appear to be exported in this kernel.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Farkas Levente wrote:
kvm-70 do not compile on centos-5 kernel-2.6.18-53.1.21.el5
Easy enough to work around, as kallsyms_lookup_name is only used in one
place:
diff -ru kvm-70/kernel/external-module-compat.h
kvm-70.new/kernel/external-module-compat.h
--- kvm-70/kernel/external-module-compa
67 matches
Mail list logo
