On (Wed) Jul 08 2009 [16:19:27], Dâniel Fraga wrote:
I like very much KVM, but I decided to test Virtualbox and it
has nice features KVM doesn't have. BUT... Virtualbox is orders of
magnitude SLOWER than KVM. Virtualbox just can't compete with KVM
regarding speed. KVM is much, much, much
On (Thu) Jul 09 2009 [08:27:48], Robert Wimmer wrote:
Hi there,
back in days before kernel 2.6.25/2.6.26 and KVM 70-77 KVM decided to
crash from time to time. That time we used XFS as filesystem (/ and /boot
where ext3/ext2). Since XFS worked so very well for us on physical
hosts the
On (Thu) Jul 09 2009 [07:18:54], Ján ONDREJ (SAL) wrote:
Hello,
today I have second incident, that my qemu-kvm process is running at 100%
or 200% CPU (watched using top program), but there is no response from guest
long time (some hours). First time lots of these messages appeared in
KVM ioctls are used to initialize MCE simulation and inject MCE. The
real MCE simulation is implemented in Linux kernel. The Kernel part
has been merged.
ChangeLog:
v6:
- Re-based on latest qemu-kvm.git
v5:
- Re-based on latest qemu-kvm.git
v3:
- Re-based on qemu/tcg MCE support patch
v2:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example filename scsi:0, is
interpreted as a protocol by name scsi.
This patch allows user to espace colon characters. For example the above
filename can now be expressed
Hi!
Are you using virtio-block?
Yes.
In any case, not using a released version always has risks.
Well, what do you mean by not using a released version?
The package gentoo-sources always uses released
kernels. 2.6.30-r2 in Gentoo means that this is the third
update of the stable kernel
On Wed, Jul 15, 2009 at 12:51:33PM +0530, Amit Shah wrote:
On (Thu) Jul 09 2009 [07:18:54], Ján ONDREJ (SAL) wrote:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
17110 root 20 0 4417m 3.9g 1464 S 201.3 50.9 1326:34 qemu-kvm
9886 root 20
Yes, kvm-88 fixed this problem.
I also notice another problem, when i use kvm-88(qemu-system-x86_64 with
kvm-kmod-2.6.30.1-rc2.tar.gz) installing 64bit OS (window7 debian
netbsd),
the install CD show the error message, say this system is 32bit not
64bit and can not continue to install.
I
On (Wed) Jul 15 2009 [09:52:36], Robert Wimmer wrote:
Hi!
Are you using virtio-block?
Yes.
OK, then there is a known problem. I think the fix is waiting to be
applied.
In any case, not using a released version always has risks.
Well, what do you mean by not using a released version?
On (Wed) Jul 15 2009 [09:58:51], Ján ONDREJ (SAL) wrote:
On Wed, Jul 15, 2009 at 12:51:33PM +0530, Amit Shah wrote:
On (Thu) Jul 09 2009 [07:18:54], Ján ONDREJ (SAL) wrote:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
17110 root 20 0 4417m
Ram Pai wrote:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example filename scsi:0, is
interpreted as a protocol by name scsi.
This patch allows user to espace colon characters. For example the above
filename can
On 7/15/2009 6:49 AM, Yolkfull Chow wrote:
This is a subtest in kvm. It will verify newly added pci block device now. For
Windows support,it needs to use_telnet since 'wmic' which is used to check disk
info could only be executed in telnet session not ssh. Just ran it on guest
Fedora-11.32
Hi all,
Following problem.
I recently upgraded kvm from 7.2 (Debian Lenny repository version) to
the newest 88 KVM.
Since then when I first started and stopped a Debian Lenny virtual
instance (guest) at the next (second) start I get the following error:
Grub loading, please wait. Error 2. So
- Erik Wartusch e.wartu...@mitacs.com wrote:
Hi all,
Following problem.
I recently upgraded kvm from 7.2 (Debian Lenny repository version) to
the newest 88 KVM.
Since then when I first started and stopped a Debian Lenny virtual
instance (guest) at the next (second) start I get the
On 07/15/2009 12:12 PM, Yolkfull Chow wrote:
Would submit this patch which is from our internal kvm-autotest patches
submitted by Jason.
So that we could go on test case about parameters verification(UUID, DMI data
etc).
Signed-off-by: Yolkfull Chowyz...@redhat.com
---
On Wed, Jul 8, 2009 at 4:46 AM, Michael Goldishmgold...@redhat.com wrote:
I'm resending the message because it probably got filtered out due to the
attached setup.bat file.
The contents of setup.bat were:
copy D:\rss.exe C:\
net user Administrator /active:yes
net user Administrator
- Erik Wartusch e.wartusch at mitacs.com wrote:
Hi all,
Following problem.
I recently upgraded kvm from 7.2 (Debian Lenny repository version) to
the newest 88 KVM.
Since then when I first started and stopped a Debian Lenny virtual
instance (guest) at the next (second) start I get
From abbe3b57af6a28bb81e5fb8b09b10802a8ccc3fe Mon Sep 17 00:00:00 2001
From: Dor Laor d...@redhat.com
Date: Wed, 15 Jul 2009 17:53:16 +0300
Subject: [PATCH] Fix migration issue when the destination is loaded
If the migration socket is full, we get EAGAIN for the write.
The set_fd_handler2 defers
On 7/15/09, Ram Pai linux...@us.ibm.com wrote:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example filename scsi:0, is
interpreted as a protocol by name scsi.
--- a/block/raw-posix.c
+++ b/block/raw-posix.c
I've reinstalled Debian Lenny now on a fresh virtual harddisk and now
its working... Seems like my old images I used with 72 are the problem
with 88.
Erik
Am Mittwoch, den 15.07.2009, 16:20 +0200 schrieb Erik Wartusch:
- Erik Wartusch e.wartusch at mitacs.com wrote:
Hi all,
On Wednesday 15 July 2009 06:06:54 am Erik Wartusch wrote:
Hi all,
Following problem.
I recently upgraded kvm from 7.2 (Debian Lenny repository version) to
the newest 88 KVM.
How did you install kvm-88? Did you do a proper install? including the bios
files, extboot, etc?
--Iggy
Since
Blue Swirl wrote:
I bet this won't compile on win32.
Instead of this (IMHO doomed) escape approach, maybe the filename
parameter could be specified as the next argument, for example:
-hda format=qcow2,blah,blah,filename_is_next_arg -hda filename with
funky characters like ',' ':' '!'
- Lucas Meneghel Rodrigues l...@redhat.com wrote:
On Wed, Jul 8, 2009 at 4:46 AM, Michael Goldishmgold...@redhat.com
wrote:
I'm resending the message because it probably got filtered out due
to the
attached setup.bat file.
The contents of setup.bat were:
copy D:\rss.exe C:\
I downloaded the tar.gz
http://downloads.sourceforge.net/sourceforge/kvm/kvm-88.tar.gz?use_mirror=dfn
unzipped it and followed the procedure according to the how to:
./configure --prefix=/usr/local/kvm
make
make install
modprobe kvm-intel
Erik
Am Mittwoch, den 15.07.2009, 10:11 -0500
On 7/15/09, Anthony Liguori aligu...@us.ibm.com wrote:
Blue Swirl wrote:
I bet this won't compile on win32.
Instead of this (IMHO doomed) escape approach, maybe the filename
parameter could be specified as the next argument, for example:
-hda format=qcow2,blah,blah,filename_is_next_arg
Kevin Wolf wrote:
Anthony Liguori schrieb:
Blue Swirl wrote:
I bet this won't compile on win32.
Instead of this (IMHO doomed) escape approach, maybe the filename
parameter could be specified as the next argument, for example:
-hda format=qcow2,blah,blah,filename_is_next_arg -hda
Blue Swirl wrote:
Then how about something like:
-drive name=hda,if=ide,cache=off,file_is_arg -filearg foo.img
-drive name=vda,if=virtio,cache=writeback,file_comes_next -patharg foo.img
-drive name=sdb,if=scsi,unit=1,fnarg -fnarg boo.img
The explicit ordering part seems clunky to me.
On Wednesday 15 July 2009, Anthony Liguori wrote:
Blue Swirl wrote:
I bet this won't compile on win32.
Instead of this (IMHO doomed) escape approach, maybe the filename
parameter could be specified as the next argument, for example:
-hda format=qcow2,blah,blah,filename_is_next_arg -hda
I have tested and confirmed that in KVM-86 all worked fine.
I attempted to test in KVM-87, however I was not able to finish
install due to make errors
KVM-87 configure: http://pastebin.ca/1495900
KVM-87 make: http://pastebin.ca/1495902
In KVM-88 I am able to install again, but I am not able to
On 07/15/09 17:14, Anthony Liguori wrote:
Blue Swirl wrote:
I bet this won't compile on win32.
Instead of this (IMHO doomed) escape approach, maybe the filename
parameter could be specified as the next argument, for example:
-hda format=qcow2,blah,blah,filename_is_next_arg -hda filename with
Instead of using '-drive if=none' we could use some other syntax where
the filename can be passed as separate argument. Can switches have two
arguments? If so, maybe this:
-hostdrive $file $options
This only works for a single mandatory argument that needs to contain awkward
I'm in an ongoing process of not using kvm-specific types in function
declarations. handle_unhandled() is the first victim. Since we don't
really use this data, but just the reason, remove them entirely.
Signed-off-by: Glauber Costa glom...@redhat.com
---
qemu-kvm.c |9 +++--
1 files
Hi guys,
I'm sending a series that moves further in reusing upstream code
Here I'm reusing kvm_vm_ioctl, kvm_ioctl, kvm_check_extension and
the cpuid bits for i386.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
Start using kvm_vm_ioctl's code.
For type safety, delete vm_fd from kvm_context entirely, so the
compiler can play along with us helping to detect errors I might
have made.
Signed-off-by: Glauber Costa glom...@redhat.com
---
kvm-all.c |2 ++
qemu-kvm-x86.c | 18 +-
Start using kvm_ioctl's code.
For type safety, delete fd from kvm_context entirely, so the
compiler can play along with us helping to detect errors I might
have made.
Signed-off-by: Glauber Costa glom...@redhat.com
---
kvm-all.c |2 +-
qemu-kvm-x86.c | 18 +-
use cpuid code from upstream. By doing that, we lose the following snippet
in kvm_get_supported_cpuid():
ret |= 1 12; /* MTRR */
ret |= 1 16; /* PAT */
ret |= 1 7; /* MCE */
ret |= 1 14; /* MCA */
A quick search in mailing lists says this code is not really necessary, and
use upstream check_extension code
Signed-off-by: Glauber Costa glom...@redhat.com
---
hw/device-assignment.c |2 +-
kvm-all.c |2 ++
qemu-kvm-x86.c |6 +++---
qemu-kvm.c | 18 --
qemu-kvm.h |2 +-
5 files changed, 11
Anthony Liguori schrieb:
Blue Swirl wrote:
Then how about something like:
-drive name=hda,if=ide,cache=off,file_is_arg -filearg foo.img
-drive name=vda,if=virtio,cache=writeback,file_comes_next -patharg foo.img
-drive name=sdb,if=scsi,unit=1,fnarg -fnarg boo.img
The explicit
On Wed, 2009-07-15 at 11:30 +0200, Jan Kiszka wrote:
Ram Pai wrote:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example filename scsi:0, is
interpreted as a protocol by name scsi.
This patch allows user to
On Wed, Jul 15, 2009 at 10:40:37AM -0500, Anthony Liguori wrote:
Blue Swirl wrote:
Then how about something like:
-drive name=hda,if=ide,cache=off,file_is_arg -filearg foo.img
-drive name=vda,if=virtio,cache=writeback,file_comes_next -patharg foo.img
-drive name=sdb,if=scsi,unit=1,fnarg
On Wed, Jun 24, 2009 at 01:13:46PM -0500, Anthony Liguori wrote:
This introduces some #ifdefs in pcspk to fix the build when KVM isn't enabled.
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
---
hw/pcspk.c | 15 +--
1 files changed, 9 insertions(+), 6 deletions(-)
diff
On Tue, Jul 14, 2009 at 05:30:43PM +0300, Gleb Natapov wrote:
Signed-off-by: Gleb Natapov g...@redhat.com
---
arch/ia64/kvm/kvm-ia64.c | 27 ++--
arch/x86/kvm/lapic.c |5 +---
arch/x86/kvm/x86.c | 30 ++-
virt/kvm/ioapic.c
Kevin Wolf wrote:
Can we at least allow \, instead of ,, in parameter parsing, so that the
backslash has the practical benefit of being a single universal escape
character?
Is there a good reason why we cannot simply use \char to escape
_any_ character, in every context where a user-supplied
On Tue, Jul 14, 2009 at 05:30:45PM +0300, Gleb Natapov wrote:
Use gsi indexed array instead of scanning all entries on each interrupt
injection. Also maintain back mapping from irqchip/pin to gsi to speedup
interrupt acknowledgment notifications.
Signed-off-by: Gleb Natapov g...@redhat.com
Ram Pai wrote:
I have verified with relative paths and it works.
After analyzing the code, i came to the conclusion that call to
realpath() adds no real value.
The logic in bdrv_open2() is something like this
bdrv_open2()
{
if (snapshot) {
backup = realpath(filename);
On Wed, 2009-07-15 at 19:20 +0100, Jamie Lokier wrote:
Ram Pai wrote:
I have verified with relative paths and it works.
After analyzing the code, i came to the conclusion that call to
realpath() adds no real value.
The logic in bdrv_open2() is something like this
bdrv_open2()
On Thu, Jul 09, 2009 at 05:00:42PM +0800, Sheng Yang wrote:
set_cr3() should already cover the TLB flushing.
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
arch/x86/kvm/mmu.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/mmu.c
On Mon, Jul 13, 2009 at 12:59:28PM +0300, Anssi Kolehmainen wrote:
Hi,
When I run kvm-88 with -vnc and -k fi and try to press ' (apostrophe) in
vnc window I get b in the guest. Strange enough, in SDL window
everything seems to work just fine.
Anyhow, the fix is to remove second
On Tue, Jul 14, 2009 at 05:30:45PM +0300, Gleb Natapov wrote:
@@ -147,14 +149,13 @@ int kvm_set_irq(struct kvm *kvm, int irq_source_id, int
irq, int level)
* writes to the unused one.
*/
rcu_read_lock();
- for (e = rcu_dereference(kvm-irq_routing); e e-set; e++) {
This adds a generic uio driver that can bind to any PCI device. First
user will be virtualization where a qemu userspace process needs to give
guest OS access to the device.
Interrupts are handled using the Interrupt Disable bit in the PCI command
register and Interrupt Status bit in the PCI
On Wed, Jul 15, 2009 at 02:57:59PM -0300, Marcelo Tosatti wrote:
On Tue, Jul 14, 2009 at 05:30:43PM +0300, Gleb Natapov wrote:
Signed-off-by: Gleb Natapov g...@redhat.com
---
arch/ia64/kvm/kvm-ia64.c | 27 ++--
arch/x86/kvm/lapic.c |5 +---
On Wed, Jul 15, 2009 at 10:17:22PM +0300, Michael S. Tsirkin wrote:
On Tue, Jul 14, 2009 at 05:30:45PM +0300, Gleb Natapov wrote:
@@ -147,14 +149,13 @@ int kvm_set_irq(struct kvm *kvm, int irq_source_id,
int irq, int level)
* writes to the unused one.
*/
rcu_read_lock();
On Wed, Jul 15, 2009 at 03:18:00PM -0300, Marcelo Tosatti wrote:
On Tue, Jul 14, 2009 at 05:30:45PM +0300, Gleb Natapov wrote:
Use gsi indexed array instead of scanning all entries on each interrupt
injection. Also maintain back mapping from irqchip/pin to gsi to speedup
interrupt
Jamie Lokier wrote:
Kevin Wolf wrote:
Can we at least allow \, instead of ,, in parameter parsing, so that the
backslash has the practical benefit of being a single universal escape
character?
Is there a good reason why we cannot simply use \char to escape
_any_ character, in every context
Ram Pai wrote:
I have successfully verified qcow2 files. But then I may not be trying
out the exact thing that you are talking about. Can you give me a test
case that I can verify.
Commands tried with qemu-0.10.0-1ubuntu1:
$ mkdir unlikely_subdir
$ cd unlikely_subdir
$ qemu-img create -f
Jamie Lokier wrote:
Ram Pai wrote:
I have successfully verified qcow2 files. But then I may not be trying
out the exact thing that you are talking about. Can you give me a test
case that I can verify.
Commands tried with qemu-0.10.0-1ubuntu1:
$ mkdir unlikely_subdir
$ cd
Jan Kiszka wrote:
Now, I see one significant hurdle with that: it's quite inconvenient
for Windows users, typing paths like c:\path\to\dir\file, if those
backslashes are stipped.
We could exclude Windows from this (I think to remember that filenames
are more restricted there anyway) or
On Wed, Jul 15, 2009 at 11:48:17PM +0300, Gleb Natapov wrote:
+ spin_unlock(ioapic-lock);
+ kvm_notify_acked_irq(ioapic-kvm, KVM_IRQCHIP_IOAPIC, i);
+ spin_lock(ioapic-lock);
While traversing the IOAPIC pins you drop the lock and acquire it again,
which is
On Wed, Jul 15, 2009 at 11:13:40PM +0300, Michael S. Tsirkin wrote:
This adds a generic uio driver that can bind to any PCI device. First
user will be virtualization where a qemu userspace process needs to give
guest OS access to the device.
Interrupts are handled using the Interrupt
Jamie Lokier wrote:
Jan Kiszka wrote:
Now, I see one significant hurdle with that: it's quite inconvenient
for Windows users, typing paths like c:\path\to\dir\file, if those
backslashes are stipped.
We could exclude Windows from this (I think to remember that filenames
are more restricted
On Wed, Jul 15, 2009 at 11:52:24PM +0300, Gleb Natapov wrote:
On Wed, Jul 15, 2009 at 03:18:00PM -0300, Marcelo Tosatti wrote:
On Tue, Jul 14, 2009 at 05:30:45PM +0300, Gleb Natapov wrote:
Use gsi indexed array instead of scanning all entries on each interrupt
injection. Also maintain
Jan Kiszka wrote:
Jamie Lokier wrote:
Jan Kiszka wrote:
Now, I see one significant hurdle with that: it's quite inconvenient
for Windows users, typing paths like c:\path\to\dir\file, if those
backslashes are stipped.
We could exclude Windows from this (I think to remember that filenames
On Wed, Jul 15, 2009 at 11:13:40PM +0300, Michael S. Tsirkin wrote:
This adds a generic uio driver that can bind to any PCI device. First
user will be virtualization where a qemu userspace process needs to give
guest OS access to the device.
Interrupts are handled using the Interrupt
Jan Kiszka wrote:
We would still have to deal with the fact that so far '\' had no special
meaning on Windows - except that is was the well-known path separator.
So redefining its meaning would break a bit...
That's the problem. You will break existing Windows users.
I know this goes
Anthony Liguori wrote:
Jan Kiszka wrote:
We would still have to deal with the fact that so far '\' had no special
meaning on Windows - except that is was the well-known path separator.
So redefining its meaning would break a bit...
That's the problem. You will break existing Windows
Jamie Lokier wrote:
Anthony Liguori wrote:
Jan Kiszka wrote:
We would still have to deal with the fact that so far '\' had no special
meaning on Windows - except that is was the well-known path separator.
So redefining its meaning would break a bit...
That's the problem. You
Anthony Liguori wrote:
Jamie Lokier wrote:
Anthony Liguori wrote:
Jan Kiszka wrote:
We would still have to deal with the fact that so far '\' had no special
meaning on Windows - except that is was the well-known path separator.
So redefining its meaning would break a bit...
On my desktop I have KVM working and one guest running, with the command line:
# kvm -m 512M -net nic -net tap -hda /dev/mapper/pile-evil64 -boot c
-vnc :2 -smp 2 -nographic
Next I need to set up a virtual network for testing. The plan calls
for four guest systems, and two virtual networks,
On Sun, Jul 12, 2009 at 04:10:55PM +0300, Gleb Natapov wrote:
We emulate x2apic in software, so host support is not required.
Signed-off-by: Gleb Natapov g...@redhat.com
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 00844eb..c256da7 100644
--- a/arch/x86/kvm/x86.c
+++
On Wed, Jul 15, 2009 at 6:05 PM, Stephane
Bakhosnuit...@melchior.nuitari.net wrote:
You need to add a vlan option to one of them, for example vlan=2
Otherwise kvm will bridge the interfaces together, and it's going to create
a packet storm.
I wondered about that -- but what's the relationship
You need to add a vlan option to one of them, for example vlan=2
Otherwise kvm will bridge the interfaces together, and it's going to create
a packet storm.
I wondered about that -- but what's the relationship of a KVM vlan to
my existing bridge interfaces, and how can I control which one gets
bridge name bridge id STP enabled interfaces
br0 8000.00144fa1f17a no eth0
tap0
tap1
On Wed, Jul 15, 2009 at 05:54:14PM -0500, Michael Jinks wrote:
Now I want to bring up a VM with two NICs, one attached to tap12
(bridge 0), the other on tap11 (bridge 1), but I think I've
misunderstood the versious -net options as described in the kvm man
page. It *seems* to say that the
On Wed, Jul 15, 2009 at 6:12 PM, Andreas Plesner Jacobsena...@mutt.dk wrote:
On Wed, Jul 15, 2009 at 07:05:48PM -0400, Stephane Bakhos wrote:
You need to add a vlan option to one of them, for example vlan=2
Otherwise kvm will bridge the interfaces together, and it's going to
create a packet
On Wed, Jul 15, 2009 at 07:05:48PM -0400, Stephane Bakhos wrote:
I tried fd= instead of name=, but that looks for a file descriptor
instead of a network interface name, and I didn't even know that Linux
had file descriptors for network interfaces let alone how to map them
to a tap. Nothing
# kvm -m 512M -net nic -net tap,name=tap11 -net nic -net
tap,name=tap12 -hda /vmstore/wee -vnc :11 -cdrom
/path/to/my/Windows.iso -boot d
The parameter is ifname, not name.
In that case, what does the name parameter mean? Quoting from the
manpage on my system:
-net
device tap11 is already a member of a bridge; can't enslave it to bridge br0.
/etc/kvm/kvm-ifup: could not launch network script
Could not initialize device 'tap'
That's because your kvm-ifup scripts tries to connect the tap to the
bridge and it's already there. You should either remove it
Like I said in my other network puzzlement thread, I have one KVM
guest which is working fine. Or, it was until I tried to add a second
one, and hosed my virtual bridge.
The guest is still running, but since I restarted the bridge interface
that its NIC was attached to, it's no longer attached.
On Wed, Jul 15, 2009 at 06:22:56PM -0500, Michael Jinks wrote:
# kvm -m 512M -net nic -net tap,name=tap11 -net nic -net
tap,name=tap12 -hda /vmstore/wee -vnc :11 -cdrom
/path/to/my/Windows.iso -boot d
The parameter is ifname, not name.
In that case, what does the name parameter
On Wed, Jul 15, 2009 at 6:24 PM, Chris Webbch...@arachsys.com 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 bridge
On Wed, Jul 15, 2009 at 6:35 PM, Andreas Plesner Jacobsena...@mutt.dk wrote:
On Wed, Jul 15, 2009 at 06:22:56PM -0500, Michael Jinks wrote:
I suppose that's a good sign, but it still leaves me wondering how to
control which tap connects to which bridge, if I can't attach a guest
to an
On Thu, Jul 16, 2009 at 01:12:19AM +0200, Andreas Plesner Jacobsen wrote:
I tried fd= instead of name=, but that looks for a file descriptor
instead of a network interface name, and I didn't even know that Linux
had file descriptors for network interfaces let alone how to map them
to a
Michael Jinks michael.ji...@gmail.com writes:
How do I make a guest use a specific tap? Quoting
from my initial post, my -net options are:
-net nic -net tap,name=tap11 -net nic -net tap,name=tap12
You want
-net nic,vlan=0 -net tap,vlan=0,ifname=tap11 -net nic,vlan=1 -net
Another monitor command question: trying to rescue my de-networked
guest, I thought I'd try connecting to the console, but in its
monitor:
(qemu) info vnc
Server: disabled
According to the command line where I started this kvm instance, vnc
should be enabled. Maybe it died? Is there a way to
Michael Jinks wrote:
On Wed, Jul 15, 2009 at 6:24 PM, Chris Webbch...@arachsys.com 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
Jamie Lokier wrote:
So instead of consistency, you like the idea of using different
quoting rules for the monitor than for command line arguments?
Your proposal breaks Windows in a catastrophic way. It's almost certain
that all existing front-ends/scripts will stop working after such a
Previously the KVM kernel module would allocate the address range
of 0xfffbc000-0xfffbcfff for the EPT Indentity Page Tables.
This change moves that to 0xfeffc000-0xfeffcfff.
Another issue related to this change is the VMC TSS Pages were
located at 0xfffbd000-0xfffb. This is controlled by
Previously the KVM kernel module would allocate the address range
of 0xfffbc000-0xfffbcfff for the EPT Indentity Page Tables.
A separate patch is moving that to 0xfeffc000-0xfeffcfff.
This patch updates qemu-kvm to move the VMX TSS Pages update the
KVM BIOS code to update the E820 BIOS call
I'm not sure if I'm having VNC trouble, or KVM trouble.
I'm using vinagre as my VNC client, connecting to localhost. Usually
I use TightVNC but Avi says it's broken, and it sure won't attach to a
QEMU server.
Both work fine if I connect to one of my own VNC servers (Linux).
Against a KVM
After finishing some Windows guest setups, I've now discovered thet
vinagre's send ctl-alt-delete button doesn't work either.
I'm installing the old VNC package now, hoping it's better...
On Wed, Jul 15, 2009 at 7:24 PM, Michael Jinksmichael.ji...@gmail.com wrote:
I'm not sure if I'm having
On Thursday 16 July 2009 08:12:15 Jordan Justen wrote:
Previously the KVM kernel module would allocate the address range
of 0xfffbc000-0xfffbcfff for the EPT Indentity Page Tables.
A separate patch is moving that to 0xfeffc000-0xfeffcfff.
Hi Jordan
You need one more patch for upstream kvm, to
On Thursday 16 July 2009 07:01:30 Marcelo Tosatti wrote:
On Sun, Jul 12, 2009 at 04:10:55PM +0300, Gleb Natapov wrote:
We emulate x2apic in software, so host support is not required.
Signed-off-by: Gleb Natapov g...@redhat.com
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index
On Wed, 2009-07-15 at 22:04 +0100, Jamie Lokier wrote:
Ram Pai wrote:
I have successfully verified qcow2 files. But then I may not be trying
out the exact thing that you are talking about. Can you give me a test
case that I can verify.
Commands tried with qemu-0.10.0-1ubuntu1:
$
On 07/15/2009 09:36 PM, Dor Laor wrote:
On 07/15/2009 12:12 PM, Yolkfull Chow wrote:
Would submit this patch which is from our internal kvm-autotest
patches submitted by Jason.
So that we could go on test case about parameters verification(UUID,
DMI data etc).
Signed-off-by: Yolkfull
On Wed, Jul 15, 2009 at 6:34 PM, Sheng Yang sh...@linux.intel.com wrote:
On Thursday 16 July 2009 08:12:15 Jordan Justen wrote:
Previously the KVM kernel module would allocate the address range
of 0xfffbc000-0xfffbcfff for the EPT Indentity Page Tables.
A separate patch is moving that to
On Wed, Jul 15, 2009 at 8:04 PM, Michael Jinksmichael.ji...@gmail.com wrote:
I'm installing the old VNC package now, hoping it's better...
Nope, it's worse. Carries the same sort of failure to connect that I
saw with TightVNC, immediate failure and Rect too big to stderr.
Has the world moved
On Thursday 16 July 2009 10:58:53 Jordan Justen wrote:
On Wed, Jul 15, 2009 at 6:34 PM, Sheng Yang sh...@linux.intel.com wrote:
On Thursday 16 July 2009 08:12:15 Jordan Justen wrote:
Previously the KVM kernel module would allocate the address range
of 0xfffbc000-0xfffbcfff for the EPT
On Thu, Jul 16, 2009 at 8:12 AM, Yolkfull Chowyz...@redhat.com wrote:
On 07/15/2009 09:36 PM, Dor Laor wrote:
On 07/15/2009 12:12 PM, Yolkfull Chow wrote:
Would submit this patch which is from our internal kvm-autotest
patches submitted by Jason.
So that we could go on test case about
Thats great Michael !!
On Wed, Jul 15, 2009 at 8:56 PM, Michael Goldishmgold...@redhat.com wrote:
- Lucas Meneghel Rodrigues l...@redhat.com wrote:
On Wed, Jul 8, 2009 at 4:46 AM, Michael Goldishmgold...@redhat.com
wrote:
I'm resending the message because it probably got filtered out
On Wed, Jul 15, 2009 at 8:08 PM, Sheng Yangsh...@linux.intel.com wrote:
On Thursday 16 July 2009 10:58:53 Jordan Justen wrote:
On Wed, Jul 15, 2009 at 6:34 PM, Sheng Yang sh...@linux.intel.com wrote:
On Thursday 16 July 2009 08:12:15 Jordan Justen wrote:
Motivation for making these
1 - 100 of 103 matches
Mail list logo
