Re: Fail to create disk.img (SOLVED)

[Soren Hansen <soren@ubuntu.com>]

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

On Thu, Aug 07, 2008 at 02:37:03PM +0800, Stephen Liu wrote:
>>> On running $ sudo kvm-bridge -m 512 -hdb disk.img -cdrom /dev/scd0
>>> -boot d -smp 2
>>> nohup: appending output to `nohup.out'
>>> It always appends output to `nohup.out'
>> What is the problem?
> Hi Soren,

Hello.

> What I have been trying around is to solve networking problem on VM.

How is that related to appending output to nohup.out?

> However it is quite slow on booting and on starting other Window
> applications as well.  IIRC during installing KVM packages I came
> across a document on Internet informing me to install a package
> qemu-??? (something like that).  

I have no clue as to what this might be.

> Following packages have been installed on Host
> kqemu-common
> kqemu-source
> kqemu-modules

kqemu has nothing to do with kvm. It's a different means for
"accelerating" qemu.

> Each time to start Vista I have to run;
> # kvm -hdb vista.img -cdrom /dev/scd0 -m 1024 -vnc :1
> 
> and put the Vista installer on CDRom.  The above command was run by me
> creating vista.img
> 
> 
> If running;
> # kvm vista.img -vnc :1
> 
> I can't start Vista.  

Stephen, this shall be my last e-mail to you.

Having to explain everything multiple times is tiring, and a very poor
use of my (or anyone's) time. This particular issue, I've already
explained twice; both times in this thread. Last time was in the very
e-mail to which you have just responded. I find it mind boggling that I
need to remind you that this list is read by many people, most of whom
are very busy.  Yet you have the audacity to ask the same questions and
report the same "problems" over and over. I shall not allow you to steal
any more of my time, so you have just become only the second person ever
to be redirected to /dev/null (in case you don't know what /dev/null is,
it's where I keep all my very special e-mail).

For the third time: When you put "-hdb vista.img" on your command line,
you're attaching vista.img as primary slave. If you put "-hda vista.img"
or just "vista.img" you're attaching it as primary master. Very few
bootloaders will be happy about being installed in one place only to be
moved to another place when actually booting. It seems Vista's
bootloader is no different.

-- 
Soren Hansen               | 
Virtualisation specialist  | Ubuntu Server Team
Canonical Ltd.             | http://www.ubuntu.com/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]