From mboxrd@z Thu Jan 1 00:00:00 1970 From: Soren Hansen Subject: Re: Fail to create disk.img (SOLVED) Date: Thu, 7 Aug 2008 09:14:37 +0200 Message-ID: <20080807071437.GA7244@ralph.linux2go.dk> References: <20080805125116.GE13674@ralph.linux2go.dk> <285610.49651.qm@web35201.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" To: kvm@vger.kernel.org Return-path: Received: from atlas.linux2go.dk ([88.198.22.52]:35348 "EHLO atlas.linux2go.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754364AbYHGHOk (ORCPT ); Thu, 7 Aug 2008 03:14:40 -0400 Received: from localhost (0107ds1-abv.0.fullrate.dk [90.185.52.147]) by atlas.linux2go.dk (Postfix) with ESMTP id C557C40A35D for ; Thu, 7 Aug 2008 09:14:37 +0200 (CEST) Content-Disposition: inline In-Reply-To: <285610.49651.qm@web35201.mail.mud.yahoo.com> Sender: kvm-owner@vger.kernel.org List-ID: --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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). =20 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 >=20 > and put the Vista installer on CDRom. The above command was run by me > creating vista.img >=20 >=20 > If running; > # kvm vista.img -vnc :1 >=20 > I can't start Vista. =20 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. --=20 Soren Hansen |=20 Virtualisation specialist | Ubuntu Server Team Canonical Ltd. | http://www.ubuntu.com/ --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iJwEAQECAAYFAkiaoNwACgkQo+Mz6+DAzGxHaQP+IT7plf4tD91p90a8BzUXY0Ll n/QT19X0sKPxFmiZ9mdr4Wr2ka7C1YsmFqMtjoEQpqyvyLZWoHuzZZ4N7unyiRi0 Ce3pGqiSsyVIkRMorAGUNwKGeeFzqsblBl6lZ3vrZWQf29oun0ljbkGnvRbMPRFS QUQCz14RO0wtGnFyfPs= =iPrL -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--