Summary: | vcbMounter, vcbSnapshot (VMWARE ESX) fails on any Gentoo virtual machine | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Nomblot <pnomblot> |
Component: | [OLD] Core system | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | d.vanderhaghen |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrick Nomblot
2008-05-20 13:43:05 UTC
Confirmed, I have exactly the same problem with VMware ESX 3.5. VMware ESX 3.0 worked fine. Did you find any possible solution for this Patrick? I seem to have found a possible solution here: http://communities.vmware.com/thread/125432 # echo "Red Hat Enterprise Linux AS release 3 (Fake FC4)" > /etc/redhat-release I'll let you know if it works. It seems to me that VMware should just look at the OS type specified by the user when the VM was created if it fails to resolve it at runtime. It looks like a large bug in their software. FYI, I'm currently running all available ESX patches (build 95350). I'm not sure how we can help with this, however, could I ask that you try using the open-vm-tools, rather than those provided as part of ESX and let me know if there's any difference? I don't know if vmware tools is related to the problem, but if so, it's much easier for us to work on and maintain open-vm-tools than it is the pre-distributed tools... I can confirm that the solution suggested earlier works correctly (although it's only a workaround). However, the automatic vmware-tools upgrade will fail with /etc/redhat-release in place. Therefore, /etc/redhat-release should be removed when installing/upgrading vmware tools and be recreated afterwards. Mike: Thank you for your quick response. I don't believe there is anything Gentoo can do about this issue. However, it's important to leave to bug open until VMware fixes it so other people can learn from it. The problem only exists when using the vcSnapshot and vcBackup tools. When making a regular snapshot through the Virtual Infrastructure Client, the problem doesn't occur. VMware should add Gentoo to the vim.vm.GuestOsDescriptor.GuestOsIdentifier list on the ESX server side so Gentoo gets recognized and treated like other26xLinuxGuest. Also they should at least build in a fail-safe to prevent jobs from getting completely stuck and can only be fixed by an ESX reboot. Unfortunately, I'm not in a position at this time to do any more testing since the VMware server is a critical production system. Hopefully I'll get to it at a later time, or someone else will pick it up. correction: I meant vcbBackup and vcbSnapshot instead of 'vc*'. Many thank's to all for your help. I confirm that # echo "Red Hat Enterprise Linux AS release 3 (Fake FC4)" > /etc/redhat-release works fine ! this solution is exactly what I was looking. VMWARE support teams could give some help just suggesting to try such things. They simply refused to help us and we had to look closer to re-install our ESX servers with another distro. hopefully, we still have gentoo and we will be able to keep gentoo. many thank's to all gentoo people ! Is this still a problem with current versions? (In reply to Andreas K. Hüttel from comment #7) > Is this still a problem with current versions? No reply. |