OpenBSD geometry disk problem

Hello,

I'm trying tu play with OpenBSD into KVM-36, and I find KVM has the same issue that had VirtualBox: OpenBSD cannot detect the disk geometry due to a timeout......Check this out:
http://forums.virtualbox.org/viewtopic.php?p=4522

Someone else with the same problem?

Regards

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

what happen when you run it with --no-kvm?
is it still happen?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

it works!!!

Great :)

Regards.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

ohh, wait it mean we have bug in kvm!
and runing with --no-kvm mean your guest will run very slow. please tell us what is the cpu you use, and the exact message you get plus is it after installtion? in the middle? after boot? while booting? please give as much information as you can.
thansk

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

yes, it runs slowly.....

My config:

CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
Kernel: 2.6.22 (ubuntu 2.6.22-10-generic)
KVM: 36 and 35 tested.

I attach you two screenshots:

- In the first one, you can see at the bottom, how OpenBSD 4.2 kernel
detects an invalid disk geometry. In fact, the kernel does not detect nothing, so it supposes that there is a ST506 disk.

- In the second screenshot, you have kernel messages of timeout while
accessing the disk.

Nothing of this happens with no-kvm flag enabled. I also tried with no-acpi flag, but with the same results.

Regards,
Javier.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

This may be related to the large memory support. Maybe we are overwriting the disk geometry information in nvram.

Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

this bug started at commit 091b206f6c56f2329e11bac2fa40d6f236ab0bc2 and it related to the changes that were made in vmx.c

Laurent, can you help us with this?
(openbsd find the harddisk to be 68mb while it should be 2048mb)

thanks.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Of course.

Could you provide me the disk image (or how to create one) ?

Laurent

------------- Laurent.Vivier-6ktuUTfB/[email protected]  --------------
          "Software is hard" - Donald Knuth

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

i just created image of 2giga:
qemu-img create -f qcow disk.img 2G

and ran it with the openbsd41-i386-07-05-06.iso i searched now in good this seems like link to it:
http://ftp.twaren.net/BSD/OpenBSD/iso/4.1/openbsd41-i386-07-05-06.iso

you dont have to install or to do anything like that, the during the boot from the cd.

thanks!

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

and it only does that when running under kvm, -no-kvm (AKA qemu in emulated mode) gets it right :

"Intel 82371SB ISA" rev 0x00 at pci0 dev 1 function 0 not configured pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <QEMU HARDDISK>
wd0: 16-sector PIO, LBA48, 2048MB, 419434 sectors wd0(pciide0:0:0): using PIO mode 0, DMA mode 2

Carlo

PS. using the last OpenBSD pre4.2 snapshot iso (install42.iso) from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

This patch correct the disk probe problem met with OpenBSD.

This issue appears with commit 091b206f6c56f2329e11bac2fa40d6f236ab0bc2 because before it, the decoding was done internally to kvm and after it is done by x86_emulate.c (which doesn't do it correctly).

---
 drivers/kvm/x86_emulate.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

index 9e2b27a..f294a49 100644
@@ -586,11 +586,10 @@ x86_decode_insn(struct x86_emulate_ctxt *ctxt, struct x86_emulate_ops *ops)
 		case 0xf0:	/* LOCK */
 			c->lock_prefix = 1;
 			break;
+		case 0xf2:	/* REPNE/REPNZ */
 		case 0xf3:	/* REP/REPE/REPZ */
 			c->rep_prefix = 1;
 			break;
-		case 0xf2:	/* REPNE/REPNZ */
-			break;
 		default:
 			goto done_prefixes;
 		}

1.5.2.4


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

thanks.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Applied, thanks.

error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/