Debian on Hyper-VDebian Lenny as Xen domU fails to bootDebian - corrupted GRUBHyper-V Ubuntu Networking...
Why did Kant, Hegel, and Adorno leave some words and phrases in the Greek alphabet?
Is the destination of a commercial flight important for the pilot?
Student evaluations of teaching assistants
What would be the benefits of having both a state and local currencies?
How do I keep an essay about "feeling flat" from feeling flat?
is this a spam?
Ways to speed up user implemented RK4
Why does John Bercow say “unlock” after reading out the results of a vote?
The plural of 'stomach"
Why is delta-v is the most useful quantity for planning space travel?
How can I use the arrow sign in my bash prompt?
At which point does a character regain all their Hit Dice?
Why is `const int& k = i; ++i; ` possible?
What is the opposite of 'gravitas'?
when is out of tune ok?
How does it work when somebody invests in my business?
Will it be accepted, if there is no ''Main Character" stereotype?
How was Earth single-handedly capable of creating 3 of the 4 gods of chaos?
Modify casing of marked letters
Failed to fetch jessie backports repository
Can somebody explain Brexit in a few child-proof sentences?
Applicability of Single Responsibility Principle
There is only s̶i̶x̶t̶y one place he can be
What would happen if the UK refused to take part in EU Parliamentary elections?
Debian on Hyper-V
Debian Lenny as Xen domU fails to bootDebian - corrupted GRUBHyper-V Ubuntu Networking Problems Copying Large Amounts of DataUbuntu Server and Hyper-VCentOS 6 on Hyper-V - network adapter doesn't work (no checksum feature)Veeam Hyper-V backup error: Microsoft Hyper-V VSS Writer VSS_WS_FAILED_AT_POST_SNAPSHOTLinux swap partition not mounted by systemd on boot after dist-upgradeInstall debian 8 on a LVM Volume with Type RAID1 GRUB2 cant find volume groupDebian Lost filesystem. Corrupted filesystemTroubles with booting xen VM in Hyper-V
I installed Debian with kernel 2.6.32-5-686 on a Hyper-V virtual machine. I had to add a legacy network card.
I follow this tutorial http://www.yusufozturk.info/linux-server/debian-2-6-36-kernel-upgrade-for-hyper-v-client-drivers.html to add Hyper-V driver but when I reboot with the new kernel i got this error:
BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev() failed! ret -16
And at the very first boot log (that i can not copy because i did not find it in dmesg or boot log) i see a mount /dev error.
Thank you.
debian hyper-v linux-kernel legacy
add a comment |
I installed Debian with kernel 2.6.32-5-686 on a Hyper-V virtual machine. I had to add a legacy network card.
I follow this tutorial http://www.yusufozturk.info/linux-server/debian-2-6-36-kernel-upgrade-for-hyper-v-client-drivers.html to add Hyper-V driver but when I reboot with the new kernel i got this error:
BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev() failed! ret -16
And at the very first boot log (that i can not copy because i did not find it in dmesg or boot log) i see a mount /dev error.
Thank you.
debian hyper-v linux-kernel legacy
What version of Debian are you running? That blog talks about a newer kernel than you mention; is there a particular reason? What do you mean by "crash"? Error messages?
– Chris S
Aug 28 '12 at 15:18
Debian GNU/Linux 6.0.5 (squeeze). I tried to recompile the kernel v. 2.6.36 as the blog said, but i did not unserstand why that version. During bootup I saw a list of number as matrix ex.[15 12 35 94 86] and after a few it freeze...
– Tobia
Aug 29 '12 at 6:35
I edited the topic because using a compile deb package i solve that boot freeze, however i still have some error...
– Tobia
Aug 29 '12 at 8:09
add a comment |
I installed Debian with kernel 2.6.32-5-686 on a Hyper-V virtual machine. I had to add a legacy network card.
I follow this tutorial http://www.yusufozturk.info/linux-server/debian-2-6-36-kernel-upgrade-for-hyper-v-client-drivers.html to add Hyper-V driver but when I reboot with the new kernel i got this error:
BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev() failed! ret -16
And at the very first boot log (that i can not copy because i did not find it in dmesg or boot log) i see a mount /dev error.
Thank you.
debian hyper-v linux-kernel legacy
I installed Debian with kernel 2.6.32-5-686 on a Hyper-V virtual machine. I had to add a legacy network card.
I follow this tutorial http://www.yusufozturk.info/linux-server/debian-2-6-36-kernel-upgrade-for-hyper-v-client-drivers.html to add Hyper-V driver but when I reboot with the new kernel i got this error:
BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev() failed! ret -16
And at the very first boot log (that i can not copy because i did not find it in dmesg or boot log) i see a mount /dev error.
Thank you.
debian hyper-v linux-kernel legacy
debian hyper-v linux-kernel legacy
edited Aug 29 '12 at 8:08
Tobia
asked Aug 28 '12 at 15:07
TobiaTobia
52962456
52962456
What version of Debian are you running? That blog talks about a newer kernel than you mention; is there a particular reason? What do you mean by "crash"? Error messages?
– Chris S
Aug 28 '12 at 15:18
Debian GNU/Linux 6.0.5 (squeeze). I tried to recompile the kernel v. 2.6.36 as the blog said, but i did not unserstand why that version. During bootup I saw a list of number as matrix ex.[15 12 35 94 86] and after a few it freeze...
– Tobia
Aug 29 '12 at 6:35
I edited the topic because using a compile deb package i solve that boot freeze, however i still have some error...
– Tobia
Aug 29 '12 at 8:09
add a comment |
What version of Debian are you running? That blog talks about a newer kernel than you mention; is there a particular reason? What do you mean by "crash"? Error messages?
– Chris S
Aug 28 '12 at 15:18
Debian GNU/Linux 6.0.5 (squeeze). I tried to recompile the kernel v. 2.6.36 as the blog said, but i did not unserstand why that version. During bootup I saw a list of number as matrix ex.[15 12 35 94 86] and after a few it freeze...
– Tobia
Aug 29 '12 at 6:35
I edited the topic because using a compile deb package i solve that boot freeze, however i still have some error...
– Tobia
Aug 29 '12 at 8:09
What version of Debian are you running? That blog talks about a newer kernel than you mention; is there a particular reason? What do you mean by "crash"? Error messages?
– Chris S
Aug 28 '12 at 15:18
What version of Debian are you running? That blog talks about a newer kernel than you mention; is there a particular reason? What do you mean by "crash"? Error messages?
– Chris S
Aug 28 '12 at 15:18
Debian GNU/Linux 6.0.5 (squeeze). I tried to recompile the kernel v. 2.6.36 as the blog said, but i did not unserstand why that version. During bootup I saw a list of number as matrix ex.[15 12 35 94 86] and after a few it freeze...
– Tobia
Aug 29 '12 at 6:35
Debian GNU/Linux 6.0.5 (squeeze). I tried to recompile the kernel v. 2.6.36 as the blog said, but i did not unserstand why that version. During bootup I saw a list of number as matrix ex.[15 12 35 94 86] and after a few it freeze...
– Tobia
Aug 29 '12 at 6:35
I edited the topic because using a compile deb package i solve that boot freeze, however i still have some error...
– Tobia
Aug 29 '12 at 8:09
I edited the topic because using a compile deb package i solve that boot freeze, however i still have some error...
– Tobia
Aug 29 '12 at 8:09
add a comment |
6 Answers
6
active
oldest
votes
Stay away from any in-kernel Hyper-V drivers based on anything let's around say 3.0, since early version were considered staging and were sometimes utterly unstable.
Hyper-V drivers got fully integrated upstream (moved out of staging) with 3.4. While Debian Wheezy (7.0) will be based on 3.2, it will contain a backport from Kernel 3.4, I'm using it here.
Thus said for squeeze: Install with legacy NIC and IDE only drives, then get the Wheezy kernel from squeeze-backports and reboot. Then you'll be able to use paravirt NIC, SCSI disks, additionally you'll get mouse integration and support for more than 1 vCPU.
1
Thank you very much, can you be a little more verbose about "then get the Wheezy kernel from squeeze-backports and reboot"?
– Tobia
Sep 11 '12 at 7:11
In corner cases like this I usually just fetch the latest kernel from kernel.org and recompile it in the Debian Way™. For example, one of the backup servers I need to keep my eye on was very unreliable with Debian Squeeze default kernel; iSCSI support is a bit flaky on that one. I compiled my own kernel 3.x, now the server uptime is about one year, no problems whatsoever.
– Janne Pikkarainen
Oct 11 '12 at 15:37
@Tobia that might be good fodder for a separate follow-up question
– Joel Coel
Oct 11 '12 at 15:38
add a comment |
Debian Wheezy (7.0) contains a backport Hyper-V drivers from Kernel 3.4
But the Hyper-V kernel modules, at minimum:
- hv_vmbus
- hv_utils
- hv_storvsc
- hv_netvsc
are missing in the installer image of Debian Wheezy created before 2012-11-13
Solution:
You need use .iso created after 2012-11-14, or the .iso
by Arnaud Patard
See details here.
add a comment |
Check this out: http://docs.homelinux.org/doku.php?id=using_linux_ic_with_debian_squeeze the kernels there have the storvsc ata_piix fix ;)
Seems good, but is there also i386 version?
– Tobia
Oct 12 '12 at 6:36
add a comment |
Here is how to install Debian 7 (wheezy) on hyper-V.
Currently, the netinst image doesn't contains the hyper-v drivers. (tested with netinst beta 2). You may replace your network card by a legacy network card, but it won't be enough since the debian Netinst does not detect the disk, so you can't install anything.
The solution I use is to download the Debian 6 netinst "business card". Add a "legacy network card", and boot on the install disc.
When netinst ask you for the hostname for your new system, switch to another console (Alt-F2) and type
echo wheezy > /etc/default-release
Then return to the first console (Alt-F1) and proceed.
At the end of the installation, you will have a working Debian 7 (Wheezy), with modern kernel that support Hyper-V. So you may remove the legacy network card and use the native driver for network and disk.
By now this issue with thet netboot ISO has been resolved, you can now yank in the latest daily builds (and thus likely the final builds once it's you) and have working storage without additionaly hacking.
– nokofi
Mar 14 '13 at 12:31
add a comment |
With Debian jessie the hyper-v stuff is no more a problem, the modules are already integrated and are stable. You need only to compile and install the hyper-v tools (kvp and vss), I found this howto: http://docs.homelinux.org/hyper-v:debian_jessie_hyper-v and all will be fine ;)
add a comment |
If you are running Debian 6.0 (Squeeze), You can upgrade to 7.0 (Wheezy), it’s so simple:
just answer Y every time.
apt-get update
apt-get upgrade
nano /etc/apt/sources.list
and replace every squeeze
with wheezy
, CTRL+X, Y,enter.
apt-get update
apt-get upgrade
apt-get dist-upgrade
reboot
your new kernel will be selected, login, then you can lsmod | grep hv
and see the hyper-v modules loaded (hv_vmbus, hv_netvsc, hv_blkvsc, hv_storvsc), connect your non-legacy network adapter and do ip show link
then you’ll see it (you can be sure by checking the MAC).
But why stay there?, now you can go to Debian 8.2 (jessie) by following the same instructions but this time use “jessie” on your sourcelist.
I wasn’t able to go directly from 6 to 8.
If you have trouble with “public key is not available” then follow instructions from here.
Sometimes running on Hyper-v it throws two errors:
Error: Driver ‘pcspkr’ is already registered
SMBus base address uninitialized – upgrade bios or use force_addr=0xaddr
to get rid of those errors just blacklist two modules by:
echo 'blacklist pcspkr' >> /etc/modprobe.d/fbdev-blacklist.conf
echo 'blacklist i2c_piix4' >> /etc/modprobe.d/fbdev-blacklist.conf
then do:
update-initramfs -u
reboot
Enjoy.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f422047%2fdebian-on-hyper-v%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Stay away from any in-kernel Hyper-V drivers based on anything let's around say 3.0, since early version were considered staging and were sometimes utterly unstable.
Hyper-V drivers got fully integrated upstream (moved out of staging) with 3.4. While Debian Wheezy (7.0) will be based on 3.2, it will contain a backport from Kernel 3.4, I'm using it here.
Thus said for squeeze: Install with legacy NIC and IDE only drives, then get the Wheezy kernel from squeeze-backports and reboot. Then you'll be able to use paravirt NIC, SCSI disks, additionally you'll get mouse integration and support for more than 1 vCPU.
1
Thank you very much, can you be a little more verbose about "then get the Wheezy kernel from squeeze-backports and reboot"?
– Tobia
Sep 11 '12 at 7:11
In corner cases like this I usually just fetch the latest kernel from kernel.org and recompile it in the Debian Way™. For example, one of the backup servers I need to keep my eye on was very unreliable with Debian Squeeze default kernel; iSCSI support is a bit flaky on that one. I compiled my own kernel 3.x, now the server uptime is about one year, no problems whatsoever.
– Janne Pikkarainen
Oct 11 '12 at 15:37
@Tobia that might be good fodder for a separate follow-up question
– Joel Coel
Oct 11 '12 at 15:38
add a comment |
Stay away from any in-kernel Hyper-V drivers based on anything let's around say 3.0, since early version were considered staging and were sometimes utterly unstable.
Hyper-V drivers got fully integrated upstream (moved out of staging) with 3.4. While Debian Wheezy (7.0) will be based on 3.2, it will contain a backport from Kernel 3.4, I'm using it here.
Thus said for squeeze: Install with legacy NIC and IDE only drives, then get the Wheezy kernel from squeeze-backports and reboot. Then you'll be able to use paravirt NIC, SCSI disks, additionally you'll get mouse integration and support for more than 1 vCPU.
1
Thank you very much, can you be a little more verbose about "then get the Wheezy kernel from squeeze-backports and reboot"?
– Tobia
Sep 11 '12 at 7:11
In corner cases like this I usually just fetch the latest kernel from kernel.org and recompile it in the Debian Way™. For example, one of the backup servers I need to keep my eye on was very unreliable with Debian Squeeze default kernel; iSCSI support is a bit flaky on that one. I compiled my own kernel 3.x, now the server uptime is about one year, no problems whatsoever.
– Janne Pikkarainen
Oct 11 '12 at 15:37
@Tobia that might be good fodder for a separate follow-up question
– Joel Coel
Oct 11 '12 at 15:38
add a comment |
Stay away from any in-kernel Hyper-V drivers based on anything let's around say 3.0, since early version were considered staging and were sometimes utterly unstable.
Hyper-V drivers got fully integrated upstream (moved out of staging) with 3.4. While Debian Wheezy (7.0) will be based on 3.2, it will contain a backport from Kernel 3.4, I'm using it here.
Thus said for squeeze: Install with legacy NIC and IDE only drives, then get the Wheezy kernel from squeeze-backports and reboot. Then you'll be able to use paravirt NIC, SCSI disks, additionally you'll get mouse integration and support for more than 1 vCPU.
Stay away from any in-kernel Hyper-V drivers based on anything let's around say 3.0, since early version were considered staging and were sometimes utterly unstable.
Hyper-V drivers got fully integrated upstream (moved out of staging) with 3.4. While Debian Wheezy (7.0) will be based on 3.2, it will contain a backport from Kernel 3.4, I'm using it here.
Thus said for squeeze: Install with legacy NIC and IDE only drives, then get the Wheezy kernel from squeeze-backports and reboot. Then you'll be able to use paravirt NIC, SCSI disks, additionally you'll get mouse integration and support for more than 1 vCPU.
answered Sep 8 '12 at 7:36
nokofinokofi
136116
136116
1
Thank you very much, can you be a little more verbose about "then get the Wheezy kernel from squeeze-backports and reboot"?
– Tobia
Sep 11 '12 at 7:11
In corner cases like this I usually just fetch the latest kernel from kernel.org and recompile it in the Debian Way™. For example, one of the backup servers I need to keep my eye on was very unreliable with Debian Squeeze default kernel; iSCSI support is a bit flaky on that one. I compiled my own kernel 3.x, now the server uptime is about one year, no problems whatsoever.
– Janne Pikkarainen
Oct 11 '12 at 15:37
@Tobia that might be good fodder for a separate follow-up question
– Joel Coel
Oct 11 '12 at 15:38
add a comment |
1
Thank you very much, can you be a little more verbose about "then get the Wheezy kernel from squeeze-backports and reboot"?
– Tobia
Sep 11 '12 at 7:11
In corner cases like this I usually just fetch the latest kernel from kernel.org and recompile it in the Debian Way™. For example, one of the backup servers I need to keep my eye on was very unreliable with Debian Squeeze default kernel; iSCSI support is a bit flaky on that one. I compiled my own kernel 3.x, now the server uptime is about one year, no problems whatsoever.
– Janne Pikkarainen
Oct 11 '12 at 15:37
@Tobia that might be good fodder for a separate follow-up question
– Joel Coel
Oct 11 '12 at 15:38
1
1
Thank you very much, can you be a little more verbose about "then get the Wheezy kernel from squeeze-backports and reboot"?
– Tobia
Sep 11 '12 at 7:11
Thank you very much, can you be a little more verbose about "then get the Wheezy kernel from squeeze-backports and reboot"?
– Tobia
Sep 11 '12 at 7:11
In corner cases like this I usually just fetch the latest kernel from kernel.org and recompile it in the Debian Way™. For example, one of the backup servers I need to keep my eye on was very unreliable with Debian Squeeze default kernel; iSCSI support is a bit flaky on that one. I compiled my own kernel 3.x, now the server uptime is about one year, no problems whatsoever.
– Janne Pikkarainen
Oct 11 '12 at 15:37
In corner cases like this I usually just fetch the latest kernel from kernel.org and recompile it in the Debian Way™. For example, one of the backup servers I need to keep my eye on was very unreliable with Debian Squeeze default kernel; iSCSI support is a bit flaky on that one. I compiled my own kernel 3.x, now the server uptime is about one year, no problems whatsoever.
– Janne Pikkarainen
Oct 11 '12 at 15:37
@Tobia that might be good fodder for a separate follow-up question
– Joel Coel
Oct 11 '12 at 15:38
@Tobia that might be good fodder for a separate follow-up question
– Joel Coel
Oct 11 '12 at 15:38
add a comment |
Debian Wheezy (7.0) contains a backport Hyper-V drivers from Kernel 3.4
But the Hyper-V kernel modules, at minimum:
- hv_vmbus
- hv_utils
- hv_storvsc
- hv_netvsc
are missing in the installer image of Debian Wheezy created before 2012-11-13
Solution:
You need use .iso created after 2012-11-14, or the .iso
by Arnaud Patard
See details here.
add a comment |
Debian Wheezy (7.0) contains a backport Hyper-V drivers from Kernel 3.4
But the Hyper-V kernel modules, at minimum:
- hv_vmbus
- hv_utils
- hv_storvsc
- hv_netvsc
are missing in the installer image of Debian Wheezy created before 2012-11-13
Solution:
You need use .iso created after 2012-11-14, or the .iso
by Arnaud Patard
See details here.
add a comment |
Debian Wheezy (7.0) contains a backport Hyper-V drivers from Kernel 3.4
But the Hyper-V kernel modules, at minimum:
- hv_vmbus
- hv_utils
- hv_storvsc
- hv_netvsc
are missing in the installer image of Debian Wheezy created before 2012-11-13
Solution:
You need use .iso created after 2012-11-14, or the .iso
by Arnaud Patard
See details here.
Debian Wheezy (7.0) contains a backport Hyper-V drivers from Kernel 3.4
But the Hyper-V kernel modules, at minimum:
- hv_vmbus
- hv_utils
- hv_storvsc
- hv_netvsc
are missing in the installer image of Debian Wheezy created before 2012-11-13
Solution:
You need use .iso created after 2012-11-14, or the .iso
by Arnaud Patard
See details here.
edited Dec 2 '12 at 4:55
HopelessN00b
48.5k24115194
48.5k24115194
answered Nov 30 '12 at 12:12
vvmvvm
312
312
add a comment |
add a comment |
Check this out: http://docs.homelinux.org/doku.php?id=using_linux_ic_with_debian_squeeze the kernels there have the storvsc ata_piix fix ;)
Seems good, but is there also i386 version?
– Tobia
Oct 12 '12 at 6:36
add a comment |
Check this out: http://docs.homelinux.org/doku.php?id=using_linux_ic_with_debian_squeeze the kernels there have the storvsc ata_piix fix ;)
Seems good, but is there also i386 version?
– Tobia
Oct 12 '12 at 6:36
add a comment |
Check this out: http://docs.homelinux.org/doku.php?id=using_linux_ic_with_debian_squeeze the kernels there have the storvsc ata_piix fix ;)
Check this out: http://docs.homelinux.org/doku.php?id=using_linux_ic_with_debian_squeeze the kernels there have the storvsc ata_piix fix ;)
answered Oct 11 '12 at 22:00
ozzy88ozzy88
91
91
Seems good, but is there also i386 version?
– Tobia
Oct 12 '12 at 6:36
add a comment |
Seems good, but is there also i386 version?
– Tobia
Oct 12 '12 at 6:36
Seems good, but is there also i386 version?
– Tobia
Oct 12 '12 at 6:36
Seems good, but is there also i386 version?
– Tobia
Oct 12 '12 at 6:36
add a comment |
Here is how to install Debian 7 (wheezy) on hyper-V.
Currently, the netinst image doesn't contains the hyper-v drivers. (tested with netinst beta 2). You may replace your network card by a legacy network card, but it won't be enough since the debian Netinst does not detect the disk, so you can't install anything.
The solution I use is to download the Debian 6 netinst "business card". Add a "legacy network card", and boot on the install disc.
When netinst ask you for the hostname for your new system, switch to another console (Alt-F2) and type
echo wheezy > /etc/default-release
Then return to the first console (Alt-F1) and proceed.
At the end of the installation, you will have a working Debian 7 (Wheezy), with modern kernel that support Hyper-V. So you may remove the legacy network card and use the native driver for network and disk.
By now this issue with thet netboot ISO has been resolved, you can now yank in the latest daily builds (and thus likely the final builds once it's you) and have working storage without additionaly hacking.
– nokofi
Mar 14 '13 at 12:31
add a comment |
Here is how to install Debian 7 (wheezy) on hyper-V.
Currently, the netinst image doesn't contains the hyper-v drivers. (tested with netinst beta 2). You may replace your network card by a legacy network card, but it won't be enough since the debian Netinst does not detect the disk, so you can't install anything.
The solution I use is to download the Debian 6 netinst "business card". Add a "legacy network card", and boot on the install disc.
When netinst ask you for the hostname for your new system, switch to another console (Alt-F2) and type
echo wheezy > /etc/default-release
Then return to the first console (Alt-F1) and proceed.
At the end of the installation, you will have a working Debian 7 (Wheezy), with modern kernel that support Hyper-V. So you may remove the legacy network card and use the native driver for network and disk.
By now this issue with thet netboot ISO has been resolved, you can now yank in the latest daily builds (and thus likely the final builds once it's you) and have working storage without additionaly hacking.
– nokofi
Mar 14 '13 at 12:31
add a comment |
Here is how to install Debian 7 (wheezy) on hyper-V.
Currently, the netinst image doesn't contains the hyper-v drivers. (tested with netinst beta 2). You may replace your network card by a legacy network card, but it won't be enough since the debian Netinst does not detect the disk, so you can't install anything.
The solution I use is to download the Debian 6 netinst "business card". Add a "legacy network card", and boot on the install disc.
When netinst ask you for the hostname for your new system, switch to another console (Alt-F2) and type
echo wheezy > /etc/default-release
Then return to the first console (Alt-F1) and proceed.
At the end of the installation, you will have a working Debian 7 (Wheezy), with modern kernel that support Hyper-V. So you may remove the legacy network card and use the native driver for network and disk.
Here is how to install Debian 7 (wheezy) on hyper-V.
Currently, the netinst image doesn't contains the hyper-v drivers. (tested with netinst beta 2). You may replace your network card by a legacy network card, but it won't be enough since the debian Netinst does not detect the disk, so you can't install anything.
The solution I use is to download the Debian 6 netinst "business card". Add a "legacy network card", and boot on the install disc.
When netinst ask you for the hostname for your new system, switch to another console (Alt-F2) and type
echo wheezy > /etc/default-release
Then return to the first console (Alt-F1) and proceed.
At the end of the installation, you will have a working Debian 7 (Wheezy), with modern kernel that support Hyper-V. So you may remove the legacy network card and use the native driver for network and disk.
answered Nov 8 '12 at 15:17
megarmegar
26026
26026
By now this issue with thet netboot ISO has been resolved, you can now yank in the latest daily builds (and thus likely the final builds once it's you) and have working storage without additionaly hacking.
– nokofi
Mar 14 '13 at 12:31
add a comment |
By now this issue with thet netboot ISO has been resolved, you can now yank in the latest daily builds (and thus likely the final builds once it's you) and have working storage without additionaly hacking.
– nokofi
Mar 14 '13 at 12:31
By now this issue with thet netboot ISO has been resolved, you can now yank in the latest daily builds (and thus likely the final builds once it's you) and have working storage without additionaly hacking.
– nokofi
Mar 14 '13 at 12:31
By now this issue with thet netboot ISO has been resolved, you can now yank in the latest daily builds (and thus likely the final builds once it's you) and have working storage without additionaly hacking.
– nokofi
Mar 14 '13 at 12:31
add a comment |
With Debian jessie the hyper-v stuff is no more a problem, the modules are already integrated and are stable. You need only to compile and install the hyper-v tools (kvp and vss), I found this howto: http://docs.homelinux.org/hyper-v:debian_jessie_hyper-v and all will be fine ;)
add a comment |
With Debian jessie the hyper-v stuff is no more a problem, the modules are already integrated and are stable. You need only to compile and install the hyper-v tools (kvp and vss), I found this howto: http://docs.homelinux.org/hyper-v:debian_jessie_hyper-v and all will be fine ;)
add a comment |
With Debian jessie the hyper-v stuff is no more a problem, the modules are already integrated and are stable. You need only to compile and install the hyper-v tools (kvp and vss), I found this howto: http://docs.homelinux.org/hyper-v:debian_jessie_hyper-v and all will be fine ;)
With Debian jessie the hyper-v stuff is no more a problem, the modules are already integrated and are stable. You need only to compile and install the hyper-v tools (kvp and vss), I found this howto: http://docs.homelinux.org/hyper-v:debian_jessie_hyper-v and all will be fine ;)
answered Apr 30 '15 at 12:40
AlejandroAlejandro
111
111
add a comment |
add a comment |
If you are running Debian 6.0 (Squeeze), You can upgrade to 7.0 (Wheezy), it’s so simple:
just answer Y every time.
apt-get update
apt-get upgrade
nano /etc/apt/sources.list
and replace every squeeze
with wheezy
, CTRL+X, Y,enter.
apt-get update
apt-get upgrade
apt-get dist-upgrade
reboot
your new kernel will be selected, login, then you can lsmod | grep hv
and see the hyper-v modules loaded (hv_vmbus, hv_netvsc, hv_blkvsc, hv_storvsc), connect your non-legacy network adapter and do ip show link
then you’ll see it (you can be sure by checking the MAC).
But why stay there?, now you can go to Debian 8.2 (jessie) by following the same instructions but this time use “jessie” on your sourcelist.
I wasn’t able to go directly from 6 to 8.
If you have trouble with “public key is not available” then follow instructions from here.
Sometimes running on Hyper-v it throws two errors:
Error: Driver ‘pcspkr’ is already registered
SMBus base address uninitialized – upgrade bios or use force_addr=0xaddr
to get rid of those errors just blacklist two modules by:
echo 'blacklist pcspkr' >> /etc/modprobe.d/fbdev-blacklist.conf
echo 'blacklist i2c_piix4' >> /etc/modprobe.d/fbdev-blacklist.conf
then do:
update-initramfs -u
reboot
Enjoy.
add a comment |
If you are running Debian 6.0 (Squeeze), You can upgrade to 7.0 (Wheezy), it’s so simple:
just answer Y every time.
apt-get update
apt-get upgrade
nano /etc/apt/sources.list
and replace every squeeze
with wheezy
, CTRL+X, Y,enter.
apt-get update
apt-get upgrade
apt-get dist-upgrade
reboot
your new kernel will be selected, login, then you can lsmod | grep hv
and see the hyper-v modules loaded (hv_vmbus, hv_netvsc, hv_blkvsc, hv_storvsc), connect your non-legacy network adapter and do ip show link
then you’ll see it (you can be sure by checking the MAC).
But why stay there?, now you can go to Debian 8.2 (jessie) by following the same instructions but this time use “jessie” on your sourcelist.
I wasn’t able to go directly from 6 to 8.
If you have trouble with “public key is not available” then follow instructions from here.
Sometimes running on Hyper-v it throws two errors:
Error: Driver ‘pcspkr’ is already registered
SMBus base address uninitialized – upgrade bios or use force_addr=0xaddr
to get rid of those errors just blacklist two modules by:
echo 'blacklist pcspkr' >> /etc/modprobe.d/fbdev-blacklist.conf
echo 'blacklist i2c_piix4' >> /etc/modprobe.d/fbdev-blacklist.conf
then do:
update-initramfs -u
reboot
Enjoy.
add a comment |
If you are running Debian 6.0 (Squeeze), You can upgrade to 7.0 (Wheezy), it’s so simple:
just answer Y every time.
apt-get update
apt-get upgrade
nano /etc/apt/sources.list
and replace every squeeze
with wheezy
, CTRL+X, Y,enter.
apt-get update
apt-get upgrade
apt-get dist-upgrade
reboot
your new kernel will be selected, login, then you can lsmod | grep hv
and see the hyper-v modules loaded (hv_vmbus, hv_netvsc, hv_blkvsc, hv_storvsc), connect your non-legacy network adapter and do ip show link
then you’ll see it (you can be sure by checking the MAC).
But why stay there?, now you can go to Debian 8.2 (jessie) by following the same instructions but this time use “jessie” on your sourcelist.
I wasn’t able to go directly from 6 to 8.
If you have trouble with “public key is not available” then follow instructions from here.
Sometimes running on Hyper-v it throws two errors:
Error: Driver ‘pcspkr’ is already registered
SMBus base address uninitialized – upgrade bios or use force_addr=0xaddr
to get rid of those errors just blacklist two modules by:
echo 'blacklist pcspkr' >> /etc/modprobe.d/fbdev-blacklist.conf
echo 'blacklist i2c_piix4' >> /etc/modprobe.d/fbdev-blacklist.conf
then do:
update-initramfs -u
reboot
Enjoy.
If you are running Debian 6.0 (Squeeze), You can upgrade to 7.0 (Wheezy), it’s so simple:
just answer Y every time.
apt-get update
apt-get upgrade
nano /etc/apt/sources.list
and replace every squeeze
with wheezy
, CTRL+X, Y,enter.
apt-get update
apt-get upgrade
apt-get dist-upgrade
reboot
your new kernel will be selected, login, then you can lsmod | grep hv
and see the hyper-v modules loaded (hv_vmbus, hv_netvsc, hv_blkvsc, hv_storvsc), connect your non-legacy network adapter and do ip show link
then you’ll see it (you can be sure by checking the MAC).
But why stay there?, now you can go to Debian 8.2 (jessie) by following the same instructions but this time use “jessie” on your sourcelist.
I wasn’t able to go directly from 6 to 8.
If you have trouble with “public key is not available” then follow instructions from here.
Sometimes running on Hyper-v it throws two errors:
Error: Driver ‘pcspkr’ is already registered
SMBus base address uninitialized – upgrade bios or use force_addr=0xaddr
to get rid of those errors just blacklist two modules by:
echo 'blacklist pcspkr' >> /etc/modprobe.d/fbdev-blacklist.conf
echo 'blacklist i2c_piix4' >> /etc/modprobe.d/fbdev-blacklist.conf
then do:
update-initramfs -u
reboot
Enjoy.
edited 2 mins ago
Community♦
1
1
answered Dec 22 '15 at 13:13
Alon OrAlon Or
1111
1111
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f422047%2fdebian-on-hyper-v%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What version of Debian are you running? That blog talks about a newer kernel than you mention; is there a particular reason? What do you mean by "crash"? Error messages?
– Chris S
Aug 28 '12 at 15:18
Debian GNU/Linux 6.0.5 (squeeze). I tried to recompile the kernel v. 2.6.36 as the blog said, but i did not unserstand why that version. During bootup I saw a list of number as matrix ex.[15 12 35 94 86] and after a few it freeze...
– Tobia
Aug 29 '12 at 6:35
I edited the topic because using a compile deb package i solve that boot freeze, however i still have some error...
– Tobia
Aug 29 '12 at 8:09