OpenSolaris 09/2007 (Sun Solaris Express)

OpenSolaris 09/2007 (Sun Solaris Express)

[magicboiz]

[-- Attachment #1: Type: text/plain, Size: 238 bytes --]

Hi list,

you I always report OS that do not start with kvm.... :))

Sun Solaris Express(9/07), does not detect the hard disk......I attach
an screenshot.

Kernel:2.6.23
kvm: 45 and 46
CPU: Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz

[-- Attachment #2: Pantallazo-QEMU-KVM-Solaris.png --]
[-- Type: image/png, Size: 15012 bytes --]

[-- Attachment #3: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: OpenSolaris 09/2007 (Sun Solaris Express)

[Carlo Marcelo Arenas Belon]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

On Wed, Oct 10, 2007 at 03:53:10PM +0200, magicboiz wrote:
> Sun Solaris Express(9/07), does not detect the hard disk......I attach
> an screenshot.

from the screenshot it seems that the problem is not with the hard disk but
with the cdrom.

attached patch to qemu (not yet committed upstream) fixed that problem for me.

Carlo

[-- Attachment #2: qemu-get-configuration.patch --]
[-- Type: text/plain, Size: 2928 bytes --]

Index: hw/ide.c
===================================================================
RCS file: /sources/qemu/qemu/hw/ide.c,v
retrieving revision 1.72
diff -u -p -r1.72 ide.c
--- hw/ide.c	18 Nov 2007 01:44:37 -0000	1.72
+++ hw/ide.c	26 Nov 2007 07:43:43 -0000
@@ -541,7 +541,7 @@ static void ide_atapi_identify(IDEState 
     put_le16(p + 21, 512); /* cache size in sectors */
     put_le16(p + 22, 4); /* ecc bytes */
     padstr((uint8_t *)(p + 23), QEMU_VERSION, 8); /* firmware version */
-    padstr((uint8_t *)(p + 27), "QEMU CD-ROM", 40); /* model */
+    padstr((uint8_t *)(p + 27), "QEMU DVD-ROM", 40); /* model */
     put_le16(p + 48, 1); /* dword I/O (XXX: should not be set on CDROM) */
 #ifdef USE_DMA_CDROM
     put_le16(p + 49, 1 << 9 | 1 << 8); /* DMA and LBA supported */
@@ -1630,12 +1630,13 @@ static void ide_atapi_cmd(IDEState *s)
         buf[6] = 0; /* reserved */
         buf[7] = 0; /* reserved */
         padstr8(buf + 8, 8, "QEMU");
-        padstr8(buf + 16, 16, "QEMU CD-ROM");
+        padstr8(buf + 16, 16, "QEMU DVD-ROM");
         padstr8(buf + 32, 4, QEMU_VERSION);
         ide_atapi_cmd_reply(s, 36, max_len);
         break;
     case GPCMD_GET_CONFIGURATION:
         {
+            uint32_t len;
             int64_t total_sectors;
 
             /* only feature 0 is supported */
@@ -1644,17 +1645,27 @@ static void ide_atapi_cmd(IDEState *s)
                                     ASC_INV_FIELD_IN_CMD_PACKET);
                 break;
             }
-            memset(buf, 0, 32);
+            max_len = ube16_to_cpu(packet + 7);
             bdrv_get_geometry(s->bs, &total_sectors);
-            buf[3] = 16;
-            buf[7] = total_sectors <= 1433600 ? 0x08 : 0x10; /* current profile */
-            buf[10] = 0x10 | 0x1;
-            buf[11] = 0x08; /* size of profile list */
+            memset(buf, 0, 32);
+            if (total_sectors) {
+                if (total_sectors > 1433600) {
+                    buf[7] = 0x10; /* DVD-ROM */
+                } else {
+                    buf[7] = 0x08; /* CD-ROM */
+                }
+            } else {
+                buf[7] = 0x00; /* no current profile */
+            }
+            buf[10] = 0x02 | 0x01; /* persistent and current */
+            buf[11] = 0x08; /* size of profile list = 4 bytes per profile */
             buf[13] = 0x10; /* DVD-ROM profile */
-            buf[14] = buf[7] == 0x10; /* (in)active */
+            buf[14] = buf[13] == buf[7]; /* (in)active */
             buf[17] = 0x08; /* CD-ROM profile */
-            buf[18] = buf[7] == 0x08; /* (in)active */
-            ide_atapi_cmd_reply(s, 32, 32);
+            buf[18] = buf[17] == buf[7]; /* (in)active */
+            len = 8 + 4 + buf[11]; /* headers + size of profile list */
+            cpu_to_ube32(buf, len - 4); /* data length */
+            ide_atapi_cmd_reply(s, len, max_len);
             break;
         }
     default:

[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: OpenSolaris 09/2007 (Sun Solaris Express)

[magicboiz]

Well done Carlo.

The patch works perfectly with my OpenSolaris and kvm-53.

Thx!

El lun, 26-11-2007 a las 19:31 -0600, Carlo Marcelo Arenas Belon
escribió:
> On Wed, Oct 10, 2007 at 03:53:10PM +0200, magicboiz wrote:
> > Sun Solaris Express(9/07), does not detect the hard disk......I attach
> > an screenshot.
> 
> from the screenshot it seems that the problem is not with the hard disk but
> with the cdrom.
> 
> attached patch to qemu (not yet committed upstream) fixed that problem for me.
> 
> Carlo


-------------------------------------------------------------------------
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
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: OpenSolaris 09/2007 (Sun Solaris Express)

[Avi Kivity]

magicboiz wrote:
> Well done Carlo.
>
> The patch works perfectly with my OpenSolaris and kvm-53.
>
>   

Good to know.

> Thx!
>
> El lun, 26-11-2007 a las 19:31 -0600, Carlo Marcelo Arenas Belon
> escribió:
>   
>> On Wed, Oct 10, 2007 at 03:53:10PM +0200, magicboiz wrote:
>>     
>>> Sun Solaris Express(9/07), does not detect the hard disk......I attach
>>> an screenshot.
>>>       
>> from the screenshot it seems that the problem is not with the hard disk but
>> with the cdrom.
>>
>> attached patch to qemu (not yet committed upstream) fixed that problem for me.
>>     

Has it been submitted?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: OpenSolaris 09/2007 (Sun Solaris Express)

[Carlo Marcelo Arenas Belon]

On Tue, Nov 27, 2007 at 10:22:57PM +0200, Avi Kivity wrote:
> magicboiz wrote:
> > Well done Carlo.
> >
> > The patch works perfectly with my OpenSolaris and kvm-53.
> 
> Good to know.

Also tested it with Nexenta alpha 7, and Indiana and had it added as part
of my gentoo package for kvm-54

> >> attached patch to qemu (not yet committed upstream) fixed that problem for me.
> >>     
> 
> Has it been submitted?

yes, as can be seen in :

  http://lists.gnu.org/archive/html/qemu-devel/2007-11/msg00758.html

no response yet, but I'll try a RESEND tomorrow

Carlo

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

real mode emulation and memory consumption

[Kamble, Nitin A]

Hi Avi,
 I am noticing that with SL 10.1 The QEMU process memory consumption
steadily increases, up the the guest memory size and then the guest dies
with unhandled vmexit. If I change the guest memory size I can see the
qemu process dies accordingly, after reaching the size of allotted guest
memory.
  Does this hint you to any issues?

Thanks & Regards,
Nitin
Linux Open Source Technology Center, Intel Corporation
------------------------------------------------------------------------
----

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Re: real mode emulation and memory consumption

[Kamble, Nitin A]

>-----Original Message-----
>From: Kamble, Nitin A
>Sent: Tuesday, November 27, 2007 5:05 PM
>To: 'Avi Kivity'
>Cc: kvm-devel
>Subject: real mode emulation and memory consumption
>
>Hi Avi,
> I am noticing that with SL 10.1 The QEMU process memory consumption
>steadily increases, up the the guest memory size and then the guest
dies
>with unhandled vmexit. If I change the guest memory size I can see the
qemu
>process dies accordingly, after reaching the size of allotted guest
memory.
>  Does this hint you to any issues?

BTW this is the behavior with master branch without any changes.

>
>Thanks & Regards,
>Nitin
>Linux Open Source Technology Center, Intel Corporation
>-----------------------------------------------------------------------
----
>-

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Re: real mode emulation and memory consumption

[Avi Kivity]

Kamble, Nitin A wrote:
> Hi Avi,
>  I am noticing that with SL 10.1 The QEMU process memory consumption
> steadily increases, up the the guest memory size and then the guest dies
> with unhandled vmexit. If I change the guest memory size I can see the
> qemu process dies accordingly, after reaching the size of allotted guest
> memory.
>   Does this hint you to any issues?
>
>   

Are you talking about RSS?  That's normal behavior (except for the 
untimely death).  kvm allocates memory on demand, like regular Linux 
processes.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Re: real mode emulation and memory consumption

[Kamble, Nitin A]

>Kamble, Nitin A wrote:
>> Hi Avi,
>>  I am noticing that with SL 10.1 The QEMU process memory consumption
>> steadily increases, up the the guest memory size and then the guest
dies
>> with unhandled vmexit. If I change the guest memory size I can see
the
>> qemu process dies accordingly, after reaching the size of allotted
guest
>> memory.
>>   Does this hint you to any issues?
>>
>>
>
>Are you talking about RSS?  That's normal behavior (except for the
>untimely death).  kvm allocates memory on demand, like regular Linux
>processes.
>

Yes, the RES column in the TOP. Why is it normal behavior? I see the
guest is looping in the boot-loader switching between real mode and
protected mode without make any progress, and at the same time the
residential memory consumption of the qemu process is steadily
increasing, and once it crosses the amount of physical memory configured
for the guest, the KVM driver gets the invalid vmexit.
  The interesting part is if I change the amount of physical memory to
the guest, the time when the guest dies changes accordingly, and looking
at the top output one can predict when it is going to crash.
  Where is that memory getting consumed in the qemu process? Why is it
affecting the KVM driver?

Thanks & Regards
Nitin

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Re: real mode emulation and memory consumption

[Avi Kivity]

Kamble, Nitin A wrote:
>> Kamble, Nitin A wrote:
>>     
>>> Hi Avi,
>>>  I am noticing that with SL 10.1 The QEMU process memory consumption
>>> steadily increases, up the the guest memory size and then the guest
>>>       
> dies
>   
>>> with unhandled vmexit. If I change the guest memory size I can see
>>>       
> the
>   
>>> qemu process dies accordingly, after reaching the size of allotted
>>>       
> guest
>   
>>> memory.
>>>   Does this hint you to any issues?
>>>
>>>
>>>       
>> Are you talking about RSS?  That's normal behavior (except for the
>> untimely death).  kvm allocates memory on demand, like regular Linux
>> processes.
>>
>>     
>
> Yes, the RES column in the TOP. Why is it normal behavior? 

When the guest accesses a page for the first time, it is added to RSS. 
When Linux swaps it out, it is removed from RSS.

> I see the
> guest is looping in the boot-loader switching between real mode and
> protected mode without make any progress, and at the same time the
> residential memory consumption of the qemu process is steadily
> increasing, and once it crosses the amount of physical memory configured
> for the guest, the KVM driver gets the invalid vmexit.
>   

Well, this part is not normal ;)  however I have no insight as to why it
is happening.

>   The interesting part is if I change the amount of physical memory to
> the guest, the time when the guest dies changes accordingly, and looking
> at the top output one can predict when it is going to crash.
>   Where is that memory getting consumed in the qemu process? Why is it
> affecting the KVM driver?

It's probably just a bug with a surprising side effect.  Maybe it is a
memory-clearing loop gone wild.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4