2008/5/26 Henrik Holst <[EMAIL PROTECTED]>:
>
> We have performed some quick benchmarks against kvm-69 on an Intel Q6600
> with 8GB RAM and equipped with 4 SATA drives (Maxtor DiamondMax 10
> 6V300F0).
>
> During these tests we noticed a problem with the virtio bl
ee if it works or not? If so it could be
the linux driver that is faulty.
/Henrik Holst
--
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
2008/7/23 Henrik Holst <[EMAIL PROTECTED]>
>
> I do not know if this is a bug in qemu or the linux kernel sym53c8xx
> module (I haven't had the opportunity to test with anything other than
> Linux at the moment) but if one starts an qemu instance with -m 4096
> and lar
the newer
isolinux menus to work but the older isolinux (for example the
installer to ubuntu 7.10) still does not work. It no longer segfaults
though but instead the guest completely hangs. Much improvement
though!
/Henrik Holst
--
To unsubscribe from this list: send the line "unsubscribe kvm&qu
2008/7/28 Anthony Liguori <[EMAIL PROTECTED]>:
> Henrik Holst wrote:
>>
>> There is a boot regression in kvm-72:
>>
>> scsi and virtio images will not survive a "reboot" from within the
>> guest. Only drives with if=ide survives a rebooting of t
2008/7/28 Henrik Holst <[EMAIL PROTECTED]>:
> 2008/7/28 Anthony Liguori <[EMAIL PROTECTED]>:
>> Henrik Holst wrote:
>>>
>>> There is a boot regression in kvm-72:
>>>
>>> scsi and virtio images will not survive a "reboot" from wi
dows guests so far ?
yes and there does exist a windows driver (I do think that it only
contains a driver for the PV network card though). It can be
downloaded from the sourceforge page:
http://sourceforge.net/project/showfiles.php?group_id=180599&package_id=267943
/Henrik Holst
--
To unsu
>Performed following test but failed.
>
># kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc IP:0
>Could not parse VNC address
>
># kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc IP:1
>Could not parse VNC address
You should run it as:
# kvm -hda ubun
p that you are writing
on right now!). If you install it on the same machine that you run
qemu/kvm on then simply put 127.0.0.1 as the remote server.
/Henrik Holst
--
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
his will boot just fine:
qemu -m 256 -drive file=test.img,if=ide,media=disk -boot c
So I will have to dig into previous revisions of qemu to see where it
went wrong.
/Henrik Holst
--
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
2008/7/28 Henrik Holst <[EMAIL PROTECTED]>:
>> Since this probably is due to something in qemu it would be great if
>> the release-log to kvm could include towards which revision of the
>> qemu svn repository that was merged. Or am I to understand that the
>> merge wa
1 makes it work so there is
still something very strange going on.
I have tried to locate what it might be but cannot find why ide devices
survives the reboot while scsi and virtio does not...
On the plus side it seams like kvm-73 fixed one issue for us where a
ubuntu-8.04-i386 server guest run
n one guest
so the second one cannot bind to port 5900.
/Henrik Holst
--
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
oot from Hard Disk failed: could not read boot disk
>> ... More failed boot devices that shouldn't boot anyway...
>> FATAL: No bootable device
>>
>>
>
> This was caused by the extboot rom writing into itself, thus failing
> checksum on the next reboot. I fixed
2008-06-17 14:09:07.0 +0200
@@ -15,3 +15,6 @@
# Translate Menu to the Windows Application key.
Menu 0xdd
+
+# AltGR
+ISO_Level3_Shift 0xb8
regards, Henrik Holst
Witsbits AB
--
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
t is worth, I can now confirm the fix. You have no idea the
happiness that this is giving me :)
Now if only scsi would work for guest with more than 4GB ram or on
BSD ;)
Regards, Henrik Holst
Witsbits AB
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a
got applied in 2.6.26.3 and 2.6.25.16.
> > >
> >
> > So it was some signaling-bug on the .. client side?
>
> No, it was a kernel race condition causing the qemu-kvm process to stop
> receiving SIGALRM signals.
So is it the host kernel that should be patched?
/Henrik Holst
Witsbits AB
--
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
ind anything in the FAQ.
That should be possible with KVM as long as you have a cpu that supports
the extensions that KVM needs:
http://kvm.qumranet.com/kvmwiki/Documents/processor_support
If not you will have to use pure qemu which is quite a bit slower:
http://bellard.org/qemu/ or try with VMWa
mån 2008-10-13 klockan 11:44 +0200 skrev Henrik Holst:
> mån 2008-10-13 klockan 11:33 +0200 skrev Henrik Holst:
> > "segmentation fault" lines, probably from modprobe
> >
> > Ubuntu-8.04 boots just fine under kvm-77 so it feels like a mismatch
> > with the gu
e errors what so ever.
If giving the guest more than 2GiB of memory there is a stream of
"segmentation fault" lines, probably from modprobe
Ubuntu-8.04 boots just fine under kvm-77 so it feels like a mismatch
with the guest 2.6.27 kernel. Tested both 2.27-4 and 2.27-7 to no avail.
The ho
mån 2008-10-13 klockan 11:33 +0200 skrev Henrik Holst:
> "segmentation fault" lines, probably from modprobe
>
> Ubuntu-8.04 boots just fine under kvm-77 so it feels like a mismatch
> with the guest 2.6.27 kernel. Tested both 2.27-4 and 2.27-7 to no avail.
Encountered the
0x110/0x215
Mar 7 19:30:47 prince kernel: [12310060.704319] []
sys_execve+0x35/0x4c
Mar 7 19:30:47 prince kernel: [12310060.704319] []
stub_execve+0x6a/0xc0
Regards, Henrik Holst
Witsbits AB
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a me
2010/3/8 Jan Kiszka :
> Henrik Holst wrote:
>> Hi,
>>
>> I'm running a few Debian Lenny host machines with kernel 2.6.26, in
>> production we use kvm-kmod-2.6.31.5 without any problems. Today I
>> tested to change to kvm-kmod-2.6.33 and everything went just
without success.
cache=writeback and cache=off was a little bit better than the default
cache=writethrough but not with any useful improvement.
/Henrik Holst
https://Witsbits.com - Utility Computing
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message
ons 2008-11-19 klockan 12:26 -0600 skrev Anthony Liguori:
> Ryan Harper wrote:
> > * Henrik Holst <[EMAIL PROTECTED]> [2008-11-18 08:42]:
> >
> >> The bundled qemu in kvm-78 and kvm-79 slows down disk i/o with qcow2
> >> images by an order of 10. If
s OK
again. I must have misspelled somehow and qemu didn't quit on me or
there was something else going on at the time of my tests.
Thanks!
/Henrik Holst
https://witsbits.com
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL P
mån 2008-12-15 klockan 12:26 +0200 skrev Avi Kivity:
> Henrik Holst wrote:
> > Now I haven't tried kvm-81 but scsi with 4GB of RAM or more is severely
> > broken in QEMU for all other tested KVM versions (80 and downwards).
> >
>
> kvm-81 contains this:
>
&
e potential for severe data loss
> with the latter option).
>
Now I haven't tried kvm-81 but scsi with 4GB of RAM or more is severely
broken in QEMU for all other tested KVM versions (80 and downwards).
/Henrik Holst
--
To unsubscribe from this list: send the line "unsubscribe kv
28 matches
Mail list logo