tries
to probe a windows 7 on second disk (KVM)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system adminis
2021-04-06 23:13 GMT-04:00, Arnaud Rebillout :
> Dear Maintainer,
>
> hw-detect already installs the package qemu-guest-agent when kvm/qemu
> virtualization is detect, in 'hw-detect.finish-install.d/08hw-detect':
>
> kvm|qemu)
> apt-install --with-recommends qem
Package: hw-detect
Severity: normal
User: de...@kali.org
Usertags: origin-kali
Dear Maintainer,
hw-detect already installs the package qemu-guest-agent when kvm/qemu
virtualization is detect, in 'hw-detect.finish-install.d/08hw-detect':
kvm|qemu)
apt-install --with-recommends qemu
-07-12 business card in KVM
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no ide
011-08-01 encrypted LV in KVM
VM
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have n
esting as a VM in virtualbox
/ kvm gives me an error: no kernel modules were found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith
Your message dated Sun, 2 Aug 2020 11:59:33 +0200
with message-id <20200802115933.cf302c905408a94a8ab7f...@mailbox.org>
and subject line Re: #825793 Installing the lilo bootloader on a qemu/kvm VM
fails
has caused the Debian Bug report #825793,
regarding Installing the lilo bootloader on
Marvin Renich wrote (30 May 2016 01:39:01):
> Installing lilo bootloader on qemu/kvm virtual machine fails.
lilo-installer has been removed, so closing this bug.
Holger
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Package: installation-reports
Severity: normal
Tags: d-i
Dear Maintainer,
-- Package-specific info:
Boot method: CD
Image version: debian testing dvd rom - build date 28/10/2019
Date:
Machine: lenovo thinkpad x200
Partitions:
Base System Installation Checklist:
[O] = OK, [E] = Error
ot; step in the
installer). This seems like more of a bug with how apt-get handles
failure. Is there a way to reassign this bug to that package?
Thanks,
Zach
Control: tag -1 - d-i
Hi Zachary,
And thanks for your report.
Zachary Palmer (2019-01-23):
I am installing Debian 9.6 usin
Processing control commands:
> tag -1 - d-i
Bug #920284 [debian-installer] debian-installer: Installing Debain 9.6 on amd64
KVM via netinst fails in "select and install software"
Removed tag(s) d-i.
--
920284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920284
Debian Bug Tr
Control: tag -1 - d-i
Hi Zachary,
And thanks for your report.
Zachary Palmer (2019-01-23):
> I am installing Debian 9.6 using a netinst image on an amd64 virtual
> machine (kvm). Everything runs as expected until the "Select and
> Install Software" step, which fails with
Package: debian-installer
Severity: important
Tags: d-i
Dear Maintainer,
I am installing Debian 9.6 using a netinst image on an amd64 virtual machine
(kvm). Everything runs as expected until the "Select and Install Software"
step, which fails with the generic message "Installat
age, and it's what I generally
>>>> use to install on real hardware.
>>>>
>>>> I'm less familiar with netboot, but have used it for PXE installs (right?)
>>>>
>>>> What I'm missing is how I can use either of them on a remote KVM VPS,
>&
On 12/08/18 11:20, Jose R R wrote:
> UpCloud provide a similar interface to Virt-Manager when installing
> your own OS. They address the issue being discussed here -- by
> describing 'a trick' to install your own OS:
Thanks Jose - I don't think this method is applicable to my
situation/provider,
miliar with the netinst image, and it's what I generally
>> > > use to install on real hardware.
>> > >
>> > > I'm less familiar with netboot, but have used it for PXE installs
>> > > (right?)
>> > >
>> > > What I'm missi
; use to install on real hardware.
> > >
> > > I'm less familiar with netboot, but have used it for PXE installs (right?)
> > >
> > > What I'm missing is how I can use either of them on a remote KVM VPS,
> > > where I get to see the boot process on some kind
sed it for PXE installs (right?)
>>
>> What I'm missing is how I can use either of them on a remote KVM VPS,
>> where I get to see the boot process on some kind of remote console, and
>> I have the opportunity to provide a bootable ISO, but not much else.
>>
>> I've t
w I can use either of them on a remote KVM VPS,
> where I get to see the boot process on some kind of remote console, and
> I have the opportunity to provide a bootable ISO, but not much else.
>
> I've tried providing the netinst ISO, and it boots but can't find itself
> for install
On 11/08/18 22:43, Ben Hutchings wrote:
> On Sat, 2018-08-11 at 20:14 +1200, Richard Hector wrote:
>> Hi - I hope I'm in the right place; feel free to redirect me.
>>
>> I want to install on a KVM-based VPS, using an ordinary installer (ie
>> not using the im
On Sat, 2018-08-11 at 20:14 +1200, Richard Hector wrote:
> Hi - I hope I'm in the right place; feel free to redirect me.
>
> I want to install on a KVM-based VPS, using an ordinary installer (ie
> not using the image provided).
>
> I used the provider's method to provide an
Hi - I hope I'm in the right place; feel free to redirect me.
I want to install on a KVM-based VPS, using an ordinary installer (ie
not using the image provided).
I used the provider's method to provide an ISO, and supplied the
standard amd64 netinst image - it boots fine, but can't find
Package: os-prober
Version: 1.65+deb8u1
uname: Linux black 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03)
x86_64 GNU/Linux
Short: os-prober invoked during kernel upgrade disrupts KVM guest
It happened already twice but this is first time I was able to bind
together 2 events from KVM host
Your message dated Sat, 24 Jun 2017 20:39:26 +0200
with message-id <20170624183926.gf27...@mraw.org>
and subject line Re: Bug#847230: installation-reports: Reiser4 successfull
remote install on Cloud provider KVM infrastructure via netboot image
has caused the Debian Bug report #847230,
reg
Your message dated Sat, 24 Jun 2017 20:40:06 +0200
with message-id <20170624184006.gg27...@mraw.org>
and subject line Re: Bug#849268: installation-reports: Jessie-backported
Reiser4-patched Linux 4.8.15-1 on UpCloud 8-core/48Gig RAM KVM Cloud
infrastructure successful installation
has
Package: installation-reports
Boot method: KVM (virt-install) boot from ISO image
Image version: debian-stretch-DI-rc2-amd64-netinst.iso
Date: Tue Feb 7 12:49:26 EET 2017
Machine: KVM virtual host, with virtio, running under Debian 7.11 (stretch)
Processor: virtual, single core
Memory: 1 GB
Your message dated Fri, 20 Jan 2017 13:04:29 +
with message-id <e1cuyrl-000iyw...@fasolo.debian.org>
and subject line Bug#648208: fixed in os-prober 1.72
has caused the Debian Bug report #648208,
regarding linux: KVM guests randomly get I/O errors on VirtIO based devices
to be marked a
Your message dated Fri, 20 Jan 2017 13:04:29 +
with message-id <e1cuyrl-000iyw...@fasolo.debian.org>
and subject line Bug#648208: fixed in os-prober 1.72
has caused the Debian Bug report #648208,
regarding os-prober: blockdev --setro affects running kvm instances
to be marked a
Machine: https://www.upcloud.com KVM Cloud infrastructure
Partitions:
udev devtmpfs 10240 0 10240 0% /dev
tmpfs tmpfs 98931408976 9884164 1% /run
/dev/vda6 reiser4 20423272 4523220 15900052 23% /
tmpfs tmpfs 24732840 144
Standard Time (PST)
Machine: upCloud Provider https://www.upcloud.com/ QEMU/KVM cloud
Infrastructure-as-a-Service (IaaS)
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev devtmpfs 10240 0 10240 0% /dev
tmpfs tmpfs 204100
>> Since version 1.45, os-prober instead uses grub-mount when it's
available
>> -- and if grub is installed to use os-prober, it will pull it in.
>
>> So unless another bootloader is also using os-prober, or someone
>> installs and uses it by hand, this won't happen in unstable/testing.
> It's
Your message dated Sat, 22 Oct 2016 09:06:21 +0200
with message-id <20161022090621.2316e3da@a68n.lokal>
and subject line not waiting for anything
has caused the Debian Bug report #840720,
regarding installation-report: stretch/testing setup inside qemu/kvm with
virt-manager
to be marked a
/debian-testing-amd64-netinst.iso
Date: 2016-10-13
Machine: kvm vm, see attachment
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev devtmpfs500520 0500520 0% /dev
tmpfs tmpfs 1020283420 98608 4% /run
/dev/vda1
---
So this is partial fix for the cases where there is no qeth/ctc
device, ie. PCI only LPAR & z/VM or KVM virtual machines. In such
cases we shouldn't bother the user with pointless questions. If there
is e.g. PCI and qeth network cards, and user doesn't want to
configure qeth card,
Package: installation-reports
Severity: important
Tags: d-i
Installing lilo bootloader on qemu/kvm virtual machine fails.
-- Package-specific info:
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/stretch_di_alpha6/amd64/iso-cd/debian-stretch-DI-alpha6-amd64-netinst.iso
Date
in unstable/testing.
It's not really the case:
Using grub-2.02_beta2 and os-prober-1.65 If there is a KVM virtual
machine using an ext4 FS on LVM and writing on it, a simple
grub-mkconfig on, the server(hypervisor) create disk I/O errors on the
virtual machine.
So this problem is a real one.
You
Steven Chamberlain ste...@pyro.eu.org (2014-08-21):
retitle 758757 kfreebsd-10: d-i bugs caused by qemu-system-i386+kvm
thanks
On 21/08/14 00:23, Steven Chamberlain wrote:
Using qemu-system-i386 with the -smp 2 flag, I started seeing weird
issues early in d-i:
It seems more likely
this was triggered by -enable-kvm (on a wheezy
linux-amd64 host).
Without that flag it looks reliable so far, even with -smp 2 (but I'm
worried it could be non-deterministic).
While this might be a bug in the emulation layer indeed, another view
would be that -enable-kvm means stuff go quicker and you
/debian-testing-amd64-netinst.iso,
2014-06-02 Date: 2014-06-08, about 15.00 h to 17.00 h
Machine: virt-manager KVM guest
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/vda1 ext4 19620732 1301112 17299872 7% /
udev devtmpfs 10240
Processing control commands:
tag -1 + wontfix moreinfo - patch
Bug #726298 [busybox] Give guidance to console-switching installer users
Added tag(s) moreinfo and wontfix.
Bug #726298 [busybox] Give guidance to console-switching installer users
Removed tag(s) patch.
--
726298:
Control: tag -1 + wontfix moreinfo - patch
14.10.2013 14:45, Thiemo Nagel wrote:
severity 726298 wishlist
retitle 726298 Give guidance to console-switching installer users
reassign 726298 busybox
tags 726298 + patch
thanks
It's all my fault. I just realized that X is fine, I just didn't
Package: debian-installer
Version: daily
Severity: normal
Tags: d-i
Hello,
when booting the graphical install (daily build) as KVM guest and switching to
the text console via Ctrl-Alt-F2 at any time during installation, the graphics
is crashing.
The following error message is displayed
Thiemo Nagel thiemo.na...@gmail.com (2013-10-14):
Hello,
when booting the graphical install (daily build) as KVM guest and switching to
the text console via Ctrl-Alt-F2 at any time during installation, the graphics
is crashing.
The following error message is displayed on the first console
Cyril Brulebois k...@debian.org (2013-10-14):
That's the X server not being to be started again. What would be
interesting and what led to this situation. Previous X log
(Xorg.0.log.old most likely) would be nice to have, along with the
syslog, I assume.
-ENOTENOUGHCOFFEE.
That's the X
Processing commands for cont...@bugs.debian.org:
severity 726298 wishlist
Bug #726298 [debian-installer] debian-installer: graphical install as KVM guest
crashes when switching to text console
Severity set to 'wishlist' from 'normal'
retitle 726298 Give guidance to console-switching installer
severity 726298 wishlist
retitle 726298 Give guidance to console-switching installer users
reassign 726298 busybox
tags 726298 + patch
thanks
It's all my fault. I just realized that X is fine, I just didn't
expect it to live on console #5. Maybe the attached patch could help
prevent others
Your message dated Sat, 20 Jul 2013 14:01:13 +0200
with message-id 201307201401.32133.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #636675,
regarding Debian Testing Cd install on KVM virtualisation stops at Select and
install
Your message dated Tue, 16 Jul 2013 14:33:03 +0200
with message-id 201307161433.14583.hol...@layer-acht.org
and subject line old kreebsd bugs
has caused the Debian Bug report #629921,
regarding debian-kfreebsd (i386) install fails in qemu (kvm), unable to
partition hard disk
to be marked as done
Package: grub-installer
Severity: normal
Hi.
I'm trying to install Debian on an IDE image of a KVM / libvirt / virt-manager
which has a second (SCSI) drive configured, containing an image of a
single-partition disk containing a Windows 7 system.
While the installer runs the grub
Your message dated Tue, 18 Dec 2012 11:43:48 +0400
with message-id 50d01eb4.8030...@msgid.tls.msk.ru
and subject line Bug#599200: base-installer: Install amd64 kernel on i686 kvm
guest - and fail to boot
has caused the Debian Bug report #599200,
regarding base-installer: Install amd64 kernel
Package: installation-reports
Version: 2.47
Severity: wishlist
-- Package-specific info:
Boot method: CD
Image version: business card daily 2012-07-12
Date: 2012-07-12
Installed using the graphical installer
Selected desktop environment: Xfce
Machine: KVM virtual machine
Partitions: df -Tl
Package: os-prober
Version: 1.42
Severity: important
I had the following issue with os-prober:
While running an apt-get upgrade, a kvm instance running on the same
machine reported journal write errors on it's virtual disk.
The virtual disk is a logical volume on the host filesystem.
Further
09.11.2011 19:29, Jan Niehusmann wrote:
Package: os-prober
Version: 1.42
Severity: important
I had the following issue with os-prober:
While running an apt-get upgrade, a kvm instance running on the same
machine reported journal write errors on it's virtual disk.
The virtual disk
On Wed, Nov 09, 2011 at 08:22:08PM +0400, Michael Tokarev wrote:
09.11.2011 19:29, Jan Niehusmann wrote:
It would be better if the user had a chance to select which devices
should be scanned. At least the user should be warned that running
os-prober while devices are used by other processes
Jan Niehusmann wrote:
Os-prober then calls blockdev --setro on devices it considers not
mounted.
Since version 1.45, os-prober instead uses grub-mount when it's available
-- and if grub is installed to use os-prober, it will pull it in.
So unless another bootloader is also using os-prober, or
Processing commands for cont...@bugs.debian.org:
reassign 636675 installation-reports
Bug #636675 [debian gnu/linux testing squeeze - official snapshot amd64]
Debian Testing Cd install on KVM virtualisation stops at Select and install
software stage
Warning: Unknown package 'debian'
Warning
Machine: KVM VM
Partitions: df -Tl will do; the raw partition table is preferred
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card:[O]
Configure network: [O]
Detect CD: [O]
Load
This is also true with virtualbox 4.0.10 , and daily (06. july) mini.iso
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2039042.QKsQ1LX2nb@shumarija
Forgot to say it partitions the hard drive succesfully if using ZFS , but
installation fails - bzat not availible...
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Package: installation-reports
Boot method: cd
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/kfreebsd-i386/iso-cd/debian-testing-kfreebsd-i386-CD-1.iso
Date: 2011/06/09 11:28 AM CST
Machine: QEMU Virtual machine (KVM)
Processor:
Memory: 128 (qemu default)
Partitions: none (empty
09.06.2011 20:37, Austin English wrote:
Package: installation-reports
Boot method: cd
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/kfreebsd-i386/iso-cd/debian-testing-kfreebsd-i386-CD-1.iso
Date: 2011/06/09 11:28 AM CST
Machine: QEMU Virtual machine (KVM)
Processor
/09 11:28 AM CST
Machine: QEMU Virtual machine (KVM)
Processor:
Memory: 128 (qemu default)
Partitions: none (empty disk)
Please provide your kvm command line and qemu-kvm package version too.
Also, if you tried installing it on an scsi (virtual) drive, try the
same with ide instead - scsi
Your message dated Sat, 22 Jan 2011 17:56:37 +
with message-id 1295718997.2505.215.camel@eeepc.Belkin
and subject line
has caused the Debian Bug report #509186,
regarding [Installation-Report] Failure in KVM 2Gb
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 10 Jan 2011 07:13:09 +0100
with message-id 20110110061309.gt20...@mykerinos.kheops.frmug.org
and subject line Re: Bug#609502: installation-report: successful squeeze rc1
install in kvm
has caused the Debian Bug report #609502,
regarding installation-report: successful
Package: installation-reports
Version: 2.43
Severity: normal
I just completed an install in kvm using the rc1 businesscard (i386).
Installed the desktop task and rebooted into gnome, with all default
options. I get a 800x600 resolution in X, but that's probably an X
driver bug, so...
Everything
, lm mode is
always masked in guest even if the host is capable of
running 64bit code. When running 64bit host kernel and
32bit kvm userland it correctly shows lm flag and 64bit
guest actually works.
Tagging this as unreproducible for now. Meanwhile I'll
try to find kvm-85 package
Processing commands for cont...@bugs.debian.org:
tags 599200 + unreproducible
Bug #599200 [base-installer] base-installer: Install amd64 kernel on i686 kvm
guest - and fail to boot
Added tag(s) unreproducible.
thanks
Stopping processing here.
Please contact me if you need assistance
severity 599200 important
thanks
[Ben Hutchings]
Please specify exactly which versions of kvm/qemu-kvm and the kernel you
are running in the host, and whether you are using the kvm modules from
the linux-image-2.6.26-2-686 or built from kvm-source.
I finally found time to have a look
Processing commands for cont...@bugs.debian.org:
severity 599200 important
Bug #599200 [base-installer] base-installer: Install amd64 kernel on i686 kvm
guest - and fail to boot
Severity set to 'important' from 'grave'
thanks
Stopping processing here.
Please contact me if you need assistance
On Wed, Oct 06, 2010 at 12:53:04AM +0200, Petter Reinholdtsen wrote:
[Lennart Sorensen]
Well try starting the kvm with '-cpu qemu32'. That should provide
the feature flags of a nice 32bit x86.
I tried this by adding
cpu match='exact'
modelqemu32/model
/cpu
to the libvirtm
On Wed, Oct 06, 2010 at 10:39:17AM -0400, Lennart Sorensen wrote:
On Wed, Oct 06, 2010 at 12:53:04AM +0200, Petter Reinholdtsen wrote:
[Lennart Sorensen]
Well try starting the kvm with '-cpu qemu32'. That should provide
the feature flags of a nice 32bit x86.
I tried this by adding
Package: base-installer
Version: 1.110
Severity: grave
User: debian-...@lists.debian.org
UserTags: debian-edu
I discovered this using the Debian Edu DVD and installing on a i686
kvm guest on a i686 Lenny host. The problem is that installation now
is successfull, but the installed machine
This is the /proc/cpuinfo in the i686 kvm guest:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 2
model name : QEMU Virtual CPU version 0.10.0
stepping: 3
cpu MHz : 2999.338
cache size : 2048 KB
fdiv_bug: no
hlt_bug
On Tue, Oct 5, 2010 at 18:28:43 +0200, Jürgen Leibner wrote:
I installed today the same way as Petter Reinholdtsen does, but on
virtualbox-ose version 3.2.8-dfsg-2.
uname -a on the host system gives:
Linux laptop-jl 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010
x86_64 GNU/Linux
On Tue, Oct 05, 2010 at 07:08:03PM +0200, Jürgen Leibner wrote:
If there would be an addititional menu which gives one the possibility to
choose such a mixed system then I would be able to choose a mixed system.
But in this case, there is an Install, suggesting a 32-bit overall system
and on
On Tue, Oct 05, 2010 at 06:27:55PM +0200, Petter Reinholdtsen wrote:
This is the /proc/cpuinfo in the i686 kvm guest:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 2
model name : QEMU Virtual CPU version 0.10.0
stepping: 3
cpu MHz
On Tue, Oct 05, 2010 at 08:42:18PM +0200, Jürgen Leibner wrote:
On Tuesday 05 October 2010 19:41 Lennart Sorensen wrote:
...
Most people would prefer the 64bit kernel with 32bit userspace. I
think there is an option in expert mode to select your kernel
yourself from a list, but unless
affects 599200 qemu-kvm
thanks
[Lennart Sorensen]
The 'lm' flag means this system has 64bit support. If in fact it
doesn't, then the VM is broken. The installer did the right thing
based on the CPU feature flags.
Assuming this is true, I suggest two things are done to make sure d-i
work
Processing commands for cont...@bugs.debian.org:
affects 599200 qemu-kvm
Bug #599200 [base-installer] base-installer: Install amd64 kernel on i686 kvm
guest - and fail to boot
Added indication that 599200 affects qemu-kvm
thanks
Stopping processing here.
Please contact me if you need
On Tue, Oct 05, 2010 at 11:07:15PM +0200, Petter Reinholdtsen wrote:
affects 599200 qemu-kvm
thanks
[Lennart Sorensen]
The 'lm' flag means this system has 64bit support. If in fact it
doesn't, then the VM is broken. The installer did the right thing
based on the CPU feature flags
[Lennart Sorensen]
I suspect if you run kvm with the -cpu option you can specify what
you desire. I believe the default is to simply match whatever the
host has, so if the host has a 64bit cpu, then the guest will too.
Well, the host is using a 32-bit kernel too, so 64-bit kvm with
hardware
On Wed, Oct 06, 2010 at 12:01:45AM +0200, Petter Reinholdtsen wrote:
[Lennart Sorensen]
I suspect if you run kvm with the -cpu option you can specify what
you desire. I believe the default is to simply match whatever the
host has, so if the host has a 64bit cpu, then the guest will too
[Lennart Sorensen]
Well try starting the kvm with '-cpu qemu32'. That should provide
the feature flags of a nice 32bit x86.
I tried this by adding
cpu match='exact'
modelqemu32/model
/cpu
to the libvirtm XML file for the virtual machine, which caused '-cpu
qemu32' to be part
On Tue, 2010-10-05 at 23:07 +0200, Petter Reinholdtsen wrote:
affects 599200 qemu-kvm
thanks
[Lennart Sorensen]
The 'lm' flag means this system has 64bit support. If in fact it
doesn't, then the VM is broken. The installer did the right thing
based on the CPU feature flags
Hi
I have a problem with text debian installer. I load debian installer from pxe,
and manage remote server with DRAC cards v3-v5 and usb kvm switch.
Pressing a key will result in multiple characters of that key being displayed,
tab and space affected.
It is similar on https
Package: installation-reports
Boot method: netinst in kvm
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/20081218-1/amd64/
(Downloaded with jigdo: md5sum OK)
Date: 19 december 2008
Machine: KVM emulator on a Dell Latitude D630 amd64
Processor: QEMU Virtual CPU version
reassign 498879 lilo
severity 498879 wishlist
retitle 498879 lilo: please add support for virtio drives
thanks
On Sun, Sep 14, 2008 at 06:58:17PM -0300, André Luís Lopes wrote:
Frans Pop escreveu:
Are you sure that the problem is XFS? It could also be that lilo does not
support KVM's
Processing commands for [EMAIL PROTECTED]:
reassign 498879 lilo
Bug#498879: LILO fails when doing XFS on / on KVM virtual disk
Bug reassigned from package `lilo-installer' to `lilo'.
severity 498879 wishlist
Bug#498879: LILO fails when doing XFS on / on KVM virtual disk
Severity set
Processing commands for [EMAIL PROTECTED]:
reassign 498879 lilo-installer
Bug#498879: [debian-testing-i386-netinst] LILO fails when doing XFS on / (daily
from 20080913)
Bug reassigned from package `installation-reports' to `lilo-installer'.
retitle 498879 LILO fails when doing XFS on / on KVM
reassign 498879 lilo-installer
retitle 498879 LILO fails when doing XFS on / on KVM virtual disk
thanks
On Sunday 14 September 2008, André Luís Lopes wrote:
Comments/Problems:
I do not use LILO personally, but as I probably will use XFS for
some future projects, I wanted to know how well
Your message dated Thu, 04 Sep 2008 13:02:11 +
with message-id [EMAIL PROTECTED]
and subject line Bug#497238: fixed in hw-detect 1.67
has caused the Debian Bug report #497238,
regarding issues with detecting kvm hard disk
to be marked as done.
This means that you claim that the problem has
reassign 497238 hw-detect
thanks
On Sun, Aug 31, 2008 at 10:01:32AM +0200, Andreas Barth wrote:
With virtio, the hard disk wasn't detected. After udpkg -i
.../virtio-modules-2.6.26-1-amd64-di*,
the rest went fine (including automatic detection).
This has been discussed on the mailling-list
Jérémy Bobbio [EMAIL PROTECTED] writes:
reassign 497238 hw-detect
thanks
On Sun, Aug 31, 2008 at 10:01:32AM +0200, Andreas Barth wrote:
With virtio, the hard disk wasn't detected. After udpkg -i
.../virtio-modules-2.6.26-1-amd64-di*,
the rest went fine (including automatic detection).
Package: installation-reports
Boot method: from virtual cdrom
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-businesscard.iso
This build finished at Sat Aug 30 21:35:59 UTC 2008.
Date: 31. August 2008
Machine: kvm, running
-2.6.26-1-486-di… which is a bit cumbersome.
Indeed, using modules=virtio-modules-2.6.26-1-486-di at the install
prompt I was able to complete the installation under KVM using
paravirtualized network/block devices and there was no need to go back
back to main-menu and choose the virtio module manually
-modules-2.6.26-1-486-di… which is a bit cumbersome.
Indeed, using modules=virtio-modules-2.6.26-1-486-di at the install
prompt I was able to complete the installation under KVM using
paravirtualized network/block devices and there was no need to go back
back to main-menu and choose the virtio
unstable fully updated as of some minutes ago, using kernel 2.6.26-1-686
(package version 2.6.26-3) from Debian and KVM version 72+dfsg-1, also
from Debian.
I'm able to use virtualized network and disks only if I manually go
back to main-menu, lower the debconf priority to low and select
Your message dated Sat, 16 Aug 2008 23:39:59 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: Bug#494608: installation-report: KVM install debian lenny
20080810-09:14: no detection of hard drive
has caused the Debian Bug report #494608,
regarding installation-report: KVM install
Subject: installation-report: KVM install debian lenny 20080810-09:14: no
detection of hard drive
Package: installation-reports
Version: 2.35
Severity: normal
*** Please type your report below this line ***
-- Package-specific info:
Boot method: CD
Image version:
http://cdimage.debian.org
Hello,
Just to say that the disk is detected with
http://cdimage.debian.org/cdimage/daily-builds/daily/20080808-2/amd64/iso-cd/debian-testing-amd64-businesscard.iso
Regards.
--
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1
--
To UNSUBSCRIBE,
1 - 100 of 105 matches
Mail list logo
