Martin Maurer wrote:
Using IDE boot disk, no problem. Win2008 (64bit) works without any problems - 6 
gb ram in the guest.

After successful booting IDE, I added a second disk using SCSI: windows see the 
disk but cannot initialize the disk.

So SCSI looks quite unusable if you run windows guest (win2003 sp2 also stops 
during install), or should we load any SCSI driver during setup? Win2008 uses 
LSI Logic 8953U PCI SCSI Adapter, 53C895A Device (LSI Logic Driver 4.16.6.0, 
signed)

Any other expierences running SCSI on windows?

You're right, its broken right now :(
At least ide is stable.
Best Regards,

Martin

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Martin Maurer
Sent: Donnerstag, 24. Juli 2008 11:46
To: kvm@vger.kernel.org
Subject: RE: scsi broken > 4GB RAM

Sorry, just returned to the installer - also stopped with the same
error code, using just 2 gb ram.

Best Regards,

Martin Maurer

[EMAIL PROTECTED]
http://www.proxmox.com

____________________________________________________________________
Proxmox Server Solutions GmbH
Kohlgasse 51/10, 1050 Vienna, Austria
Phone: +43 1 545 4497 11 Fax: +43 1 545 4497 22
Commercial register no.: FN 258879 f
Registration office: Handelsgericht Wien


-----Original Message-----
From: Martin Maurer
Sent: Donnerstag, 24. Juli 2008 11:44
To: kvm@vger.kernel.org
Subject: RE: scsi broken > 4GB RAM

Hi,

I tried windows server 2008 (64 bit) on Proxmox VE 0.9beta2 (KVM 71),
see http://pve.proxmox.com):

Some details:
--memory 6144 --cdrom
en_windows_server_2008_datacenter_enterprise_standard_x64_dvd_X14-
26714.iso --name win2008-6gb-scsi --smp 1 --bootdisk scsi0 --scsi0 80

The installer shows 80 GB harddisk but freezes after clicking next
for
a minute then:

"Windows could not creat a partition on disk 0. The error occurred
while preparing the computerĀ“s system volume. Error code:
0x8004245F."
I also got installer problems if I just use scsi as boot disk (no
high
memory) on several windows versions, including win2003 and xp. So I
decided to use IDE, works without any issue on windows.

But: I reduced the memory to 2048 and the installer continues to
work!
Best Regards,

Martin Maurer

[EMAIL PROTECTED]
http://www.proxmox.com

____________________________________________________________________
Proxmox Server Solutions GmbH
Kohlgasse 51/10, 1050 Vienna, Austria
Phone: +43 1 545 4497 11 Fax: +43 1 545 4497 22
Commercial register no.: FN 258879 f
Registration office: Handelsgericht Wien


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
Behalf Of Henrik Holst
Sent: Mittwoch, 23. Juli 2008 23:09
To: kvm@vger.kernel.org
Subject: scsi broken > 4GB RAM

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 larger the scsi emulated disk fails in the Linux guest.

If booting any install cd the /dev/sda is seen as only 512B in size
and if booting an ubuntu 8.04-amd64 with the secondary drive as
scsi
it is seen with the correct size but one cannot read not write the
partition table.

Is there anyone out there that could test say a Windows image on
scsi
with 4GB or more of RAM and see 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
--
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


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

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

Reply via email to